From owner-freebsd-current Sun Sep 10 00:26:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA24401 for current-outgoing; Sun, 10 Sep 1995 00:26:45 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA24387 for ; Sun, 10 Sep 1995 00:26:37 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.9) id JAA19218 for freebsd-current@FreeBSD.ORG; Sun, 10 Sep 1995 09:25:46 +0200 From: John Hay Message-Id: <199509100725.JAA19218@zibbi.mikom.csir.co.za> Subject: ncrcontrol don't compile To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Sun, 10 Sep 1995 09:25:46 +0200 (SAT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 643 Sender: current-owner@FreeBSD.ORG Precedence: bulk Hi, The current ncrcontrol won't compile anymore. angel:/usr/src/usr.sbin/ncrcontrol # make cc -O -I/usr/src/usr.sbin/ncrcontrol/../../sys -c /usr/src/usr.sbin/ncrcontrol/ncrcontrol.c /usr/src/usr.sbin/ncrcontrol/ncrcontrol.c: In function `sn': /usr/src/usr.sbin/ncrcontrol/ncrcontrol.c:886: structure has no member named `p_script' /usr/src/usr.sbin/ncrcontrol/ncrcontrol.c: In function `dump_ncr': /usr/src/usr.sbin/ncrcontrol/ncrcontrol.c:1328: structure has no member named `p_script' /usr/src/usr.sbin/ncrcontrol/ncrcontrol.c:1363: structure has no member named `p_script' *** Error code 1 Stop. -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Sun Sep 10 01:06:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA27738 for current-outgoing; Sun, 10 Sep 1995 01:06:10 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA27714 for ; Sun, 10 Sep 1995 01:05:50 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA27567; Sun, 10 Sep 1995 17:58:09 +1000 Date: Sun, 10 Sep 1995 17:58:09 +1000 From: Bruce Evans Message-Id: <199509100758.RAA27567@godzilla.zeta.org.au> To: pst@shockwave.com, wosch@freebsd.first.gmd.de Subject: Re: 20-40% faster wc(1) Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >I don't understand... the original isspace() was just a lookup in a table >followed by an 'and'. I assume this changed because of the rune code? The rune code has 2 or 3 more tests. >The question you should be asking yourself is WHY is isspace(3) slow? Because gcc does a poor job of optimizing away the extra tests. >Not kludging wc. I do not think this patch should be accepted. Any program that lexes input could benefit from having specialized ctype tables. It would be interesting to generate correct ones automagically. The proposed patch is close to generating a correct one for wc. + u_char spbuf[256]; /* buffer for isspace lookup */ + + for (ch = 0; ch < 256; ch++) + spbuf[ch] = isspace(ch); Correct (?) version: #if UCHAR_MAX >= 4096 #define ISSPACE(ch) isspace(ch) #else u_char myctype[UCHAR_MAX + 1]; for (ch = 0; ch <= UCHAR_MAX; ch++) myctype[ch] = isspace(ch) == 1 : 0; #ifdef maybe /* It might be best to coalesce the space and newline tests. */ myctype['\n'] |= 2; #endif #define ISSPACE(ch) (myctype[ch] != 0) #endif Bruce Annotated gcc output: .align 2,0x90 // do { /* for loop rearranged */ L71: // ch = *p++; // gcc generates its usual poor sign extension code. It should // keep the top 24 bits of %edx as 0 and load the char into the // low 8 bits, saving 5 cycles out of 6 on i486's. movzbl (%esi),%edx // Increment p. Code is best possible. 1 cycle on an i486. incl %esi // if (ch == '\n') // gcc could save a byte or two of space here, and perhaps some // time, by comparing only the low 8 bits. // A better algorithm would use a special character type test // that lumps newlines with spaces. 1 cycle on an i486. cmpl $10,%edx // The branch is usually taken. Better i486 code would arrange for // it not to be taken. Usually 3 cycles on an i486. jne L72 // ++linect; // Usually not executed. incl -16484(%ebp) L72: // if (isspace(ch)) // #define isspace(c) __istype((c), _S) // static __inline int // __istype(_BSD_RUNE_T_ _c, // unsigned long _f) // { // Poor register allocation wastes 2 cycles on i486's. Perhaps gcc // was challenged by the inline. movl %edx,%ecx movl %ecx,%edx // /* / * ctype is hacked to work // * with bogus negative args // * although this breaks it // * on EOF. Negative args // * are generated by the // * common bug `isfoo(*cp)'. // */ // if (_c < 0) // _c = (unsigned char) _c; // At this point `c' is known to be the conversion of an unsigned char // to an int, so the above 2 lines can be optimized out. And they were. // return ((((_c & _CRMASK) // Similarly, _c & _CRMASK is known to be 0. gcc half figures this // out, then it stupidly generates the comparision of 0 with 0, // wasting 5 cycles on a 486. movb $0,%dl testl %edx,%edx je L76 // ?___runetype(_c) : // The following is never executed by wc. pushl %ecx call ____runetype addl $4,%esp shrl $14,%eax movl %eax,%edx jmp L84 .align 2,0x90 L76: // _CurrentRuneLocale->runetype[_c]) & _f) ? 1 : 0); // } // isspace() introduces only a little bloat. // First an indirection. Costs 1 cycle (+ cache misses) on i486's. movl __CurrentRuneLocale,%edx // Then a complicated address mode. Probably costs a cycle on i486's. movb 53(%edx,%ecx,4),%dl // Back to gcc pessimizations. Pay 2 cycles (guess on which machine :-) // to merge with the runetype case that can't happen. shrl $6,%edx L84: // Do the classification. Stupidly branch for the usual case. // Usually 1 + 3 cycles. andl $1,%edx je L73 // gotsp = 1; // !isspace() case is usually not reached. movw $1,-16500(%ebp) jmp L68 .align 2,0x90 L73: // else if (gotsp) { // Back to C code pessimizations. `register short gotsp' is // actually `unregister slow'. The short costs a cycle. gcc // apparently ran out of registers and had to keep the flag in // memory. As usual, stupidly branch for the usual case. // Usually 3 + 3 cycles. cmpw $0,-16500(%ebp) je L68 // gotsp = 0; // Usually not executed. movw $0,-16500(%ebp) // ++wordct; // Usually not executed. incl -16488(%ebp) // } L68: // } while (len-- != 0); /* for loop rearranged */ // Test for loop exit. 1 cycle. decl %ebx // Neither the C code nor gcc was smart enough to test against 0. // 1 more cycle. cmpl $-1,%ebx // Normally don't exit. 3 cycles. jne L71 From owner-freebsd-current Sun Sep 10 03:21:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA12323 for current-outgoing; Sun, 10 Sep 1995 03:21:31 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA12301 for ; Sun, 10 Sep 1995 03:21:23 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.9) id MAA19407; Sun, 10 Sep 1995 12:19:46 +0200 From: John Hay Message-Id: <199509101019.MAA19407@zibbi.mikom.csir.co.za> Subject: Re: Sig 11 and -current problems. To: davidg@Root.COM Date: Sun, 10 Sep 1995 12:19:46 +0200 (SAT) Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: <199509100315.UAA02218@corbin.Root.COM> from "David Greenman" at Sep 9, 95 08:15:42 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2048 Sender: current-owner@FreeBSD.ORG Precedence: bulk > > >"Make world" again. Led to similar sig 11s of "make" mostly. > >vii) Abandon make world, reboot with kernel built from Aug sources; > >viii) Rebuild with "Make world". No sig 11s. Make completes with no > >problems all the way and install the binaries, libs, lkms etc.. > >ix) Rebuild a Kernel now, and reboot. All seems to be fine. > > > >So in a jist, I guess, the order of the making a "Kernel" with supped sources, > >as opposed to "make world install" , followed by the kernel rebuild, seems to > >result in a working machine once again. > > Hmmm, that's interesting. John told me earlier that he was having trouble > with some binaries if they were built with -O2...I don't know why we didn't > notice these earlier (-O2 is known broken in gcc 2.6.3). I don't know if this > is at all related. > Thanks for the info. > > -DG > Well I haven't got rid of al the sig 11s yet. :( The only way at the moment for me is to run with a kernel that I compiled on 3 Sept. At first I had lots of sig 11s. Then I recompiled all the libraries, installed them and recompiled and installed all the programs that sig 11ed. That left me with just a few - rm, sed and login that still sig 11 when I reboot with a new kernel. I then did a make world which I had to help a little because ncrcontrol didn't compile. When I rebooted with a new kernel, login still coredumped with a sig 11. I then recompiled login static and now it works. Then when I started X, xterm coredumped with a sig 11. Well I don't have the diskspace to recompile X, so now I am using the old kernel again. It seems to be working fine with the new libs and programs. (Maybe we have forward compatability and not backward compatability? :-)) Something that I don't understand is why userlevel programs like sed, login xterm etc. are so sensitive to the vm changes. I thought that they shouldn't even be aware of the changes. They don't seem to care if being run on an old kernel. This is on -current (getting it withctm) not -stable. -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Sun Sep 10 03:45:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14627 for current-outgoing; Sun, 10 Sep 1995 03:45:56 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA14613 for ; Sun, 10 Sep 1995 03:45:53 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA17909 for ; Sun, 10 Sep 1995 12:37:23 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA18606 for current@FreeBSD.ORG; Sun, 10 Sep 1995 12:37:22 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA20649 for current@FreeBSD.ORG; Sun, 10 Sep 1995 09:14:42 +0200 From: J Wunsch Message-Id: <199509100714.JAA20649@uriah.heep.sax.de> Subject: Re: test coverage of LINT To: current@FreeBSD.ORG Date: Sun, 10 Sep 1995 09:14:40 +0200 (MET DST) Reply-To: current@FreeBSD.ORG In-Reply-To: <199509100344.NAA19536@godzilla.zeta.org.au> from "Bruce Evans" at Sep 10, 95 01:44:35 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1129 Sender: current-owner@FreeBSD.ORG Precedence: bulk As Bruce Evans wrote: > > `grep 'define N.*0'' in /sys/compile/LINT should produce no output but > actually produces the left half of the following: > od.h:#define NOD 0 # source files missing Under development. Only the hooks are reserved yet, there used to be some discussion on the SCSI list about required changes to the SCSI configuration stuff. > su.h:#define NSU 0 # should be enabled ??? IMHO, it's obsolete and has been replaced by the `uk' device. Julian? Peter? > BTW1, most drivers are unecessarily ifdefed with > > #include "foo.h" > #if NFOO > 0 > > #endif > > NFOO is guaranteed to be > 0 if the driver is configured (except possibly > for cases involving cross references). I'd like to remove these ifdefs. I'd rather temporarily add an #else\n#error "Should not happen" to see if there are some weird constellations. You won't recognize any ill side-effects (except of the bloat) otherwise (the driver won't be referenced anyway). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Sep 10 03:47:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA14855 for current-outgoing; Sun, 10 Sep 1995 03:47:04 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA14843 for ; Sun, 10 Sep 1995 03:47:02 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA17905; Sun, 10 Sep 1995 12:37:21 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA18605; Sun, 10 Sep 1995 12:37:21 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id JAA20049; Sun, 10 Sep 1995 09:05:06 +0200 From: J Wunsch Message-Id: <199509100705.JAA20049@uriah.heep.sax.de> Subject: Re: whereis To: freebsd-current@FreeBSD.ORG (FreeBSD-current users) Date: Sun, 10 Sep 1995 09:05:04 +0200 (MET DST) Cc: root@io.cts.com (Morgan Davis) Reply-To: freebsd-current@FreeBSD.ORG (FreeBSD-current users) In-Reply-To: <199509100001.RAA08139@io.cts.com> from "Morgan Davis" at Sep 9, 95 05:01:47 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 624 Sender: current-owner@FreeBSD.ORG Precedence: bulk As Morgan Davis wrote: > > I've often wondered why the 'whereis' command doesn't use your $PATH > in addition to the default path it searches. Is there some compelling > reason for not doing this? What you're requesting is covered by "which -a". "whereis" has been crippled beyond recognition in 4.4BSD. It has to be rewritten, the current functionality is absolutely useless. Either Wolfram Schneider (but with low priority for this) or me will revamp it probably in Perl. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Sep 10 05:19:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA20144 for current-outgoing; Sun, 10 Sep 1995 05:19:17 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id FAA20138 for ; Sun, 10 Sep 1995 05:19:15 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA17219; Sun, 10 Sep 1995 08:19:11 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01434; Sun, 10 Sep 95 08:16:34 EDT Date: Sun, 10 Sep 95 08:16:34 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509101216.AA01434@borg.ess.harris.com> To: freebsd-current@freefall.FreeBSD.org Subject: Re: Sig 11 and -current problems. Sender: current-owner@FreeBSD.org Precedence: bulk well to add more fuel to the fire I still have the sig11's :-( I have tried to "hand walk" the process, and was able to do it once but then after that a make world died again my make worlds always(90% of the time) die during the installation of libcompat?? then everything is unstable. I am now trying a 29 august kernel, then I will try a july kernel. Later, Jim Leppek > From owner-freebsd-current@freefall.freebsd.org Sun Sep 10 06:27:23 1995 > From: John Hay > Subject: Re: Sig 11 and -current problems. > To: davidg@Root.COM > Date: Sun, 10 Sep 1995 12:19:46 +0200 (SAT) > Cc: FreeBSD-current@FreeBSD.ORG > X-Mailer: ELM [version 2.4 PL23] > Mime-Version: 1.0 > Content-Type> : > text/plain> ; > charset=US-ASCII> > Content-Transfer-Encoding: 7bit > Sender: current-owner@FreeBSD.ORG > > > > > >"Make world" again. Led to similar sig 11s of "make" mostly. > > >vii) Abandon make world, reboot with kernel built from Aug sources; > > >viii) Rebuild with "Make world". No sig 11s. Make completes with no > > >problems all the way and install the binaries, libs, lkms etc.. > > >ix) Rebuild a Kernel now, and reboot. All seems to be fine. > > > > > >So in a jist, I guess, the order of the making a "Kernel" with supped sources, > > >as opposed to "make world install" , followed by the kernel rebuild, seems to > > >result in a working machine once again. > > > > Hmmm, that's interesting. John told me earlier that he was having trouble > > with some binaries if they were built with -O2...I don't know why we didn't > > notice these earlier (-O2 is known broken in gcc 2.6.3). I don't know if this > > is at all related. > > Thanks for the info. > > > > -DG > > > Well I haven't got rid of al the sig 11s yet. :( The only way at the moment > for me is to run with a kernel that I compiled on 3 Sept. > > At first I had lots of sig 11s. Then I recompiled all the libraries, installed > them and recompiled and installed all the programs that sig 11ed. That left > me with just a few - rm, sed and login that still sig 11 when I reboot with > a new kernel. I then did a make world which I had to help a little because > ncrcontrol didn't compile. When I rebooted with a new kernel, login still > coredumped with a sig 11. I then recompiled login static and now it works. > Then when I started X, xterm coredumped with a sig 11. > > Well I don't have the diskspace to recompile X, so now I am using the old > kernel again. It seems to be working fine with the new libs and programs. > (Maybe we have forward compatability and not backward compatability? :-)) > > Something that I don't understand is why userlevel programs like sed, login > xterm etc. are so sensitive to the vm changes. I thought that they shouldn't > even be aware of the changes. They don't seem to care if being run on an old > kernel. > > This is on -current (getting it withctm) not -stable. > > -- > John Hay -- John.Hay@csir.co.za > From owner-freebsd-current Sun Sep 10 05:33:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA20546 for current-outgoing; Sun, 10 Sep 1995 05:33:40 -0700 Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA20540 for ; Sun, 10 Sep 1995 05:33:32 -0700 Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.144.4]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id OAA15507; Sun, 10 Sep 1995 14:20:25 +0200 From: Wolfram Schneider Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.12/8.6.9) id OAA09230; Sun, 10 Sep 1995 14:20:15 +0200 Date: Sun, 10 Sep 1995 14:20:15 +0200 Message-Id: <199509101220.OAA09230@caramba.cs.tu-berlin.de> To: Bruce Evans Cc: current@freebsd.org Subject: Re: 20-40% faster wc(1) In-Reply-To: <199509100758.RAA27567@godzilla.zeta.org.au> References: <199509100758.RAA27567@godzilla.zeta.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: current-owner@freebsd.org Precedence: bulk Bruce Evans writes: >#ifdef maybe > /* It might be best to coalesce the space and newline tests. */ > myctype['\n'] |= 2; >#endif change: if (ch == '\n') ++linect; if (ISSPACE(ch)) gotsp = 1; to: if (ISSPACE(ch)) { gotsp = 1; if (ch == '\n') ++linect; } save ~20% user time :-))) [not a gcc bug, the algorithm was buggy] Wolfram From owner-freebsd-current Sun Sep 10 07:49:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA26292 for current-outgoing; Sun, 10 Sep 1995 07:49:48 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA26273 for ; Sun, 10 Sep 1995 07:49:44 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id QAA16035 ; Sun, 10 Sep 1995 16:49:42 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id QAA01082 ; Sun, 10 Sep 1995 16:49:41 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id PAA18879; Sun, 10 Sep 1995 15:24:06 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509101324.PAA18879@keltia.Freenix.FR> Subject: Re: Sig 11 and -current problems. To: jleppek@suw2k.ess.harris.com (James Leppek) Date: Sun, 10 Sep 1995 15:24:06 +0200 (MET DST) Cc: freebsd-current@freefall.freebsd.org In-Reply-To: <9509101216.AA01434@borg.ess.harris.com> from "James Leppek" at Sep 10, 95 08:16:34 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1083 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that James Leppek said: > well to add more fuel to the fire I still have the sig11's :-( > I have tried to "hand walk" the process, and was able to do it > once but then after that a make world died again > my make worlds always(90% of the time) die during the installation > of libcompat?? then everything is unstable. > I am now trying a 29 august kernel, then I will try a july kernel. There are no clear pattern for the sig11. My make world failed in a program in the games/ directory... Two hours ago I started getting sig11 from emacs (10 times trying to write an Usenet article). I stopped for some time and finally got my article. Now I just got three sig11 from emacs trying to write this answer right now. (now in vi...) I have another make world going just now. The only thing that have changed in my system since Sep. 3 is the VM so I think the problem is here. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #0: Sat Sep 9 17:49:09 MET DST 1995 From owner-freebsd-current Sun Sep 10 08:09:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA28006 for current-outgoing; Sun, 10 Sep 1995 08:09:33 -0700 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA27996 for ; Sun, 10 Sep 1995 08:09:31 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id IAA07882; Sun, 10 Sep 1995 08:09:04 -0700 Message-Id: <199509101509.IAA07882@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: John Hay cc: davidg@Root.COM, FreeBSD-current@FreeBSD.ORG Subject: Re: Sig 11 and -current problems. In-reply-to: Your message of "Sat, 10 Sep 1995 12:19:46 +0200." <199509101019.MAA19407@zibbi.mikom.csir.co.za> Date: Sun, 10 Sep 1995 08:09:04 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.ORG Precedence: bulk Have you explicitly rebuilt and installed your LKMs? >Well I haven't got rid of al the sig 11s yet. :( The only way at the moment >for me is to run with a kernel that I compiled on 3 Sept. ... >-- >John Hay -- John.Hay@csir.co.za -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Sep 10 08:27:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA28591 for current-outgoing; Sun, 10 Sep 1995 08:27:24 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA28583 for ; Sun, 10 Sep 1995 08:27:21 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA17998; Sun, 10 Sep 1995 11:27:16 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01524; Sun, 10 Sep 95 11:24:39 EDT Date: Sun, 10 Sep 95 11:24:39 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509101524.AA01524@borg.ess.harris.com> To: freebsd-current@freefall.FreeBSD.org Subject: Re: Sig 11 and -current problems. Sender: current-owner@FreeBSD.org Precedence: bulk august 29th kernel fails with fatal trap 26 page not present... and crash any attempt to continue the make after it fails with a sig11 or 10 fails again with another signal. I have had to reboot to continue the process. here are the steps I have followed and its still building: 1)hand walk the build to get compiler, libs , lkms and other critical components, build worlds will crash, just reboot and keep going 2)build a new kernel 3)try make world, it won't work but should get farther 4) try it again, mine is still compiling but it is the longest run yet Jim Leppek > From radha@ccnet.ccnet.com Sun Sep 10 10:42:51 1995 > To: jleppek@suw2k.ess.harris.com (James Leppek) > Subject: Re: Sig 11 and -current problems. > Date: Sun, 10 Sep 1995 07:36:22 +0000 > From: Radha Krishnan > > >well to add more fuel to the fire I still have the sig11's :-( > >I have tried to "hand walk" the process, and was able to do it > >once but then after that a make world died again > >my make worlds always(90% of the time) die during the installation > >of libcompat?? then everything is unstable. > I hope I'm not leading you off on a tangent. Yes, the make world does, > fall apart at various stages, if I attempt it on a "kernel" built with > the new supped sources ( Say 1 week old ). However, I've typically, > completed the "make world" process by simply "make" once the process fails. > This again does fail in various stages ( with sig 11s and core-dumps ). > But ensuring the process completes, ( by repeated "make" as opposed to > "make world")., and a reboot, seemed to cure my problem. ( I rebuilt the > kernel too later, just for completeness). > >I am now trying a 29 august kernel, then I will try a july kernel. > I am confident that Aug 29th kernel, would have no problems with > make world. The reason is that an old kernel of mine ( built Sep 1st ), also > has no problems. > > > >Later, > > > >Jim Leppek > > > >> From owner-freebsd-current@freefall.freebsd.org Sun Sep 10 06:27:23 1995 > >> From: John Hay > >> Subject: Re: Sig 11 and -current problems. > >> To: davidg@Root.COM > >> Date: Sun, 10 Sep 1995 12:19:46 +0200 (SAT) > >> Cc: FreeBSD-current@FreeBSD.ORG > >> X-Mailer: ELM [version 2.4 PL23] > >> Mime-Version: 1.0 > >> Content-Type> : > text/plain> ; > charset=US-ASCII> > >> Content-Transfer-Encoding: 7bit > >> Sender: current-owner@FreeBSD.ORG > >> > >> > > >> > >"Make world" again. Led to similar sig 11s of "make" mostly. > >> > >vii) Abandon make world, reboot with kernel built from Aug sources; > >> > >viii) Rebuild with "Make world". No sig 11s. Make completes with no > >> > >problems all the way and install the binaries, libs, lkms etc.. > >> > >ix) Rebuild a Kernel now, and reboot. All seems to be fine. > >> > > > >> > >So in a jist, I guess, the order of the making a "Kernel" with supped sources, > >> > >as opposed to "make world install" , followed by the kernel rebuild, seems to > >> > >result in a working machine once again. > >> > > >> > Hmmm, that's interesting. John told me earlier that he was having trouble > >> > with some binaries if they were built with -O2...I don't know why we didn't > >> > notice these earlier (-O2 is known broken in gcc 2.6.3). I don't know if this > >> > is at all related. > >> > Thanks for the info. > >> > > >> > -DG > >> > > >> Well I haven't got rid of al the sig 11s yet. :( The only way at the moment > >> for me is to run with a kernel that I compiled on 3 Sept. > >> > >> At first I had lots of sig 11s. Then I recompiled all the libraries, installed > >> them and recompiled and installed all the programs that sig 11ed. That left > >> me with just a few - rm, sed and login that still sig 11 when I reboot with > >> a new kernel. I then did a make world which I had to help a little because > >> ncrcontrol didn't compile. When I rebooted with a new kernel, login still > >> coredumped with a sig 11. I then recompiled login static and now it works. > >> Then when I started X, xterm coredumped with a sig 11. > >> > >> Well I don't have the diskspace to recompile X, so now I am using the old > >> kernel again. It seems to be working fine with the new libs and programs. > >> (Maybe we have forward compatability and not backward compatability? :-)) > >> > >> Something that I don't understand is why userlevel programs like sed, login > >> xterm etc. are so sensitive to the vm changes. I thought that they shouldn't > >> even be aware of the changes. They don't seem to care if being run on an old > >> kernel. > >> > >> This is on -current (getting it withctm) not -stable. > >> > >> -- > >> John Hay -- John.Hay@csir.co.za > >> > > > From owner-freebsd-current Sun Sep 10 08:39:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA29277 for current-outgoing; Sun, 10 Sep 1995 08:39:14 -0700 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA29266 for ; Sun, 10 Sep 1995 08:39:09 -0700 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.11/8.6.9) id RAA19962; Sun, 10 Sep 1995 17:38:07 +0200 From: John Hay Message-Id: <199509101538.RAA19962@zibbi.mikom.csir.co.za> Subject: Re: Sig 11 and -current problems. To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 10 Sep 1995 17:38:07 +0200 (SAT) Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: <199509101509.IAA07882@aslan.cdrom.com> from "Justin T. Gibbs" at Sep 10, 95 08:09:04 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 609 Sender: current-owner@FreeBSD.ORG Precedence: bulk Yes I did a make clean and then a make all and then a make install in the lkm directory. It did not help. > > > Have you explicitly rebuilt and installed your LKMs? > > >Well I haven't got rid of al the sig 11s yet. :( The only way at the moment > >for me is to run with a kernel that I compiled on 3 Sept. > > ... > > >-- > >John Hay -- John.Hay@csir.co.za > > -- > Justin T. Gibbs > =========================================== > Software Developer - Walnut Creek CDROM > FreeBSD: Turning PCs into workstations > =========================================== > -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Sun Sep 10 09:23:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA02180 for current-outgoing; Sun, 10 Sep 1995 09:23:55 -0700 Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA02173 for ; Sun, 10 Sep 1995 09:23:51 -0700 Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id MAA01247; Sun, 10 Sep 1995 12:23:25 -0400 From: John Capo Message-Id: <199509101623.MAA01247@irbs.irbs.com> Subject: Re: Sig 11 and -current problems. To: jhay@mikom.csir.co.za (John Hay) Date: Sun, 10 Sep 1995 12:23:24 -0400 (EDT) Cc: gibbs@freefall.freebsd.org, FreeBSD-current@FreeBSD.ORG In-Reply-To: <199509101538.RAA19962@zibbi.mikom.csir.co.za> from "John Hay" at Sep 10, 95 05:38:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1166 Sender: current-owner@FreeBSD.ORG Precedence: bulk John Hay writes: > > Yes I did a make clean and then a make all and then a make install in the > lkm directory. It did not help. > > > > > > Have you explicitly rebuilt and installed your LKMs? > > > > >Well I haven't got rid of al the sig 11s yet. :( The only way at the moment > > >for me is to run with a kernel that I compiled on 3 Sept. > > I don't see any way that the sequence of build kernel or make world then build kernel should affect this unless you are using LKMs. I am running libraries and apps supped yesterday AM. They were built with a kernel from August 21. They run just fine. Any kernel built after John's vm changes causes random cores. I don't use LKMs. irbs 12% ls -al /lkm total 2 drwxr-xr-x 2 bin bin 1024 Jul 14 11:22 . drwxr-xr-x 19 root wheel 512 Sep 7 21:28 .. Last mail I saw from John was that he was able to reproduce the problem but I have not seen anything since. This system has run -current since its inception and 0.1 and the patchkit before that. And it runs fine on an August 21 kernel. John, can you shed some light on this? What can we do to help find this gremlin? John Capo IRBS Engineering From owner-freebsd-current Sun Sep 10 09:24:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA02243 for current-outgoing; Sun, 10 Sep 1995 09:24:34 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA02234 for ; Sun, 10 Sep 1995 09:24:33 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA18256; Sun, 10 Sep 1995 12:24:26 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01547; Sun, 10 Sep 95 12:21:51 EDT Date: Sun, 10 Sep 95 12:21:51 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509101621.AA01547@borg.ess.harris.com> To: freebsd-current@freefall.FreeBSD.org Subject: Re: Sig 11 and -current problems. Sender: current-owner@FreeBSD.org Precedence: bulk I do not think there is a "one pass" solution for the current problem. I am also a little puzzled as to how the VM changes(if they are at fault) can cause such pervasive problems??? I would have thought they would be isolated inside the kernel and outside of most of the binaries... after the procedure I mentioned before my build is still running... I sure miss my 32meg machine, I didn't have to wait nearly as long. I had a motherboard go bad and could not get an 8 slot 30pin SIMM replacement they only had a 4 30pin +2 72pin SIMM board, boy do I feel the difference when I am waiting for a world build instead of sleeping thru one :-) I also have 5 spare 4meg SIMMS sitting on the shelf :-( Hmmm, guess I am rambling a bit, sorry up late watching worlds go by.... Jim Leppek > From owner-freebsd-current@freefall.freebsd.org Sun Sep 10 11:53:33 1995 > From: John Hay > Subject: Re: Sig 11 and -current problems. > To: gibbs@freefall.freebsd.org (Justin T. Gibbs) > Date: Sun, 10 Sep 1995 17:38:07 +0200 (SAT) > Cc: FreeBSD-current@FreeBSD.ORG > X-Mailer: ELM [version 2.4 PL23] > Mime-Version: 1.0 > Content-Type> : > text/plain> ; > charset=US-ASCII> > Content-Transfer-Encoding: 7bit > Sender: current-owner@FreeBSD.ORG > > Yes I did a make clean and then a make all and then a make install in the > lkm directory. It did not help. > > > > > > Have you explicitly rebuilt and installed your LKMs? > > > > >Well I haven't got rid of al the sig 11s yet. :( The only way at the moment > > >for me is to run with a kernel that I compiled on 3 Sept. > > > > ... > > > > >-- > > >John Hay -- John.Hay@csir.co.za > > > > -- > > Justin T. Gibbs > > =========================================== > > Software Developer - Walnut Creek CDROM > > FreeBSD: Turning PCs into workstations > > =========================================== > > > > -- > John Hay -- John.Hay@csir.co.za > From owner-freebsd-current Sun Sep 10 09:37:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA03079 for current-outgoing; Sun, 10 Sep 1995 09:37:35 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA03071 for ; Sun, 10 Sep 1995 09:37:33 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id LAA27877; Sun, 10 Sep 1995 11:30:31 -0500 Received: by olympus (4.1/TSS2.1) id AA03869; Sun, 10 Sep 95 11:30:01 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9509101630.AA03869@olympus> Subject: Re: sig 11 To: jdl@chromatic.com Date: Sun, 10 Sep 1995 11:30:01 -0500 (CDT) Cc: jc@irbs.com, freebsd-current@freebsd.org In-Reply-To: <199509092313.QAA28456@xenon.chromatic.com> from "Jon Loeliger" at Sep 9, 95 04:13:12 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1072 Sender: current-owner@freebsd.org Precedence: bulk > > John Capo scribbled: > > These kinds of problems are all part of running -current. Current > > is a development tree and is quite often broken for one reason or > > another. Like the docs say, "The bleeding edge". > > > > Sounds like you should be running -stable rather than -current. > > Hmmm. Is the problem here that people always think they want > to be running "the latest release" and they equate that to > the "current" system and get it wrong? Should we maybe rename > the -current as like, -development, -devel, -bleed or something? > To make it *really* obvious. I mean, I had to actually *read* > FAQ to find this out... :-) > > jdl > Let's not. I don't think I could stand to watch my box come up and say FreeBSD bleeds. :-) One simply must give rope to allow people to hang themselves, else, they will weave their own. -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Sun Sep 10 09:53:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA04910 for current-outgoing; Sun, 10 Sep 1995 09:53:05 -0700 Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA04877 for ; Sun, 10 Sep 1995 09:52:58 -0700 Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id MAA01477; Sun, 10 Sep 1995 12:48:57 -0400 From: John Capo Message-Id: <199509101648.MAA01477@irbs.irbs.com> Subject: Re: SIGUSR 10 & 11 on kernel from src-cur.0965 To: dyson@freefall.freebsd.org (John Dyson) Date: Sun, 10 Sep 1995 12:48:57 -0400 (EDT) Cc: davidg@root.com, jhs@vector.eikon.e-technik.tu-muenchen.de, current@FreeBSD.org In-Reply-To: <199509092048.NAA29202@freefall.freebsd.org> from "John Dyson" at Sep 9, 95 01:48:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1019 Sender: current-owner@FreeBSD.org Precedence: bulk John Dyson writes: > > > > > >My 24x80 style tty login is still getting SIGUSR 10 & 11 on a kernel from > > >the 69K src-cur.0965.gz (latest i've got) > > > > This is another reminder to people: There were changes that were made to > > -current in the area of the VOP/VFS layering. This REQUIRES that all of your > > LKMs be rebuilt or else you WILL have sig 10/11/?? and panics caused by this. > > Also, the sources for SUP/CTM weren't automatically updated until just very > > recently - the cron entry was missing after freefall's upgrade. PLEASE re-SUP > > and/or whatever CTM people do and make sure that your source tree is up to > > date. > > > > -DG > > > You are all going to be very unhappy with me :-(, but I am going to have > to change the VOP_GETPAGES/VOP_GETPAGES interface one more time. I'll > make all kinds of noises when it happens (I am sure that others will > too :-)). > > Sorry, > John > Is this a fix for the sig 10, 11 problems a lot of us are seeing? John Capo IRBS Engineering From owner-freebsd-current Sun Sep 10 09:53:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA05090 for current-outgoing; Sun, 10 Sep 1995 09:53:42 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA05075 for ; Sun, 10 Sep 1995 09:53:40 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id JAA07222; Sun, 10 Sep 1995 09:52:28 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id JAA02698; Sun, 10 Sep 1995 09:54:40 -0700 Message-Id: <199509101654.JAA02698@corbin.Root.COM> To: jleppek@suw2k.ess.harris.com (James Leppek) cc: freebsd-current@freefall.freebsd.org Subject: Re: Sig 11 and -current problems. In-reply-to: Your message of "Sun, 10 Sep 95 12:21:51 EDT." <9509101621.AA01547@borg.ess.harris.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 10 Sep 1995 09:54:40 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >I do not think there is a "one pass" solution for the current problem. >I am also a little puzzled as to how the VM changes(if they are at fault) >can cause such pervasive problems??? I would have thought they would >be isolated inside the kernel and outside of most of the binaries... Among John's changes were some to the way that fault clusters work. When the system does clustering, it must determine the number of contiguous blocks on the disk. If it calculates this number too large, it will page in some garbage. Once this gets paged in, it will "stick" in the cache until it is flushed. The affect of this is that machines with lots of memory will tend to work better than machines with small amounts of memory (because the small memory machines will flush out the garbage quickly and/or do less aggressive clustering - avoiding the problem completely). The problem *might* be in the new ffs_bmap() routine that now calculates the amount of "run behind" (the amount of contiguous pages before the requested block). In any case, the problem sounds very much to be either in the vnode_pager or related routines (ffs_bmap, etc). I don't have time to look into this at the moment, but perhaps John will be able to some time soon. -DG From owner-freebsd-current Sun Sep 10 09:58:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA06595 for current-outgoing; Sun, 10 Sep 1995 09:58:40 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA06566 for ; Sun, 10 Sep 1995 09:58:37 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA18401; Sun, 10 Sep 1995 12:58:31 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01584; Sun, 10 Sep 95 12:55:55 EDT Date: Sun, 10 Sep 95 12:55:55 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509101655.AA01584@borg.ess.harris.com> To: faulkner@mpd.tandem.com Subject: Re: sig 11 Cc: freebsd-current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk I agree, I do not think anyone here is complaining, just trying to pass along information to help isolate the problem or just identify that there is a real one. while I wish I had the time to be a more active "core" member, the best I can be is part of the "informal" test organization and porting apps as time permits for local folks running stable. I try to keep up with the cvs msgs and do a rebuild weekly or when I see a "try this" type message to provide stability feedback or help confirm that lone message that comes in that says "my system crashed" and the first reponses are "must be your hardware". I know I have avoided swapping drives/cards/SIMMS because of the many folks running current who can send at least a confirmation message that says "I saw something like that to, thought it was just me". Isn't this what "current" folks are supposed to be doing? Hmmm, just saw a message that says more VOP changes coming :-) Jim Leppek > From owner-freebsd-current@freefall.freebsd.org Sun Sep 10 12:37:24 1995 > From: faulkner@mpd.tandem.com (Boyd Faulkner) > Subject: Re: sig 11 > To: jdl@chromatic.com > Date: Sun, 10 Sep 1995 11:30:01 -0500 (CDT) > Cc: jc@irbs.com, freebsd-current@freebsd.org > X-Mailer: ELM [version 2.4 PL17] > Content-Type> : > text> > Sender: current-owner@freebsd.org > > > > > John Capo scribbled: > > > These kinds of problems are all part of running -current. Current > > > is a development tree and is quite often broken for one reason or > > > another. Like the docs say, "The bleeding edge". > > > > > > Sounds like you should be running -stable rather than -current. > > > > Hmmm. Is the problem here that people always think they want > > to be running "the latest release" and they equate that to > > the "current" system and get it wrong? Should we maybe rename > > the -current as like, -development, -devel, -bleed or something? > > To make it *really* obvious. I mean, I had to actually *read* > > FAQ to find this out... :-) > > > > jdl > > > Let's not. I don't think I could stand to watch my box come up and say > > FreeBSD bleeds. :-) > > One simply must give rope to allow people to hang themselves, else, they will > weave their own. > > -- > _______________________________________________________________________ > > Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner > _______________________________________________________________________ > From owner-freebsd-current Sun Sep 10 10:02:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA08386 for current-outgoing; Sun, 10 Sep 1995 10:02:33 -0700 Received: from runner.utsa.edu (runner.jpl.utsa.edu [129.115.50.16]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA08359 for ; Sun, 10 Sep 1995 10:02:29 -0700 Received: by runner.utsa.edu (5.0/SMI-SVR4) id AA15328; Sun, 10 Sep 1995 12:05:33 -0500 From: ferovick@runner.jpl.utsa.edu (David C Ferovick) Message-Id: <9509101705.AA15328@runner.utsa.edu> Subject: LED command timeout errors To: freebsd-current@freefall.freebsd.org Date: Sun, 10 Sep 1995 12:05:32 -0500 (CDT) Reply-To: ferovick@runner.jpl.utsa.edu X-Mailer: ELM [version 2.4 PL23beta2] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 639 Sender: current-owner@FreeBSD.org Precedence: bulk When I am using my lexmark keyboard (standard ps/2 style keyboard and an adapter to convert the jack to a normal-din connector instead of the smaller one) I am unable to see the LEDs for capslock numlock and scrollock.. If I use any of these keys during the session, I will eventually get LED command timeout errors from the PCVT driver...This happens in all versions of FreeBSD that I have tried and on 2 machines, one a 386/25 with a OPTI chipset, and one a 486dx2 80 with a NEAT chipset...Both have AMI bios'es although i am unaware of the bios revision numbers right now... Any ideas? --Dave Ferovick (ferovick@runner.jpl.utsa.edu) From owner-freebsd-current Sun Sep 10 10:08:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA10405 for current-outgoing; Sun, 10 Sep 1995 10:08:23 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA10321 for ; Sun, 10 Sep 1995 10:08:11 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id DAA11210; Mon, 11 Sep 1995 03:07:38 +1000 Date: Mon, 11 Sep 1995 03:07:38 +1000 From: Bruce Evans Message-Id: <199509101707.DAA11210@godzilla.zeta.org.au> To: jc@irbs.com, jhay@mikom.csir.co.za Subject: Re: Sig 11 and -current problems. Cc: FreeBSD-current@FreeBSD.ORG, gibbs@freefall.freebsd.org Sender: current-owner@FreeBSD.ORG Precedence: bulk >I am running libraries and apps supped yesterday AM. They were >built with a kernel from August 21. They run just fine. Any kernel >built after John's vm changes causes random cores. I don't use LKMs. >irbs 12% ls -al /lkm >total 2 >drwxr-xr-x 2 bin bin 1024 Jul 14 11:22 . >drwxr-xr-x 19 root wheel 512 Sep 7 21:28 .. >Last mail I saw from John was that he was able to reproduce the >problem but I have not seen anything since. I thought he fixed it. I saw sig 11's from Sep 6-8 but none since then. This was on a test machine that doesn't do much more than boot kernels. It has fairly old executables (most were installed on Sep 3 before the critical vm changes) and older libs. I haven't trusted kernels built after Sep 2 on my development machine. I don't use LKM's. Bruce From owner-freebsd-current Sun Sep 10 10:08:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA10533 for current-outgoing; Sun, 10 Sep 1995 10:08:50 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA10517 for ; Sun, 10 Sep 1995 10:08:47 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id KAA12289; Sun, 10 Sep 1995 10:07:33 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id KAA02726; Sun, 10 Sep 1995 10:09:45 -0700 Message-Id: <199509101709.KAA02726@corbin.Root.COM> To: jleppek@suw2k.ess.harris.com (James Leppek), freebsd-current@freefall.freebsd.org Subject: Re: Sig 11 and -current problems. In-reply-to: Your message of "Sun, 10 Sep 95 09:54:40 PDT." <199509101654.JAA02698@corbin.Root.COM> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 10 Sep 1995 10:09:44 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >>I do not think there is a "one pass" solution for the current problem. >>I am also a little puzzled as to how the VM changes(if they are at fault) >>can cause such pervasive problems??? I would have thought they would >>be isolated inside the kernel and outside of most of the binaries... > > Among John's changes were some to the way that fault clusters work. When the >system does clustering, it must determine the number of contiguous blocks on >the disk. If it calculates this number too large, it will page in some garbage. >Once this gets paged in, it will "stick" in the cache until it is flushed. The >affect of this is that machines with lots of memory will tend to work better ^^^^^^ Should be "worse". Sory about that... >than machines with small amounts of memory (because the small memory machines >will flush out the garbage quickly and/or do less aggressive clustering - >avoiding the problem completely). > The problem *might* be in the new ffs_bmap() routine that now calculates >the amount of "run behind" (the amount of contiguous pages before the >requested block). In any case, the problem sounds very much to be either in >the vnode_pager or related routines (ffs_bmap, etc). I don't have time to look >into this at the moment, but perhaps John will be able to some time soon. > >-DG -DG From owner-freebsd-current Sun Sep 10 10:17:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA11704 for current-outgoing; Sun, 10 Sep 1995 10:17:18 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA11694 ; Sun, 10 Sep 1995 10:17:16 -0700 Date: Sun, 10 Sep 1995 10:17:16 -0700 From: John Dyson Message-Id: <199509101717.KAA11694@freefall.freebsd.org> To: jleppek@suw2k.ess.harris.com, roberto@keltia.Freenix.FR Subject: Re: Sig 11 and -current problems. Cc: freebsd-current@freefall.freebsd.org Sender: current-owner@FreeBSD.org Precedence: bulk Regarding the strange sig11 problems, I am NOT abandoning it, and will be working it today, etc. I am going to make a few suggestions to those that can modify their kernels, so keep tuned in :-). John dyson@root.com From owner-freebsd-current Sun Sep 10 10:18:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA11766 for current-outgoing; Sun, 10 Sep 1995 10:18:21 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA11760 for ; Sun, 10 Sep 1995 10:18:18 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA18490; Sun, 10 Sep 1995 13:18:13 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA01611; Sun, 10 Sep 95 13:15:37 EDT Date: Sun, 10 Sep 95 13:15:37 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509101715.AA01611@borg.ess.harris.com> To: freebsd-current@freefall.FreeBSD.org Subject: Re: Sig 11 and -current problems. Sender: current-owner@FreeBSD.org Precedence: bulk That makes sense, and also explains why walking thru the build works because it would change what information is paged and when it would be flushed, you hope for enough faults to flush the bad data out before it gets touched :-). The strange part is that my latest build is still running??? I would have thought to see a fairly deterministic failure once the VM and cluster changes had been incorporated. Oh well... Jim (its still compiling) Leppek > From owner-freebsd-current@freefall.freebsd.org Sun Sep 10 12:56:40 1995 > To: jleppek@suw2k.ess.harris.com (James Leppek) > Cc: freebsd-current@freefall.freebsd.org > Subject: Re: Sig 11 and -current problems. > From: David Greenman > Reply-To: davidg@Root.COM > Date: Sun, 10 Sep 1995 09:54:40 -0700 > Sender: current-owner@FreeBSD.org > > >I do not think there is a "one pass" solution for the current problem. > >I am also a little puzzled as to how the VM changes(if they are at fault) > >can cause such pervasive problems??? I would have thought they would > >be isolated inside the kernel and outside of most of the binaries... > > Among John's changes were some to the way that fault clusters work. When the > system does clustering, it must determine the number of contiguous blocks on > the disk. If it calculates this number too large, it will page in some garbage. > Once this gets paged in, it will "stick" in the cache until it is flushed. The > affect of this is that machines with lots of memory will tend to work better > than machines with small amounts of memory (because the small memory machines > will flush out the garbage quickly and/or do less aggressive clustering - > avoiding the problem completely). > The problem *might* be in the new ffs_bmap() routine that now calculates > the amount of "run behind" (the amount of contiguous pages before the > requested block). In any case, the problem sounds very much to be either in > the vnode_pager or related routines (ffs_bmap, etc). I don't have time to look > into this at the moment, but perhaps John will be able to some time soon. > > -DG > From owner-freebsd-current Sun Sep 10 10:20:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12139 for current-outgoing; Sun, 10 Sep 1995 10:20:09 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12130 ; Sun, 10 Sep 1995 10:20:08 -0700 From: John Dyson Message-Id: <199509101720.KAA12130@freefall.freebsd.org> Subject: Re: Sig 11 and -current problems. To: davidg@Root.COM Date: Sun, 10 Sep 1995 10:20:08 -0700 (PDT) Cc: jleppek@suw2k.ess.harris.com, freebsd-current@freefall.freebsd.org In-Reply-To: <199509101654.JAA02698@corbin.Root.COM> from "David Greenman" at Sep 10, 95 09:54:40 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 414 Sender: current-owner@FreeBSD.org Precedence: bulk > The problem *might* be in the new ffs_bmap() routine that now calculates > the amount of "run behind" (the amount of contiguous pages before the > requested block). In any case, the problem sounds very much to be either in > the vnode_pager or related routines (ffs_bmap, etc). I don't have time to look > into this at the moment, but perhaps John will be able to some time soon. > John will today!!! John From owner-freebsd-current Sun Sep 10 10:20:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12197 for current-outgoing; Sun, 10 Sep 1995 10:20:57 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12187 ; Sun, 10 Sep 1995 10:20:56 -0700 From: John Dyson Message-Id: <199509101720.KAA12187@freefall.freebsd.org> Subject: Re: SIGUSR 10 & 11 on kernel from src-cur.0965 To: jc@irbs.com (John Capo) Date: Sun, 10 Sep 1995 10:20:56 -0700 (PDT) Cc: davidg@root.com, jhs@vector.eikon.e-technik.tu-muenchen.de, current@FreeBSD.org In-Reply-To: <199509101648.MAA01477@irbs.irbs.com> from "John Capo" at Sep 10, 95 12:48:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 313 Sender: current-owner@FreeBSD.org Precedence: bulk > > to change the VOP_GETPAGES/VOP_GETPAGES interface one more time. I'll > > make all kinds of noises when it happens (I am sure that others will > > too :-)). > > > > Sorry, > > John > > > > Is this a fix for the sig 10, 11 problems a lot of us are seeing? No, sorry, but I will be working it today. John From owner-freebsd-current Sun Sep 10 11:10:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14206 for current-outgoing; Sun, 10 Sep 1995 11:10:10 -0700 Received: from cps201.cps.cmich.edu (cps201.cps.cmich.edu [141.209.20.201]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA14200 for ; Sun, 10 Sep 1995 11:10:09 -0700 Received: from cps201 (cps201.cps.cmich.edu [141.209.20.201]) by cps201.cps.cmich.edu (8.6.12/8.6.12) with SMTP id OAA15330; Sun, 10 Sep 1995 14:10:10 -0400 Date: Sun, 10 Sep 1995 14:10:08 -0400 (EDT) From: Mail Archive X-Sender: archive@cps201 To: David Greenman cc: John Capo , roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: sig 11 In-Reply-To: <199509092031.NAA00235@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Sat, 9 Sep 1995, David Greenman wrote: > > Okay, everyone else has reported back that the problems have gone away > after rebuilding everything. The only remaining report of sig 11 type of > trouble is yours. Can you send me more information about your system, a > "dmesg" would be useful, for example. Also, when was the last time you > updated your sources? It's possible that the update you did was during a > time when changes were being made and thus the changes may be incomplete. > Whooops no it wasn't sed still cores on the new kernel it doesn't on the old release kernel... -current kernel looks to be hosed as of a 4pm EST sup yesterday... From owner-freebsd-current Sun Sep 10 11:10:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14225 for current-outgoing; Sun, 10 Sep 1995 11:10:13 -0700 Received: from cps201.cps.cmich.edu (cps201.cps.cmich.edu [141.209.20.201]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA14219 for ; Sun, 10 Sep 1995 11:10:12 -0700 Received: from cps201 (cps201.cps.cmich.edu [141.209.20.201]) by cps201.cps.cmich.edu (8.6.12/8.6.12) with SMTP id OAA15263; Sun, 10 Sep 1995 14:08:52 -0400 Date: Sun, 10 Sep 1995 14:08:48 -0400 (EDT) From: Mail Archive X-Sender: archive@cps201 To: David Greenman cc: John Capo , roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: sig 11 In-Reply-To: <199509092031.NAA00235@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Sat, 9 Sep 1995, David Greenman wrote: > > Okay, everyone else has reported back that the problems have gone away > after rebuilding everything. The only remaining report of sig 11 type of > trouble is yours. Can you send me more information about your system, a > "dmesg" would be useful, for example. Also, when was the last time you > updated your sources? It's possible that the update you did was during a > time when changes were being made and thus the changes may be incomplete. > OK it was a RAM problem... sorry guys.... From owner-freebsd-current Sun Sep 10 11:23:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14661 for current-outgoing; Sun, 10 Sep 1995 11:23:10 -0700 Received: (from sos@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14652 ; Sun, 10 Sep 1995 11:23:10 -0700 Message-Id: <199509101823.LAA14652@freefall.freebsd.org> Subject: Re: LED command timeout errors To: ferovick@runner.jpl.utsa.edu Date: Sun, 10 Sep 1995 11:23:09 -0700 (PDT) Cc: freebsd-current@freefall.freebsd.org In-Reply-To: <9509101705.AA15328@runner.utsa.edu> from "David C Ferovick" at Sep 10, 95 12:05:32 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 909 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to David C Ferovick who wrote: > > When I am using my lexmark keyboard (standard ps/2 style keyboard and an > adapter to convert the jack to a normal-din connector instead of the > smaller one) I am unable to see the LEDs for capslock numlock and scrollock.. > If I use any of these keys during the session, I will eventually get > LED command timeout errors from the PCVT driver...This happens in all > versions of FreeBSD that I have tried and on 2 machines, one a 386/25 > with a OPTI chipset, and one a 486dx2 80 with a NEAT chipset...Both > have AMI bios'es although i am unaware of the bios revision numbers > right now... > > Any ideas? What happens if you use syscons instead of pcvt ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org | sos@login.dknet.dk) FreeBSD Core Team So much code to hack -- so little time From owner-freebsd-current Sun Sep 10 11:56:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA16268 for current-outgoing; Sun, 10 Sep 1995 11:56:12 -0700 Received: from eikon.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA16248 for ; Sun, 10 Sep 1995 11:55:57 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id UAA22015; Sun, 10 Sep 1995 20:55:31 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with SMTP id UAA00435; Sun, 10 Sep 1995 20:06:52 +0200 Message-Id: <199509101806.UAA00435@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: current@freebsd.org Subject: Re: SIGUSR 10 & 11 on kernel from src-cur.0965 In-reply-to: Your message of "Sat, 09 Sep 1995 13:28:49 PDT." <199509092028.NAA00222@corbin.Root.COM> Date: Sun, 10 Sep 1995 20:06:51 +0200 From: "\"\"Julian Stacey \"\"" Sender: current-owner@freebsd.org Precedence: bulk David (cc current) FYI Re. > >My 24x80 style tty login is still getting SIGUSR 10 & 11 on a kernel from > >the 69K src-cur.0965.gz (latest i've got) > > This is another reminder to people: There were changes that were made to > -current in the area of the VOP/VFS layering. This REQUIRES that all of your > LKMs be rebuilt or else you WILL have sig 10/11/?? and panics caused by this. > Also, the sources for SUP/CTM weren't automatically updated until just very > recently - the cron entry was missing after freefall's upgrade. PLEASE re-SUP > and/or whatever CTM people do and make sure that your source tree is up to > date. I've never used lkm's, (never reduced my config, just ignored 'em till now), I'm typing this into a vi called from reply from wish, from exmh from X11R6, from xinit, & before booting I did mv /lkm /lkm.mv The system is running fine, with an old kernel, but all commands lib etc based on this CTM: 69897 Sep 9 12:03 src-cur.0965.gz (The latest I have as at Sun Sep 10 20:03:58 MSZ 1995 However if I try to login using a current kernel (src-cur.0965 CTM) I get: Sep 10 19:20:03 vector /kernel.nu: pid 155: login: uid 0: exited on signal 10 Sep 10 19:20:15 vector /kernel.nu: pid 159: login: uid 0: exited on signal 11 Sep 10 19:20:33 vector /kernel.nu: pid 169: login: uid 0: exited on signal 10 This suggests to me the SIGBUS & SIGSEGV I see are not coming from an inconsistent between lkm's, & kernel, but from something inside the kernel. BTW I'm also seeing xdm failures, but that may be unassociated (as were my exmh form failures I mentioned (solution posted to ports). Hope this info may help you Julian S jhs@freebsd.org From owner-freebsd-current Sun Sep 10 12:03:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA16676 for current-outgoing; Sun, 10 Sep 1995 12:03:15 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA16670 for ; Sun, 10 Sep 1995 12:03:14 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15026; Sun, 10 Sep 1995 11:53:31 -0700 From: Terry Lambert Message-Id: <199509101853.LAA15026@phaeton.artisoft.com> Subject: Re: 20-40% faster wc(1) To: bde@zeta.org.au (Bruce Evans) Date: Sun, 10 Sep 1995 11:53:31 -0700 (MST) Cc: pst@shockwave.com, wosch@freebsd.first.gmd.de, current@freebsd.org In-Reply-To: <199509100758.RAA27567@godzilla.zeta.org.au> from "Bruce Evans" at Sep 10, 95 05:58:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 580 Sender: current-owner@freebsd.org Precedence: bulk > > >I don't understand... the original isspace() was just a lookup in a table > >followed by an 'and'. I assume this changed because of the rune code? > > The rune code has 2 or 3 more tests. > > >The question you should be asking yourself is WHY is isspace(3) slow? > > Because gcc does a poor job of optimizing away the extra tests. [ ... GCC code generation analysis ... ] Bruce, you should send this to the GCC people, *really*. 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-current Sun Sep 10 13:17:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA20674 for current-outgoing; Sun, 10 Sep 1995 13:17:54 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA20666 for ; Sun, 10 Sep 1995 13:17:51 -0700 Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id QAA06090 for current@FreeBSD.ORG; Sun, 10 Sep 1995 16:07:59 -0400 From: Peter Dufault Message-Id: <199509102007.QAA06090@hda.com> Subject: Re: test coverage of LINT To: current@FreeBSD.ORG Date: Sun, 10 Sep 1995 16:07:58 -0400 (EDT) In-Reply-To: <199509100714.JAA20649@uriah.heep.sax.de> from "J Wunsch" at Sep 10, 95 09:14:40 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1060 Sender: current-owner@FreeBSD.ORG Precedence: bulk > > As Bruce Evans wrote: > > > > `grep 'define N.*0'' in /sys/compile/LINT should produce no output but > > actually produces the left half of the following: > > > od.h:#define NOD 0 # source files missing > > Under development. Only the hooks are reserved yet, there used to be > some discussion on the SCSI list about required changes to the SCSI > configuration stuff. Yes, I owe that configuration work to Joerg. > > > su.h:#define NSU 0 # should be enabled ??? > > IMHO, it's obsolete and has been replaced by the `uk' device. > It's old use was replaced by the ability to set the position of SCSI devices via config. Until changed, both SSC and SU can be enabled in LINT: > pseudo-device su # "scsi user" > pseudo-device ssc # "super scsi" and anything needed in su will be folded into ssc. I have these enabled here and use "super scsi" regularly. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Sun Sep 10 14:42:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA23821 for current-outgoing; Sun, 10 Sep 1995 14:42:56 -0700 Received: (from gclarkii@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA23813 for freebsd-current; Sun, 10 Sep 1995 14:42:55 -0700 From: Gary Clark II Message-Id: <199509102142.OAA23813@freefall.freebsd.org> Subject: Sig 10, etc. To: freebsd-current Date: Sun, 10 Sep 1995 14:42:55 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 791 Sender: current-owner@FreeBSD.org Precedence: bulk Hi, I'm running a current system. Here are the strings from my kernel with the same sup date. FreeBSD 2.2-CURRENT #0: Wed Aug 30 14:12:20 CDT 1995 root@main.gbdata.com:/usr/src/sys/compile/MAIN I have NO problems. Here is how I did the upgrade: 1. sup all sources except games. 2. make world 3. make a new kernel 4. reboot on new kenrel 5. make install on user source 6. reboot 7. use machine:) This has worked everytime I can remember except the 2.0->2.0.5 1.1.5.1->2.0 upgrades. Your milage may vary:) Gary -- Gary Clark II (N5VMF) | FreeBSD support and service gclarkii@FreeBSD.ORG | mail info@gbdata.com for information FreeBSD FAQ at ftp.FreeBSD.ORG in ~pub/FreeBSD/FreeBSD-current/src/share/FAQ/Text/FreeBSD.FAQ From owner-freebsd-current Sun Sep 10 15:52:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA26344 for current-outgoing; Sun, 10 Sep 1995 15:52:10 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA26329 for ; Sun, 10 Sep 1995 15:52:08 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id SAA24969; for ; Sun, 10 Sep 1995 18:51:58 -0400 Date: Sun, 10 Sep 95 18:49:36 PDT From: "Ugen J.S.Antsilevich" Subject: Re: LED command timeout errors To: ferovick@runner.jpl.utsa.edu, sos@FreeBSD.org Cc: freebsd-current@freefall.freebsd.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk >In reply to David C Ferovick who wrote: >> >> When I am using my lexmark keyboard (standard ps/2 style keyboard and an >> adapter to convert the jack to a normal-din connector instead of the >> smaller one) I am unable to see the LEDs for capslock numlock and scrollock.. Same with me..i have some sort of no-name keyboard and using pcvt i am unable to see the leds, they are just off all the time..With syscons they are doing pretty well...Also Ctrl+Alt+Del doesnt works in pcvt and there are a couple of odd things with keyboard mapping like Backspace etc but theese are resolvable... > >What happens if you use syscons instead of pcvt ?? > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Soren Schmidt (sos@FreeBSD.org | sos@login.dknet.dk) FreeBSD Core Team > So much code to hack -- so little time --Ugen From owner-freebsd-current Sun Sep 10 17:51:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA00115 for current-outgoing; Sun, 10 Sep 1995 17:51:28 -0700 Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.35.13]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA00108 for ; Sun, 10 Sep 1995 17:51:26 -0700 Received: (from james@localhost) by miller.cs.uwm.edu (8.6.10/8.6.10) id TAA18536; Sun, 10 Sep 1995 19:51:25 -0500 Date: Sun, 10 Sep 1995 19:51:25 -0500 From: Jim Lowe Message-Id: <199509110051.TAA18536@miller.cs.uwm.edu> To: nate@rocky.sri.MT.net Subject: Re: GUS Max support? Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > > gus0 at 0x220 irq 15 drq 1 flags 0x3 on isa > > I noticed the LINT line for this had the line with flags 0x3 commented > out. What do the above flags do for you? > Ummm... I think the comments in the lint file describe this. The flags (if defined) are used to define the read dma channel for the gus/gus-max card when in full duplex mode. If the read dma channel is not defined, then the gus card runs in the standard 1/2 duplex mode. If the flags are defined and the drq (write dma channel) is different than the flags (read dma channel), then the gus card runs in full duplex mode. -Jim From owner-freebsd-current Sun Sep 10 17:51:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA00145 for current-outgoing; Sun, 10 Sep 1995 17:51:34 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA00137 for current@freebsd.org; Sun, 10 Sep 1995 17:51:33 -0700 Date: Sun, 10 Sep 1995 17:51:33 -0700 From: John Dyson Message-Id: <199509110051.RAA00137@freefall.freebsd.org> To: current@freebsd.org Subject: Progress so far on the Sig-11 problem Sender: current-owner@freebsd.org Precedence: bulk I am having problems reproducing the problem. It takes quite-a-while to get it to happen, and only appears when I am running in less than 8MB. I have verified that the pre-zero code is not the culprit (but have done some minor cleanups.) Another major change is that the original vnode_pager_haspage was not correct (on the *very* conservative side) on the estimate of the cluster size. That problem was *fixed* with another bug being introduced. The bug has been fixed in -current, but I am not sure that the Sig-11 problems were related. I am still searching for it... John dyson@freebsd.org From owner-freebsd-current Sun Sep 10 17:53:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA00226 for current-outgoing; Sun, 10 Sep 1995 17:53:55 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA00220 for ; Sun, 10 Sep 1995 17:53:51 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA09951; Sun, 10 Sep 1995 17:50:19 -0700 To: jleppek@suw2k.ess.harris.com (James Leppek) cc: faulkner@mpd.tandem.com, freebsd-current@freebsd.org Subject: Re: sig 11 In-reply-to: Your message of "Sun, 10 Sep 1995 12:55:55 EDT." <9509101655.AA01584@borg.ess.harris.com> Date: Sun, 10 Sep 1995 17:50:19 -0700 Message-ID: <9949.810780619@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > I agree, I do not think anyone here is complaining, just trying > to pass along information to help isolate the problem or just > identify that there is a real one. while I wish I had the time > to be a more active "core" member, the best I can be is part of > the "informal" test organization and porting apps as time permits > for local folks running stable. I try to keep up with the And this kind of work is appreciated, believe me! We can't find bugs unless somebody is occasionally willing to "bleed" a little like this and help the developers track down problems with configurations they (the developers) don't have ready access to themselves. Jordan From owner-freebsd-current Sun Sep 10 18:39:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA01106 for current-outgoing; Sun, 10 Sep 1995 18:39:34 -0700 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA01087 ; Sun, 10 Sep 1995 18:39:31 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id SAA09332; Sun, 10 Sep 1995 18:39:22 -0700 Message-Id: <199509110139.SAA09332@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: current@FreeBSD.org, stable@FreeBSD.org Subject: Aic7xxx Wide Support Date: Sun, 10 Sep 1995 18:39:21 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk Rod Grimes has just discovered a problem with the Wide support in the aic7xxx driver that I think anyone using or thinking of using these controllers should know about. Although I cannot reproduce this on the wide Seagate Hawk drives that I have access to, the driver will drop bytes in certain scenarios during read transfers on at least Quantum Atlas and Micropolis Wide drives. I hope to have a solution to this problem shortly. Until then, if you experience problems with this driver, please let me know. So far, disabling wide transfers in Scsi-Select is a temporary work around. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Sep 10 18:45:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA01227 for current-outgoing; Sun, 10 Sep 1995 18:45:20 -0700 Received: from prosun.first.gmd.de (prosun.first.gmd.de [192.35.150.136]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA01221 for ; Sun, 10 Sep 1995 18:45:17 -0700 Received: from freebsd.first.gmd.de by prosun.first.gmd.de (4.1/SMI-4.1) id AA05507; Mon, 11 Sep 95 03:45:07 +0200 Received: by freebsd.first.gmd.de (DAA11406); Mon, 11 Sep 1995 03:44:36 +0200 From: Gerd Truschinski Message-Id: <199509110144.DAA11406@freebsd.first.gmd.de> Subject: Some install failures To: current@freebsd.org Date: Mon, 11 Sep 1995 03:44:36 +0159 (MET DST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1418 Sender: current-owner@freebsd.org Precedence: bulk Hi there, I tried to use send-pr. But it seems to have some problems here. So I send it to the list. >Environment: 486 with SCSI drives. I have installed only the ...bin/bin* on a new system. My sources are from freebsd.first.gmd.de, ca. 1.Sept.95 >Description: 1. During the 'make world' update there was a file missing: /usr/share/dict/eign and this is the error message ===> share/doc/memfs indexbib -o ref.bib /home/src/share/doc/papers/memfs/ref.bib indexbib: fetch error: can't open /usr/share/dict/eign 2. tcsh: During the install of this port there are some Directories missing: /usr/local/share/nls/C /usr/local/share/de_DE.ISO_8859 and all the other ..ISO.. directories >How-To-Repeat: Install a virgian system. I have to do it because Xfree killed my first partition (the memory mapped mode of the SVGA server) >Fix: I am not good in scripts. So it is up to you 1. put 'eign' in the bin distribution or install indxbib correctly befor it is used 2. Build first the directories in which tcsh try to install the 'tcsh.cat' files Have fun, /gT/ -- Gerd Truschinski | Yes, this is the sort of scenario I gt@freebsd.first.gmd.de | think up to amuse myself in the evenings. emma@cs.tu-berlin.de | -- with confirmation from Larisa From owner-freebsd-current Sun Sep 10 21:12:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA06964 for current-outgoing; Sun, 10 Sep 1995 21:12:27 -0700 Received: from chrome.onramp.net (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA06954 for ; Sun, 10 Sep 1995 21:12:25 -0700 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.onramp.net (8.6.11/8.6.9) with SMTP id XAA06549; Sun, 10 Sep 1995 23:11:32 -0500 Message-Id: <199509110411.XAA06549@chrome.onramp.net> X-Authentication-Warning: chrome.onramp.net: Host localhost.jdl.com didn't use HELO protocol To: vak@cronyx.ru cc: freebsd-current@freebsd.org Subject: Success with the ATAPI NEC-260 CDROM! In-reply-to: Your message of "Tue, 05 Sep 1995 20:48:49 +0400." Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Sun, 10 Sep 1995 23:11:32 -0500 From: Jon Loeliger Sender: current-owner@freebsd.org Precedence: bulk Apparently, vak@cronyx.ru scribbled: > Great! > > Now it should work. Here is the (final?) patch. > > Serge Serge, Thanks for waiting. I'm finally home again, and I've been able to test your latest patch. It is definitely *much* better now! wd0: probe started wd0: checking RW register on port 0x1f0 + 0x4 wd0: reseting wd0: diagnosing wd0: Error : 0x1 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S atapi0.1 at 0x1f0: attach called atapi.1 at 0x1f0: identify not ready, status=1 wd1: probe started wd1: checking RW register on port 0x170 + 0x4 wd1: reseting wd1: diagnosing wd0: Error : 0x1 wdc1 at 0x170-0x177 irq 15 on isa atapi1.0 at 0x170: attach called wdc1: unit 0 (atapi): , removable, iordy wcd0: info 80-85-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-0-0-0-0-0-0-34-2e-32-33-20-20-20-20-4e-45-43-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-20-43-44-2d-52-4f-4d-20-44-52-49-56-45-3a-32-36-30-0-0-0-0-0-0-0-0-0-a-0-0-0-3-0-0-3-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-b4-0-b4-0-0-0-0-0-0-0-0-0-0 atapi1.0: req im 5a-0-2a-0-0-0-0-0-18-0-0-0-0-0-0-0 len=24 atapi1.0: start atapi1.0: send cmd 5a-0-2a-0-0-0-0-0-18-0-0-0-0-0-0-0 atapi1.0: intr ireason=0x3, len=24, status=41, error=64 atapi1.0: phase complete wcd1: result of mode sense is code=100, error=0xf01df474 atapi1.0: req im 5a-0-2a-0-0-0-0-0-18-0-0-0-0-0-0-0 len=24 atapi1.0: start atapi1.0: send cmd 5a-0-2a-0-0-0-0-0-18-0-0-0-0-0-0-0 atapi1.0: intr ireason=0x2, len=24, status=48, error=0 atapi1.0: phase data in atapi1.0: intr ireason=0x3, len=24, status=40, error=0 atapi1.0: phase complete wcd0: result of second mode sense is code=0, error=0xf01df474 wcd0: 344Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray wcd0: medium type unknown, unlocked wcd0: cap 0-16-0-0-0-0-0-0-2a-e-0-0-71-65-29-3-61-1-0-1-0-1-61-1 atapi1.1 at 0x170: attach called atapi.1 at 0x170: no device An "lsdev" shows: wdc0 Unknown ST506/ESDI/IDE disk controller wd0 Unknown ST506/ESDI/IDE disk wdc1 Unknown ST506/ESDI/IDE disk controller wcd0 Idle ATAPI compact disc: NEC CD-ROM DRIVE: Which is *really* nice! I've done a MAKEDEV to get: zinc: {158} ll wcd* brw-r----- 1 root operator 19, 0 Aug 23 12:23 wcd0c I then: zinc: {160} mount -t cd9660 /dev/wcd0c /cdrom zinc: {161} ls /cdrom 00_index.txt catscan ddeml.dll msajt110.dll splash3.bmp beerhelp.hlp catscans fullpic setup.exe threed.vbx beerpicl cmdialog.vbx gloss.hlp setup.lst vbdb300.dll beerpics commdlg.dll homebrew.exe setup1.ex_ vbrun300.dll beertxt ctl3d.dll labels setupkit.dl_ ver.dl_ brewing2.mdb ddeml.dl_ msaes110.dll setupkit.dll ver.dll Success! The Walnut Creek Beer Homebrewing Guide CD! I looked at a few files in here and the data appears to be good too. This is most excellent! Hey Serge, Thanks! This last patch did it! jdl PS- Hmmm... It looks like something has corrupted *some* of the files on my disk, though. Those homebrew.exe's just aren't running on my FreeBSD system... Anyone have any ideas? PPS- Don't make me put a smiley in there... From owner-freebsd-current Sun Sep 10 23:47:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA10939 for current-outgoing; Sun, 10 Sep 1995 23:47:39 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA10918 for ; Sun, 10 Sep 1995 23:47:18 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA07997 for ; Mon, 11 Sep 1995 08:44:25 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA25557 for freebsd-current@freefall.freebsd.org; Mon, 11 Sep 1995 08:44:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA23474 for freebsd-current@freefall.freebsd.org; Mon, 11 Sep 1995 08:36:28 +0200 From: J Wunsch Message-Id: <199509110636.IAA23474@uriah.heep.sax.de> Subject: Re: LED command timeout errors To: freebsd-current@freefall.freebsd.org Date: Mon, 11 Sep 1995 08:36:28 +0200 (MET DST) Reply-To: freebsd-current@freefall.freebsd.org In-Reply-To: from "Ugen J.S.Antsilevich" at Sep 10, 95 06:49:36 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1015 Sender: current-owner@FreeBSD.org Precedence: bulk As Ugen J.S.Antsilevich wrote: > > >> When I am using my lexmark keyboard (standard ps/2 style keyboard and an > >> adapter to convert the jack to a normal-din connector instead of the > >> smaller one) I am unable to see the LEDs for capslock numlock and > scrollock.. > Same with me..i have some sort of no-name keyboard and using pcvt > i am unable to see the leds, they are just off all the time..With Do you get syslog messages that the LEDs cannot be handled? > syscons they are doing pretty well...Also Ctrl+Alt+Del doesnt works > in pcvt and there are a couple of odd things with keyboard mapping like > Backspace etc but theese are resolvable... Both is intention. Now that shutdown_nice() does the right thing, pcvt will eventually switch to it in the next version. I'm still not sure if it should be enabled by default. (In other words: i hate it. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Sep 10 23:50:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA11079 for current-outgoing; Sun, 10 Sep 1995 23:50:43 -0700 Received: from mailhub.cts.com (root@mailhub.cts.com [192.188.72.25]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id XAA11073 for ; Sun, 10 Sep 1995 23:50:43 -0700 Received: from io.cts.com by mailhub.cts.com with smtp (Smail3.1.29.1 #19) id m0ss2h8-000V2OC; Sun, 10 Sep 95 23:50 PDT Received: (from root@localhost) by io.cts.com (8.6.12/8.6.9) id XAA11860 for freebsd-current@FreeBSD.ORG; Sun, 10 Sep 1995 23:50:47 -0700 From: Morgan Davis Message-Id: <199509110650.XAA11860@io.cts.com> Subject: Re: whereis To: freebsd-current@FreeBSD.ORG Date: Sun, 10 Sep 1995 23:50:46 -0700 (PDT) In-Reply-To: <199509100705.JAA20049@uriah.heep.sax.de> from "J Wunsch" at Sep 10, 95 09:05:04 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 665 Sender: current-owner@FreeBSD.ORG Precedence: bulk J Wunsch writes: > > As Morgan Davis wrote: > > > > I've often wondered why the 'whereis' command doesn't use your $PATH > > in addition to the default path it searches. Is there some compelling > > reason for not doing this? > > What you're requesting is covered by "which -a". It sure is! Thanks a bunch. Works perfectly. > "whereis" has been crippled beyond recognition in 4.4BSD. It has to > be rewritten, the current functionality is absolutely useless. Either > Wolfram Schneider (but with low priority for this) or me will revamp > it probably in Perl. Yup. You're talking about the original whereis, the one that can find man pages, too, right? From owner-freebsd-current Mon Sep 11 00:22:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA11747 for current-outgoing; Mon, 11 Sep 1995 00:22:19 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA11741 for ; Mon, 11 Sep 1995 00:22:17 -0700 Received: (from jkh@localhost) by time.cdrom.com (8.6.12/8.6.9) id AAA01160 for current@freefall; Mon, 11 Sep 1995 00:22:14 -0700 Date: Mon, 11 Sep 1995 00:22:14 -0700 From: "Jordan K. Hubbard" Message-Id: <199509110722.AAA01160@time.cdrom.com> To: current@freefall.FreeBSD.org Subject: Is nullfs broken in -current? Sender: current-owner@FreeBSD.org Precedence: bulk I just attempted to use it to loop "/usr/src" and "/usr/obj" mounts on my system (^&*$@%!! broken make macros!) and every time I compile anything substantive from /usr/src I now get a divide by zero and panic. I could go into more detail here and will if this isn't immediately reproducible by those interested in nullfs. Last person I saw in that code was... David? Jordan From owner-freebsd-current Mon Sep 11 00:32:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA12243 for current-outgoing; Mon, 11 Sep 1995 00:32:59 -0700 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id AAA12232 for ; Mon, 11 Sep 1995 00:32:48 -0700 Received: from utis156.cs.utwente.nl by utrhcs.cs.utwente.nl (5.x/csrelayMX-SVR4_1.1tmp/RB) id AA29933; Mon, 11 Sep 1995 09:32:25 +0200 Received: by utis156.cs.utwente.nl (4.1/RBCS-1.0.1) id AA29516; Mon, 11 Sep 95 09:32:17 +0200 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@FreeBSD.org (FreeBSD-current users), kieber@sax.de (Ulf Kieber) Subject: Re: SLIP routing problem In-Reply-To: Your message of "Fri, 08 Sep 1995 21:16:56 +0200." <199509081916.VAA14347@uriah.heep.sax.de> Date: Mon, 11 Sep 1995 09:32:16 +0200 Message-Id: <29515.810804736@utis156.cs.utwente.nl> From: Andras Olah Sender: current-owner@FreeBSD.org Precedence: bulk Joerg, Sorry, I don't know the exact solution to your problem, but at least I know where you have to look further. The host specific route in your routing table is a cloned route. These are generated to enable TCP to store host-specific metrics in the routing table. This facility is used by T/TCP and is by the congestion control/avoidance algorithms in standard TCP. My guess for the solution is that cloned routes should be automatically discarded if they're in conflict with the new route being added instead of preventing adding the new route. Since I'm not really familiar with the details of the routing code, I may be wrong. The route cloning code is Garrett's work, so probably he's the one who may know the right solution to your problem. You can find the code in netinet/in_rmx.c. Andras PS: netstat -ra will show you the cloned routes as well, by default they are suppressed. On Fri, 08 Sep 1995 21:16:56 +0200, J Wunsch wrote: [ ... ] > Sep 8 20:16:55 sax pppd[2010]: pppd 2.1.2 started by ppufo, uid 68 > Sep 8 20:16:55 sax pppd[2010]: Connect: ppp0 <--> /dev/ttyd1 > Sep 8 20:16:59 sax pppd[2010]: local IP address 193.175.26.126 > Sep 8 20:16:59 sax pppd[2010]: remote IP address 193.175.26.117 > Sep 8 20:16:59 sax pppd[2010]: ioctl(SIOCAIFADDR): Address already exists > > 44 sax:~> /sbin/route get 193.175.26.117 > route to: ufo > destination: ufo > gateway: sax-gw1 > interface: ed0 > flags: > recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire > 0 0 0 0 0 0 0 3597 > > The interesting fact here is that "sax-gw1" is the _ethernet_ interface. > So now i've got the following picture: > > o at startup time of any pointopoint interface, all routes to that > interface are being cleared, and everything is started from scratch > [in_ifscrub() is called] > > o the link breaks, and all routes to the interface are being cleared > immediately > > o anyway, since there have been active connections over that link, > further packets with the destination to that pointopoint interface > will arrive; since the link is down, the only route that does apply > to them is the _default_ route, which points back to the world via > the ethernet > > o this somehow (?) creates a routing table entry for this host, tagged > for the (default route) ethernet interface, with an expiration time > of 3600 seconds The default route is referenced which creates a host specific cloned route. > o the pointopoint link comes back after redialing, but somehow (?) > the bogus route through the ethernet interface will not be cleared > by in_ifscrub() as it ought to be, and the subsequent attempt to > create the interface route for this address fails since the routing > code claims a route would already exist From owner-freebsd-current Mon Sep 11 00:44:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA12453 for current-outgoing; Mon, 11 Sep 1995 00:44:28 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA12443 ; Mon, 11 Sep 1995 00:44:27 -0700 From: John Dyson Message-Id: <199509110744.AAA12443@freefall.freebsd.org> Subject: Re: Is nullfs broken in -current? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 11 Sep 1995 00:44:26 -0700 (PDT) Cc: current@freefall.FreeBSD.org In-Reply-To: <199509110722.AAA01160@time.cdrom.com> from "Jordan K. Hubbard" at Sep 11, 95 00:22:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 827 Sender: current-owner@FreeBSD.org Precedence: bulk > > I just attempted to use it to loop "/usr/src" and "/usr/obj" mounts on > my system (^&*$@%!! broken make macros!) and every time I compile > anything substantive from /usr/src I now get a divide by zero and > panic. I could go into more detail here and will if this isn't > immediately reproducible by those interested in nullfs. Last person > I saw in that code was... David? > > Jordan > All of the layered filesystem stuff is slated to be fixed for 2.2. I am too busy right now to even look at it right now because of that irritating Sig-11 problem. The VFS layering needs work (and even in the original 4.4Lite stuff was "not good".) The getpage/putpage stuff is the first step in the fixes. (Other things include proper NFS locking -- right now NFS doesn't VOP_LOCK at all!!!) John dyson@freebsd.org From owner-freebsd-current Mon Sep 11 01:03:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA13317 for current-outgoing; Mon, 11 Sep 1995 01:03:48 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA13301 for ; Mon, 11 Sep 1995 01:03:41 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id RAA19061 for freebsd-current@freefall.freebsd.org; Mon, 11 Sep 1995 17:44:22 +0930 From: Michael Smith Message-Id: <199509110814.RAA19061@genesis.atrad.adelaide.edu.au> Subject: PCVT in early kernel startup stages To: freebsd-current@freefall.freebsd.org Date: Mon, 11 Sep 1995 17:44:22 +0930 (CST) In-Reply-To: <199509110636.IAA23474@uriah.heep.sax.de> from "J Wunsch" at Sep 11, 95 08:36:28 am Content-Type: text Content-Length: 1051 Sender: current-owner@FreeBSD.org Precedence: bulk Hoya Joerg! I'm the fool responsible for the new userconfig(), and it's not working with pcvt (I don't have a test machine just yet). What I'd like to find out is : - What the cursor keys return to cngetc() - How to do inverse video and low/high intensity using the cn* hooks. If you have a moment to look at it, it was committed to -current a few days ago - since then it's been determinted that it's not working with serial consoles (working with Bruce Evans on that one) and also with pcvt. I followed the pcvt code as far as I could, but your comment about spaghetti is well and trucly correct 8( Any information you might be able to provide would be great. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Mon Sep 11 03:06:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA18132 for current-outgoing; Mon, 11 Sep 1995 03:06:35 -0700 Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA18124 for ; Mon, 11 Sep 1995 03:06:29 -0700 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0ss5gf-000I0RC; Mon, 11 Sep 95 12:02 MET DST Received: by ernie.altona.hamburg.com (Smail3.1.29.1 #3) id m0ss57t-00000fC; Mon, 11 Sep 95 11:26 MET DST Message-Id: From: hm@altona.hamburg.com (Hellmuth Michaelis) Subject: Re: LED command timeout errors To: ferovick@runner.jpl.utsa.edu Date: Mon, 11 Sep 1995 11:26:05 +0200 (MET DST) Cc: freebsd-current@freefall.freebsd.org In-Reply-To: <9509101705.AA15328@runner.utsa.edu> from "David C Ferovick" at Sep 10, 95 12:05:32 pm Reply-To: hm@altona.hamburg.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1206 Sender: current-owner@FreeBSD.org Precedence: bulk >From the keyboard of David C Ferovick: > When I am using my lexmark keyboard (standard ps/2 style keyboard and an > adapter to convert the jack to a normal-din connector instead of the > smaller one) I am unable to see the LEDs for capslock numlock and scrollock.. > If I use any of these keys during the session, I will eventually get > LED command timeout errors from the PCVT driver I'd love to get such a keyboard on my desk to eventually being able to reproduce the problem you describe. It seems there are some strange keyboards out there who have the problems you describe. There are several things you can do: - send the keyboard to me to have a look at what it does ;-) - start debugging the pcvt keyboard code and send diffs - compile your kernel with PCVT_NO_LED_UPDATE, this will stop touching the keyboard leds (this is for those weird keyboards like yours) - have a look in the code where option PCVT_PORTIO_DELAY is used and defined, switch to using the DELAY() method and increase the delay time hellmuth -- Hellmuth Michaelis hm@altona.hamburg.com Hamburg, Europe (A)bort, (R)etry, (I)nstall BSD ? From owner-freebsd-current Mon Sep 11 04:23:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA19126 for current-outgoing; Mon, 11 Sep 1995 04:23:22 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA19089 for ; Mon, 11 Sep 1995 04:22:00 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA19965 for ; Mon, 11 Sep 1995 13:20:56 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id NAA26957 for freebsd-current@FreeBSD.ORG; Mon, 11 Sep 1995 13:20:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id MAA24151 for freebsd-current@FreeBSD.ORG; Mon, 11 Sep 1995 12:38:57 +0200 From: J Wunsch Message-Id: <199509111038.MAA24151@uriah.heep.sax.de> Subject: Re: whereis To: freebsd-current@FreeBSD.ORG Date: Mon, 11 Sep 1995 12:38:57 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.ORG In-Reply-To: <199509110650.XAA11860@io.cts.com> from "Morgan Davis" at Sep 10, 95 11:50:46 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 799 Sender: current-owner@FreeBSD.ORG Precedence: bulk As Morgan Davis wrote: > > > "whereis" has been crippled beyond recognition in 4.4BSD. It has to > > be rewritten, the current functionality is absolutely useless. Either > > Wolfram Schneider (but with low priority for this) or me will revamp > > it probably in Perl. > > Yup. You're talking about the original whereis, the one that can find > man pages, too, right? ...and the source. I've got a prototype in Perl for review to Wolfram Schneider (hacked after the old man page). Stay tuned... Btw. (Rod?), would copying parts of a 1.1.5.1 manual page into the current one violate the license agreement? I don't see much sense in rewording it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Sep 11 04:32:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA19291 for current-outgoing; Mon, 11 Sep 1995 04:32:45 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA19282 for ; Mon, 11 Sep 1995 04:32:42 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id EAA23310 for ; Mon, 11 Sep 1995 04:24:48 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA19990; Mon, 11 Sep 1995 13:21:21 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id NAA26968; Mon, 11 Sep 1995 13:21:15 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id MAA24205; Mon, 11 Sep 1995 12:46:30 +0200 From: J Wunsch Message-Id: <199509111046.MAA24205@uriah.heep.sax.de> Subject: Re: SLIP routing problem To: olah@cs.utwente.nl (Andras Olah) Date: Mon, 11 Sep 1995 12:46:29 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org, kieber@sax.de In-Reply-To: <29515.810804736@utis156.cs.utwente.nl> from "Andras Olah" at Sep 11, 95 09:32:16 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 786 Sender: current-owner@FreeBSD.org Precedence: bulk Hi Andras, thanks for your comments. > My guess for the solution is that cloned routes should be > automatically discarded if they're in conflict with the new route > being added instead of preventing adding the new route. Since I'm Agreed. > not really familiar with the details of the routing code, I may be > wrong. The route cloning code is Garrett's work, so probably he's > the one who may know the right solution to your problem. You can > find the code in netinet/in_rmx.c. A-ha. Ok, unless Garrett steps forward, i'll have a look. The problem has reached a high degree of annoyance, and should IMHO also be fixed in 2.1. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Sep 11 05:28:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA20015 for current-outgoing; Mon, 11 Sep 1995 05:28:52 -0700 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id FAA20009 for ; Mon, 11 Sep 1995 05:28:42 -0700 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA27285; Mon, 11 Sep 95 14:31:15 +0100 Date: Mon, 11 Sep 95 14:31:15 +0100 Message-Id: <9509111331.AA27285@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: se@zpr.uni-koeln.de Cc: current@freebsd.org In-Reply-To: <199509091920.AA16534@Sysiphos> (se@zpr.uni-koeln.de) Subject: Re: NCR problem: progress X-Mailer: Emacs Sender: current-owner@freebsd.org Precedence: bulk >>>>> Stefan Esser writes: > You can disable tagged commands for a single target: > # ncrcontrol -t 4 -s tags=0 > (sets max. 0 tags (i.e. send no TAG message at all) > for target 4). This seems to solve my problems with the Micropolis 4110: no errors, no crashes :-) I will now try to reenable synchronous transfers. Thanks for your help, Jean-Marc > Regards, STefan > -- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================== > http://www.zpr.uni-koeln.de/staff/esser/esser.html _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Mon Sep 11 06:57:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA21399 for current-outgoing; Mon, 11 Sep 1995 06:57:40 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA21386 for ; Mon, 11 Sep 1995 06:57:38 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id GAA01403 for freebsd-current@FreeBSD.ORG; Mon, 11 Sep 1995 06:57:33 -0700 From: "Rodney W. Grimes" Message-Id: <199509111357.GAA01403@GndRsh.aac.dev.com> Subject: Re: whereis To: freebsd-current@FreeBSD.ORG Date: Mon, 11 Sep 1995 06:57:33 -0700 (PDT) In-Reply-To: <199509111038.MAA24151@uriah.heep.sax.de> from "J Wunsch" at Sep 11, 95 12:38:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1046 Sender: current-owner@FreeBSD.ORG Precedence: bulk > > As Morgan Davis wrote: > > > > > "whereis" has been crippled beyond recognition in 4.4BSD. It has to > > > be rewritten, the current functionality is absolutely useless. Either > > > Wolfram Schneider (but with low priority for this) or me will revamp > > > it probably in Perl. > > > > Yup. You're talking about the original whereis, the one that can find > > man pages, too, right? > > ...and the source. I've got a prototype in Perl for review to > Wolfram Schneider (hacked after the old man page). Stay tuned... > > Btw. (Rod?), would copying parts of a 1.1.5.1 manual page into the > current one violate the license agreement? I don't see much sense in > rewording it. ``Cease all use of and distribution of Net/2 code''. Your ``useing'' it because your reading it to figure out what they did. You would cause walnut creek to ``distribute'' it if you put it in :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Sep 11 06:58:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA21460 for current-outgoing; Mon, 11 Sep 1995 06:58:09 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA21454 for ; Mon, 11 Sep 1995 06:58:08 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id JAA18288; for ; Mon, 11 Sep 1995 09:58:07 -0400 Date: Mon, 11 Sep 95 09:53:32 PDT From: "Ugen J.S.Antsilevich" Subject: dset & userconfig To: freebsd-current@FreeBSD.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Hi! Two questions... While i was out userconfig completely changed and everybody forgot that dset should have some support from userconfig in order to save kernel information back.Currently dset is of no use - it would not notice any change you do in userconfig. I don't know, i am still not so set up to touch it so mey be anyone in the busness would like to fix it? Second question is lame, but - how da hell i am getting this userconfig to work.I have pcvt and when entering this nice red config screen(could we PLEEASE change pcvt defaults???) - only buttons which work for me are TAB and ENTER so the only thing i can do is expand first list of devices and that's it....I guess this is some incompatibility betwin pcvt and config but this does not helps me much... Thanx. --Ugen From owner-freebsd-current Mon Sep 11 07:56:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA23916 for current-outgoing; Mon, 11 Sep 1995 07:56:31 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA23910 for ; Mon, 11 Sep 1995 07:56:29 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id HAA11155; Mon, 11 Sep 1995 07:55:44 -0700 Message-Id: <199509111455.HAA11155@precipice.shockwave.com> To: "Ugen J.S.Antsilevich" cc: freebsd-current@FreeBSD.org Subject: Re: dset & userconfig In-reply-to: Your message of "Mon, 11 Sep 1995 09:53:32 PDT." Date: Mon, 11 Sep 1995 07:55:44 -0700 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk One other comment about the new userconfig. Has it been tested and does it work on a SERIAL console hooked up to a DUMB terminal? Sometimes, more is less. Please make sure this works! From: "Ugen J.S.Antsilevich" Subject: dset & userconfig Hi! Two questions... While i was out userconfig completely changed and everybody forgot that dset should have some support from userconfig in order to save kernel information back.Currently dset is of no use - it would not notice any change you do in userconfig. I don't know, i am still not so set up to touch it so mey be anyo >>ne in the busness would like to fix it? Second question is lame, but - how da hell i am getting this userconfig to work.I have pcvt and when entering this nice red config screen(could we PLEEASE change pcvt defaults???) - only buttons which work for me are TAB and ENTER so the only thing i can do is expand first list of devices and that >>'s it....I guess this is some incompatibility betwin pcvt and config but this does not helps me much... Thanx. --Ugen From owner-freebsd-current Mon Sep 11 08:18:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA24363 for current-outgoing; Mon, 11 Sep 1995 08:18:20 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA24357 for ; Mon, 11 Sep 1995 08:18:15 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA17321; Tue, 12 Sep 1995 01:15:37 +1000 Date: Tue, 12 Sep 1995 01:15:37 +1000 From: Bruce Evans Message-Id: <199509111515.BAA17321@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, ugen@latte.worldbank.org Subject: Re: dset & userconfig Sender: current-owner@FreeBSD.org Precedence: bulk >While i was out userconfig completely changed and everybody forgot that dset >should have some support from userconfig in order to save kernel information >back.Currently dset is of no use - it would not notice any change you do in >userconfig. I don't know, i am still not so set up to touch it so mey be anyone >in the busness would like to fix it? Was all the support in save_dev()? It wasn't well documented :-). (dset works on a copy of the devtabs instead of on the originals because some write to the devtabs.) dset is too quiet about the problem, with or without -q. (_isa_devlist no longer exists so the first nlist() fails.). > Second question is lame, but - how da hell i am getting this userconfig >to work.I have pcvt and when entering this nice red config screen(could we >PLEEASE change pcvt defaults???) - only buttons which work for me are TAB >and ENTER so the only thing i can do is expand first list of devices and that's >it....I guess this is some incompatibility betwin pcvt and config but this >does not helps me much... userconfig() handles the scancodeish values returned by sccngetc() for arrow keys (588 = up arrow). It attempts to handle ANSI escape sequences for arrow keys (`ESC [ A' for up arrow) but this seems to be broken (it doesn't work here for a serial terminal). pcvt apparently returns something different from syscons. I think it returns ESC [ A for the up arrow not on the numeric keypad but that doesn't work. Bruce From owner-freebsd-current Mon Sep 11 08:33:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA24727 for current-outgoing; Mon, 11 Sep 1995 08:33:32 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA24721 for ; Mon, 11 Sep 1995 08:33:31 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id LAA29496; for ; Mon, 11 Sep 1995 11:31:45 -0400 Date: Mon, 11 Sep 95 11:29:45 PDT From: "Ugen J.S.Antsilevich" Subject: Re: dset & userconfig To: freebsd-current@FreeBSD.org, Bruce Evans X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk >Was all the support in save_dev()? It wasn't well documented :-). (dset >works on a copy of the devtabs instead of on the originals because some >write to the devtabs.) dset is too quiet about the problem, with or >without -q. (_isa_devlist no longer exists so the first nlist() fails.). Good somebody knows..:))) So i hope i can be safe here..:) >userconfig() handles the scancodeish values returned by sccngetc() for >arrow keys (588 = up arrow). It attempts to handle ANSI escape >sequences for arrow keys (`ESC [ A' for up arrow) but this seems to be >broken (it doesn't work here for a serial terminal). pcvt apparently >returns something different from syscons. I think it returns ESC [ A >for the up arrow not on the numeric keypad but that doesn't work. Yap...probably something like that..anyway as a fact it is completely unsuable..So actually we don't have userconfig at all.... --Ugen From owner-freebsd-current Mon Sep 11 08:59:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA25223 for current-outgoing; Mon, 11 Sep 1995 08:59:39 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA25213 for ; Mon, 11 Sep 1995 08:59:35 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA18486; Tue, 12 Sep 1995 01:55:19 +1000 Date: Tue, 12 Sep 1995 01:55:19 +1000 From: Bruce Evans Message-Id: <199509111555.BAA18486@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, ugen@latte.worldbank.org Subject: Re: dset & userconfig Sender: current-owner@FreeBSD.org Precedence: bulk >>userconfig() handles the scancodeish values returned by sccngetc() for >>arrow keys (588 = up arrow). It attempts to handle ANSI escape >>sequences for arrow keys (`ESC [ A' for up arrow) but this seems to be >>broken (it doesn't work here for a serial terminal). pcvt apparently >>returns something different from syscons. I think it returns ESC [ A >>for the up arrow not on the numeric keypad but that doesn't work. >Yap...probably something like that..anyway as a fact it is completely >unsuable..So actually we don't have userconfig at all.... Use syscons. You can now have pcvt and syscons in the same kernel and can switch between them using userconfig. At least, you could switch between them if userconfig worked :-). The problem with serial consoles seems to be that dolist() redraws stuff while in the middle of an escape sequence, so input is lost (input is polled). Typing the escape sequence works. It works in pcvt. Type `Esc [ A' and `Esc [ B' to move up and down. Bruce From owner-freebsd-current Mon Sep 11 10:04:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA26583 for current-outgoing; Mon, 11 Sep 1995 10:04:42 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA26577 for ; Mon, 11 Sep 1995 10:04:40 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id NAA12258; for ; Mon, 11 Sep 1995 13:04:37 -0400 Date: Mon, 11 Sep 95 13:02:57 PDT From: "Ugen J.S.Antsilevich" Subject: Re: dset & userconfig To: freebsd-current@FreeBSD.org, Bruce Evans X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk >(input is polled). Typing the escape sequence works. It works in >pcvt. Type `Esc [ A' and `Esc [ B' to move up and down. He he..aren't we on the way to the user friendly interface..With this we would beat Mac and Win95 together..he he..Just kidding..:)) --Ugen From owner-freebsd-current Mon Sep 11 10:13:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA26707 for current-outgoing; Mon, 11 Sep 1995 10:13:55 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA26701 for ; Mon, 11 Sep 1995 10:13:54 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA28627; Mon, 11 Sep 1995 13:13:37 -0400 Date: Mon, 11 Sep 1995 13:13:37 -0400 From: "Garrett A. Wollman" Message-Id: <9509111713.AA28627@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@freebsd.org Subject: test coverage of LINT In-Reply-To: <199509100344.NAA19536@godzilla.zeta.org.au> References: <199509100344.NAA19536@godzilla.zeta.org.au> Sender: current-owner@freebsd.org Precedence: bulk < said: > do that since the file contents doesn't change like it should. For lfs.h, > the behaviour is different but probably still broken: if the LFS option > isn't enabled, then lfs.h defines NLFS as 0; otherwise lfs.h isn't created. > Nothing actually includes lfs.h so there is no problem in practice (but > config doesn't know that). This is standard behavior, demonstrating the difference between `option' and `pseudo-device' declarations in the config file. Config has no way of knowing which declaration you didn't specify, and so it generates the header as if the unspecified option were a pseudo-device. > NFOO is guaranteed to be > 0 if the driver is configured (except possibly > for cases involving cross references). I'd like to remove these ifdefs. Since they don't hurt anything, I am inclined to leave them in as a reminder to people looking at the source code what "foo.h" and NFOO are for. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon Sep 11 10:37:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA27046 for current-outgoing; Mon, 11 Sep 1995 10:37:29 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA27040 ; Mon, 11 Sep 1995 10:37:24 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA18629; Mon, 11 Sep 1995 10:30:14 -0700 From: Terry Lambert Message-Id: <199509111730.KAA18629@phaeton.artisoft.com> Subject: Re: Is nullfs broken in -current? To: dyson@freefall.freebsd.org (John Dyson) Date: Mon, 11 Sep 1995 10:30:14 -0700 (MST) Cc: jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199509110744.AAA12443@freefall.freebsd.org> from "John Dyson" at Sep 11, 95 00:44:26 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1738 Sender: current-owner@FreeBSD.org Precedence: bulk > All of the layered filesystem stuff is slated to be fixed for 2.2. I am > too busy right now to even look at it right now because of that irritating > Sig-11 problem. The VFS layering needs work (and even in the original > 4.4Lite stuff was "not good".) The getpage/putpage stuff is the first > step in the fixes. (Other things include proper NFS locking -- right now > NFS doesn't VOP_LOCK at all!!!) I agree that the layering is quite broken. Most of the code that came from the BSD 4.4Lite and Lite2 distributions and implements the file system framework itself is bad. In general, the implementation is one that assumes static linking while the architecture is one that assumes dynamic. Basically, there should not be a static dependence on the size of the function tables that is caused by the first initialization setting the table size rather than a sizeof operation on a NULL-filled table. All file systems, static or otherwise, should use the same registration procedure. The NFS locking is currently being worked on. The last report I heard was that it was to the point of being able to take and ignore all requests, such that Sun machines wuit their bitching. I've rolled some additional fixes for handle-to-open-file-instance conversion using a callback registration mechanism only when NFS is loaded. The getpage/putpage stuff doesn't seem to be a particularly profound change for anything but the page management, which is as it should be, considering the file system framework still wants to be able to share the majority of code between FreeBSD/NetBSD/Other systems. 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-current Mon Sep 11 10:42:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA27136 for current-outgoing; Mon, 11 Sep 1995 10:42:59 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA27130 for ; Mon, 11 Sep 1995 10:42:58 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA18641; Mon, 11 Sep 1995 10:35:20 -0700 From: Terry Lambert Message-Id: <199509111735.KAA18641@phaeton.artisoft.com> Subject: Re: Is nullfs broken in -current? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 11 Sep 1995 10:35:20 -0700 (MST) Cc: current@freefall.freebsd.org In-Reply-To: <199509110722.AAA01160@time.cdrom.com> from "Jordan K. Hubbard" at Sep 11, 95 00:22:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1301 Sender: current-owner@FreeBSD.org Precedence: bulk > I just attempted to use it to loop "/usr/src" and "/usr/obj" mounts on > my system (^&*$@%!! broken make macros!) and every time I compile > anything substantive from /usr/src I now get a divide by zero and > panic. I could go into more detail here and will if this isn't > immediately reproducible by those interested in nullfs. Last person > I saw in that code was... David? The NULL and UNION FS's are problematic. So is the PORTAL. The page management changes will affect both of them in terms of page propagation, but should not in fact affect other areas significantly. That is, the page ops need to be written to pass the pages through to the underlying layer (layerS, in the union case). It's getting on time to consider a file system test bed. The page operations are clearly the cause of the recent instabilities; they are just as clearly a necessary step forward in terms of performance and the ability to go multithreaded in support of SMP and multithreading (this last a significant performance win in even a UP kernel -- to the tune of a 70% increase in overall file system throuput in the USL UFS implementation on a UP box, actually). 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-current Mon Sep 11 10:55:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA27345 for current-outgoing; Mon, 11 Sep 1995 10:55:05 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA27336 ; Mon, 11 Sep 1995 10:55:05 -0700 From: John Dyson Message-Id: <199509111755.KAA27336@freefall.freebsd.org> Subject: Re: Is nullfs broken in -current? To: terry@lambert.org (Terry Lambert) Date: Mon, 11 Sep 1995 10:55:04 -0700 (PDT) Cc: jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199509111730.KAA18629@phaeton.artisoft.com> from "Terry Lambert" at Sep 11, 95 10:30:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1696 Sender: current-owner@FreeBSD.org Precedence: bulk > > The NFS locking is currently being worked on. The last report I heard > was that it was to the point of being able to take and ignore all > requests, such that Sun machines wuit their bitching. I've rolled > some additional fixes for handle-to-open-file-instance conversion > using a callback registration mechanism only when NFS is loaded. > That is not the locking that I am talking about. I am talking about the VOP_LOCK entry points (not related.) The problem with implementing VOP_LOCK properly is that nfs operations have to be locked differently than ffs. (Otherwise nfs timeouts don't happen correctly, and other evil things occur.) I have a fix that practically eliminates the concurrency problems in nfs. > The getpage/putpage stuff doesn't seem to be a particularly profound > change for anything but the page management, which is as it should be, > considering the file system framework still wants to be able to share > the majority of code between FreeBSD/NetBSD/Other systems. > The page management needs to be filtered by the other filesystem layers. For "leaf" type filesystems there is some default handling in the vnode_pager. REMEMBER, we have a *fully* merged VM/Buffer cache!!! For layered filesystems, there needs to be some special stuff. (nullfs should share the VM objects with the underlying filesystem for example.) Also we still have compatibility with the older less effective clustering, and non-merged VM/Buffer cache filesystems. For example, ext2fs was almost not a port, but practically dropped right in. I have a few more things to do to fix it though (there is code missing to make certain VM operations work correctly.) John dyson@root.com From owner-freebsd-current Mon Sep 11 11:04:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA27542 for current-outgoing; Mon, 11 Sep 1995 11:04:58 -0700 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA27409 for ; Mon, 11 Sep 1995 10:57:01 -0700 Received: by Sysiphos id AA16687 (5.67b/IDA-1.5 for current@freebsd.org); Mon, 11 Sep 1995 19:56:24 +0200 Message-Id: <199509111756.AA16687@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 11 Sep 1995 19:56:23 +0200 In-Reply-To: Mark Dawson "Re: PCI and Compaq Proliant" (Sep 11, 18:19) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Mark Dawson Subject: Re: PCI and Compaq Proliant Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk On Sep 11, 18:19, Mark Dawson wrote: } Subject: Re: PCI and Compaq Proliant } Stefan, } } I made the following one line change to the i386/isa/pcibus.c code which } gives me the promising results you can see below. } } *** pcibus.c Mon Sep 11 17:38:48 1995 } --- pcibus.c- Mon Sep 11 18:14:30 1995 } *************** } *** 160,166 **** } } oldval = inl (CONF1_ADDR_PORT); } outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK); } ! /* outb (CONF1_ADDR_PORT +3, 0); XXX md */ } result = inl (CONF1_ADDR_PORT); } outl (CONF1_ADDR_PORT, oldval); } } --- 160,166 ---- } } oldval = inl (CONF1_ADDR_PORT); } outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK); } ! outb (CONF1_ADDR_PORT +3, 0); } result = inl (CONF1_ADDR_PORT); } outl (CONF1_ADDR_PORT, oldval); Do I understand that right: You commented out the line reading outb (CONF1_ADDR_PORT +3, 0); and now it works ? That's bad news actually. Quoting from the PCI specs rev. 2.0, section 6.4.3.1.1: % Anytime a host bridge sees a full DWORD I/O write to CONFIG_ADDRESS, % the bridge must latch the data into its CONFIG_ADDRESS register. % On full DWORD I/O reads to CONFIG_ADDRESS, the bridge must return % the data in CONFIG_ADDRESS. Any other types of access to this address % (non-DWORD) must be treated like a normal I/O access and no special % action must be taken. Therefor the only I/O space consumed by the % register is a DWORD at the given address. I/O devices using BYTE or % WORD registers are not affected because they will be passed on unchanged. In fact, the code in 2.0.5R failed to correctly recognize configuration mechanism 1, which wasn't used by then. And the new code (which doesn't seem to work on your Compaq) was put in, because it uses the only specifically method to distinguish config mech. 1 vs. 2 chip sets ... } [I've got a Compaq Proliant 1500 arriving this week and I'm keeping my } fingers crossed that the Prosignia and Proliant share the same PCI } architecture.] } } Any ideas why such a small change should made so much difference? No, not really. The device at pci0:0 is the main PCI bus bridge chip, and that has a vendor ID of 0xe11. Do you know which vendor that is ? } Should I be worried by the "pci_map_mem failed" lines? No, there seems to be a consistency check being overly pessimistic. This was treated as a fatal error before, but I changed it into a warning to learn about people who own systems that trigger this message to have them help me debug the code :) Guess there is some condition reversed, but it's a low priority item to me currently ... } FreeBSD 2.1-STABLE #4: Mon Sep 11 17:42:09 BST 1995 } md@ida.dcs.qmw.ac.uk:/export/FreeBSD-sup/src/sys/compile/BOOTMFS } CPU: 90-MHz Pentium 735\90 (Pentium-class CPU) } Origin = "GenuineIntel" Id = 0x524 Stepping=4 } Features=0x1bf } Probing for devices on the pci0 bus: } configuration mode 1 allows 32 devices. } pci0:0: vendor=0xe11, device=0x1000pci_conf_read(1): addr=80000008 data=1 } , class=old [no driver assigned] I'd really like to know who got vendor ID 0x0e11 ... } pci_map_mem failed: device's memrange 0x2200000-0x22000ff is } incompatible with its bridge's memrange 0x4000000-0xffffffff This message is obviously bogus ... A memory range of 0x2200000-0x22000ff is just 256 bytes, and that's too small for anything ... Everything else looked Ok. There is no way I could remove the outb() from the code! We'll have to find another way to make your system work. I was mislead by the report of configuration mech. 1 you got into believing, that the board was correctly setup to accept configuration space accesses. But in fact, it looks like the BYTE write is not ignored, and has some nasty effect. This is surrising, because it gets overwritten by the following outl() anyway ... O well ... Could you please give this a try: oldval = inl (CONF1_ADDR_PORT); outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK); outb (CONF1_ADDR_PORT +3, 0); result = inl (CONF1_ADDR_PORT); outb (CONF1_ADDR_PORT +3, (unsigned)CONF1_ENABLE_CHK >> 24); /****/ outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK); /****/ outl (CONF1_ADDR_PORT, oldval); And if it seems to work, could you please try each of the both lines alone ... It would be no problem to add them to the probe code, since they are supposed to be NOPs. But the first outb() was supposed to be a NOP, too :) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/staff/esser/esser.html From owner-freebsd-current Mon Sep 11 12:01:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA28554 for current-outgoing; Mon, 11 Sep 1995 12:01:49 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA28548 for ; Mon, 11 Sep 1995 12:01:45 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA20196 for current@freebsd.org; Mon, 11 Sep 1995 11:52:20 -0700 From: Terry Lambert Message-Id: <199509111852.LAA20196@phaeton.artisoft.com> Subject: BAD BUG IN UFS RENAME To: current@freebsd.org Date: Mon, 11 Sep 1995 11:52:20 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 652 Sender: current-owner@freebsd.org Precedence: bulk Well, I've discovered some very interesting brain damage. In the case of an attemped cross-device rename, both NAMEI buffers are freed twice. In the case of a rename of a->b where a + b have the same inode numbers but not the same name, the, the from buffer is freed twice. I'm about to engage in a cleanup of this very code, I'm just reporting the problem to note the justification of the cleanup. The code of interest for this bungle is in: kern/vfs_syscalls.c (rename) ufs/ufs/ufs_vnops.c (ufs_rename) 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-current Mon Sep 11 12:54:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA29990 for current-outgoing; Mon, 11 Sep 1995 12:54:55 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA29983 for ; Mon, 11 Sep 1995 12:54:39 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA06881 for ; Mon, 11 Sep 1995 21:54:05 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA00644 for freebsd-current@freebsd.org; Mon, 11 Sep 1995 21:54:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id VAA25715 for freebsd-current@freebsd.org; Mon, 11 Sep 1995 21:53:22 +0200 From: J Wunsch Message-Id: <199509111953.VAA25715@uriah.heep.sax.de> Subject: Re: dset & userconfig To: freebsd-current@freebsd.org Date: Mon, 11 Sep 1995 21:53:21 +0200 (MET DST) Reply-To: freebsd-current@freebsd.org In-Reply-To: <199509111555.BAA18486@godzilla.zeta.org.au> from "Bruce Evans" at Sep 12, 95 01:55:19 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 732 Sender: current-owner@freebsd.org Precedence: bulk As Bruce Evans wrote: > > The problem with serial consoles seems to be that dolist() redraws > stuff while in the middle of an escape sequence, so input is lost > (input is polled). Typing the escape sequence works. It works in > pcvt. Type `Esc [ A' and `Esc [ B' to move up and down. I think pcvt defaults (bogusly?) to the "application" mode cursor keys: Esc O A, Esc O B etc. I've promised to help with this, but i've first got to complete the merge of our pcvt modifications with the official release 3.30 of pcvt. I've been promising this already for too long to Hellmuth... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Sep 11 13:10:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA00519 for current-outgoing; Mon, 11 Sep 1995 13:10:48 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA00513 for ; Mon, 11 Sep 1995 13:10:42 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id NAA07191; Mon, 11 Sep 1995 13:09:22 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id NAA03186; Mon, 11 Sep 1995 13:11:37 -0700 Message-Id: <199509112011.NAA03186@corbin.Root.COM> To: Terry Lambert cc: current@freebsd.org, mckusick@mckusick.com Subject: Re: BAD BUG IN UFS RENAME In-reply-to: Your message of "Mon, 11 Sep 95 11:52:20 PDT." <199509111852.LAA20196@phaeton.artisoft.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 11 Sep 1995 13:11:36 -0700 Sender: current-owner@freebsd.org Precedence: bulk >Well, I've discovered some very interesting brain damage. > >In the case of an attemped cross-device rename, both NAMEI buffers are >freed twice. Yes, I think I see this - the VOP_ABORTOP's on both cn buffers, followed by the explicit free's in rename()? >In the case of a rename of a->b where a + b have the same inode numbers >but not the same name, the, the from buffer is freed twice. Hmmm, I think I see it free the *to* buffer twice, but I don't see what you're seeing regarding the *from* buffer. Also, in rename(), the case where the file has the same name, too, will cause *both* buffers to be freed twice - note the two VOP_ABORTOP's followed by the explicit frees. Lite2 has the same bugs. -DG From owner-freebsd-current Mon Sep 11 13:32:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA02292 for current-outgoing; Mon, 11 Sep 1995 13:32:15 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA02071 for ; Mon, 11 Sep 1995 13:31:24 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA20905; Mon, 11 Sep 1995 13:23:16 -0700 From: Terry Lambert Message-Id: <199509112023.NAA20905@phaeton.artisoft.com> Subject: Re: BAD BUG IN UFS RENAME To: davidg@root.com Date: Mon, 11 Sep 1995 13:23:16 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org, mckusick@mckusick.com In-Reply-To: <199509112011.NAA03186@corbin.Root.COM> from "David Greenman" at Sep 11, 95 01: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 Content-Length: 1425 Sender: current-owner@freebsd.org Precedence: bulk > > >Well, I've discovered some very interesting brain damage. > > > >In the case of an attemped cross-device rename, both NAMEI buffers are > >freed twice. > > Yes, I think I see this - the VOP_ABORTOP's on both cn buffers, followed by > the explicit free's in rename()? Yes. It's not obvious because they check the HASBUF in the VOP_ABORTOP; the actual rename stuff will work for UFS, assuming that there aren't any cascade errors, but not for other file systems. This because they check that the SAVESTART bit isn't set to determine the free behaviour. So it's not as blatant as it would seem the first time you glance at it; it *will* work except it blows in a couple of error cases and one interaction with the miscfs/union/union_subr.c code. This could very well be the MSDOSFS rename bug. The union stuff fails similarly. SAVESTART is only set in two modules: vfs_syscalls and nfs_serv.c; the first in the rename case, and the second on lookup, create, mknod, rename, and symlink. Actually, nulling out the VOP_ABORTOP free and explicitly freeing the HASBUF buffer (the plan) will fix the problem areas as well as the layering. I'm also planning on a freed flag for the DIAGNOSTIC case to ensure a re-free will fail with a panic(), but this is not a high priority. 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-current Mon Sep 11 13:54:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA04557 for current-outgoing; Mon, 11 Sep 1995 13:54:14 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA04547 for ; Mon, 11 Sep 1995 13:54:09 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA26687 for current@freebsd.org; Mon, 11 Sep 1995 13:47:00 -0700 Date: Mon, 11 Sep 1995 13:47:00 -0700 From: Terry Lambert Message-Id: <199509112047.NAA26687@phaeton.artisoft.com> To: current@freebsd.org Subject: Find *still* broken... Sender: current-owner@freebsd.org Precedence: bulk The command find /sys -type f -exec grep VOP_LINK {} \; -print and find /sys -type f -exec grep VOP_LINK {} \; -print > foo & tail -f foo Still produce diffrent output because find does not flush stdout when doing a -print. 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-current Mon Sep 11 14:28:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA06418 for current-outgoing; Mon, 11 Sep 1995 14:28:04 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA06412 for ; Mon, 11 Sep 1995 14:28:00 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA03444 ; Mon, 11 Sep 1995 23:27:50 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA06064 ; Mon, 11 Sep 1995 23:27:49 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id TAA03559; Mon, 11 Sep 1995 19:50:22 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509111750.TAA03559@keltia.Freenix.FR> Subject: Re: Is nullfs broken in -current? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 11 Sep 1995 19:50:22 +0200 (MET DST) Cc: current@freefall.freebsd.org In-Reply-To: <199509110722.AAA01160@time.cdrom.com> from "Jordan K. Hubbard" at Sep 11, 95 00:22:14 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that Jordan K. Hubbard said: > panic. I could go into more detail here and will if this isn't > immediately reproducible by those interested in nullfs. Last person > I saw in that code was... David? Whenever you're trying to write something it will panic. I was trying a while to use like you do and anytime I did a "cvs update" it paniced. It has been broken for a long time but I see that John said they'll be fixed in 2.2. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Mon Sep 11 14:28:33 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA06471 for current-outgoing; Mon, 11 Sep 1995 14:28:33 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA06461 for ; Mon, 11 Sep 1995 14:28:27 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA03440 for ; Mon, 11 Sep 1995 23:27:49 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA06061 for freebsd-current@freefall.freebsd.org; Mon, 11 Sep 1995 23:27:48 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id TAA03535; Mon, 11 Sep 1995 19:44:18 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509111744.TAA03535@keltia.Freenix.FR> Subject: Re: LED command timeout errors To: freebsd-current@freefall.freebsd.org Date: Mon, 11 Sep 1995 19:44:18 +0200 (MET DST) Cc: freebsd-current@freefall.freebsd.org In-Reply-To: <199509110636.IAA23474@uriah.heep.sax.de> from "J Wunsch" at Sep 11, 95 08:36:28 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that J Wunsch said: > Both is intention. Now that shutdown_nice() does the right thing, > pcvt will eventually switch to it in the next version. I'm still not > sure if it should be enabled by default. (In other words: i hate > it. :) I think I remember a discussion about making Ctrl-Alt-Del function sysctl-able... Am I just dreaming or is there anyone who remember it too ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Mon Sep 11 15:00:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA07657 for current-outgoing; Mon, 11 Sep 1995 15:00:42 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA07651 for ; Mon, 11 Sep 1995 15:00:40 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id PAA09158 for ; Mon, 11 Sep 1995 15:00:36 -0700 To: current@freefall.FreeBSD.org Subject: libforms - thumbs up or down? Date: Mon, 11 Sep 1995 15:00:36 -0700 Message-ID: <9156.810856836@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk The current libforms does not work in -current; the only available example hangs. This makes me wonder if we shouldn't just remove libforms entirely since _nothing_ currently uses it. It's a nice idea and all, but we have to be a little mercenary about not keeping things around that just never quite made it into the spotlight for some reason. I nuked my own `dmenu' utility out for this reason, and libftp went as well when it was found to be insufficient for today's needs (passive mode ftp, for one thing). We should either improve libforms enough so that it's ready to use in *something* FreeBSD related or appreciate that it's not going to happen in the forseeable future and nuke it for now. We can always bring it back if we find a use for it and if we DON'T find a use for it then we've also not got the extra bloat in our source tree. Useful bloat I'm usually in favor of, bloat unused by any sort of application or client I'm not. Jordan From owner-freebsd-current Mon Sep 11 15:16:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA08242 for current-outgoing; Mon, 11 Sep 1995 15:16:50 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA08230 for ; Mon, 11 Sep 1995 15:16:47 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA03703; Mon, 11 Sep 1995 16:18:54 -0600 Date: Mon, 11 Sep 1995 16:18:54 -0600 From: Nate Williams Message-Id: <199509112218.QAA03703@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: current@freefall.freebsd.org Subject: Re: libforms - thumbs up or down? In-Reply-To: <9156.810856836@time.cdrom.com> References: <9156.810856836@time.cdrom.com> Sender: current-owner@FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > This makes me wonder if we shouldn't just remove libforms entirely > since _nothing_ currently uses it. I argued for it's demise a long time ago, but Paul defended it's existance as something that was asked for and would be used. I still don't see a use for it *in the tree*, though I suppose one could use it. I consider it: ' bloat unused by any sort of application or client ....', which means it's useless since no application or client IN the tree uses it. Nate From owner-freebsd-current Mon Sep 11 15:18:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA08399 for current-outgoing; Mon, 11 Sep 1995 15:18:11 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA08354 for ; Mon, 11 Sep 1995 15:17:51 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id AAA13223; Tue, 12 Sep 1995 00:17:36 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id AAA13939; Tue, 12 Sep 1995 00:17:36 +0200 Message-Id: <199509112217.AAA13939@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: libforms - thumbs up or down? Date: Tue, 12 Sep 1995 00:17:35 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > The current libforms does not work in -current; the only available > example hangs. Thumb down. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key From owner-freebsd-current Mon Sep 11 15:34:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA09133 for current-outgoing; Mon, 11 Sep 1995 15:34:07 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA09127 for ; Mon, 11 Sep 1995 15:34:06 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id PAA26573 for ; Mon, 11 Sep 1995 15:33:43 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id IAA20219; Tue, 12 Sep 1995 08:13:37 +0930 From: Michael Smith Message-Id: <199509112243.IAA20219@genesis.atrad.adelaide.edu.au> Subject: Re: dset & userconfig To: ugen@latte.worldbank.org (Ugen J.S.Antsilevich) Date: Tue, 12 Sep 1995 08:13:37 +0930 (CST) Cc: freebsd-current@FreeBSD.org In-Reply-To: from "Ugen J.S.Antsilevich" at Sep 11, 95 09:53:32 am Content-Type: text Content-Length: 1933 Sender: current-owner@FreeBSD.org Precedence: bulk Ugen J.S.Antsilevich stands accused of saying: > While i was out userconfig completely changed and everybody forgot that dset > should have some support from userconfig in order to save kernel information > back.Currently dset is of no use - it would not notice any change you do in > userconfig. I don't know, i am still not so set up to touch it so mey be anyone > in the busness would like to fix it? It's all my fault 8) I made the (obviously lame) assumption that dset just read the condfig out of the running kernel and wrote it back into the one on disk. This is obviously at least partly true, as if you don't boot with -c, userconfig() is never called. Let's guess; dset uses the unexplained save_dev function and the isa_device list created by userconfig 8) I'll fix this ASAP. > Second question is lame, but - how da hell i am getting this userconfig > to work.I have pcvt and when entering this nice red config screen(could we > PLEEASE change pcvt defaults???) - only buttons which work for me are TAB > and ENTER so the only thing i can do is expand first list of devices and that's > it....I guess this is some incompatibility betwin pcvt and config but this > does not helps me much... This is a major stumbling block just now; it looks like pcvt doesn't actually _do_ cursor keys at that point in the boot process, so I'm considering asking Jordan to pull the plug on the new userconfig until I manage to work that out. (serial console operation appears to be broken as well 8( ) > --Ugen Sorry for any inconvenience. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Mon Sep 11 16:28:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA11027 for current-outgoing; Mon, 11 Sep 1995 16:28:58 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA11019 for ; Mon, 11 Sep 1995 16:28:57 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id PAA26688 for ; Mon, 11 Sep 1995 15:49:56 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id PAA05521; Mon, 11 Sep 1995 15:50:11 -0700 To: John Dyson cc: current@FreeBSD.org Subject: Re: Progress so far on the Sig-11 problem In-reply-to: Your message of "Sun, 10 Sep 1995 17:51:33 PDT." <199509110051.RAA00137@freefall.freebsd.org> Date: Mon, 11 Sep 1995 15:50:11 -0700 Message-ID: <5519.810859811@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > I am having problems reproducing the problem. It takes quite-a-while to > get it to happen, and only appears when I am running in less than 8MB. Interesting. I just reproduced it with a 64MB machine running -current (vi and sendmail started to die off) as well as a 16MB box (sendmail and others). It's gotten so bad for me that I'm right now in the process of reverting my two development machines to 2.1. I can't afford the downtime right now. Jordan From owner-freebsd-current Mon Sep 11 16:29:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA11046 for current-outgoing; Mon, 11 Sep 1995 16:29:00 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA11029 for ; Mon, 11 Sep 1995 16:28:58 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id PAA26584 for ; Mon, 11 Sep 1995 15:35:26 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id IAA20231; Tue, 12 Sep 1995 08:16:29 +0930 From: Michael Smith Message-Id: <199509112246.IAA20231@genesis.atrad.adelaide.edu.au> Subject: Re: dset & userconfig To: pst@shockwave.com (Paul Traina) Date: Tue, 12 Sep 1995 08:16:29 +0930 (CST) Cc: ugen@latte.worldbank.org, freebsd-current@FreeBSD.org In-Reply-To: <199509111455.HAA11155@precipice.shockwave.com> from "Paul Traina" at Sep 11, 95 07:55:44 am Content-Type: text Content-Length: 893 Sender: current-owner@FreeBSD.org Precedence: bulk Paul Traina stands accused of saying: > > One other comment about the new userconfig. > > Has it been tested and does it work on a SERIAL console hooked up to a > DUMB terminal? It has been tested on what I have to hand; to wit, one FreeBSD machine. I don't have an asr33 anymore; and my LA120 is making some small fish very happy. _minimal_ ANSI is required/ > Sometimes, more is less. Please make sure this works! Agreed; that's why it's out, so that people can find bugs in it, so that I can fix them. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Mon Sep 11 16:29:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA11086 for current-outgoing; Mon, 11 Sep 1995 16:29:04 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA11056 for ; Mon, 11 Sep 1995 16:29:01 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id PAA26699 for ; Mon, 11 Sep 1995 15:51:52 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id IAA20273; Tue, 12 Sep 1995 08:33:14 +0930 From: Michael Smith Message-Id: <199509112303.IAA20273@genesis.atrad.adelaide.edu.au> Subject: Re: dset & userconfig To: bde@zeta.org.au (Bruce Evans) Date: Tue, 12 Sep 1995 08:33:14 +0930 (CST) Cc: freebsd-current@FreeBSD.org, ugen@latte.worldbank.org In-Reply-To: <199509111555.BAA18486@godzilla.zeta.org.au> from "Bruce Evans" at Sep 12, 95 01:55:19 am Content-Type: text Content-Length: 1224 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans stands accused of saying: > The problem with serial consoles seems to be that dolist() redraws > stuff while in the middle of an escape sequence, so input is lost > (input is polled). Typing the escape sequence works. It works in > pcvt. Type `Esc [ A' and `Esc [ B' to move up and down. Ah puke. Thanks a million Bruce; that looks like it. The immediate patch is to add the marked line below : if (delta) { showparams(ofsent(*ofs,*list)); drawline(row+*ofs,detail,ofsent(*ofs,*list),1,dhelp); >>> delta = 0; <<< Add this line } At the top of dolist() in sys/i386/i386/userconfig.c I'll mail a small patch to Jordan to cover this and a few other things straight away. You're currently getting a redraw after _every_ keypress, which isn't what's supposed to happen 8( Now to deal with pcvt 8) > Bruce -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Mon Sep 11 16:29:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA11103 for current-outgoing; Mon, 11 Sep 1995 16:29:05 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA11068 for ; Mon, 11 Sep 1995 16:29:02 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id PAA26596 for ; Mon, 11 Sep 1995 15:38:49 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id IAA20250; Tue, 12 Sep 1995 08:20:10 +0930 From: Michael Smith Message-Id: <199509112250.IAA20250@genesis.atrad.adelaide.edu.au> Subject: Re: dset & userconfig To: bde@zeta.org.au (Bruce Evans) Date: Tue, 12 Sep 1995 08:20:09 +0930 (CST) Cc: freebsd-current@FreeBSD.org, ugen@latte.worldbank.org In-Reply-To: <199509111515.BAA17321@godzilla.zeta.org.au> from "Bruce Evans" at Sep 12, 95 01:15:37 am Content-Type: text Content-Length: 1242 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans stands accused of saying: > userconfig() handles the scancodeish values returned by sccngetc() for > arrow keys (588 = up arrow). It attempts to handle ANSI escape > sequences for arrow keys (`ESC [ A' for up arrow) but this seems to be > broken (it doesn't work here for a serial terminal). pcvt apparently > returns something different from syscons. I think it returns ESC [ A > for the up arrow not on the numeric keypad but that doesn't work. I hope to work on this tonight (now +12 hours); but I admit it has me baffled. ANSI keycode testing was done using xterm to generate the appropriate escape sequences, and also under syscons. In both of these situations, everything works fine, which seems to point to a timing problem with unbuffered serial console input. I have just purchased a VT320 in order to pursue this problem. > Bruce -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Mon Sep 11 17:53:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA13686 for current-outgoing; Mon, 11 Sep 1995 17:53:20 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA13680 for ; Mon, 11 Sep 1995 17:53:18 -0700 Received: from [171.69.108.40] (transience.shockwave.com [171.69.108.40]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id RAA11985; Mon, 11 Sep 1995 17:51:28 -0700 X-Sender: pst@precipice.shockwave.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Sep 1995 17:51:52 -0700 To: Michael Smith From: pst@shockwave.com (Paul Traina) Subject: Re: dset & userconfig Cc: bde@zeta.org.au (Bruce Evans), freebsd-current@FreeBSD.org, ugen@latte.worldbank.org Sender: current-owner@FreeBSD.org Precedence: bulk While you're at it, why don't you make it accept commands from the keypad in either mode... ESC [ A or ESC O A ... paul From owner-freebsd-current Mon Sep 11 17:53:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA13700 for current-outgoing; Mon, 11 Sep 1995 17:53:22 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA13687 for ; Mon, 11 Sep 1995 17:53:20 -0700 Received: from [171.69.108.40] (transience.shockwave.com [171.69.108.40]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id RAA11982; Mon, 11 Sep 1995 17:51:25 -0700 X-Sender: pst@precipice.shockwave.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 11 Sep 1995 17:51:49 -0700 To: Michael Smith From: pst@shockwave.com (Paul Traina) Subject: Re: dset & userconfig Cc: ugen@latte.worldbank.org, freebsd-current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >It has been tested on what I have to hand; to wit, one FreeBSD machine. >I don't have an asr33 anymore; and my LA120 is making some small fish >very happy. _minimal_ ANSI is required/ OK, I have a bug report to file. BUG: new userconfig() assumes a minimal ANSI terminal. FIX: make it work on a glass tty or ASR-33. Not all the world is ANSI!!! :-( From owner-freebsd-current Mon Sep 11 17:53:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA13782 for current-outgoing; Mon, 11 Sep 1995 17:53:35 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA13768 for ; Mon, 11 Sep 1995 17:53:33 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA00326 for ; Mon, 11 Sep 1995 17:53:30 -0700 To: current@freefall.FreeBSD.org Subject: Sound code: Anyone for -current code in 2.1? Date: Mon, 11 Sep 1995 17:53:30 -0700 Message-ID: <324.810867210@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk Well, I've proven to my satisfaction that the GUS MAX doesn't really work correctly in 2.1-STABLE (at least not with `maplay', at it's documented as broken in 2.1's LINT) so I just need to know whether or not all the soundblaster et al users out there are happier with the -current sound code, or the 2.1-STABLE stuff. If it's 2.1-STABLE then I'll bow to the needs of the many and take a broken GUS MAX for the time being. If it's 2.2, then I'll do the work to integrate it into 2.1. You folks decide. Feedback please? Jordan From owner-freebsd-current Mon Sep 11 18:00:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA14022 for current-outgoing; Mon, 11 Sep 1995 18:00:51 -0700 Received: from disperse.demon.co.uk (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA14015 for ; Mon, 11 Sep 1995 18:00:42 -0700 Received: from post.demon.co.uk by disperse.demon.co.uk id aa15830; 11 Sep 95 21:02 +0100 Received: from palmer.demon.co.uk by post.demon.co.uk id aa17944; 11 Sep 95 20:59 +0100 Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id TAA06412 ; Mon, 11 Sep 1995 19:37:27 +0100 X-Message: This is a dial-up site. Quick responses to e-mails should not be relied upon. Thanks! To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: Is nullfs broken in -current? In-reply-to: Your message of "Mon, 11 Sep 1995 00:22:14 PDT." <199509110722.AAA01160@time.cdrom.com> Date: Mon, 11 Sep 1995 19:37:26 +0100 Message-ID: <6410.810844646@palmer.demon.co.uk> From: Gary Palmer Sender: current-owner@FreeBSD.org Precedence: bulk In message <199509110722.AAA01160@time.cdrom.com>, "Jordan K. Hubbard" writes: >I just attempted to use it to loop "/usr/src" and "/usr/obj" mounts on >my system (^&*$@%!! broken make macros!) and every time I compile >anything substantive from /usr/src I now get a divide by zero and >panic. I could go into more detail here and will if this isn't >immediately reproducible by those interested in nullfs. Last person >I saw in that code was... David? Amazing - I'm getting to the end of my mail backlog :-) Comment: AFAIK, nullfs has always been broken for `writing' - but I used it successfully on my machine here for over 2 months read only fine. I think that may be your problem... Gary From owner-freebsd-current Mon Sep 11 18:04:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA14156 for current-outgoing; Mon, 11 Sep 1995 18:04:13 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA14150 for ; Mon, 11 Sep 1995 18:04:12 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15770(5)>; Mon, 11 Sep 1995 18:03:37 PDT Received: by crevenia.parc.xerox.com id <177475>; Mon, 11 Sep 1995 18:03:29 -0700 From: Bill Fenner To: current@freebsd.org Subject: userconfig doesn't work on tvi925 Message-Id: <95Sep11.180329pdt.177475@crevenia.parc.xerox.com> Date: Mon, 11 Sep 1995 18:03:22 PDT Sender: current-owner@freebsd.org Precedence: bulk Hi, I have a headless PC with a tvi925 clone as its console. The new userconfig assumes a vt100, so it is completely useless in this situation. Is there any chance of adding a "dumb terminal" mode and defaulting to it if you are on a serial console? (With, of course, a command in "dumb" mode that can switch you to full screen mode?) Bill From owner-freebsd-current Mon Sep 11 18:10:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA14317 for current-outgoing; Mon, 11 Sep 1995 18:10:55 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA14311 for ; Mon, 11 Sep 1995 18:10:53 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id SAA00384; Mon, 11 Sep 1995 18:10:05 -0700 To: pst@shockwave.com (Paul Traina) cc: Michael Smith , ugen@latte.worldbank.org, freebsd-current@FreeBSD.org Subject: Re: dset & userconfig In-reply-to: Your message of "Mon, 11 Sep 1995 17:51:49 PDT." Date: Mon, 11 Sep 1995 18:10:05 -0700 Message-ID: <382.810868205@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > >It has been tested on what I have to hand; to wit, one FreeBSD machine. > >I don't have an asr33 anymore; and my LA120 is making some small fish > >very happy. _minimal_ ANSI is required/ > > OK, I have a bug report to file. > > BUG: new userconfig() assumes a minimal ANSI terminal. > > FIX: make it work on a glass tty or ASR-33. Not all the world is ANSI!!! :- This was hardly unknown at the start, and I was the one who told Michael to feel free in assuming ANSI as a minimum price of entry. However, it was perhaps the wrong decision to make this interface the *only* one and I am talking now with Michael about making the entire visual interface a command available from the wretched, inferior, ugly CLI interface we have now. I may even go a few steps towards improving that CLI, like adding wildcarding to `disable' and other such creature comforts. Would that make you happ(y|ier)? Jordan From owner-freebsd-current Mon Sep 11 18:23:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA14700 for current-outgoing; Mon, 11 Sep 1995 18:23:23 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA14694 for ; Mon, 11 Sep 1995 18:23:19 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA14593; Mon, 11 Sep 1995 18:14:25 -0700 From: Terry Lambert Message-Id: <199509120114.SAA14593@phaeton.artisoft.com> Subject: Re: Is nullfs broken in -current? To: gary@palmer.demon.co.uk (Gary Palmer) Date: Mon, 11 Sep 1995 18:14:25 -0700 (MST) Cc: jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <6410.810844646@palmer.demon.co.uk> from "Gary Palmer" at Sep 11, 95 07:37:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 467 Sender: current-owner@FreeBSD.org Precedence: bulk > AFAIK, nullfs has always been broken for `writing' - but I used it > successfully on my machine here for over 2 months read only fine. I > think that may be your problem... Document an instance and a mount command line that would cause this to be useful. If I agree, and it doesn't just work on the Lite2 code, I'll fix it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Sep 11 18:48:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA15441 for current-outgoing; Mon, 11 Sep 1995 18:48:21 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA15435 for ; Mon, 11 Sep 1995 18:48:18 -0700 Received: from puffin.pelican.com by pelican.com with smtp (Smail3.1.28.1 #5) id m0ssKRj-000K2lC; Mon, 11 Sep 95 18:47 WET DST Received: by puffin.pelican.com (Smail3.1.29.1 #9) id m0ssKRj-0000RfC; Mon, 11 Sep 95 18:47 PDT Message-Id: From: pete@puffin.pelican.com (Pete Carah) Subject: DEC 21041 To: current@freebsd.org Date: Mon, 11 Sep 1995 18:47:34 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 387 Sender: current-owner@freebsd.org Precedence: bulk I'm blessed with a supply of SMC cards using DEC 21041 instead of 21040; all their new cards come this way. This isn't recognized by de0 driver (and may not even be recognized by the PCI probes?). It also isn't recognized by last spring's SMC windoze driver or diganostic, so they really did something to it. Does anyone know what the difference is and what patch is needed? -- Pete From owner-freebsd-current Mon Sep 11 18:48:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA15487 for current-outgoing; Mon, 11 Sep 1995 18:48:49 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA15480 for ; Mon, 11 Sep 1995 18:48:47 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id SAA00254; Mon, 11 Sep 1995 18:47:14 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id SAA03593; Mon, 11 Sep 1995 18:49:25 -0700 Message-Id: <199509120149.SAA03593@corbin.Root.COM> To: Bill Fenner cc: current@freebsd.org Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 95 18:03:22 PDT." <95Sep11.180329pdt.177475@crevenia.parc.xerox.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 11 Sep 1995 18:49:24 -0700 Sender: current-owner@freebsd.org Precedence: bulk > I have a headless PC with a tvi925 clone as its console. The new >userconfig assumes a vt100, so it is completely useless in this situation. >Is there any chance of adding a "dumb terminal" mode and defaulting to it >if you are on a serial console? (With, of course, a command in "dumb" >mode that can switch you to full screen mode?) Well, I just spent 20 minutes on the phone with Jordan convincing him that we should bring back the CLI mode. The compromise is to provide both the CLI and the "visual" interface. Kernel bloat, yes, but someday this whole thing will hopefully be moved into a "/boot" and won't be part of the kernel. -DG From owner-freebsd-current Mon Sep 11 19:10:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA16332 for current-outgoing; Mon, 11 Sep 1995 19:10:09 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id TAA16326 for ; Mon, 11 Sep 1995 19:10:05 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA00628; Mon, 11 Sep 1995 22:09:59 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA03373; Mon, 11 Sep 95 22:07:21 EDT Date: Mon, 11 Sep 95 22:07:21 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509120207.AA03373@borg.ess.harris.com> To: freebsd-current@freefall.FreeBSD.org, dyson@freefall.FreeBSD.org Subject: Re: Progress so far on the Sig-11 problem Sender: current-owner@FreeBSD.org Precedence: bulk I have a 16meg 486 system and all I need to do is start X. all xterms after initial startup die with sig 11 then after a few tries the xterms start to work but xarchie keeps faulting sig 6. It may be that all X and X apps will need to be rebuilt...ouch I realize everyone using current is definitely at risk but I do not think there is any question now that current is very broken. Well, maybe this message/thread is enough since everyone supping current should be reading this list :-) It looks like the packaged version of xarchie (dated may 16) will always sig 6 for me. You may want to try it to see if it helps isolate things. Jim Leppek > From owner-freebsd-current@freefall.freebsd.org Mon Sep 11 18:40:32 1995 > Date: Sun, 10 Sep 1995 17:51:33 -0700 > From: John Dyson > To: current@freebsd.org > Subject: Progress so far on the Sig-11 problem > Sender: current-owner@freebsd.org > > > I am having problems reproducing the problem. It takes quite-a-while to > get it to happen, and only appears when I am running in less than 8MB. > I have verified that the pre-zero code is not the culprit (but have done some > minor cleanups.) Another major change is that the original vnode_pager_haspage > was not correct (on the *very* conservative side) on the estimate of the > cluster size. That problem was *fixed* with another bug being introduced. > The bug has been fixed in -current, but I am not sure that the Sig-11 > problems were related. I am still searching for it... > > John > dyson@freebsd.org > From owner-freebsd-current Mon Sep 11 19:12:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA16452 for current-outgoing; Mon, 11 Sep 1995 19:12:39 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA16446 for ; Mon, 11 Sep 1995 19:12:37 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id TAA00300; Mon, 11 Sep 1995 19:11:23 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id TAA03673; Mon, 11 Sep 1995 19:13:34 -0700 Message-Id: <199509120213.TAA03673@corbin.Root.COM> To: pete@puffin.pelican.com (Pete Carah) cc: current@freebsd.org Subject: Re: DEC 21041 In-reply-to: Your message of "Mon, 11 Sep 95 18:47:34 PDT." From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 11 Sep 1995 19:13:24 -0700 Sender: current-owner@freebsd.org Precedence: bulk >I'm blessed with a supply of SMC cards using DEC 21041 instead of 21040; >all their new cards come this way. > >This isn't recognized by de0 driver (and may not even be recognized by >the PCI probes?). It also isn't recognized by last spring's SMC >windoze driver or diganostic, so they really did something to it. > >Does anyone know what the difference is and what patch is needed? I have a version of the driver from Matt Thomas that has this working, but I had some serious performance problems with the driver, and I haven't heard back from Matt about this...so I haven't yet brought in his changes. -DG From owner-freebsd-current Mon Sep 11 19:14:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA16526 for current-outgoing; Mon, 11 Sep 1995 19:14:08 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA16518 for ; Mon, 11 Sep 1995 19:13:57 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id MAA02117; Tue, 12 Sep 1995 12:11:08 +1000 Date: Tue, 12 Sep 1995 12:11:08 +1000 From: Bruce Evans Message-Id: <199509120211.MAA02117@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, ugen@latte.worldbank.org Subject: Re: dset & userconfig Cc: freebsd-current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >It's all my fault 8) I made the (obviously lame) assumption that dset >just read the condfig out of the running kernel and wrote it back into >the one on disk. >This is obviously at least partly true, as if you don't boot with -c, >userconfig() is never called. Then the list of changed devtabs is empty and dset has a particularly easy job of doing nothing. >This is a major stumbling block just now; it looks like pcvt doesn't >actually _do_ cursor keys at that point in the boot process, so I'm >considering asking Jordan to pull the plug on the new userconfig until I >manage to work that out. Also, in user mode it normally returns different escape sequences for the two sets of arrow keys. Bruce From owner-freebsd-current Mon Sep 11 19:32:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA16865 for current-outgoing; Mon, 11 Sep 1995 19:32:37 -0700 Received: from jolt.eng.umd.edu (jolt.eng.umd.edu [129.2.102.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA16855 for ; Mon, 11 Sep 1995 19:32:31 -0700 Received: from latte.eng.umd.edu (latte.eng.umd.edu [129.2.98.15]) by jolt.eng.umd.edu (8.6.10/8.6.4) with ESMTP id WAA19924; Mon, 11 Sep 1995 22:32:28 -0400 Received: (chuckr@localhost) by latte.eng.umd.edu (8.6.10/8.6.4) id WAA22656; Mon, 11 Sep 1995 22:32:28 -0400 Date: Mon, 11 Sep 1995 22:32:27 -0400 (EDT) From: Chuck Robey To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: Sound code: Anyone for -current code in 2.1? In-Reply-To: <324.810867210@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 11 Sep 1995, Jordan K. Hubbard wrote: > Well, I've proven to my satisfaction that the GUS MAX doesn't really > work correctly in 2.1-STABLE (at least not with `maplay', at it's > documented as broken in 2.1's LINT) so I just need to know whether or > not all the soundblaster et al users out there are happier with the > -current sound code, or the 2.1-STABLE stuff. > > If it's 2.1-STABLE then I'll bow to the needs of the many and take a > broken GUS MAX for the time being. If it's 2.2, then I'll do the work > to integrate it into 2.1. You folks decide. Feedback please? I'd integrated the v.30 code into 2.0.5, then went current when the new gus code went into current. I've had no trouble with it at all. This is just my personal experience, Amancio is really the one who knows the code best, but I thought you'd like to know. > > Jordan > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Mon Sep 11 20:07:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA17896 for current-outgoing; Mon, 11 Sep 1995 20:07:52 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA17884 for ; Mon, 11 Sep 1995 20:07:49 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA14847 for current@freebsd.org; Mon, 11 Sep 1995 20:00:40 -0700 From: Terry Lambert Message-Id: <199509120300.UAA14847@phaeton.artisoft.com> Subject: Potentially serious NFS problem To: current@freebsd.org Date: Mon, 11 Sep 1995 20:00:40 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2319 Sender: current-owner@freebsd.org Precedence: bulk Doug, are you there? 8-). I have detected a problem in the NFS server code, though at present I am not certain whether it will manifest as a memory leak or as a double freeing of cn_pnbuf's (which depends on what's meant by VOP_ABORTOP() when called in nfs/nfs_serv.c). I found this when tracking the path name buffer allocation/deallocation layering violations in the standard FS code. What is happening is that there are instances where an allocated path name buffer (cn_pnbuf) is being "discarded" inconsistantly. In nfsrv_create() it is being explicitly FREE'ed after a call to VOP_CREATE() has failed. It is *never* freed, explicitly or by VOP_ABORTOP() side effect, in the success case. In the case of a truncate, it is being free'ed and a call is issued to VOP_ABORTOP() (which in the current code, will also free it). This type of thing occurs in numerous places. It's almost as if the programmer were half-aware that a side effect of a VOP_LOOKUP with a cn_nameiop of CREATE or RENAME implies a SAVENAME in the underlying file systems? I'm not prepared to crack this nut all by myself at present, especially with active work in the NFS code taking place. My current changes to all other file systems are to remove the implied freeing of the cn_pnbuf by all VOP_ABORTOP() routines in all other file systems and the implied freeing of cn_pnbuf in the VOP_ routines that expect to be called with (cn_flags & HASBUF) true. -- My suggested changes for the NFS code would be to make all buffer frees explicit by a call to a routine called nfs_nameifree() to be located in nfs/nfs_subs.c: nfs_nameifree( ndp) register struct nameidata *ndp; { struct componentname *cnp = &ndp->ni_cnd; if( cnp->cn_flags & HASBUF) FREE(cnp->cn_pnbuf, M_NAMEI); } And assume the underlying file system does *NOT* free the buffer on *any* VOP_ calls whatsoever. This would fit with my current patches, but would result in needing a combined code integration (I'm willing to work on that too, despite the getpage/putpage changes throwing all my diffs off). I have client side patches for nfs_node.c and nfs_vnops.c (of course). This is strictly an NFS server code problem. 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-current Mon Sep 11 20:14:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA18226 for current-outgoing; Mon, 11 Sep 1995 20:14:30 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA18217 for ; Mon, 11 Sep 1995 20:14:16 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA04285; Tue, 12 Sep 1995 13:12:36 +1000 Date: Tue, 12 Sep 1995 13:12:36 +1000 From: Bruce Evans Message-Id: <199509120312.NAA04285@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, pst@shockwave.com Subject: Re: dset & userconfig Cc: bde@zeta.org.au, freebsd-current@freebsd.org, ugen@latte.worldbank.org Sender: current-owner@freebsd.org Precedence: bulk >While you're at it, why don't you make it accept commands from the keypad >in either >mode... ESC [ A or ESC O A Because there are too many modes, e.g., for pcvt: numeric keypad up: ESC O x cursor keypad up: ESC O A numeric keypad Del: ESC O n cursor keypad Del: ESC [ 3 ~ ^?: / (broken) For 1001 serial terminals: see termcap.src. Bruce From owner-freebsd-current Mon Sep 11 22:02:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA21261 for current-outgoing; Mon, 11 Sep 1995 22:02:25 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA21255 for ; Mon, 11 Sep 1995 22:02:24 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id WAA12444; Mon, 11 Sep 1995 22:01:48 -0700 Message-Id: <199509120501.WAA12444@precipice.shockwave.com> To: current@freebsd.org cc: Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 1995 18:03:22 PDT." <95Sep11.180329pdt.177475@crevenia.parc.xerox.com> Date: Mon, 11 Sep 1995 22:01:47 -0700 From: Paul Traina Sender: current-owner@freebsd.org Precedence: bulk Jordan, I was speaking with a friend about the new userconfig stuff today, and he had what I think is a simply grand idea. I am really concerned that this crap is in the kernel. I don't think it belongs there, but I was convinced by the old "dumb terminal" userconfig that it was good. Here is my suggestion. Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a sysctl interface and a staticly linked program in /sbin to operate that interface. This keeps the kernel clean, and gives you access to fancy stuff in user mode. If you want to have the old userconfig for emergencies, I have absolutely no objection to that (it would be nice if it was #ifdef'ed). Yes, I'm sorry, I realize it's a pain in the ass to throw away work, but we're really better off with a separation between kernel and user mode stuff. (hell, then you can use curses if you want). Paul From: Bill Fenner Subject: userconfig doesn't work on tvi925 Hi, I have a headless PC with a tvi925 clone as its console. The new userconfig assumes a vt100, so it is completely useless in this situation. Is there any chance of adding a "dumb terminal" mode and defaulting to it if you are on a serial console? (With, of course, a command in "dumb" mode that can switch you to full screen mode?) Bill From owner-freebsd-current Mon Sep 11 22:05:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA21369 for current-outgoing; Mon, 11 Sep 1995 22:05:05 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA21363 for ; Mon, 11 Sep 1995 22:05:04 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id WAA12462; Mon, 11 Sep 1995 22:02:59 -0700 Message-Id: <199509120502.WAA12462@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: Michael Smith , ugen@latte.worldbank.org, freebsd-current@FreeBSD.org Subject: Re: dset & userconfig In-reply-to: Your message of "Mon, 11 Sep 1995 18:10:05 PDT." <382.810868205@time.cdrom.com> Date: Mon, 11 Sep 1995 22:02:59 -0700 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk From: "Jordan K. Hubbard" Subject: Re: dset & userconfig > >It has been tested on what I have to hand; to wit, one FreeBSD machine. > >I don't have an asr33 anymore; and my LA120 is making some small fish > >very happy. _minimal_ ANSI is required/ > > OK, I have a bug report to file. > > BUG: new userconfig() assumes a minimal ANSI terminal. > > FIX: make it work on a glass tty or ASR-33. Not all the world is ANSI!!! >>:- This was hardly unknown at the start, and I was the one who told Michael to feel free in assuming ANSI as a minimum price of entry. However, it was perhaps the wrong decision to make this interface the *only* one and I am talking now with Michael about making the entire visual interface a command available from the wretched, inferior, ugly CLI interface we have now. I may even go a few steps towards improving that CLI, like adding wildcarding to `disable' and other such creature comforts. Would that make you happ(y|ier)? See the last message I just sent out. I think having the "ugly" userconfig as an #ifdef'ed thing, and a user mode program to operate a sysctl interface is where we want to be. Paul From owner-freebsd-current Mon Sep 11 22:13:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA21503 for current-outgoing; Mon, 11 Sep 1995 22:13:51 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA21497 for ; Mon, 11 Sep 1995 22:13:48 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id WAA00735; Mon, 11 Sep 1995 22:12:36 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id WAA04710; Mon, 11 Sep 1995 22:14:47 -0700 Message-Id: <199509120514.WAA04710@corbin.Root.COM> To: Paul Traina cc: current@freebsd.org, Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 95 22:01:47 PDT." <199509120501.WAA12444@precipice.shockwave.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 11 Sep 1995 22:14:47 -0700 Sender: current-owner@freebsd.org Precedence: bulk >Jordan, > >I was speaking with a friend about the new userconfig stuff today, and >he had what I think is a simply grand idea. > >I am really concerned that this crap is in the kernel. I don't think >it belongs there, but I was convinced by the old "dumb terminal" >userconfig that it was good. > >Here is my suggestion. > >Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a >sysctl interface and a staticly linked program in /sbin to operate that >interface. This keeps the kernel clean, and gives you access to fancy >stuff in user mode. If you want to have the old userconfig for emergencies, >I have absolutely no objection to that (it would be nice if it was #ifdef'ed). > >Yes, I'm sorry, I realize it's a pain in the ass to throw away work, but >we're really better off with a separation between kernel and user mode stuff. > >(hell, then you can use curses if you want). That's all nice and fine, and we *should* write a user program to do configuration, but this has nothing to do with why 'userconfig' was created. It was created so that people could boot/install FreeBSD without having to rip their machine apart and reconfigure all of their hardware to conform to our GENERIC kernel. If you can't boot the system, then you can't run the fancy user program from /sbin to do the dirty deed. -DG From owner-freebsd-current Mon Sep 11 22:46:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA22856 for current-outgoing; Mon, 11 Sep 1995 22:46:04 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA22850 for ; Mon, 11 Sep 1995 22:46:01 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id WAA01537; Mon, 11 Sep 1995 22:45:54 -0700 To: Paul Traina cc: current@freebsd.org, Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 1995 22:01:47 PDT." <199509120501.WAA12444@precipice.shockwave.com> Date: Mon, 11 Sep 1995 22:45:53 -0700 Message-ID: <1535.810884753@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > Here is my suggestion. It won't work. > Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a > sysctl interface and a staticly linked program in /sbin to operate that > interface. This keeps the kernel clean, and gives you access to fancy > stuff in user mode. If you want to have the old userconfig for emergencies, Not if you never GET to user mode, it doesn't! Perhaps by complicating the interface we've obscured the purpose somewhat, but the primary purpose remains "getting the user installed on the hard disk." What also needs to happen is for `dset' to get folded into sysinstall so that the second kernel to come off the bindist can also be tweaked to track whatever changes the user had to make in coming up off the floppy. Jordan From owner-freebsd-current Mon Sep 11 22:54:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA23046 for current-outgoing; Mon, 11 Sep 1995 22:54:08 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA23036 for ; Mon, 11 Sep 1995 22:53:37 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA02510 for ; Tue, 12 Sep 1995 07:52:39 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id HAA04349 for freebsd-current@FreeBSD.ORG; Tue, 12 Sep 1995 07:52:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id HAA28056 for freebsd-current@FreeBSD.ORG; Tue, 12 Sep 1995 07:50:34 +0200 From: J Wunsch Message-Id: <199509120550.HAA28056@uriah.heep.sax.de> Subject: Re: dset & userconfig To: freebsd-current@FreeBSD.ORG Date: Tue, 12 Sep 1995 07:50:34 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.ORG In-Reply-To: <199509112243.IAA20219@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Sep 12, 95 08:13:37 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 404 Sender: current-owner@FreeBSD.ORG Precedence: bulk As Michael Smith wrote: > > ..., so I'm > considering asking Jordan to pull the plug on the new userconfig until I > manage to work that out. Nope. 2.2-current is the development branch. Let it in, this will press people (like me, for pcvt :-) to fix it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Sep 11 23:27:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA24419 for current-outgoing; Mon, 11 Sep 1995 23:27:55 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA24413 for ; Mon, 11 Sep 1995 23:27:53 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id XAA12850; Mon, 11 Sep 1995 23:26:43 -0700 Message-Id: <199509120626.XAA12850@precipice.shockwave.com> To: davidg@Root.COM cc: current@freebsd.org, Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 1995 22:14:47 PDT." <199509120514.WAA04710@corbin.Root.COM> Date: Mon, 11 Sep 1995 23:26:43 -0700 From: Paul Traina Sender: current-owner@freebsd.org Precedence: bulk From: David Greenman Subject: Re: userconfig doesn't work on tvi925 >Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a >sysctl interface and a staticly linked program in /sbin to operate that >interface. This keeps the kernel clean, and gives you access to fancy >stuff in user mode. If you want to have the old userconfig for emergencies, >I have absolutely no objection to that (it would be nice if it was #ifdef'ed > >Yes, I'm sorry, I realize it's a pain in the ass to throw away work, but >we're really better off with a separation between kernel and user mode stuff > >(hell, then you can use curses if you want). That's all nice and fine, and we *should* write a user program to do configuration, but this has nothing to do with why 'userconfig' was created. It was created so that people could boot/install FreeBSD without having to rip their machine apart and reconfigure all of their hardware to conform to our GENERIC kernel. If you can't boot the system, then you can't run the fanc user program from /sbin to do the dirty deed. I realize that. Please re-read the fourth and fifth lines that you quoted from me. From owner-freebsd-current Mon Sep 11 23:32:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA24526 for current-outgoing; Mon, 11 Sep 1995 23:32:05 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA24520 for ; Mon, 11 Sep 1995 23:32:03 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id XAA12900; Mon, 11 Sep 1995 23:30:52 -0700 Message-Id: <199509120630.XAA12900@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: current@freebsd.org, Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 1995 22:45:53 PDT." <1535.810884753@time.cdrom.com> Date: Mon, 11 Sep 1995 23:30:52 -0700 From: Paul Traina Sender: current-owner@freebsd.org Precedence: bulk From: "Jordan K. Hubbard" Subject: Re: userconfig doesn't work on tvi925 > Here is my suggestion. It won't work. > Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a > sysctl interface and a staticly linked program in /sbin to operate that > interface. This keeps the kernel clean, and gives you access to fancy > stuff in user mode. If you want to have the old userconfig for > emergencies. Not if you never GET to user mode, it doesn't! Perhaps by complicating the interface we've obscured the purpose somewhat, but the primary purpose remains "getting the user installed on the hard disk." Please re-read the last line you quoted...and now let me expand... What also needs to happen is for `dset' to get folded into sysinstall so that the second kernel to come off the bindist can also be tweaked to track whatever changes the user had to make in coming up off the floppy. All you need to get to user mode on the install disk is a working floppy drive and a working console. It's -highly- unlikely you will need to change the floppy drive or the location/irq of com1, or the address of your vga device. In point of fact, you're ALREADY hosed if those aren't where you expected them to be, because the boot loader and the console driver that userconfig() uses wouldn't work in the first place. QED, you can boot the kernel, get into user mode, and run the fancy program. If my logic is false, then you STILL have the old dumb-terminal userconfig program for emergency hardware changes or initial boot without a reboot. From owner-freebsd-current Mon Sep 11 23:56:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA25121 for current-outgoing; Mon, 11 Sep 1995 23:56:55 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA25115 for ; Mon, 11 Sep 1995 23:56:53 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id XAA01529; Mon, 11 Sep 1995 23:55:21 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id XAA04880; Mon, 11 Sep 1995 23:57:32 -0700 Message-Id: <199509120657.XAA04880@corbin.Root.COM> To: Paul Traina cc: current@freebsd.org, Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 95 23:30:52 PDT." <199509120630.XAA12900@precipice.shockwave.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 11 Sep 1995 23:57:10 -0700 Sender: current-owner@freebsd.org Precedence: bulk >All you need to get to user mode on the install disk is a working floppy >drive and a working console. It's -highly- unlikely you will need to change >the floppy drive or the location/irq of com1, or the address of your vga >device. In point of fact, you're ALREADY hosed if those aren't where you >expected them to be, because the boot loader and the console driver that >userconfig() uses wouldn't work in the first place. The configuration for the disk controller that you'll be installing on has to be set before the kernel does it's device probes. Otherwise there is no way to access the disk to save the settings. We can't save them to the floppy and reboot because the kernel is special (it's "kzip" compressed). This is actually one of several "chicken and egg" complications. This means that the kernel-based "userconfig" is a requirement at least for now. This whole thread started when the idea was proposed to improve the current interface to make it more 'new user' friendly. Whether or not that was a good idea remains to be seen. I personally don't like the 'visual' interface as I find it quite a bit more difficult to use than the simple CLI. ...but my opinion appears to be a minority one. I don't see the harm in making 'userconfig' a USERCONFIG kernel option, however. In fact, it originally started out being an option, but everyone seemed to agree that it was too useful to ever be without...so we made it standard. -DG From owner-freebsd-current Tue Sep 12 01:00:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA27101 for current-outgoing; Tue, 12 Sep 1995 01:00:17 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA27092 for ; Tue, 12 Sep 1995 01:00:12 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id RAA21554; Tue, 12 Sep 1995 17:40:47 +0930 From: Michael Smith Message-Id: <199509120810.RAA21554@genesis.atrad.adelaide.edu.au> Subject: Re: userconfig doesn't work on tvi925 To: pst@shockwave.com (Paul Traina) Date: Tue, 12 Sep 1995 17:40:47 +0930 (CST) Cc: current@freebsd.org, fenner@parc.xerox.com In-Reply-To: <199509120501.WAA12444@precipice.shockwave.com> from "Paul Traina" at Sep 11, 95 10:01:47 pm Content-Type: text Content-Length: 1304 Sender: current-owner@freebsd.org Precedence: bulk Paul Traina stands accused of saying: > Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a > sysctl interface and a staticly linked program in /sbin to operate that > interface. This keeps the kernel clean, and gives you access to fancy > stuff in user mode. If you want to have the old userconfig for emergencies, > I have absolutely no objection to that (it would be nice if it was #ifdef'ed). Tell me how you plan to boot the system to the point where you can run this usermode program. Remember that the whole idea behind the 'pretty' userconfig was to aid the less cerebral among us in getting FreeBSD to the booted point at all. The original design was simple and straightforward; feeping creaturitis has since bloated it a little, but it's not what you'd call a monster. > (hell, then you can use curses if you want). That wouldn't help; dumb terminals still wouldn't be supported. > Paul -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Tue Sep 12 01:02:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA27216 for current-outgoing; Tue, 12 Sep 1995 01:02:07 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA27210 for ; Tue, 12 Sep 1995 01:02:02 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id RAA21563; Tue, 12 Sep 1995 17:42:27 +0930 From: Michael Smith Message-Id: <199509120812.RAA21563@genesis.atrad.adelaide.edu.au> Subject: Re: userconfig doesn't work on tvi925 To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 12 Sep 1995 17:42:26 +0930 (CST) Cc: pst@shockwave.com, current@freebsd.org, fenner@parc.xerox.com In-Reply-To: <1535.810884753@time.cdrom.com> from "Jordan K. Hubbard" at Sep 11, 95 10:45:53 pm Content-Type: text Content-Length: 806 Sender: current-owner@freebsd.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > What also needs to happen is for `dset' to get folded into sysinstall > so that the second kernel to come off the bindist can also be tweaked > to track whatever changes the user had to make in coming up off the > floppy. This is a no-goer. Bruce's seperate-userconfig idea, with a freeform data area is probably the only winner in this, and it's complicated 8( > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Tue Sep 12 02:52:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA01057 for current-outgoing; Tue, 12 Sep 1995 02:52:12 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA01044 for ; Tue, 12 Sep 1995 02:52:07 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id KAA02553; Tue, 12 Sep 1995 10:54:50 +0100 Date: Tue, 12 Sep 1995 10:54:48 +0100 (BST) From: Doug Rabson To: Terry Lambert cc: current@freebsd.org Subject: Re: Potentially serious NFS problem In-Reply-To: <199509120300.UAA14847@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Mon, 11 Sep 1995, Terry Lambert wrote: > Doug, are you there? 8-). Still here :-) > I have detected a problem in the NFS server code, though at present I am > not certain whether it will manifest as a memory leak or as a double > freeing of cn_pnbuf's (which depends on what's meant by VOP_ABORTOP() > when called in nfs/nfs_serv.c). > > ... > > I'm not prepared to crack this nut all by myself at present, especially > with active work in the NFS code taking place. I am not currently working on the nfs code. I think that John is working on the client code but not the server. Feel free to make changes to the server side. > > My current changes to all other file systems are to remove the implied > freeing of the cn_pnbuf by all VOP_ABORTOP() routines in all other > file systems and the implied freeing of cn_pnbuf in the VOP_ routines > that expect to be called with (cn_flags & HASBUF) true. > > -- > > My suggested changes for the NFS code would be to make all buffer > frees explicit by a call to a routine called nfs_nameifree() to be > located in nfs/nfs_subs.c: > > nfs_nameifree( ndp) > register struct nameidata *ndp; > { > struct componentname *cnp = &ndp->ni_cnd; > > if( cnp->cn_flags & HASBUF) > FREE(cnp->cn_pnbuf, M_NAMEI); > } > > And assume the underlying file system does *NOT* free the buffer on *any* > VOP_ calls whatsoever. This would fit with my current patches, but would > result in needing a combined code integration (I'm willing to work on > that too, despite the getpage/putpage changes throwing all my diffs off). This definately sounds like the right thing to do. Go for it! > > I have client side patches for nfs_node.c and nfs_vnops.c (of course). > This is strictly an NFS server code problem. Agreed. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-current Tue Sep 12 03:53:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA02722 for current-outgoing; Tue, 12 Sep 1995 03:53:55 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA02714 for ; Tue, 12 Sep 1995 03:53:37 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA16300 for ; Tue, 12 Sep 1995 12:50:58 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA06122 for current@freefall.freebsd.org; Tue, 12 Sep 1995 12:50:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA28282 for current@freefall.freebsd.org; Tue, 12 Sep 1995 08:03:47 +0200 From: J Wunsch Message-Id: <199509120603.IAA28282@uriah.heep.sax.de> Subject: Re: libforms - thumbs up or down? To: current@freefall.freebsd.org Date: Tue, 12 Sep 1995 08:03:46 +0200 (MET DST) Reply-To: current@freefall.freebsd.org In-Reply-To: <199509112218.QAA03703@rocky.sri.MT.net> from "Nate Williams" at Sep 11, 95 04:18:54 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 442 Sender: current-owner@FreeBSD.org Precedence: bulk As Nate Williams wrote: > > I argued for it's demise a long time ago, but Paul defended it's > existance as something that was asked for and would be used. I still > don't see a use for it *in the tree*, though I suppose one could use it. Find somebody to maintain it, and move it out to ports. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Sep 12 04:15:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA03121 for current-outgoing; Tue, 12 Sep 1995 04:15:04 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA03107 for ; Tue, 12 Sep 1995 04:14:53 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA16296 for ; Tue, 12 Sep 1995 12:50:57 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA06121 for freebsd-current@freefall.freebsd.org; Tue, 12 Sep 1995 12:50:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA28263 for freebsd-current@freefall.freebsd.org; Tue, 12 Sep 1995 08:02:43 +0200 From: J Wunsch Message-Id: <199509120602.IAA28263@uriah.heep.sax.de> Subject: Re: LED command timeout errors To: freebsd-current@freefall.freebsd.org Date: Tue, 12 Sep 1995 08:02:43 +0200 (MET DST) Reply-To: freebsd-current@freefall.freebsd.org In-Reply-To: <199509111744.TAA03535@keltia.Freenix.FR> from "Ollivier Robert" at Sep 11, 95 07:44:18 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 479 Sender: current-owner@FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > I think I remember a discussion about making Ctrl-Alt-Del function > sysctl-able... Am I just dreaming or is there anyone who remember it too ? I've got the patches by Thomas Graichen still sitting in my mail queue. :-( If anybody cares to integrate them, i'm more than happy to hand this over. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Sep 12 04:46:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA03705 for current-outgoing; Tue, 12 Sep 1995 04:46:16 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA03698 for ; Tue, 12 Sep 1995 04:46:15 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id VAA21984; Tue, 12 Sep 1995 21:27:26 +0930 From: Michael Smith Message-Id: <199509121157.VAA21984@genesis.atrad.adelaide.edu.au> Subject: Re: userconfig doesn't work on tvi925 To: pst@shockwave.com (Paul Traina) Date: Tue, 12 Sep 1995 21:27:25 +0930 (CST) Cc: davidg@Root.COM, current@FreeBSD.ORG, fenner@parc.xerox.com In-Reply-To: <199509120626.XAA12850@precipice.shockwave.com> from "Paul Traina" at Sep 11, 95 11:26:43 pm Content-Type: text Content-Length: 757 Sender: current-owner@FreeBSD.ORG Precedence: bulk Paul Traina stands accused of saying: > >stuff in user mode. If you want to have the old userconfig for emergencies, > >I have absolutely no objection to that (it would be nice if it was #ifdef'ed > I realize that. Please re-read the fourth and fifth lines that > you quoted from me. I don't call a newbie booting the kernel on non-conforming hardware an "emergency". -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Tue Sep 12 04:48:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA03775 for current-outgoing; Tue, 12 Sep 1995 04:48:47 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA03769 for ; Tue, 12 Sep 1995 04:48:45 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id VAA21994; Tue, 12 Sep 1995 21:29:56 +0930 From: Michael Smith Message-Id: <199509121159.VAA21994@genesis.atrad.adelaide.edu.au> Subject: Re: userconfig doesn't work on tvi925 To: pst@shockwave.com (Paul Traina) Date: Tue, 12 Sep 1995 21:29:55 +0930 (CST) Cc: jkh@time.cdrom.com, current@freebsd.org, fenner@parc.xerox.com In-Reply-To: <199509120630.XAA12900@precipice.shockwave.com> from "Paul Traina" at Sep 11, 95 11:30:52 pm Content-Type: text Content-Length: 855 Sender: current-owner@freebsd.org Precedence: bulk Paul Traina stands accused of saying: > QED, you can boot the kernel, get into user mode, and run the fancy program. > If my logic is false, then you STILL have the old dumb-terminal userconfig > program for emergency hardware changes or initial boot without a reboot. So great; you get into user mode, you run the fancy program, and where do you save your results? Can't write it into the kernel; it's compressed. Can't write it to the harddisk; you don't have a driver. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Tue Sep 12 05:18:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA04128 for current-outgoing; Tue, 12 Sep 1995 05:18:22 -0700 Received: (from gclarkii@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA04121 for current; Tue, 12 Sep 1995 05:18:21 -0700 From: Gary Clark II Message-Id: <199509121218.FAA04121@freefall.freebsd.org> Subject: libforms - thumbs up or down? To: current Date: Tue, 12 Sep 1995 05:18:21 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 504 Sender: current-owner@FreeBSD.org Precedence: bulk Well, if we are going on a `hunting' trip, lets kill of that poor info I brought in. We have a newer version in ports and I see no reason for both, either update or dump. GB P.S.: What was the outcome on Lynx??? In or Out? -- Gary Clark II (N5VMF) | FreeBSD support and service gclarkii@FreeBSD.ORG | mail info@gbdata.com for information FreeBSD FAQ at ftp.FreeBSD.ORG in ~pub/FreeBSD/FreeBSD-current/src/share/FAQ/Text/FreeBSD.FAQ From owner-freebsd-current Tue Sep 12 05:50:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA04675 for current-outgoing; Tue, 12 Sep 1995 05:50:43 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA04669 for ; Tue, 12 Sep 1995 05:50:41 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id NAA03349 for current@freefall.freebsd.org; Tue, 12 Sep 1995 13:50:35 +0100 From: Paul Richards Message-Id: <199509121250.NAA03349@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: current@freefall.freebsd.org Date: Tue, 12 Sep 1995 13:50:33 +0100 (BST) In-Reply-To: <199509120603.IAA28282@uriah.heep.sax.de> from "J Wunsch" at Sep 12, 95 08:03:46 am Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 665 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to J Wunsch who said > > As Nate Williams wrote: > > > > I argued for it's demise a long time ago, but Paul defended it's > > existance as something that was asked for and would be used. I still > > don't see a use for it *in the tree*, though I suppose one could use it. > > Find somebody to maintain it, and move it out to ports. I only wrote it in the first place because Jordan wanted something for a new all singing all dancing sysinstall. If he's not interested in it any more it can be ditched. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Tue Sep 12 05:58:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA04836 for current-outgoing; Tue, 12 Sep 1995 05:58:32 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA04828 ; Tue, 12 Sep 1995 05:58:31 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id FAA03347; Tue, 12 Sep 1995 05:58:28 -0700 To: Gary Clark II cc: current@freefall.freebsd.org Subject: Re: libforms - thumbs up or down? In-reply-to: Your message of "Tue, 12 Sep 1995 05:18:21 PDT." <199509121218.FAA04121@freefall.freebsd.org> Date: Tue, 12 Sep 1995 05:58:28 -0700 Message-ID: <3344.810910708@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > P.S.: What was the outcome on Lynx??? In or Out? Well, most everyone said `in' and my position is that I'm still waiting for your bmake port.. :-) Jordan From owner-freebsd-current Tue Sep 12 06:02:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA04995 for current-outgoing; Tue, 12 Sep 1995 06:02:43 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA04988 for ; Tue, 12 Sep 1995 06:02:41 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id GAA03402; Tue, 12 Sep 1995 06:02:37 -0700 To: paul@FreeBSD.org cc: current@freefall.freebsd.org Subject: Re: libforms - thumbs up or down? In-reply-to: Your message of "Tue, 12 Sep 1995 13:50:33 BST." <199509121250.NAA03349@server.netcraft.co.uk> Date: Tue, 12 Sep 1995 06:02:37 -0700 Message-ID: <3400.810910957@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > I only wrote it in the first place because Jordan wanted something > for a new all singing all dancing sysinstall. If he's not interested > in it any more it can be ditched. Well, interested in the concept but it seems like things are shifting away from our original plan enough at this point that libforms may very likely never come into play now. Let me give it one last look before I make my final determination on that, but don't also forget that it's presently sort of broken anyway.. :-( Jordan From owner-freebsd-current Tue Sep 12 06:07:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA05157 for current-outgoing; Tue, 12 Sep 1995 06:07:50 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA05148 for ; Tue, 12 Sep 1995 06:07:47 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id OAA03502; Tue, 12 Sep 1995 14:07:01 +0100 From: Paul Richards Message-Id: <199509121307.OAA03502@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 12 Sep 1995 14:07:01 +0100 (BST) Cc: paul@FreeBSD.org, current@freefall.freebsd.org In-Reply-To: <3400.810910957@time.cdrom.com> from "Jordan K. Hubbard" at Sep 12, 95 06:02:37 am Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 952 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > > I only wrote it in the first place because Jordan wanted something > > for a new all singing all dancing sysinstall. If he's not interested > > in it any more it can be ditched. > > Well, interested in the concept but it seems like things are shifting > away from our original plan enough at this point that libforms may > very likely never come into play now. Let me give it one last look > before I make my final determination on that, but don't also forget > that it's presently sort of broken anyway.. :-( Really, I don't care either way. I doubt it's very broken, probably just a single fix needed somewhere since it was working when I committed it, I'm just not interested in it at the moment, having more fun hacking virtual hosting environments. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Tue Sep 12 06:33:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA07085 for current-outgoing; Tue, 12 Sep 1995 06:33:06 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA07079 for ; Tue, 12 Sep 1995 06:33:04 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id JAA03707; for ; Tue, 12 Sep 1995 09:33:01 -0400 Date: Tue, 12 Sep 95 09:29:05 PDT From: "Ugen J.S.Antsilevich" Subject: DESPERATELY NEED HELP.... To: freebsd-current@FreeBSD.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Hmm..i hope this one got your attention... Well, so i'v got pretty strange problemm...i sup'ed -current, i "made world", rebooted and...Well, in process of boot random programms running from rc fail on either memory fault or bus error, then login starts but as soon as i type login and password it fails on same signal 11 as well...I am unable to log into system or to do anything. It still sorta works in single user mode, i can mount disks and even rerun make (it fails a couple of times on 10 and 11 though) but this is no use - i can't login...HEEEEEELP!!!!! I really would like to have working -curren...:( --Ugen From owner-freebsd-current Tue Sep 12 07:08:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA11972 for current-outgoing; Tue, 12 Sep 1995 07:08:01 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA11964 for ; Tue, 12 Sep 1995 07:07:56 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA30803; Tue, 12 Sep 1995 10:07:52 -0400 Date: Tue, 12 Sep 1995 10:07:52 -0400 From: "Garrett A. Wollman" Message-Id: <9509121407.AA30803@halloran-eldar.lcs.mit.edu> To: Paul Traina Cc: current@freebsd.org Subject: Re: userconfig doesn't work on tvi925 In-Reply-To: <199509120501.WAA12444@precipice.shockwave.com> References: <95Sep11.180329pdt.177475@crevenia.parc.xerox.com> <199509120501.WAA12444@precipice.shockwave.com> Sender: current-owner@freebsd.org Precedence: bulk < said: > Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a > sysctl interface There already is a sysctl interface; it's called devconf. There are some bits of glue that still need to be written, and the whole thing is badly in need of a redesign which I have been promising for a month now and may actually get to one of these weekends. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Sep 12 07:22:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA12233 for current-outgoing; Tue, 12 Sep 1995 07:22:58 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA12224 for ; Tue, 12 Sep 1995 07:22:56 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA30833; Tue, 12 Sep 1995 10:22:41 -0400 Date: Tue, 12 Sep 1995 10:22:41 -0400 From: "Garrett A. Wollman" Message-Id: <9509121422.AA30833@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: current@freefall.freebsd.org Subject: Re: Is nullfs broken in -current? In-Reply-To: <199509120114.SAA14593@phaeton.artisoft.com> References: <6410.810844646@palmer.demon.co.uk> <199509120114.SAA14593@phaeton.artisoft.com> Sender: current-owner@FreeBSD.org Precedence: bulk < said: >> AFAIK, nullfs has always been broken for `writing' - but I used it >> successfully on my machine here for over 2 months read only fine. I >> think that may be your problem... > Document an instance and a mount command line that would cause this to > be useful. > If I agree, and it doesn't just work on the Lite2 code, I'll fix it. # mount -t null -o union /dsk2/src1 /usr/src # mount -t null -o union /dsk3/src2 /usr/src # cd /usr/src # make world -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Sep 12 07:48:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA13315 for current-outgoing; Tue, 12 Sep 1995 07:48:04 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA13305 for ; Tue, 12 Sep 1995 07:48:01 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id KAA12257; for ; Tue, 12 Sep 1995 10:47:57 -0400 Date: Tue, 12 Sep 95 10:46:43 PDT From: "Ugen J.S.Antsilevich" Subject: HELP--second try.. To: freebsd-current@FreeBSD.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk OK..let's get it straight then.. Is there ANYBODY having -current running on his machine????? --Ugen From owner-freebsd-current Tue Sep 12 07:53:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA13501 for current-outgoing; Tue, 12 Sep 1995 07:53:46 -0700 Received: from greatdane.cisco.com (greatdane.cisco.com [171.69.1.141]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA13492 for ; Tue, 12 Sep 1995 07:53:42 -0700 Received: from [171.69.60.11] (halaee-mac.cisco.com [171.69.60.11]) by greatdane.cisco.com (8.6.8+c/8.6.5) with SMTP id HAA24757; Tue, 12 Sep 1995 07:53:07 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Sep 1995 07:54:40 -0700 To: "Ugen J.S.Antsilevich" , freebsd-current@FreeBSD.org From: rlfs@cisco.com (Ricky Li Fo Sjoe) Subject: Re: DESPERATELY NEED HELP.... Sender: current-owner@FreeBSD.org Precedence: bulk At 9:29 AM 9/12/95, Ugen J.S.Antsilevich wrote: >Hmm..i hope this one got your attention... > > Well, so i'v got pretty strange problemm...i sup'ed -current, i "made world", >rebooted and...Well, in process of boot random programms running from rc >fail on either memory fault or bus error, then login starts but as soon as i >type login and password it fails on same signal 11 as well...I am unable >to log >into system or to do anything. It still sorta works in single user mode, i can >mount disks and even rerun make (it fails a couple of times on 10 and 11 >though) but this is no use - i can't login...HEEEEEELP!!!!! I really would >like >to have working -curren...:( >--Ugen I witnesses similar problems last night. I downloaded, I thought, from 2.0.5-RELEASE to 2.0.5-950622-SNAP. I still see the sporadic Signal 11 error while trying to build a new kernel. Yesterday, I finally built a new kernel, under 2.0.5-RELEASE and tried to boot it. All my boot apps, even single-user mode, failed with 'error 14'. This is what forced me to do the reload. I've been told that 2.1-STABLE is supposed to be somewhat ok. Would I be better off going to this release? rlfs +===============================================+ | r.sjoe@ieee.org or rlfs@cisco.com | | Cisco Systems | | (408)526-8286 | +===============================================+ From owner-freebsd-current Tue Sep 12 08:20:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA14769 for current-outgoing; Tue, 12 Sep 1995 08:20:46 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA14761 for ; Tue, 12 Sep 1995 08:20:35 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id LAA13856; Tue, 12 Sep 1995 11:14:22 -0400 Date: Tue, 12 Sep 1995 11:14:21 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: DESPERATELY NEED HELP.... To: Ricky Li Fo Sjoe cc: "Ugen J.S.Antsilevich" , freebsd-current@FreeBSD.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Tue, 12 Sep 1995, Ricky Li Fo Sjoe wrote: > I've been told that 2.1-STABLE is supposed to be somewhat ok. Would I be > better off going to this release? Yes! -current is the leading bleeding edge....remember the life expectancy of an infantry man walking point in a combat zone is 6 seconds...run -stable. i upgraded to -stable the night before last, have done a make world and make install can a couple makes and all is well. Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Tue Sep 12 08:24:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA15060 for current-outgoing; Tue, 12 Sep 1995 08:24:44 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA14894 for ; Tue, 12 Sep 1995 08:21:51 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA28347 for ; Tue, 12 Sep 1995 17:21:26 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id RAA07643 for current@FreeBSD.org; Tue, 12 Sep 1995 17:21:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id OAA29278 for current@FreeBSD.org; Tue, 12 Sep 1995 14:13:46 +0200 From: J Wunsch Message-Id: <199509121213.OAA29278@uriah.heep.sax.de> Subject: Re: userconfig doesn't work on tvi925 To: current@FreeBSD.org Date: Tue, 12 Sep 1995 14:13:46 +0200 (MET DST) Reply-To: current@FreeBSD.org In-Reply-To: <199509120657.XAA04880@corbin.Root.COM> from "David Greenman" at Sep 11, 95 11:57:10 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 610 Sender: current-owner@FreeBSD.org Precedence: bulk As David Greenman wrote: > > I don't see the harm in making 'userconfig' a USERCONFIG kernel option, > however. In fact, it originally started out being an option, but everyone > seemed to agree that it was too useful to ever be without...so we made it > standard. This reminds me: is there any chance to get parts of the kernel pageable? (My current understanding is that a.out lacks the ability to carry additional sections that would be required for this.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Sep 12 08:40:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA15926 for current-outgoing; Tue, 12 Sep 1995 08:40:07 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA15918 for ; Tue, 12 Sep 1995 08:40:05 -0700 Received: from puffin.pelican.com by pelican.com with smtp (Smail3.1.28.1 #5) id m0ssXRJ-000K2lC; Tue, 12 Sep 95 08:40 WET DST Received: by puffin.pelican.com (Smail3.1.29.1 #9) id m0ssXRJ-0000RfC; Tue, 12 Sep 95 08:40 PDT Message-Id: From: pete@puffin.pelican.com (Pete Carah) Subject: PSM in 950726-SNAP To: current@freebsd.org Date: Tue, 12 Sep 1995 08:40:00 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 432 Sender: current-owner@freebsd.org Precedence: bulk I have a PS/2 mouse on an ASUS P55TP4/XE (with apparently-working pipeline-burst cache); if I move the mouse too fast (any time, not just during X operations) it locks the keyboard and mouse. As usual network logins work fine. (this with syscons) 1. Is there a way to unlock this without rebooting? 2. Do I have a hardware problem or is it a driver-interaction problem between syscons and psm0? Thanks in advance, -- Pete From owner-freebsd-current Tue Sep 12 08:49:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA16836 for current-outgoing; Tue, 12 Sep 1995 08:49:25 -0700 Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA16681 for ; Tue, 12 Sep 1995 08:47:14 -0700 Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.6.11/8.6.9) id RAA00295; Tue, 12 Sep 1995 17:01:21 +0200 From: "Christoph P. Kukulies" Message-Id: <199509121501.RAA00295@gilberto.physik.RWTH-Aachen.DE> Subject: Re: DESPERATELY NEED HELP.... To: ugen@latte.worldbank.org (Ugen J.S.Antsilevich) Date: Tue, 12 Sep 1995 17:01:20 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org In-Reply-To: from "Ugen J.S.Antsilevich" at Sep 12, 95 09:29:05 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1068 Sender: current-owner@FreeBSD.org Precedence: bulk > > Hmm..i hope this one got your attention... > > Well, so i'v got pretty strange problemm...i sup'ed -current, i "made world", > rebooted and...Well, in process of boot random programms running from rc > fail on either memory fault or bus error, then login starts but as soon as i > type login and password it fails on same signal 11 as well...I am unable to log > into system or to do anything. It still sorta works in single user mode, i can > mount disks and even rerun make (it fails a couple of times on 10 and 11 > though) but this is no use - i can't login...HEEEEEELP!!!!! I really would like > to have working -curren...:( > --Ugen Ugen, haven't you seen the thread of 'sig 11' ad nauseam in this list? Everyone is waiting for a stable -current these days while John Dyson is working hard to shake this out. If you want a working -current you have to be patient or contribute in reporting symptoms. If you want a stable system in general stick with 2.0.5-RELEASE or 950726-SNAP. > > --Chris Christoph P. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Tue Sep 12 09:45:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA19451 for current-outgoing; Tue, 12 Sep 1995 09:45:10 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA19439 for ; Tue, 12 Sep 1995 09:45:08 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id JAA05571; Tue, 12 Sep 1995 09:44:55 -0700 To: "Ugen J.S.Antsilevich" cc: freebsd-current@FreeBSD.org Subject: Re: HELP--second try.. In-reply-to: Your message of "Tue, 12 Sep 1995 10:46:43 PDT." Date: Tue, 12 Sep 1995 09:44:55 -0700 Message-ID: <5569.810924295@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk Yes, yes, Ugen. But we STILL DON'T HAVE AN ANSWER TO YOUR PROBLEM! I told you this two days ago and you still keep sending this "HELP! HELP!" stuff here! Run 2.1-stable or very possibly LOSE. That is the current state of life in -current! Yes, the problem is known about. No, we don't know when it will be fixed. Yes, the people working on it are tired of being asked! :-) Jordan From owner-freebsd-current Tue Sep 12 10:00:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA20023 for current-outgoing; Tue, 12 Sep 1995 10:00:44 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA20017 for ; Tue, 12 Sep 1995 10:00:41 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA03776; Tue, 12 Sep 1995 09:58:33 -0700 From: "Rodney W. Grimes" Message-Id: <199509121658.JAA03776@GndRsh.aac.dev.com> Subject: Re: Potentially serious NFS problem To: dfr@render.com (Doug Rabson) Date: Tue, 12 Sep 1995 09:58:33 -0700 (PDT) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: from "Doug Rabson" at Sep 12, 95 10:54:48 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1495 Sender: current-owner@freebsd.org Precedence: bulk > > On Mon, 11 Sep 1995, Terry Lambert wrote: > > > Doug, are you there? 8-). > > Still here :-) > > > I have detected a problem in the NFS server code, though at present I am > > not certain whether it will manifest as a memory leak or as a double > > freeing of cn_pnbuf's (which depends on what's meant by VOP_ABORTOP() > > when called in nfs/nfs_serv.c). > > > > ... > > > > I'm not prepared to crack this nut all by myself at present, especially > > with active work in the NFS code taking place. > > I am not currently working on the nfs code. I think that John is working > on the client code but not the server. Feel free to make changes to the > server side. While your in there poking around see if why when you kill -1 mountd on the server if a client is doing I/O at that time it causes an error to be returned and causes what ever was running to die. This is a sick bug, it makes FreeBSD unsutable for production NFS server applications as adding or removing or changing the /etc/exports file and hupping mountd is a quite standard procedure. client% tar cf /dev/null server:/foo/bar server% echo "/new/disk/area -root=0 host1 host2" >>/etc/exports server% kill -1 `cat /var/run/mountd.pid` client> BOOM!!!!, it use to panic, that has been fixed, now it returns an I/O error to the user land process :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 12 10:26:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA21850 for current-outgoing; Tue, 12 Sep 1995 10:26:34 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA21844 for ; Tue, 12 Sep 1995 10:26:32 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id NAA04154; for ; Tue, 12 Sep 1995 13:24:44 -0400 Date: Tue, 12 Sep 95 13:22:52 PDT From: "Ugen J.S.Antsilevich" Subject: Re: DESPERATELY NEED HELP.... To: "Christoph P. Kukulies" Cc: freebsd-current@FreeBSD.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk >Ugen, haven't you seen the thread of 'sig 11' ad nauseam in this list? Nope.. i guess i just was on something else..i'll try to get the old mails to see... >If you want a stable system in general stick with 2.0.5-RELEASE >or 950726-SNAP. Unfortunately :) i would like to do some work for FreeBSd so i 'l have to get current i guess.. --Ugen From owner-freebsd-current Tue Sep 12 10:27:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA21899 for current-outgoing; Tue, 12 Sep 1995 10:27:23 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA21891 for ; Tue, 12 Sep 1995 10:27:08 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA03990; Tue, 12 Sep 1995 10:26:55 -0700 From: "Rodney W. Grimes" Message-Id: <199509121726.KAA03990@GndRsh.aac.dev.com> Subject: Re: PSM in 950726-SNAP To: pete@puffin.pelican.com (Pete Carah) Date: Tue, 12 Sep 1995 10:26:55 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Pete Carah" at Sep 12, 95 08:40:00 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 635 Sender: current-owner@freebsd.org Precedence: bulk > > I have a PS/2 mouse on an ASUS P55TP4/XE (with apparently-working > pipeline-burst cache); if I move the mouse too fast (any time, not > just during X operations) it locks the keyboard and mouse. As usual > network logins work fine. (this with syscons) > > 1. Is there a way to unlock this without rebooting? Not that I know of :-(. > 2. Do I have a hardware problem or is it a driver-interaction problem > between syscons and psm0? It is an interaction problem. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 12 10:42:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA22166 for current-outgoing; Tue, 12 Sep 1995 10:42:15 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA22149 for ; Tue, 12 Sep 1995 10:42:13 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id KAA14390; Tue, 12 Sep 1995 10:40:31 -0700 Message-Id: <199509121740.KAA14390@precipice.shockwave.com> To: Michael Smith cc: davidg@Root.COM, current@FreeBSD.ORG, fenner@parc.xerox.com Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Tue, 12 Sep 1995 21:27:25 +0930." <199509121157.VAA21984@genesis.atrad.adelaide.edu.au> Date: Tue, 12 Sep 1995 10:40:30 -0700 From: Paul Traina Sender: current-owner@FreeBSD.ORG Precedence: bulk I don't call a newbie booting the kernel on non-conforming hardware an "emergency". I would certainly consider an utter newbie booting a kernel on a machine that doesn't have the FDC in the right location to be an "exception"... Wouldn't you? From owner-freebsd-current Tue Sep 12 11:05:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA22827 for current-outgoing; Tue, 12 Sep 1995 11:05:19 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA22821 for ; Tue, 12 Sep 1995 11:05:17 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA06673; Tue, 12 Sep 1995 12:07:15 -0600 Date: Tue, 12 Sep 1995 12:07:15 -0600 From: Nate Williams Message-Id: <199509121807.MAA06673@rocky.sri.MT.net> To: Paul Traina Cc: Michael Smith , davidg@Root.COM, current@FreeBSD.ORG, fenner@parc.xerox.com Subject: Re: userconfig doesn't work on tvi925 In-Reply-To: <199509121740.KAA14390@precipice.shockwave.com> References: <199509121157.VAA21984@genesis.atrad.adelaide.edu.au> <199509121740.KAA14390@precipice.shockwave.com> Sender: current-owner@FreeBSD.ORG Precedence: bulk > I don't call a newbie booting the kernel on non-conforming hardware an > "emergency". > > I would certainly consider an utter newbie booting a kernel on a machine > that doesn't have the FDC in the right location to be an > "exception"... Maybe not, but a newbie booting a kernel which has it's ethernet controller configured differently than our configuration is certainly an emergency. This arguement can be extended to talk about the non-SCSI CD controllers, or serial ports, or .... Nate From owner-freebsd-current Tue Sep 12 11:06:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23011 for current-outgoing; Tue, 12 Sep 1995 11:06:24 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA22995 for ; Tue, 12 Sep 1995 11:06:18 -0700 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA06203; Tue, 12 Sep 1995 14:06:00 -0400 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA04278; Tue, 12 Sep 95 14:03:19 EDT Date: Tue, 12 Sep 95 14:03:19 EDT From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9509121803.AA04278@borg.ess.harris.com> To: freebsd-current@FreeBSD.org, ugen@latte.worldbank.org Subject: Re: HELP--second try.. Sender: current-owner@FreeBSD.org Precedence: bulk Yes, I have been running a version of current since Hmmm, I think it was january 1993 when I first snagged a freebsd copy. I have a feeling there may be one or two others :-) :-) Jim Leppek > From owner-freebsd-current@freefall.freebsd.org Tue Sep 12 13:49:55 1995 > Date: Tue, 12 Sep 95 10:46:43 PDT > From: "Ugen J.S.Antsilevich" > Subject: HELP--second try.. > To: freebsd-current@FreeBSD.org > X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. > Mime-Version: 1.0 > Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> > Sender: current-owner@FreeBSD.org > > OK..let's get it straight then.. > Is there ANYBODY having -current running on his machine????? > --Ugen > > From owner-freebsd-current Tue Sep 12 11:32:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23584 for current-outgoing; Tue, 12 Sep 1995 11:32:02 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA23578 for ; Tue, 12 Sep 1995 11:31:59 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01164 for current@freebsd.org; Tue, 12 Sep 1995 11:31:19 -0700 From: Terry Lambert Message-Id: <199509121831.LAA01164@phaeton.artisoft.com> Subject: Statistics request To: current@freebsd.org Date: Tue, 12 Sep 1995 11:31:16 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 629 Sender: current-owner@freebsd.org Precedence: bulk I need the output of the following command from several FreeBSD machines that are running as NFS servers: vmstat -m | grep namei | grep -v UFS If you are running FreeBSD box as an NFS server, I would *greatly* appreciate this information. The output may look something like: namei 0 0K 4K 8892K 49283 0 0 1K ^ ^ I am *most* interested in non-0 values for the marked columns! If you don't send the information by the 14th, don't send it. 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-current Tue Sep 12 12:19:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA24648 for current-outgoing; Tue, 12 Sep 1995 12:19:21 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA24633 for ; Tue, 12 Sep 1995 12:19:18 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA04151; Tue, 12 Sep 1995 12:19:04 -0700 From: "Rodney W. Grimes" Message-Id: <199509121919.MAA04151@GndRsh.aac.dev.com> Subject: Re: Statistics request To: terry@lambert.org (Terry Lambert) Date: Tue, 12 Sep 1995 12:19:03 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199509121831.LAA01164@phaeton.artisoft.com> from "Terry Lambert" at Sep 12, 95 11:31:16 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1707 Sender: current-owner@freebsd.org Precedence: bulk > > I need the output of the following command from several FreeBSD machines > that are running as NFS servers: > > vmstat -m | grep namei | grep -v UFS > > If you are running FreeBSD box as an NFS server, I would *greatly* > appreciate this information. The output may look something like: > > namei 0 0K 4K 8892K 49283 0 0 1K > ^ ^ > > I am *most* interested in non-0 values for the marked columns! I just got this by doing a find from a client over 100Mb/s network and repeadly running your command on the client: namei 1 1K 6K 8873K 134819 0 0 16,32,64,1K namei 1 1K 6K 8873K 144778 0 0 16,32,64,1K namei 1 1K 6K 8873K 144813 0 0 16,32,64,1K namei 1 1K 6K 8873K 150365 0 0 16,32,64,1K namei 1 1K 6K 8873K 159415 0 0 16,32,64,1K namei 1 1K 6K 8873K 159967 0 0 16,32,64,1K Those are just spot selecting the non-0 ones... Now fire up 3 copies of find: namei 2 1K 6K 8873K 168480 0 0 16,32,64,1K namei 2 1K 6K 8873K 172299 0 0 16,32,64,1K namei 1 1K 6K 8873K 172415 0 0 16,32,64,1K > > If you don't send the information by the 14th, don't send it. 8-). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 12 13:44:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA26933 for current-outgoing; Tue, 12 Sep 1995 13:44:17 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA26925 for ; Tue, 12 Sep 1995 13:44:13 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02216; Tue, 12 Sep 1995 13:42:52 -0700 From: Terry Lambert Message-Id: <199509122042.NAA02216@phaeton.artisoft.com> Subject: Re: Statistics request To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 12 Sep 1995 13:42:51 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.org In-Reply-To: <199509121919.MAA04151@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 12, 95 12:19:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1297 Sender: current-owner@FreeBSD.org Precedence: bulk > Those are just spot selecting the non-0 ones... > > Now fire up 3 copies of find: > namei 2 1K 6K 8873K 168480 0 0 16,32,64,1K > namei 2 1K 6K 8873K 172299 0 0 16,32,64,1K > namei 1 1K 6K 8873K 172415 0 0 16,32,64,1K The question is whether it self-zero's. If it does, then care has been taken to doubly-break the buffer allocation code in nfs_namei(), which is what I'm trying to determine. I would expect that if this were the case, it would re-zero when idle. If it is only singly broken, I'd expect the number of buffers to increase and keep increasing, or to start freeing stuff that isn't allocated. I haven't determined what statistic free unallocated buffers would bump; unfortunately, I think it would be hidden in the noise on anything that could reproduce the error cases. Garrett has reported 0's in the idle case on his box. I will probably need to write some shell test cases to specifically exercise the bogus code. Anyone have any idea what statistic will show preterbation when I free a buffer twice? I'd like to watch that one too. 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-current Tue Sep 12 13:48:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA27368 for current-outgoing; Tue, 12 Sep 1995 13:48:24 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA27355 for ; Tue, 12 Sep 1995 13:48:20 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA20442 ; Tue, 12 Sep 1995 22:48:09 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA10375 ; Tue, 12 Sep 1995 22:48:08 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id WAA17935; Tue, 12 Sep 1995 22:14:53 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509122014.WAA17935@keltia.Freenix.FR> Subject: Re: Find *still* broken... To: terry@lambert.org (Terry Lambert) Date: Tue, 12 Sep 1995 22:14:52 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: <199509112047.NAA26687@phaeton.artisoft.com> from "Terry Lambert" at Sep 11, 95 01:47:00 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@freebsd.org Precedence: bulk It seems that Terry Lambert said: > Still produce diffrent output because find does not flush stdout > when doing a -print. Here is a fix: Index: function.c =================================================================== RCS file: /spare/FreeBSD-current/src/usr.bin/find/function.c,v retrieving revision 1.4 diff -u -2 -r1.4 function.c --- 1.4 1995/08/07 19:17:28 +++ function.c 1995/09/12 20:12:06 @@ -782,4 +782,5 @@ { (void)printf("%s\n", entry->fts_path); + (void)fflush(stdout); return (1); } -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Tue Sep 12 13:49:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA27483 for current-outgoing; Tue, 12 Sep 1995 13:49:06 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA27464 for ; Tue, 12 Sep 1995 13:48:57 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA20458 ; Tue, 12 Sep 1995 22:48:13 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA10387 ; Tue, 12 Sep 1995 22:48:12 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id WAA19124; Tue, 12 Sep 1995 22:20:38 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509122020.WAA19124@keltia.Freenix.FR> Subject: Re: Progress so far on the Sig-11 problem To: dyson@freefall.freebsd.org (John Dyson) Date: Tue, 12 Sep 1995 22:20:37 +0200 (MET DST) Cc: current@FreeBSD.org In-Reply-To: <199509110051.RAA00137@freefall.freebsd.org> from "John Dyson" at Sep 10, 95 05:51:33 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that John Dyson said: > I am having problems reproducing the problem. It takes quite-a-while to > get it to happen, and only appears when I am running in less than 8MB. I have 32 MB and while sed used to die at startup, now xconsole and xload die when I log with xdm. emacs die pretty often too. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Tue Sep 12 13:56:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA28063 for current-outgoing; Tue, 12 Sep 1995 13:56:07 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA28055 for ; Tue, 12 Sep 1995 13:56:05 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02265 for current@freebsd.org; Tue, 12 Sep 1995 13:55:26 -0700 From: Terry Lambert Message-Id: <199509122055.NAA02265@phaeton.artisoft.com> Subject: Re: userconfig doesn't work on tvi925 To: current@freebsd.org Date: Tue, 12 Sep 1995 13:55:26 -0700 (MST) In-Reply-To: <199509121213.OAA29278@uriah.heep.sax.de> from "J Wunsch" at Sep 12, 95 02:13:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2548 Sender: current-owner@freebsd.org Precedence: bulk > > I don't see the harm in making 'userconfig' a USERCONFIG kernel option, > > however. In fact, it originally started out being an option, but everyone > > seemed to agree that it was too useful to ever be without...so we made it > > standard. > > This reminds me: is there any chance to get parts of the kernel > pageable? > > (My current understanding is that a.out lacks the ability to carry > additional sections that would be required for this.) I think it's worse than that. One would expect that to be pageable, one would have to set the page descriptor explicitly, probably via #pragma when generating the code segements in the first place. This is what MSVC2.x does for VXD's in Win95. The programmer would then be responsible for not making as pageable any code that could execute from interrupt mode. One of the consequences of this (though it's not obvious) is that the spl/splx that allows malloc/free at interrupt level would need to go away. Pretty much, it's an abomination before God in any case. This implies an ability to schedule tasks to occur in regular processing once interrupt mode is exited. Basically, bifurcating the drivers into ISR's and soft handlers. This is both good and bad. It's good because it would make much of the kernel pageable. It's bad because of the GCC and ld hacks needed, and the restrictions that it imposes on usable driver architectures. For instance, writing a file system under Win95, you need to lock down many (most) of the pages for the FSD (File System Driver) because the plug-n-play manager can call back into routines at interrupt level, or at the very least, with paging disabled. It does this to support paging from the device itself (meaning anything in the page-in/page-out path must be locked down) and to support device change notifications so that a file system can act properly when a removable media is about to be ejected (a design flaw in the pnp module, IMO). One potential "benefit" would be the potential to, at some future date, support the use of VXD's, though this would require a kernel environment emulation several orders of magnitude more complex than that needed to support using, for instance, NetWare, UnixWare, Solaris, or SCO drivers. A better use of effort (again, IMO) would be to support the SCO, Solaris, and NetWare drivers, and if you get overambitious, NT (not Win95). Good luck decoding OMF. 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-current Tue Sep 12 14:01:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA28572 for current-outgoing; Tue, 12 Sep 1995 14:01:44 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA28563 for ; Tue, 12 Sep 1995 14:01:41 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA02293; Tue, 12 Sep 1995 13:59:16 -0700 From: Terry Lambert Message-Id: <199509122059.NAA02293@phaeton.artisoft.com> Subject: Re: Find *still* broken... To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 12 Sep 1995 13:59:15 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199509122014.WAA17935@keltia.Freenix.FR> from "Ollivier Robert" at Sep 12, 95 10:14:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 650 Sender: current-owner@freebsd.org Precedence: bulk > Here is a fix: > > Index: function.c > =================================================================== > RCS file: /spare/FreeBSD-current/src/usr.bin/find/function.c,v > retrieving revision 1.4 > diff -u -2 -r1.4 function.c > --- 1.4 1995/08/07 19:17:28 > +++ function.c 1995/09/12 20:12:06 > @@ -782,4 +782,5 @@ > { > (void)printf("%s\n", entry->fts_path); > + (void)fflush(stdout); > return (1); > } Any chance of getting this in the source tree, though? And f_print0 wants the same fix. 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-current Tue Sep 12 14:06:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA28940 for current-outgoing; Tue, 12 Sep 1995 14:06:07 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA28921 ; Tue, 12 Sep 1995 14:06:03 -0700 From: John Dyson Message-Id: <199509122106.OAA28921@freefall.freebsd.org> Subject: Re: Progress so far on the Sig-11 problem To: roberto@keltia.Freenix.FR (Ollivier Robert) Date: Tue, 12 Sep 1995 14:06:00 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199509122020.WAA19124@keltia.Freenix.FR> from "Ollivier Robert" at Sep 12, 95 10:20:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 838 Sender: current-owner@FreeBSD.org Precedence: bulk > > It seems that John Dyson said: > > I am having problems reproducing the problem. It takes quite-a-while to > > get it to happen, and only appears when I am running in less than 8MB. > > I have 32 MB and while sed used to die at startup, now xconsole and xload > die when I log with xdm. emacs die pretty often too. > > -- > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net > FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 > Well, I have come across something interesting :-). I can get -current to Sig-11, but my "-current" copy on freefall won't. It seems that changes were made that I had not tracked -- but the two versions (my freefall copy, and a new, fresh one) have IDENTICAL vm stuff (plus or minus prototyping changes, etc.) I am looking further.... John From owner-freebsd-current Tue Sep 12 14:12:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29509 for current-outgoing; Tue, 12 Sep 1995 14:12:00 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA29502 for ; Tue, 12 Sep 1995 14:11:53 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA07247; Tue, 12 Sep 1995 15:13:45 -0600 Date: Tue, 12 Sep 1995 15:13:45 -0600 From: Nate Williams Message-Id: <199509122113.PAA07247@rocky.sri.MT.net> To: Ollivier Robert Cc: terry@lambert.org (Terry Lambert), current@freebsd.org Subject: Re: Find *still* broken... In-Reply-To: <199509122014.WAA17935@keltia.Freenix.FR> References: <199509112047.NAA26687@phaeton.artisoft.com> <199509122014.WAA17935@keltia.Freenix.FR> Sender: current-owner@freebsd.org Precedence: bulk Ollivier Robert writes: > It seems that Terry Lambert said: > > Still produce diffrent output because find does not flush stdout > > when doing a -print. > > Here is a fix: Thanks, applied. Nate From owner-freebsd-current Tue Sep 12 14:17:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29830 for current-outgoing; Tue, 12 Sep 1995 14:17:54 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA29824 for ; Tue, 12 Sep 1995 14:17:49 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA07274; Tue, 12 Sep 1995 15:19:39 -0600 Date: Tue, 12 Sep 1995 15:19:39 -0600 From: Nate Williams Message-Id: <199509122119.PAA07274@rocky.sri.MT.net> To: Terry Lambert Cc: roberto@keltia.freenix.fr (Ollivier Robert), current@freebsd.org Subject: Re: Find *still* broken... In-Reply-To: <199509122059.NAA02293@phaeton.artisoft.com> References: <199509122014.WAA17935@keltia.Freenix.FR> <199509122059.NAA02293@phaeton.artisoft.com> Sender: current-owner@freebsd.org Precedence: bulk [ Find -print didn't flush stdout ] > > Any chance of getting this in the source tree, though? > > And f_print0 wants the same fix. 8-). Both are in the tree now. Thanks! Nate From owner-freebsd-current Tue Sep 12 14:33:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA00941 for current-outgoing; Tue, 12 Sep 1995 14:33:06 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA00933 for ; Tue, 12 Sep 1995 14:33:04 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id RAA21489 for current@freebsd.org; Tue, 12 Sep 1995 17:37:16 -0400 From: Mark Hittinger Message-Id: <199509122137.RAA21489@ns1.win.net> Subject: Re: Progress so far on the Sig-11 problem (fwd) To: current@freebsd.org Date: Tue, 12 Sep 1995 17:37:16 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1889 Sender: current-owner@freebsd.org Precedence: bulk > > > > It seems that John Dyson said: > > > I am having problems reproducing the problem. It takes quite-a-while to > > > get it to happen, and only appears when I am running in less than 8MB. > > > > I have 32 MB and while sed used to die at startup, now xconsole and xload > > die when I log with xdm. emacs die pretty often too. > > > Well, I have come across something interesting :-). I can get -current > to Sig-11, but my "-current" copy on freefall won't. It seems that > changes were made that I had not tracked -- but the two versions > (my freefall copy, and a new, fresh one) have IDENTICAL vm stuff (plus > or minus prototyping changes, etc.) I am looking further.... > I'm playing with this also. Thanks to John for working on it. I got the problem to go away last week with a make world, but today's make world has brought the problem back. I am beginning to suspect that the problem is related to the way the system boots, or the order that the boot happens. The box that sig 11's has the older rc setup without the sysconfig. If I manually start things without the automatic rc I can get the system to sort of run ok. If I do the automatic startup then you can't even log in. I did the shared library ldconfig last. Hopefully I am not on another wild goose chase, but it looks like the sequence of bootstrap operations, and the kinds of things which are done have some effect on the sig 11 issue. *BTW this is a box that has the dma problem and must use bounce buffers* Could the clustering be broken on a box that needs bounce buffers? How about a wrap around condition at the boundary? (Just blue skying here) When I play with the order of starting things the sig 11's do not occur. I'm posting this in the hopes that it might give John that magic "oh yeah!!". I will play with this some more tommorrow. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Tue Sep 12 14:36:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA01405 for current-outgoing; Tue, 12 Sep 1995 14:36:09 -0700 Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA01346 for ; Tue, 12 Sep 1995 14:35:50 -0700 Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.144.4]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id XAA06455 for ; Tue, 12 Sep 1995 23:24:59 +0200 From: Wolfram Schneider Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.12/8.6.9) id XAA08914; Tue, 12 Sep 1995 23:24:54 +0200 Date: Tue, 12 Sep 1995 23:24:54 +0200 Message-Id: <199509122124.XAA08914@caramba.cs.tu-berlin.de> To: current@freebsd.org Subject: /usr/libexec/locate.* MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: current-owner@freebsd.org Precedence: bulk o locate.bigram.c Bigram does not remove newline at end of filename. This break particulary the bigram algorithm and /var/db/locate.database grow up 15 %. It's really a bug!!! The bigram output is silly and need ~1/2 CPU time of database rebuilding. old: locate.bigram < $filelist | sort | uniq -c | sort -T /$TMPDIR -nr ^^^^^^^^^^^^^^ this can easy made bigram new: locate.bigram < $filelist | sort -T /$TMPDIR -nr o locate.code.c Use a lookup array instead a function. 3 x faster (GNU-code is now 6 x slower) o local.updatedb.csh # search locally or everything # find ${SRCHPATHS} -print | \ find ${SRCHPATHS} \! -fstype local -prune -or -print | \ tr '/' '\001' | \ ^^^^^^^^^^^^^^^^^^ Superfluously. Nobody need it. (sort -T $TMPDIR -f; echo $status > $errs) | tr '\001' '/' > $filelist ^^ wrong, made database 0.5% bigger ^^^^^^^^^^^^^^^^^^^^^^^^ Superfluously, see above. It double the disk space for filenames. The filenames are in a temp sort file and at the same time in $filelist. sort -T $TMPDIR -o $filelist avoid this by renaming temp sort file to $filelist. My database is 115MB big ... $LIBDIR/locate.bigram < $filelist | \ (sort -T /$TMPDIR; echo $status >> $errs) | uniq -c | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ see locate.bigram.c --- /usr/src/usr.bin/locate/bigram/locate.bigram.c Fri May 27 14:32:02 1994 +++ locate.bigram.c Tue Sep 12 14:24:56 1995 @@ -53,32 +53,51 @@ #include #include /* for MAXPATHLEN */ +#include /* memchr */ -char buf1[MAXPATHLEN] = " "; -char buf2[MAXPATHLEN]; +u_char buf1[MAXPATHLEN] = " "; +u_char buf2[MAXPATHLEN]; +unsigned int bigram[UCHAR_MAX][UCHAR_MAX]; -main ( ) + +void main ( ) { - register char *cp; - register char *oldpath = buf1, *path = buf2; + register u_char *cp; + register u_char *oldpath = buf1, *path = buf2; + register int i, j; + + /* init bigram buffer */ + for (i = 0; i < UCHAR_MAX; i++) + for (j = 0; j < UCHAR_MAX; j++) + bigram[i][j] = 0; while ( fgets ( path, sizeof(buf2), stdin ) != NULL ) { + /* chop newline */ + if ((cp = memchr(path, '\n', sizeof(buf2))) != NULL) + *cp = NULL; + /* skip longest common prefix */ - for ( cp = path; *cp == *oldpath; cp++, oldpath++ ) - if ( *oldpath == NULL ) - break; + for (cp = path; (*cp == *oldpath) != NULL; cp++, oldpath++); + /* * output post-residue bigrams only */ + while ( *cp != NULL && *(cp + 1) != NULL ) { - putchar ( *cp++ ); - putchar ( *cp++ ); - putchar ( '\n' ); + bigram[*cp][*(cp+1)]++; + cp += 2; } + if ( path == buf1 ) /* swap pointers */ path = buf2, oldpath = buf1; else path = buf1, oldpath = buf2; } + + /* output */ + for (i = 0; i < UCHAR_MAX; i++) + for (j = 0; j < UCHAR_MAX; j++) + if (bigram[i][j] != 0) + fprintf(stdout, "%4d %c%c\n", bigram[i][j], i, j); } --- 1.1 1995/09/12 16:40:45 +++ locate.code.c 1995/09/12 18:07:57 @@ -93,8 +93,20 @@ char buf2[MAXPATHLEN]; char bigrams[BGBUFSIZE + 1] = { 0 }; +#if 1 +#define BGINDEX(x) (big[(int)*x][(int)*(x+1)]) +typedef u_char bg_t; +bg_t big[UCHAR_MAX][UCHAR_MAX]; + +#else +#define BGINDEX(x) bgindex(x) +typedef int bg_t; +#endif + int bgindex __P((char *)); void usage __P((void)); +extern int optind; +extern int optopt; int main(argc, argv) @@ -104,6 +116,7 @@ register char *cp, *oldpath, *path; int ch, code, count, diffcount, oldcount; FILE *fp; + register int i, j; while ((ch = getopt(argc, argv, "")) != EOF) switch(ch) { @@ -126,14 +139,22 @@ err(1, "stdout"); (void)fclose(fp); + /* init lookup table */ + for (i = 0; i < UCHAR_MAX; i++) + for (j = 0; j < UCHAR_MAX; j++) + big[i][j] = (bg_t)-1; + + for (cp = bigrams, i = 0; *cp != NULL; i += 2, cp += 2) + big[(int)*cp][(int)*(cp + 1)] = (bg_t)i; + oldpath = buf1; path = buf2; oldcount = 0; while (fgets(path, sizeof(buf2), stdin) != NULL) { - /* Truncate newline. */ - cp = path + strlen(path) - 1; - if (cp > path && *cp == '\n') - *cp = '\0'; + + /* chop newline */ + if ((cp = memchr(path, '\n', sizeof(buf2))) != NULL) + *cp = NULL; /* Squelch characters that would botch the decoding. */ for (cp = path; *cp != NULL; cp++) { @@ -144,9 +165,9 @@ } /* Skip longest common prefix. */ - for (cp = path; *cp == *oldpath; cp++, oldpath++) - if (*oldpath == NULL) - break; + for (cp = path; (*cp == *oldpath) != NULL; cp++, oldpath++) + ; + count = cp - path; diffcount = count - oldcount + OFFSET; oldcount = count; @@ -164,7 +185,7 @@ err(1, "stdout"); break; } - if ((code = bgindex(cp)) < 0) { + if ((code = BGINDEX(cp)) == (bg_t)-1) { if (putchar(*cp++) == EOF || putchar(*cp++) == EOF) err(1, "stdout"); --- /usr/libexec/locate.updatedb.old Sun Jan 1 05:36:58 1995 +++ /usr/libexec/locate.updatedb Tue Sep 12 14:33:32 1995 @@ -58,12 +58,10 @@ # search locally or everything # find ${SRCHPATHS} -print | \ find ${SRCHPATHS} \! -fstype local -prune -or -print | \ - tr '/' '\001' | \ - (sort -T $TMPDIR -f; echo $status > $errs) | tr '\001' '/' > $filelist + sort -T $TMPDIR -o $filelist; echo $status > $errs -$LIBDIR/locate.bigram < $filelist | \ - (sort -T /$TMPDIR; echo $status >> $errs) | \ - uniq -c | sort -T /$TMPDIR -nr | \ +$LIBDIR/locate.bigram.new < $filelist | \ + sort -T $TMPDIR -nr | \ awk '{ if (NR <= 128) print $2 }' | tr -d '\012' > $bigrams # code the file list From owner-freebsd-current Tue Sep 12 14:38:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA01759 for current-outgoing; Tue, 12 Sep 1995 14:38:58 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA01750 for current@freebsd.org; Tue, 12 Sep 1995 14:38:57 -0700 Date: Tue, 12 Sep 1995 14:38:57 -0700 From: John Dyson Message-Id: <199509122138.OAA01750@freefall.freebsd.org> To: current@freebsd.org Subject: To those using -current w/Sig-11 Sender: current-owner@freebsd.org Precedence: bulk Try the exception.s in my home dir on freefall. ~dyson/exception.s. It is an older version and *might* clear up the problem... John dyson@freebsd.org From owner-freebsd-current Tue Sep 12 14:39:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA01871 for current-outgoing; Tue, 12 Sep 1995 14:39:40 -0700 Received: (from hsu@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA01860 ; Tue, 12 Sep 1995 14:39:38 -0700 Date: Tue, 12 Sep 1995 14:39:38 -0700 From: Jeffrey Hsu Message-Id: <199509122139.OAA01860@freefall.freebsd.org> To: nate@rocky.sri.MT.net, terry@lambert.org Subject: Re: Find *still* broken... Cc: current@freebsd.org, roberto@keltia.freenix.fr Sender: current-owner@freebsd.org Precedence: bulk The applied patch flushes stdout on every print, even if the output is to a pipe. I believe the correct patch is *** /usr/src/usr.bin/find/function.c.0 Sat Oct 23 14:34:03 1993 --- /usr/src/usr.bin/find/function.c Mon Jan 24 20:13:25 1994 *************** *** 240,245 **** --- 240,248 ---- if (plan->flags == F_NEEDOK && !queryuser(plan->e_argv)) return (0); + /* make sure find output is interspersed correctly with subprocesses */ + fflush(stdout); + switch (pid = vfork()) { case -1: err(1, "fork"); From owner-freebsd-current Tue Sep 12 14:45:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA02232 for current-outgoing; Tue, 12 Sep 1995 14:45:04 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA02218 for ; Tue, 12 Sep 1995 14:44:59 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA07444; Tue, 12 Sep 1995 15:47:08 -0600 Date: Tue, 12 Sep 1995 15:47:08 -0600 From: Nate Williams Message-Id: <199509122147.PAA07444@rocky.sri.MT.net> To: Jeffrey Hsu Cc: nate@rocky.sri.MT.net, current@freebsd.org Subject: Re: Find *still* broken... In-Reply-To: <199509122139.OAA01860@freefall.freebsd.org> References: <199509122139.OAA01860@freefall.freebsd.org> Sender: current-owner@freebsd.org Precedence: bulk > The applied patch flushes stdout on every print, even if the output is to a > pipe. I believe the correct patch is .... Sigh, I was just trying to be helpful. How about you go fix the mess I made and patch function.c correctly? Nate From owner-freebsd-current Tue Sep 12 15:20:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA04920 for current-outgoing; Tue, 12 Sep 1995 15:20:51 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA04901 for ; Tue, 12 Sep 1995 15:20:45 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id IAA23106; Wed, 13 Sep 1995 08:02:21 +0930 From: Michael Smith Message-Id: <199509122232.IAA23106@genesis.atrad.adelaide.edu.au> Subject: Re: userconfig doesn't work on tvi925 To: pst@shockwave.com (Paul Traina) Date: Wed, 13 Sep 1995 08:02:21 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, davidg@Root.COM, current@FreeBSD.ORG, fenner@parc.xerox.com In-Reply-To: <199509121740.KAA14390@precipice.shockwave.com> from "Paul Traina" at Sep 12, 95 10:40:30 am Content-Type: text Content-Length: 1012 Sender: current-owner@FreeBSD.ORG Precedence: bulk Paul Traina stands accused of saying: > > I don't call a newbie booting the kernel on non-conforming hardware an > "emergency". > > I would certainly consider an utter newbie booting a kernel on a machine > that doesn't have the FDC in the right location to be an "exception"... I don't follow you : You say that userconfig should only be used in an emergency. I point out that it's _required_ if one is to be able to install on hardware that isn't configured to exactly match the distribution kernel. I think you're still flogging your floppy/console only boot concept, which has already been dismissed as impractical. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Tue Sep 12 15:49:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA06160 for current-outgoing; Tue, 12 Sep 1995 15:49:17 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA06149 for ; Tue, 12 Sep 1995 15:49:09 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id PAA04509; Tue, 12 Sep 1995 15:48:47 -0700 From: "Rodney W. Grimes" Message-Id: <199509122248.PAA04509@GndRsh.aac.dev.com> Subject: Re: Statistics request To: terry@lambert.org (Terry Lambert) Date: Tue, 12 Sep 1995 15:48:46 -0700 (PDT) Cc: terry@lambert.org, current@FreeBSD.org In-Reply-To: <199509122042.NAA02216@phaeton.artisoft.com> from "Terry Lambert" at Sep 12, 95 01:42:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1973 Sender: current-owner@FreeBSD.org Precedence: bulk > > > Those are just spot selecting the non-0 ones... > > > > Now fire up 3 copies of find: > > namei 2 1K 6K 8873K 168480 0 0 16,32,64,1K > > namei 2 1K 6K 8873K 172299 0 0 16,32,64,1K > > namei 1 1K 6K 8873K 172415 0 0 16,32,64,1K > > The question is whether it self-zero's. If it does, then care has been > taken to doubly-break the buffer allocation code in nfs_namei(), which > is what I'm trying to determine. Note, I am running this on both client and server (infact every place but the test bed right now is running this:) FreeBSD GndRsh.aac.dev.com 2.1-STABLE FreeBSD 2.1-STABLE #1: Thu Sep 7 06:45:10 1995 root@burn4.aac.dev.com:/usr/src/sys/compile/GNDRSH i386 > > I would expect that if this were the case, it would re-zero when idle. While doing repeated captures to even get the above data most of the time it reported 0. It hits the 2 or 1 about 1 in 20 hits of vmstat, this is not a great way to collect data :-) > If it is only singly broken, I'd expect the number of buffers to increase > and keep increasing, or to start freeing stuff that isn't allocated. > > I haven't determined what statistic free unallocated buffers would bump; > unfortunately, I think it would be hidden in the noise on anything that > could reproduce the error cases. > > Garrett has reported 0's in the idle case on his box. > > I will probably need to write some shell test cases to specifically > exercise the bogus code. > > Anyone have any idea what statistic will show preterbation when I free > a buffer twice? I'd like to watch that one too. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 12 16:19:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA12356 for current-outgoing; Tue, 12 Sep 1995 16:19:35 -0700 Received: from maui.com (langfod@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA12350 for ; Tue, 12 Sep 1995 16:19:33 -0700 Received: (from langfod@localhost) by maui.com (8.6.10/8.6.6) id NAA10302 for current@freebsd.org; Tue, 12 Sep 1995 13:23:08 -1000 From: David Langford Message-Id: <199509122323.NAA10302@ maui.com> Subject: Major problem with IDE hard drive and current To: current@freebsd.org Date: Tue, 12 Sep 1995 13:23:07 -1000 (HST) X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 774 Sender: current-owner@freebsd.org Precedence: bulk It seems that the last few kernels I have made on my machine using current cannot find my IDE controller. wdc0 at 0x170 not found wdc1 at 0x1F0 not found I have tried compiling the "GENERIC" conf file and remaking another conf file from LINT (after stripping all unneeded stuff) but I get the same error. Oh, and yes I do have FFS enabled :) My kernel from July 29 works fine, however. Also how does one probe a device inside the new kernel "-c" thing. Thanks. -- /--------------------------------------------------------------------\ | David Langford - Kihei, Maui, Hawaii - langfod@maui.com | | Maui Research and Technology Center -- Network Administrator | \--------------------------------------------------------------------/ From owner-freebsd-current Tue Sep 12 16:36:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13899 for current-outgoing; Tue, 12 Sep 1995 16:36:46 -0700 Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13887 for ; Tue, 12 Sep 1995 16:36:42 -0700 Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id TAA22414; Tue, 12 Sep 1995 19:35:55 -0400 From: John Capo Message-Id: <199509122335.TAA22414@irbs.irbs.com> Subject: Re: To those using -current w/Sig-11 To: dyson@freefall.freebsd.org (John Dyson) Date: Tue, 12 Sep 1995 19:35:54 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199509122138.OAA01750@freefall.freebsd.org> from "John Dyson" at Sep 12, 95 02:38:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 280 Sender: current-owner@freebsd.org Precedence: bulk John Dyson writes: > > > Try the exception.s in my home dir on freefall. ~dyson/exception.s. > It is an older version and *might* clear up the problem... > Please put it in a public directory for those of those that don't have freefall accounts. John Capo IRBS Engineering From owner-freebsd-current Tue Sep 12 17:03:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA15703 for current-outgoing; Tue, 12 Sep 1995 17:03:37 -0700 Received: from mozart.american.com (mozart.american.com [204.253.96.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA15697 for ; Tue, 12 Sep 1995 17:03:36 -0700 Received: from localhost (localhost [127.0.0.1]) by mozart.american.com (8.6.12/8.6.9) with SMTP id UAA11780 for ; Tue, 12 Sep 1995 20:03:05 -0400 Message-Id: <199509130003.UAA11780@mozart.american.com> X-Authentication-Warning: mozart.american.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.5.3 12/28/94 To: current@freebsd.org Subject: more ATAPI CD issues Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Sep 1995 20:03:04 -0400 From: Josh Littlefield Sender: current-owner@freebsd.org Precedence: bulk I've stuck the -current atapi support into a stock 2.0.5 kernel, and believe I've done it correctly. I've discovered some problems with the atapi code I'd like let people know about. First, I'm running ONLY a CD ATAPI device, no hard disk. I know others have had their own issues with this, but mine seem to be different. My CD is a Sony CDU-55E. First, the current layering of wd.c is obviously not well suited to this configuration. Your ATAPI controller has to react a certain way to particular ATA commands to get to the point of being probed at all as an ATAPI CD. The 3 trials of ATA you must pass are 1) writable byte count / cyl. address registers, 2) successful wdreset(), and 3) successful WDCC_DIAGNOSE behavior. The first test is reasonable, for what its worth. My ATAPI CD fails the current implementation of wdreset(), although the ATAPI spec is pretty specific about how this should be handled and the code looks potentially correct. I need to trace this down more. I get through the WDCC_DIAGNOSE test OK. So, by ignoring wdreset() failure in the wdc probe, I can get my device recognized. At that point the atapi_probe/atapi_attach work just fine and identify the device. The next issue is with the MODE_SENSE issued by the wcd code. It asks for the CDROM Capabilites page (0x2A). It expects this in a 24 byte struct and asks for 24 bytes. However, my ATAPI spec indicates that this page is 28 bytes long, and that's also what my device tries to send. The atapi.c code considers this an overrun (although the device indicates no errors) and leaves the data on the table. By defining the last 4 bytes in the capabilities struct, giving me a 28 byte struct, I succeed with the MODE_SENSE and get valid information. I have a couple of issues/questions with this. First, wcd.c seems to be using too small a struct for this MODE_SENSE command. Perhaps this is version skew on the ATAPI spec? Second, the spec indicates that since a host doesn't know how much data will be returned with a MODE_SENSE, it should rely on the byte count registers from the device. This is probably referring to a request for ALL pages, which returns an unpredictable amount of data. However the spec says that, in general, the host should divert to the bit bucket any excess data offered by the device (and send pad bytes when the device asks for more than is required). Seems like atapi_io() should be less sensitive to overrun/underrun. Finally, even if we consider the byte count in error, it does no good to leave the data there. It would think it better to transfer the data to the bit bucket to finish the command, returning an error. My current (final?) problem is that the TEST_UNIT_READY command issued during wcd driver open never seems to generate an interrupt. I haven't solved this one yet, but it may be related to the state of the IEN bit in wd_ctrl at the end of wdreset(), since this is the first opportunity for the device to interrupt. Which reminds me that the infinite sleeps in atapi.c are less than ideal. BTW, the spec I refer to is the ATAPI for CD-ROMs spec, rev. 2.5 8/10/95. It's marked as "Status: Review Copy" so I guess some parts are in flux. But I figured its accurate for basic information. I believe there was an earlier version as well where I got this, but it was 8MB and this one was 3MB. I found it through the magic of the Internet at ftp://fission.dt.wdc.com/pub/stan dards/atapi/. -josh ======================================================================== Josh Littlefield American Internet Corporation josh@american.com 4 Preston Court tel: 617-271-9200 fax: 617-275-4930 Bedford, MA 01730-2334 From owner-freebsd-current Tue Sep 12 18:00:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA19124 for current-outgoing; Tue, 12 Sep 1995 18:00:13 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA19116 for ; Tue, 12 Sep 1995 18:00:12 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id RAA10199; Tue, 12 Sep 1995 17:59:01 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id SAA00136; Tue, 12 Sep 1995 18:01:15 -0700 Message-Id: <199509130101.SAA00136@corbin.Root.COM> To: "Rodney W. Grimes" cc: terry@lambert.org, current@freebsd.org Subject: Re: Potentially serious NFS problem In-reply-to: Your message of "Tue, 12 Sep 95 09:58:33 PDT." <199509121658.JAA03776@GndRsh.aac.dev.com> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 12 Sep 1995 18:01:14 -0700 Sender: current-owner@freebsd.org Precedence: bulk >While your in there poking around see if why when you kill -1 mountd >on the server if a client is doing I/O at that time it causes an >error to be returned and causes what ever was running to die. > >This is a sick bug, it makes FreeBSD unsutable for production NFS >server applications as adding or removing or changing the /etc/exports >file and hupping mountd is a quite standard procedure. It's caused by the need to replace the kernel export list whenever a change is made to the exports file. While the kernel export list is being rebuilt, there is a window where NFS I/O will fail if the appropriate entry hasn't yet been restored. I think the main reason the code is written this way has to do with the way the table is ordered, but I may be mistaken. It's a design flaw that might not be easily fixed. I've known about this for about 6 months, but I seem to never get enough of a break to do anything about it. -DG From owner-freebsd-current Tue Sep 12 20:54:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA03871 for current-outgoing; Tue, 12 Sep 1995 20:54:13 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA03863 ; Tue, 12 Sep 1995 20:54:10 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id UAA00717; Tue, 12 Sep 1995 20:54:06 -0700 Date: Tue, 12 Sep 1995 20:54:06 -0700 Message-Id: <199509130354.UAA00717@silvia.HIP.Berkeley.EDU> To: dyson@freebsd.org CC: current@freebsd.org In-reply-to: <199509122138.OAA01750@freefall.freebsd.org> (dyson) Subject: Re: To those using -current w/Sig-11 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: current-owner@freebsd.org Precedence: bulk * Try the exception.s in my home dir on freefall. ~dyson/exception.s. * It is an older version and *might* clear up the problem... Still the same. Everything except exception.s from yesterday's -current, 32MB, most X clients aborting. Satoshi From owner-freebsd-current Tue Sep 12 21:17:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA05597 for current-outgoing; Tue, 12 Sep 1995 21:17:23 -0700 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA05584 ; Tue, 12 Sep 1995 21:17:21 -0700 From: John Dyson Message-Id: <199509130417.VAA05584@freefall.freebsd.org> Subject: Re: To those using -current w/Sig-11 To: jc@irbs.com (John Capo) Date: Tue, 12 Sep 1995 21:17:20 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199509122335.TAA22414@irbs.irbs.com> from "John Capo" at Sep 12, 95 07:35:54 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 576 Sender: current-owner@freebsd.org Precedence: bulk > > John Dyson writes: > > > > > > Try the exception.s in my home dir on freefall. ~dyson/exception.s. > > It is an older version and *might* clear up the problem... > > > > Please put it in a public directory for those of those that don't > have freefall accounts. > > John Capo > IRBS Engineering > > I apologize for being rude.. It appears that it does not fix the problem for at least one person. If you want (and that includes anyone), I'll email the older exception.s to you, but it probably will not fix your problem :-(. Still working!!!! dyson@root.com From owner-freebsd-current Tue Sep 12 21:24:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA06215 for current-outgoing; Tue, 12 Sep 1995 21:24:12 -0700 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA06206 for ; Tue, 12 Sep 1995 21:24:11 -0700 Received: from ast.com by relay1.UU.NET with SMTP id QQzgyr08415; Wed, 13 Sep 1995 00:24:23 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA17245 (5.67b/IDA-1.5 for ); Tue, 12 Sep 1995 21:03:35 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Tue, 12 Sep 95 23:03 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0ssixX-0004w2C; Tue, 12 Sep 95 22:58 CDT Message-Id: Date: Tue, 12 Sep 95 22:58 CDT To: current@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Tue Sep 12 1995, 22:58:03 CDT Subject: Can you get xcdplayer to play last track? Sender: current-owner@freebsd.org Precedence: bulk Has anybody noticed a problem with xcdplayer 2.20 (from 2.0.5 CD) where it won't play the last track on an audio CD? For example, I will insert a disc I know has 13 tracks. Cdplayer will play track 13, including falling into track 13 by doing a "play 12-13". The "tocentries" command shows 13 tracks, plus the lead-out track. But get into xcdplayer and it will play tracks 1-12 and then stop. If you press STOP and then NEXT TRACK (the icons) until the display reads "13", then press PLAY, xcdplayer will act like it be working for a second, then xcdplayer goes to the stopped state. No audio is heard. I can't use xcd for a third opinion because it wants a missing module. (Possible bug in packages/ports?) I know it isn't the disc and the problem happens on every multi-track CD I have. I can't find a disc I own that has a single audio track, but I suspect xcdplayer would not play any of it. A two-track CD ("1. this side" and "2. the other side") I could find can only play track 1 with xcdplayer. If you are able to play the last track on a CD, please let me know what model of drive you have, and what type of drive interface it has (SCSI, IDE, MITSUMI, PANASONIC, SONY, etc). Hopefully this will let me figure out where the problem is. Also, does anybody knows how to make xcdplayer play the disc as a complete disc (linear), rather than playing track 1, stopping, playing track 2, stopping, playing track 3, stopping, etc? This gets pretty annoying on CDs that bump the track number between movements but audio is still present, such as between tracks 1 & 2 of Sgt. Peppers Lonely Hearts Club Band, and probably every ELO, Firesign Theatre and live concert disc out there. If there is no way to do this, I'll look into fixing xcdplayer. The hardware supports doing it. Thanks. Frank Durda IV uhclem%nemesis@fw.ast.com From owner-freebsd-current Tue Sep 12 21:41:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA07288 for current-outgoing; Tue, 12 Sep 1995 21:41:01 -0700 Received: from mailhub.cts.com (root@mailhub.cts.com [192.188.72.25]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id VAA07280 ; Tue, 12 Sep 1995 21:40:57 -0700 Received: from io.cts.com by mailhub.cts.com with smtp (Smail3.1.29.1 #19) id m0ssjcb-000V2CC; Tue, 12 Sep 95 21:40 PDT Received: (from root@localhost) by io.cts.com (8.6.12/8.6.9) id VAA17725; Tue, 12 Sep 1995 21:40:59 -0700 From: Morgan Davis Message-Id: <199509130440.VAA17725@io.cts.com> Subject: Re: Major problem with IDE hard drive and current To: freebsd-current@FreeBSD.org Date: Tue, 12 Sep 1995 21:40:59 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199509122323.NAA10302@ maui.com> from "David Langford" at Sep 12, 95 01:23:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 452 Sender: current-owner@FreeBSD.org Precedence: bulk David Langford writes: > > > It seems that the last few kernels I have made on my machine using current > cannot find my IDE controller. > > wdc0 at 0x170 not found > wdc1 at 0x1F0 not found > > My kernel from July 29 works fine, however. This is likely related to a similar problem I reported a couple of weeks ago. The fix involves masking out an unexpected bit from the reset status result in wd.c. What kind of IDE controller do you have? From owner-freebsd-current Tue Sep 12 21:44:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA07550 for current-outgoing; Tue, 12 Sep 1995 21:44:22 -0700 Received: from id.slip.bcm.tmc.edu (root@hou11.onramp.net [199.1.137.139]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA07542 for ; Tue, 12 Sep 1995 21:44:19 -0700 Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.12/8.6.9) id XAA09094; Tue, 12 Sep 1995 23:41:35 -0500 Date: Tue, 12 Sep 1995 23:41:35 -0500 From: Rich Murphey Message-Id: <199509130441.XAA09094@id.slip.bcm.tmc.edu> To: jkh@time.cdrom.com CC: current@freefall.freebsd.org In-reply-to: <324.810867210@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Sound code: Anyone for -current code in 2.1? Reply-to: rich@lamprey.utmb.edu Sender: current-owner@FreeBSD.org Precedence: bulk |From: "Jordan K. Hubbard" | |Well, I've proven to my satisfaction that the GUS MAX doesn't really |work correctly in 2.1-STABLE (at least not with `maplay', at it's |documented as broken in 2.1's LINT) so I just need to know whether or |not all the soundblaster et al users out there are happier with the |-current sound code, or the 2.1-STABLE stuff. | |If it's 2.1-STABLE then I'll bow to the needs of the many and take a |broken GUS MAX for the time being. If it's 2.2, then I'll do the work |to integrate it into 2.1. You folks decide. Feedback please? I'm using sound.v30.5 with 2.1-stable and a GUS MAX and have seen no real problems, so I'd vote to bring it in as well. Rich From owner-freebsd-current Tue Sep 12 23:11:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA09572 for current-outgoing; Tue, 12 Sep 1995 23:11:05 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA09551 ; Tue, 12 Sep 1995 23:10:41 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id IAA15408; Wed, 13 Sep 1995 08:10:26 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id IAA23534; Wed, 13 Sep 1995 08:10:25 +0200 Message-Id: <199509130610.IAA23534@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: current@freebsd.org, committers@freebsd.org Subject: eBones is BROKEN - please be patient!!! Date: Wed, 13 Sep 1995 08:10:25 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk Hi folks... At he moment, eBones will not compile. Please do not do anything about untill I get to it later today. Peter has done a LARGE repository copy for me and I will be following with the necessary fixes. Being in horribly different timezones has not been much help either. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key From owner-freebsd-current Tue Sep 12 23:43:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA10715 for current-outgoing; Tue, 12 Sep 1995 23:43:56 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA10708 for ; Tue, 12 Sep 1995 23:43:54 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id IAA23321 ; Wed, 13 Sep 1995 08:43:51 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id IAA11833 ; Wed, 13 Sep 1995 08:43:50 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id XAA19765; Tue, 12 Sep 1995 23:56:51 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509122156.XAA19765@keltia.Freenix.FR> Subject: Re: Progress so far on the Sig-11 problem (fwd) To: bugs@ns1.win.net (Mark Hittinger) Date: Tue, 12 Sep 1995 23:56:50 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: <199509122137.RAA21489@ns1.win.net> from "Mark Hittinger" at Sep 12, 95 05:37:16 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@freebsd.org Precedence: bulk It seems that Mark Hittinger said: > boots, or the order that the boot happens. The box that sig 11's has the > older rc setup without the sysconfig. If I manually start things without I also have the old rc files here. I will convert to sysconfig and friends someday (low priority). > and the kinds of things which are done have some effect on the sig 11 > issue. *BTW this is a box that has the dma problem and must use bounce > buffers* Could the clustering be broken on a box that needs bounce buffers? > How about a wrap around condition at the boundary? (Just blue skying here) I have an EISA system and don't use BOUNCE_BUFFERS of course. John, if you want anything to help, say so... I've reverted back to my Sep. 3 kernel for now. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Tue Sep 12 23:43:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA10730 for current-outgoing; Tue, 12 Sep 1995 23:43:59 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA10710 for ; Tue, 12 Sep 1995 23:43:56 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id IAA23325 ; Wed, 13 Sep 1995 08:43:52 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id IAA11836 ; Wed, 13 Sep 1995 08:43:51 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id AAA19788; Wed, 13 Sep 1995 00:00:24 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509122200.AAA19788@keltia.Freenix.FR> Subject: Re: Is nullfs broken in -current? To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Wed, 13 Sep 1995 00:00:24 +0200 (MET DST) Cc: terry@lambert.org, current@freefall.freebsd.org In-Reply-To: <9509121422.AA30833@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Sep 12, 95 10:22:41 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that Garrett A. Wollman said: > # mount -t null -o union /dsk2/src1 /usr/src > # mount -t null -o union /dsk3/src2 /usr/src > # cd /usr/src > # make world This one is a winner too: # mount -t null /src/src /usr/src # cvs update -d -P -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Wed Sep 13 00:17:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA11328 for current-outgoing; Wed, 13 Sep 1995 00:17:41 -0700 Received: from maui.com (langfod@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA11322 ; Wed, 13 Sep 1995 00:17:39 -0700 Received: (from langfod@localhost) by maui.com (8.6.10/8.6.6) id VAA24359; Tue, 12 Sep 1995 21:21:11 -1000 From: David Langford Message-Id: <199509130721.VAA24359@ maui.com> Subject: Re: Major problem with IDE hard drive and current To: root@io.cts.com (Morgan Davis) Date: Tue, 12 Sep 1995 21:21:11 -1000 (HST) Cc: freebsd-current@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199509130440.VAA17725@io.cts.com> from "Morgan Davis" at Sep 12, 95 09:40:59 pm X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1177 Sender: current-owner@FreeBSD.org Precedence: bulk Morgan Davis > >David Langford writes: >> >> >> It seems that the last few kernels I have made on my machine using current >> cannot find my IDE controller. >> >> wdc0 at 0x170 not found >> wdc1 at 0x1F0 not found >> >> My kernel from July 29 works fine, however. > >This is likely related to a similar problem I reported a couple of >weeks ago. The fix involves masking out an unexpected bit from the >reset status result in wd.c. > >What kind of IDE controller do you have? I have tried a Goldstar IDE controller with a "Goldstar Prime2" chip (May 94), a Goldstar with a "GM82C765" chip (Jun 92), and a multi I/O controller with the UMC UM82C863F and UM82C865F chipset (from early 93). I have used these cards since my early days with Mt. Xinu Mach Ix86. All show the same problem. I pulled wd.c from the STABLE tree and dropped it in and things come up fine. -- /--------------------------------------------------------------------\ | David Langford - Kihei, Maui, Hawaii - langfod@maui.com | | Maui Research and Technology Center -- Network Administrator | \--------------------------------------------------------------------/ From owner-freebsd-current Wed Sep 13 00:35:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA11758 for current-outgoing; Wed, 13 Sep 1995 00:35:22 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA11752 ; Wed, 13 Sep 1995 00:35:04 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA28629; Wed, 13 Sep 1995 17:31:47 +1000 Date: Wed, 13 Sep 1995 17:31:47 +1000 From: Bruce Evans Message-Id: <199509130731.RAA28629@godzilla.zeta.org.au> To: langfod@maui.com, root@io.cts.com Subject: Re: Major problem with IDE hard drive and current Cc: current@FreeBSD.org, freebsd-current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>This is likely related to a similar problem I reported a couple of >>weeks ago. The fix involves masking out an unexpected bit from the >>reset status result in wd.c. >> >>What kind of IDE controller do you have? >I have tried a Goldstar IDE controller with a "Goldstar Prime2" chip (May 94), >a Goldstar with a "GM82C765" chip (Jun 92), and a multi I/O controller with >the UMC UM82C863F and UM82C865F chipset (from early 93). >I have used these cards since my early days with Mt. Xinu Mach Ix86. >All show the same problem. >I pulled wd.c from the STABLE tree and dropped it in and things come up fine. It is probably a drive problem. What drives do both of you have? Bruce From owner-freebsd-current Wed Sep 13 01:09:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA12342 for current-outgoing; Wed, 13 Sep 1995 01:09:47 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA12336 for ; Wed, 13 Sep 1995 01:09:38 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA29848; Wed, 13 Sep 1995 18:01:01 +1000 Date: Wed, 13 Sep 1995 18:01:01 +1000 From: Bruce Evans Message-Id: <199509130801.SAA29848@godzilla.zeta.org.au> To: current@freebsd.org, terry@lambert.org Subject: Re: BAD BUG IN UFS RENAME Sender: current-owner@freebsd.org Precedence: bulk >Well, I've discovered some very interesting brain damage. >In the case of an attemped cross-device rename, both NAMEI buffers are >freed twice. >In the case of a rename of a->b where a + b have the same inode numbers >but not the same name, the, the from buffer is freed twice. Also in the case of renaming "." or ".." in msdosfs if the code that handles this is reachable. >The code of interest for this bungle is in: > kern/vfs_syscalls.c (rename) > ufs/ufs/ufs_vnops.c (ufs_rename) Also msdosfs/msdosfs_vnops.c (msdosfs_rename) miscfs/devfs/devfs_vnops.c udevfs_rename) Bruce From owner-freebsd-current Wed Sep 13 01:14:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA12446 for current-outgoing; Wed, 13 Sep 1995 01:14:27 -0700 Received: from mail.netvision.net.il (mail.NetVision.net.il [194.90.1.6]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA12439 for ; Wed, 13 Sep 1995 01:14:18 -0700 Received: from gena@NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mail.netvision.net.il (8.6.12/8.6.9) with SMTP id KAA29920; Wed, 13 Sep 1995 10:12:50 +0200 Date: Wed, 13 Sep 1995 10:12:50 +0200 Message-ID: X-Mailer: XFMail 0.3-beta [p0] on FreeBSD In-Reply-To: Reply-To: gena@NetVision.net.il X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: "Ugen J.S.Antsilevich" Subject: RE: HELP--second try.. Cc: Sender: current-owner@FreeBSD.org Precedence: bulk Yeah, me...somehow this strange sig 11 problems are gone. (Haven't seen them in 3 days) On Tue Sep 12 15:22:14 1995 Ugen J.S.Antsilevich wrote: >>OK..let's get it straight then.. >Is there ANYBODY having -current running on his machine????? >--Ugen -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena This message was sent at 09/13/95 08:11:48 by XF-Mail From owner-freebsd-current Wed Sep 13 01:32:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA12793 for current-outgoing; Wed, 13 Sep 1995 01:32:43 -0700 Received: from mailhub.cts.com (root@mailhub.cts.com [192.188.72.25]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id BAA12784 for ; Wed, 13 Sep 1995 01:32:39 -0700 Received: from io.cts.com by mailhub.cts.com with smtp (Smail3.1.29.1 #19) id m0ssnEn-000UyXC; Wed, 13 Sep 95 01:32 PDT Received: (from root@localhost) by io.cts.com (8.6.12/8.6.9) id BAA00450; Wed, 13 Sep 1995 01:32:35 -0700 From: Morgan Davis Message-Id: <199509130832.BAA00450@io.cts.com> Subject: Re: Major problem with IDE hard drive and current To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Sep 1995 01:32:35 -0700 (PDT) Cc: langfod@maui.com, current@FreeBSD.org In-Reply-To: <199509130731.RAA28629@godzilla.zeta.org.au> from "Bruce Evans" at Sep 13, 95 05:31:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 933 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: > > >I pulled wd.c from the STABLE tree and dropped it in and things come up fine. > > It is probably a drive problem. What drives do both of you have? I suppose. But why would these same drives not have the problem in previous versions of FreeBSD (going back to 2.0 for me)? You know, I recall the boot display showing the name of the hard drives before, so I was just going to suck in the relevant output from dmesg. And lo: wdreset: du->dk_status: 0x52 wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): <> wd0: size unknown, using BIOS values wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): <> wd1: size unknown, using BIOS values wd1: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S The drives are both Conners, but I'm not sure of the exact model number (without resorting to opening the case ... only if you insist.) --Morgan From owner-freebsd-current Wed Sep 13 02:21:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA16819 for current-outgoing; Wed, 13 Sep 1995 02:21:24 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA16808 for ; Wed, 13 Sep 1995 02:21:05 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA00257; Wed, 13 Sep 1995 19:16:41 +1000 Date: Wed, 13 Sep 1995 19:16:41 +1000 From: Bruce Evans Message-Id: <199509130916.TAA00257@godzilla.zeta.org.au> To: bde@zeta.org.au, root@io.cts.com Subject: Re: Major problem with IDE hard drive and current Cc: current@FreeBSD.org, langfod@maui.com Sender: current-owner@FreeBSD.org Precedence: bulk >> It is probably a drive problem. What drives do both of you have? >I suppose. But why would these same drives not have the problem in >previous versions of FreeBSD (going back to 2.0 for me)? Because the cdrom code changed the test. >You know, I recall the boot display showing the name of the hard >drives before, so I was just going to suck in the relevant output from >dmesg. And lo: >wdreset: du->dk_status: 0x52 >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa >wdc0: unit 0 (wd0): <> >wd0: size unknown, using BIOS values This shows that the WDCC_READP command failed. It shouldn't fail for any standard IDE drive, especially a modern one that supports all those flags. >The drives are both Conners, but I'm not sure of the exact model >number (without resorting to opening the case ... only if you insist.) It's probably not important. But please find out why WDCC_READP is failing. (Call wderror() in wdgetctlr(). The only normal error is "abort" which means that the drive doesn't support the command.) Bruce From owner-freebsd-current Wed Sep 13 02:59:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA19379 for current-outgoing; Wed, 13 Sep 1995 02:59:45 -0700 Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA19365 for ; Wed, 13 Sep 1995 02:59:28 -0700 Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.6.11/8.6.9) id LAA02754 for freebsd-current@freefall.cdrom.com; Wed, 13 Sep 1995 11:16:27 +0200 Date: Wed, 13 Sep 1995 11:16:27 +0200 From: "Christoph P. Kukulies" Message-Id: <199509130916.LAA02754@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.FreeBSD.org Subject: Re: sig11 Sender: current-owner@FreeBSD.org Precedence: bulk I tried ~dyson/exception.s with my -current kernel to no effect. All sorts of apps die with sig 11: Yesterday I had a reproducable effect: I wanted to build a new kernel (running a Aug 31 kernel), and got (during make depend): Sep 12 17:39:36 blues /kernel: pid 3016: awk: uid 0: exited on signal 6 Sep 12 17:39:37 blues /kernel: pid 3019: awk: uid 0: exited on signal 4 I then built awk NOSHARED and got around this. /usr/bin/login also chokes with sig 11 under a -current kernel. Looking what /usr/bin/login and /usr/bin/awk have in common wrt shared libs there is -lc.2 => /usr/lib/libc.so.2.2 (0x8052000) the only candidate. But the cause may lay somewhere else of course. BTW, I'm running a 486DX2/66, 32MB, IDE disks (bounce buffers). --Chris Christoph P. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Wed Sep 13 04:00:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA21634 for current-outgoing; Wed, 13 Sep 1995 04:00:10 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA21627 for ; Wed, 13 Sep 1995 04:00:05 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA05201; Wed, 13 Sep 1995 20:58:16 +1000 Date: Wed, 13 Sep 1995 20:58:16 +1000 From: Bruce Evans Message-Id: <199509131058.UAA05201@godzilla.zeta.org.au> To: davidg@root.com, terry@lambert.org Subject: Re: BAD BUG IN UFS RENAME Cc: current@freebsd.org, mckusick@mckusick.com Sender: current-owner@freebsd.org Precedence: bulk >> >Well, I've discovered some very interesting brain damage. >> > >> >In the case of an attemped cross-device rename, both NAMEI buffers are >> >freed twice. >> >> Yes, I think I see this - the VOP_ABORTOP's on both cn buffers, followed by >> the explicit free's in rename()? >Yes. It's not obvious because they check the HASBUF in the VOP_ABORTOP; >the actual rename stuff will work for UFS, assuming that there aren't >any cascade errors, but not for other file systems. This because they >check that the SAVESTART bit isn't set to determine the free behaviour. >So it's not as blatant as it would seem the first time you glance at it; I think it's not even actual. rename() sets SAVESTART for the source and the destination (nothing else in /sys/kern sets SAVESTART); many functions in nfs_serv.c set SAVESTART. All ABORTOPs are check SAVESTART like they are supposed to and don't free the buffer if SAVESTART is set; thus there is no problem in ufs_rename(). The braindamage, if any, is in the layering that sometimes requires the callee to free the buffer, and perhaps in the non-clearing and non-checking of HASBUF after the buffer has been freed, and perhaps in the overloading of SAVESTART and/or the non-use of SAVENAME in the ABORTOPs to decide whether the callee should free the buffer. >This could very well be the MSDOSFS rename bug. Nope, there are several known msdosfs rename bugs, all known to be different. (E.g., one is also a ufs rename bug: things have to be unlocked before calling checkpath() to avoid deadlock, but this allows races in checkpath(). Bad effects are easy to demonstrate by putting a tsleep() in checkpath() before the call to VFS_VGET() and removing a critical file or directory during the simulated blockage of VFS_VGET().) Bruce From owner-freebsd-current Wed Sep 13 06:39:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA23837 for current-outgoing; Wed, 13 Sep 1995 06:39:21 -0700 Received: from irbs.irbs.com ([199.182.75.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA23830 for ; Wed, 13 Sep 1995 06:39:18 -0700 Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id JAA01001 for freebsd-current@freefall.cdrom.com; Wed, 13 Sep 1995 09:39:10 -0400 From: John Capo Message-Id: <199509131339.JAA01001@irbs.irbs.com> Subject: US Domain Name Fees To: freebsd-current@freefall.FreeBSD.org (freebsd-current) Date: Wed, 13 Sep 1995 09:39:10 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 186 Sender: current-owner@FreeBSD.org Precedence: bulk A press release from Network Solutions announcing fees for US domain name holders has leaked out. No more free lunch. http://www.irbs.com/domain-fees.txt John Capo IRBS Engineering From owner-freebsd-current Wed Sep 13 08:46:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA14427 for current-outgoing; Wed, 13 Sep 1995 08:46:32 -0From owner-freebsd-current Wed Sep 13 10:47:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA19240 for current-outgoing; Wed, 13 Sep 1995 10:47:01 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA19234 for ; Wed, 13 Sep 1995 10:46:50 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA07728; Wed, 13 Sep 1995 10:41:43 -0700 From: Terry Lambert Message-Id: <199509131741.KAA07728@phaeton.artisoft.com> Subject: Re: BAD BUG IN UFS RENAME To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Sep 1995 10:41:43 -0700 (MST) Cc: davidg@root.com, terry@lambert.org, current@freebsd.org, mckusick@mckusick.com In-Reply-To: <199509131058.UAA05201@godzilla.zeta.org.au> from "Bruce Evans" at Sep 13, 95 08:58:16 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 718 Sender: current-owner@freebsd.org Precedence: bulk > Nope, there are several known msdosfs rename bugs, all known to be > different. (E.g., one is also a ufs rename bug: things have to be unlocked > before calling checkpath() to avoid deadlock, but this allows races > in checkpath(). Bad effects are easy to demonstrate by putting a tsleep() > in checkpath() before the call to VFS_VGET() and removing a critical > file or directory during the simulated blockage of VFS_VGET().) I was wondering why the hell this was. As far as I can tell, ufs_rename() in ufs_vnops.c is the only consumer of ufs_checkpath() in ufs_lookup.c. 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-current Wed Sep 13 10:54:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA19541 for current-outgoing; Wed, 13 Sep 1995 10:54:25 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA19533 for ; Wed, 13 Sep 1995 10:54:20 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA07769; Wed, 13 Sep 1995 10:52:16 -0700 From: Terry Lambert Message-Id: <199509131752.KAA07769@phaeton.artisoft.com> Subject: Re: Is nullfs broken in -current? To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Wed, 13 Sep 1995 10:52:16 -0700 (MST) Cc: wollman@lcs.mit.edu, terry@lambert.org, current@freefall.freebsd.org In-Reply-To: <199509122200.AAA19788@keltia.Freenix.FR> from "Ollivier Robert" at Sep 13, 95 00:00:24 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 987 Sender: current-owner@FreeBSD.org Precedence: bulk > It seems that Garrett A. Wollman said: > > # mount -t null -o union /dsk2/src1 /usr/src > > # mount -t null -o union /dsk3/src2 /usr/src > > # cd /usr/src > > # make world This one is a unionfs, not a nullfs. > This one is a winner too: > > # mount -t null /src/src /usr/src > # cvs update -d -P You are replacing the /usr/src vnode (potentially on cdrom) with the /src/src vnode from a writeable media? This seems more useful and applicable. I'll look at it. I suspect some of the problem is the delay in the vnode alias should not be occuring for the mount point itself. Part of this could be a cache issue. The name cache wants to be moved to the lookup layer instead of being implemented in each subsidiary file system. It doesn't look like the cache is flushed for the top level vnode, so potentially stale data is being returned. 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-current Wed Sep 13 10:57:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA19667 for current-outgoing; Wed, 13 Sep 1995 10:57:08 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA19643 for ; Wed, 13 Sep 1995 10:57:06 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA02082; Wed, 13 Sep 1995 13:56:52 -0400 Date: Wed, 13 Sep 1995 13:56:52 -0400 From: "Garrett A. Wollman" Message-Id: <9509131756.AA02082@halloran-eldar.lcs.mit.edu> To: Terry Lambert Cc: current@freefall.freebsd.org Subject: Re: Is nullfs broken in -current? In-Reply-To: <199509131752.KAA07769@phaeton.artisoft.com> References: <199509122200.AAA19788@keltia.Freenix.FR> <199509131752.KAA07769@phaeton.artisoft.com> Sender: current-owner@FreeBSD.org Precedence: bulk < said: >> It seems that Garrett A. Wollman said: >> > # mount -t null -o union /dsk2/src1 /usr/src >> > # mount -t null -o union /dsk3/src2 /usr/src >> > # cd /usr/src >> > # make world > This one is a unionfs, not a nullfs. No, it is NOT a bloody unionfs! `unionfs' == ``translucent filesystem''. This is a nullfs using the `union mount' mechanism. BIG DIFFERENCE. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Sep 13 11:03:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA20023 for current-outgoing; Wed, 13 Sep 1995 11:03:12 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA20017 for ; Wed, 13 Sep 1995 11:03:05 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA07814; Wed, 13 Sep 1995 11:01:43 -0700 From: Terry Lambert Message-Id: <199509131801.LAA07814@phaeton.artisoft.com> Subject: Re: Is nullfs broken in -current? To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Wed, 13 Sep 1995 11:01:43 -0700 (MST) Cc: terry@lambert.org, current@freefall.freebsd.org In-Reply-To: <9509131756.AA02082@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Sep 13, 95 01:56:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1049 Sender: current-owner@FreeBSD.org Precedence: bulk > >> > # mount -t null -o union /dsk2/src1 /usr/src > >> > # mount -t null -o union /dsk3/src2 /usr/src > >> > # cd /usr/src > >> > # make world > > > This one is a unionfs, not a nullfs. > > No, it is NOT a bloody unionfs! `unionfs' == ``translucent > filesystem''. This is a nullfs using the `union mount' mechanism. > BIG DIFFERENCE. What is the effective operational difference? It seems to me that the problem in this case is not as clear cut unless we assume all problems when using nullfs come from a single line of code. The other example only exercises the nullfs itself instead of the nullfs and the unioning code. I already now the unioning code is broken; it has warts in various file systems (but not in all of them) for lookup aliasing. It looks like it would break for UFS rename, two places in msdosfs, and in the explicit unionfs usage in anycase because of the relookup() bogosity. 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-current Wed Sep 13 11:04:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA20099 for current-outgoing; Wed, 13 Sep 1995 11:04:47 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA20080 for ; Wed, 13 Sep 1995 11:04:45 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id TAA06384 for current@freefall.freebsd.org; Wed, 13 Sep 1995 19:04:37 +0100 From: Paul Richards Message-Id: <199509131804.TAA06384@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: current@freefall.freebsd.org Date: Wed, 13 Sep 1995 19:04:37 +0100 (BST) In-Reply-To: <199509131438.QAA04286@uriah.heep.sax.de> from "J Wunsch" at Sep 13, 95 04:38:25 pm Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1446 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to J Wunsch who said > > It's hanging in draw_box(), since libforms expects this function to > take a single argument, while libncurses actually wants half a dozen > of them. > > Prototypes would have avoided this. :-) No in this case, there is a prototype for draw_box but it's never declared anywhere since it's just a function pointer. ncurses could probably do with some prototyping in it's headers then maybe it would have clashed with the one in my headers. > > This looks very weird, i'm not sure how it is _supposed_ to work from > looking at the code. Well, it looks like I decided to have an internal widget that draws a box but didn't finish it, instead of having an user-defined function to draw the box (there's evidence of how it used to be in the example.c, UserRoutine() function, I think it used to call the curses draw_box function from there as a user-supplied function. I think I was trying to provide as much libdialog L&F as I could internally and never finished it. What's missing is a device independant draw_box handler which calls the appropriate device specifica handler i.e. ncurses_draw_box(). I've added a brute force draw_box() which now does this just so people can see it run before they delete it :-) When freefall unhangs you'll see the commit. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Wed Sep 13 12:04:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA21910 for current-outgoing; Wed, 13 Sep 1995 12:04:36 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA21897 for ; Wed, 13 Sep 1995 12:04:31 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id UAA07116 for FreeBSD-current@FreeBSD.org; Wed, 13 Sep 1995 20:04:28 +0100 From: Paul Richards Message-Id: <199509131904.UAA07116@server.netcraft.co.uk> Subject: syslogd problems To: FreeBSD-current@FreeBSD.org (FreeBSD current mailing list) Date: Wed, 13 Sep 1995 20:04:28 +0100 (BST) Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 814 Sender: current-owner@FreeBSD.org Precedence: bulk Having "fixed" syslogd to not do an unconditional unlink at startup I've now got a related problem. If the machine crashes then the /dev/log file still exists and syslogd doesn't start up after boot. I still think that the fix is correct since the previous behaviour was too dangerous, there needs to be some method to cleanup after a crash though. Ideas: 1) Make syslogd more intelligent so it stats the file and sees if it's a socket. What happens if the pathname is something else's socket? 2) Removes the PATH_LOG file, probably check it's a socket just to be safe. 3) Remove /dev/log in /etc/rc before starting syslogd. (nice and easy :-) Any thoughts. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Wed Sep 13 12:31:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA22769 for current-outgoing; Wed, 13 Sep 1995 12:31:01 -0700 Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA22763 ; Wed, 13 Sep 1995 12:30:59 -0700 Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.6.12) id MAA04284; Wed, 13 Sep 1995 12:30:57 -0700 Received: from localhost by newport.ece.uci.edu (8.6.12) id MAA07698; Wed, 13 Sep 1995 12:30:55 -0700 Message-Id: <199509131930.MAA07698@newport.ece.uci.edu> To: current@freebsd.org cc: bugs@freebsd.org Subject: amd and -current Date: Wed, 13 Sep 1995 12:30:54 -0700 From: Steven Wallace Sender: current-owner@freebsd.org Precedence: bulk I have discovered a strange behavior with amd and a -current kernel. Amd will hang when autostarted by /etc/rc after it says, "/info: file server localhost type local starts up". Strangely enough, if I move amd start after inetd in /etc/rc or start it up manually there is no problems. Or if I use a kernel from a week ago there is no probs. I rebuilt /sbin/* and amd and did not make a difference. Any clues? Steven From owner-freebsd-current Wed Sep 13 12:35:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA23115 for current-outgoing; Wed, 13 Sep 1995 12:35:52 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA23108 for ; Wed, 13 Sep 1995 12:35:47 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id OAA04886; Wed, 13 Sep 1995 14:35:32 -0500 Received: by olympus (4.1/TSS2.1) id AA08745; Wed, 13 Sep 95 14:35:41 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9509131935.AA08745@olympus> Subject: Re: libforms - thumbs up or down? To: paul@FreeBSD.org Date: Wed, 13 Sep 1995 14:35:40 -0500 (CDT) Cc: jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199509121307.OAA03502@server.netcraft.co.uk> from "Paul Richards" at Sep 12, 95 02:07:01 pm X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1309 Sender: current-owner@FreeBSD.org Precedence: bulk > > In reply to Jordan K. Hubbard who said > > > > > I only wrote it in the first place because Jordan wanted something > > > for a new all singing all dancing sysinstall. If he's not interested > > > in it any more it can be ditched. > > > > Well, interested in the concept but it seems like things are shifting > > away from our original plan enough at this point that libforms may > > very likely never come into play now. Let me give it one last look > > before I make my final determination on that, but don't also forget > > that it's presently sort of broken anyway.. :-( > > Really, I don't care either way. I doubt it's very broken, probably just > a single fix needed somewhere since it was working when I committed it, I'm > just not interested in it at the moment, having more fun hacking virtual > hosting environments. > > -- > Paul Richards, Netcraft Ltd. > Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk > Phone: 0370 462071 (Mobile), +44 1225 447500 (work) > Would it be retired to the ports? Then it would be available if anyone wanted it. Boyd -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Wed Sep 13 13:26:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA25431 for current-outgoing; Wed, 13 Sep 1995 13:26:58 -0700 Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA25424 for ; Wed, 13 Sep 1995 13:26:54 -0700 Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0ssyOR-0009XtC; Wed, 13 Sep 95 13:26 PDT Date: Wed, 13 Sep 1995 13:26:51 -0700 (PDT) From: Jake Hamby To: current@freebsd.org Subject: Yet another severe Sig 11 problem with -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk I just upgraded to -current (as of 10:00 pm Sept. 12 PDT) and compiled it on my Micron 90MHz Pentium at work to see if my machine could shed any light on the Sig-11 problem so many people have reported. I built a custom kernel and rebooted, and sure enough, sig 11's on the two sed's in rc.local and sig 11's on login which locked my out of the system! This is a severe problem, and not at all like the occasional sig 11's that some people have reported. Here is some information on my system if this might help solve the problem: Micron 90MHz Pentium PCI/ISA w/ 32MB RAM BusLogic PCI SCSI controller with Conner 1GB hard drive & Plextor CDROM 3COM 3c509 ISA Ethernet card new-style 2.0.5-RELEASE startup scripts. The only LKM was the screensaver module which was rebuilt by make world, and the Sig 11's still occured when I removed it. It makes no difference whether I use a custom config or GENERIC. Anyway, good luck in finding the problem. I'm going to revert back to my 2.0.5-RELEASE kernel until you solve it. If you need any more information about my configuration, let me know. ---Jake Hamby jehamby@lightside.com From owner-freebsd-current Wed Sep 13 13:39:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA25744 for current-outgoing; Wed, 13 Sep 1995 13:39:01 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA25724 ; Wed, 13 Sep 1995 13:38:05 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id WAA16340; Wed, 13 Sep 1995 22:37:53 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id WAA09337; Wed, 13 Sep 1995 22:37:52 +0200 Message-Id: <199509132037.WAA09337@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: committers@freebsd.org, current@freebsd.org Subject: New DES library for secure/ Date: Wed, 13 Sep 1995 22:37:51 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk Hi As per the WP a while back, the DES library in eBones is to be replaced by a more up-to-date copy. I have a proposal, and I would appreciate it if we could thrash this one out with some speed so we can get cracking and use it, if possible :-) I am going to be using the crypto library from Eric Young. Not only does it have DES, but it also has IDEA, RSA etc. Some of this stuff is Illegal (or at least touchy) for use in the US, but I would not like to make it totally inacessible, so I am suggesting that this library get built a little like libc does, with lots of subdirectories and the main Makefile containing constructs of the form # Next line mandatory - the library contains at least DES .include "${.CURDIR}/des/Makefile.inc" .if exists(rsa) .include "${.CURDIR}/rsa/Makefile.inc" .endif .if exists(idea) .include "${.CURDIR}/idea/Makefile.inc" .endif And so on; _or_ # Next line mandatory - the library contains at least DES .include "${.CURDIR}/des/Makefile.inc" .include "${.CURDIR}/rsa/Makefile.inc" .include "${.CURDIR}/idea/Makefile.inc" : : with each subdirectory having US-illegal code defauting to containing only a "do nothing" Makefile.inc. This way, The US code can contain that which is perfectly legal there, and I (or anyone else) will be able to build a more complete crypto library by creating and populating the appropriate directories. I have started to build such a Makefile, and include it at the end of this mail. BTW - if this happens, the library can no longer be called 'libdes'. How would everyone feel about a new name? (Eric Young calls it 'libcrypto'). M # @(#)Makefile 8.2 (Berkeley) 2/3/94 # # $Id$ LIB=crypto CFLAGS+= -Wall -I${.CURDIR} -I${.CURDIR}/../include -I- -DPROTO CLEANFILES+= tags PRECIOUSLIB= yes .include "${.CURDIR}/des/Makefile.inc" .include "${.CURDIR}/buffer/Makefile.inc" .include "${.CURDIR}/error/Makefile.inc" .include "${.CURDIR}/idea/Makefile.inc" .include "${.CURDIR}/lhash/Makefile.inc" .include "${.CURDIR}/md/Makefile.inc" .include "${.CURDIR}/pem/Makefile.inc" .include "${.CURDIR}/rc4/Makefile.inc" .include "${.CURDIR}/rsa/Makefile.inc" .include "${.CURDIR}/x509/Makefile.inc" tags: ${SRCS} ctags ${.ALLSRC:M*.c} egrep -o "^ENTRY(.*)|^FUNC(.*)|^SYSCALL(.*)" ${.ALLSRC:M*.s} | \ sed "s;\([^:]*\):\([^(]*\)(\([^, )]*\)\(.*\);\3 \1 /^\2(\3\4$$/;" \ >> tags; sort -o tags tags .include -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key From owner-freebsd-current Wed Sep 13 14:10:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA26660 for current-outgoing; Wed, 13 Sep 1995 14:10:30 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA26654 ; Wed, 13 Sep 1995 14:10:24 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA06572 ; Wed, 13 Sep 1995 23:09:43 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA14274 ; Wed, 13 Sep 1995 23:09:42 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id WAA23195; Wed, 13 Sep 1995 22:35:42 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509132035.WAA23195@keltia.Freenix.FR> Subject: Re: syslogd problems To: paul@FreeBSD.org Date: Wed, 13 Sep 1995 22:35:42 +0200 (MET DST) Cc: FreeBSD-current@FreeBSD.org In-Reply-To: <199509131904.UAA07116@server.netcraft.co.uk> from "Paul Richards" at Sep 13, 95 08:04:28 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that Paul Richards said: > 3) Remove /dev/log in /etc/rc before starting syslogd. (nice and easy :-) This is the standard SunOS method. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Wed Sep 13 17:46:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA02618 for current-outgoing; Wed, 13 Sep 1995 17:46:48 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA02600 ; Wed, 13 Sep 1995 17:46:37 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA11697; Wed, 13 Sep 1995 17:46:10 -0700 To: Mark Murray cc: committers@freebsd.org, current@freebsd.org Subject: Re: New DES library for secure/ In-reply-to: Your message of "Wed, 13 Sep 1995 22:37:51 +0200." <199509132037.WAA09337@grumble.grondar.za> Date: Wed, 13 Sep 1995 17:46:10 -0700 Message-ID: <11695.811039570@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > I have a proposal, and I would appreciate it if we could thrash this > one out with some speed so we can get cracking and use it, if possible > :-) It all looks good to me - I say do it. > BTW - if this happens, the library can no longer be called 'libdes'. > How would everyone feel about a new name? (Eric Young calls it > 'libcrypto'). I like that name better anyway.. :-) Jordan From owner-freebsd-current Wed Sep 13 17:59:40 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA03000 for current-outgoing; Wed, 13 Sep 1995 17:59:40 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA02994 for ; Wed, 13 Sep 1995 17:59:38 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id UAA08985; Wed, 13 Sep 1995 20:52:50 -0400 Date: Wed, 13 Sep 1995 20:52:49 -0400 (EDT) From: "Jonathan M. Bresler" Subject: -stable: *** Error code ONLY one To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk {where do we discuss -stable?? here till release??} make world on -stable results in many troff warnings and a few errors. this is as of 6am EDT sup ===> usr.sbin/rmt ln -s /usr/sbin/rmt /etc/rmt ln: /etc/rmt: File exists *** Error code 1 (ignored) diff for Makefile: *** Makefile.old Wed Sep 13 20:54:55 1995 --- Makefile Wed Sep 13 20:54:48 1995 *************** *** 4,9 **** --- 4,10 ---- MAN8= rmt.8 beforeinstall: + rm -f ${DESTDIR}/etc/rmt -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt .include CONGRATULATIONS!! this is the ONLY Error reported by a make world jmb Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Wed Sep 13 18:09:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA03458 for current-outgoing; Wed, 13 Sep 1995 18:09:59 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA03439 for ; Wed, 13 Sep 1995 18:09:53 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id SAA11822; Wed, 13 Sep 1995 18:09:25 -0700 To: "Jonathan M. Bresler" cc: current@freebsd.org Subject: Re: -stable: *** Error code ONLY one In-reply-to: Your message of "Wed, 13 Sep 1995 20:52:49 EDT." Date: Wed, 13 Sep 1995 18:09:25 -0700 Message-ID: <11820.811040965@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > diff for Makefile: > > *** Makefile.old Wed Sep 13 20:54:55 1995 > --- Makefile Wed Sep 13 20:54:48 1995 > *************** > *** 4,9 **** > --- 4,10 ---- > MAN8= rmt.8 > > beforeinstall: > + rm -f ${DESTDIR}/etc/rmt > -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt Why not simply: ln -fs ${BINDIR}/rmt ${DESTDIR}/etc/rmt And skip the rm? Jordan From owner-freebsd-current Wed Sep 13 18:12:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA03609 for current-outgoing; Wed, 13 Sep 1995 18:12:16 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA03601 for ; Wed, 13 Sep 1995 18:12:13 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id VAA09301; Wed, 13 Sep 1995 21:04:51 -0400 Date: Wed, 13 Sep 1995 21:04:50 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: -stable: *** Error code ONLY one To: "Jordan K. Hubbard" cc: current@freebsd.org In-Reply-To: <11820.811040965@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Wed, 13 Sep 1995, Jordan K. Hubbard wrote: > > + rm -f ${DESTDIR}/etc/rmt > > -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt > > Why not simply: > > ln -fs ${BINDIR}/rmt ${DESTDIR}/etc/rmt > > And skip the rm? touche! i should have checked the man page ;) Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Wed Sep 13 19:07:07 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA05946 for current-outgoing; Wed, 13 Sep 1995 19:07:07 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA05936 ; Wed, 13 Sep 1995 19:06:52 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id TAA01837; Wed, 13 Sep 1995 19:05:40 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id TAA01061; Wed, 13 Sep 1995 19:07:54 -0700 Message-Id: <199509140207.TAA01061@corbin.Root.COM> To: "Jordan K. Hubbard" cc: Mark Murray , committers@freebsd.org, current@freebsd.org Subject: Re: New DES library for secure/ In-reply-to: Your message of "Wed, 13 Sep 95 17:46:10 PDT." <11695.811039570@time.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 13 Sep 1995 19:07:54 -0700 Sender: current-owner@freebsd.org Precedence: bulk >> I have a proposal, and I would appreciate it if we could thrash this >> one out with some speed so we can get cracking and use it, if possible >> :-) > >It all looks good to me - I say do it. > >> BTW - if this happens, the library can no longer be called 'libdes'. >> How would everyone feel about a new name? (Eric Young calls it >> 'libcrypto'). > >I like that name better anyway.. :-) We currently have a libcipher, and a libcrypt which is a symlink to libdescrypt. Sigh, and you want to create a libcrypto? This is getting more than a bit confusing. -DG From owner-freebsd-current Wed Sep 13 19:13:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA06253 for current-outgoing; Wed, 13 Sep 1995 19:13:54 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA06242 ; Wed, 13 Sep 1995 19:13:41 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id TAA00325; Wed, 13 Sep 1995 19:13:08 -0700 To: davidg@Root.COM cc: Mark Murray , committers@freebsd.org, current@freebsd.org Subject: Re: New DES library for secure/ In-reply-to: Your message of "Wed, 13 Sep 1995 19:07:54 PDT." <199509140207.TAA01061@corbin.Root.COM> Date: Wed, 13 Sep 1995 19:13:08 -0700 Message-ID: <323.811044788@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > We currently have a libcipher, and a libcrypt which is a symlink to > libdescrypt. Sigh, and you want to create a libcrypto? This is getting > more than a bit confusing. Hmmmm.. When you put it that way, I guess I'm inclined to agree. Maybe we need to ethnically clense the des namespace at this point? Jordan From owner-freebsd-current Wed Sep 13 20:00:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA08796 for current-outgoing; Wed, 13 Sep 1995 20:00:20 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA08785 for ; Wed, 13 Sep 1995 20:00:17 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id TAA06131; Wed, 13 Sep 1995 19:59:52 -0700 From: "Rodney W. Grimes" Message-Id: <199509140259.TAA06131@GndRsh.aac.dev.com> Subject: Re: -stable: *** Error code ONLY one To: jmb@kryten.atinc.com (Jonathan M. Bresler) Date: Wed, 13 Sep 1995 19:59:52 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Jonathan M. Bresler" at Sep 13, 95 08:52:49 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1166 Sender: current-owner@freebsd.org Precedence: bulk > > > {where do we discuss -stable?? here till release??} > > make world on -stable results in many troff warnings and a few errors. > this is as of 6am EDT sup > > ===> usr.sbin/rmt > ln -s /usr/sbin/rmt /etc/rmt > ln: /etc/rmt: File exists > *** Error code 1 (ignored) > > > diff for Makefile: > > *** Makefile.old Wed Sep 13 20:54:55 1995 > --- Makefile Wed Sep 13 20:54:48 1995 > *************** > *** 4,9 **** > --- 4,10 ---- > MAN8= rmt.8 > > beforeinstall: > + rm -f ${DESTDIR}/etc/rmt > -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt > > .include > Correct method: if [ ! -e ${DESTDIR}/etc/rmt]; then \ ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt \ fi It is not nice for make world to touch things in /etc, no matter what it is. The unsilent ignoreing of the error above was a quick hack by some one who did not bother to do it correctly. Forceful removal of my very different symbolic link in /etc is going to make me submit a bug report :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Sep 13 20:05:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA09156 for current-outgoing; Wed, 13 Sep 1995 20:05:37 -0700 Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id UAA09146 for ; Wed, 13 Sep 1995 20:05:34 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <04750-0@bunyip.cc.uq.oz.au>; Thu, 14 Sep 1995 13:04:31 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id NAA03389 for ; Thu, 14 Sep 1995 13:09:10 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id DAA08051 for ; Thu, 14 Sep 1995 03:10:11 GMT Message-Id: <199509140310.DAA08051@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.2 7/18/95 To: current@freebsd.org Subject: More in sig11 & VM problem. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 1995 13:10:10 +1000 From: Stephen Hocking Sender: current-owner@freebsd.org Precedence: bulk I saw another manifestation of this problem just now - I use MFS for my /tmp filesystem and while compiling something (it was gdb I think) it came up with complaints about the asm temp file being garbage. Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Wed Sep 13 21:00:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA16291 for current-outgoing; Wed, 13 Sep 1995 21:00:34 -0700 Received: from chrome.onramp.net (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA16282 for ; Wed, 13 Sep 1995 21:00:32 -0700 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.onramp.net (8.6.11/8.6.9) with SMTP id WAA02589; Wed, 13 Sep 1995 22:59:27 -0500 Message-Id: <199509140359.WAA02589@chrome.onramp.net> X-Authentication-Warning: chrome.onramp.net: Host localhost.jdl.com didn't use HELO protocol To: Josh Littlefield cc: current@freebsd.org Subject: Re: more ATAPI CD issues In-reply-to: Your message of "Tue, 12 Sep 1995 20:03:04 EDT." <199509130003.UAA11780@mozart.american.com> Reply-To: jdl@chromatic.com Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Wed, 13 Sep 1995 22:59:26 -0500 From: Jon Loeliger Sender: current-owner@freebsd.org Precedence: bulk Apparently, Josh Littlefield scribbled: > I've stuck the -current atapi support into a stock 2.0.5 kernel, and believe > I've done it correctly. I've discovered some problems with the atapi code > I'd like let people know about. Serge, has your "latest" patch to me been incorporated into a 1.4 release and plunked into the tree yet? > The 3 > trials of ATA you must pass are 1) writable byte count / cyl. address > registers, 2) successful wdreset(), and 3) successful WDCC_DIAGNOSE behavior. > > The first test is reasonable, for what its worth. Hmm. Not sure I agree here. My POS NEC 260 fails this test badly. Not sure why. I (w)hacked it out to get even vague functionality... > However the spec > says that, in general, the host should divert to the bit bucket any excess > data offered by the device (and send pad bytes when the device asks for more > than is required). Seems like atapi_io() should be less sensitive to > overrun/underrun. Agreed. I even read the ATAPI driver from the L camp, and it clearly black-holes the overruns and white-holes the needed extras. > My current (final?) problem is that the TEST_UNIT_READY command issued during > > wcd driver open never seems to generate an interrupt. I haven't solved this > one yet, but it may be related to the state of the IEN bit in wd_ctrl at the > end of wdreset(), since this is the first opportunity for the device to > interrupt. Which reminds me that the infinite sleeps in atapi.c are less > than ideal. Hmm.. You may need Serge's latest and greates patch that I alude to above. With minor work, I could dredge this up for you if you don't have it. jdl From owner-freebsd-current Wed Sep 13 22:07:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA19114 for current-outgoing; Wed, 13 Sep 1995 22:07:20 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA19107 for ; Wed, 13 Sep 1995 22:07:14 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA09329; Thu, 14 Sep 1995 15:02:29 +1000 Date: Thu, 14 Sep 1995 15:02:29 +1000 From: Bruce Evans Message-Id: <199509140502.PAA09329@godzilla.zeta.org.au> To: jmb@kryten.atinc.com, rgrimes@GndRsh.aac.dev.com Subject: Re: -stable: *** Error code ONLY one Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >> beforeinstall: >> + rm -f ${DESTDIR}/etc/rmt >> -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt >> >> .include >> >Correct method: > if [ ! -e ${DESTDIR}/etc/rmt]; then \ > ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt \ > fi >It is not nice for make world to touch things in /etc, no matter what >it is. The unsilent ignoreing of the error above was a quick hack >by some one who did not bother to do it correctly. Really correct method: # -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt `make install' in /usr/src doesn't install /etc/rc so why should it install /etc/rmt? Bruce From owner-freebsd-current Wed Sep 13 22:36:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA20041 for current-outgoing; Wed, 13 Sep 1995 22:36:54 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA20035 for ; Wed, 13 Sep 1995 22:36:51 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id WAA06494; Wed, 13 Sep 1995 22:35:18 -0700 From: "Rodney W. Grimes" Message-Id: <199509140535.WAA06494@GndRsh.aac.dev.com> Subject: Re: -stable: *** Error code ONLY one To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Sep 1995 22:35:18 -0700 (PDT) Cc: jmb@kryten.atinc.com, current@freebsd.org In-Reply-To: <199509140502.PAA09329@godzilla.zeta.org.au> from "Bruce Evans" at Sep 14, 95 03:02:29 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 920 Sender: current-owner@freebsd.org Precedence: bulk > > >> beforeinstall: > >> + rm -f ${DESTDIR}/etc/rmt > >> -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt > >> > >> .include > >> > > >Correct method: > > > if [ ! -e ${DESTDIR}/etc/rmt]; then \ > > ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt \ > > fi > > >It is not nice for make world to touch things in /etc, no matter what > >it is. The unsilent ignoreing of the error above was a quick hack > >by some one who did not bother to do it correctly. > > Really correct method: > > # -ln -s ${BINDIR}/rmt ${DESTDIR}/etc/rmt > > `make install' in /usr/src doesn't install /etc/rc so why should it > install /etc/rmt? Agreed, the above should be put in src/etc/Makefile and be a forced unconditional install of ${DESTDIR}/etc/rmt. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Sep 13 22:56:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA22946 for current-outgoing; Wed, 13 Sep 1995 22:56:19 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA22936 ; Wed, 13 Sep 1995 22:56:05 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id HAA16912; Thu, 14 Sep 1995 07:55:56 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id HAA10468; Thu, 14 Sep 1995 07:55:53 +0200 Message-Id: <199509140555.HAA10468@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: "Jordan K. Hubbard" , Mark Murray , committers@freebsd.org, current@freebsd.org Subject: Re: New DES library for secure/ Date: Thu, 14 Sep 1995 07:55:53 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > >> I have a proposal, and I would appreciate it if we could thrash this > >> one out with some speed so we can get cracking and use it, if possible > >> :-) > > > >It all looks good to me - I say do it. > > > >> BTW - if this happens, the library can no longer be called 'libdes'. > >> How would everyone feel about a new name? (Eric Young calls it > >> 'libcrypto'). > > > >I like that name better anyway.. :-) > > We currently have a libcipher, and a libcrypt which is a symlink to > libdescrypt. Sigh, and you want to create a libcrypto? This is getting > more than a bit confusing. Yehbo. I saw that too. The namespace is getting a bit crowded. What is a body to do? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key From owner-freebsd-current Wed Sep 13 23:40:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA25126 for current-outgoing; Wed, 13 Sep 1995 23:40:02 -0700 Received: from localhost.lightside.com (user37.lightside.com [198.81.209.37]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA25091 for ; Wed, 13 Sep 1995 23:39:59 -0700 Received: (from jehamby@localhost) by localhost.lightside.com (8.6.11/8.6.9) id XAA09504; Wed, 13 Sep 1995 23:40:41 -0700 Date: Wed, 13 Sep 1995 23:40:41 -0700 (PDT) From: Jake Hamby X-Sender: jehamby@localhost To: current@freebsd.org Subject: Finding solve to severe sig11 problem: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk Thanks to CTM, I've discovered I can produce any version of FreeBSD-current from Aug. 15 until today! I built a kernel from the Sep. 3 current (before the VM changes) and it works perfectly. Now my plan is to slowly step forward and see exactly which patch in which file is causing the Sig 11 problem in my case. If I can isolate this problem to a single patch, I will then apply all the subsequent CTM deltas and reverse that one patch. If all goes well, I'll post a diff to the list. Has anyone else attempted this? The CTM deltas are available on freefall for the taking! It's an excellent way to see which changes were made when, without requiring a program like CVS. ------------------------------------------------------------------------------ Jake Hamby | E-Mail: jehamby@lightside.com Student, Cal Poly University, Pomona | System Administrator, JPL ------------------------------------------------------------------------------ From owner-freebsd-current Wed Sep 13 23:55:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA25597 for current-outgoing; Wed, 13 Sep 1995 23:55:10 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA25591 for ; Wed, 13 Sep 1995 23:55:08 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id XAA06591; Wed, 13 Sep 1995 23:53:56 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id XAA00222; Wed, 13 Sep 1995 23:56:13 -0700 Message-Id: <199509140656.XAA00222@corbin.Root.COM> To: Jake Hamby cc: current@freebsd.org Subject: Re: Finding solve to severe sig11 problem: In-reply-to: Your message of "Wed, 13 Sep 95 23:40:41 PDT." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 13 Sep 1995 23:56:12 -0700 Sender: current-owner@freebsd.org Precedence: bulk >Thanks to CTM, I've discovered I can produce any version of >FreeBSD-current from Aug. 15 until today! I built a kernel from the >Sep. 3 current (before the VM changes) and it works perfectly. Now my >plan is to slowly step forward and see exactly which patch in which file >is causing the Sig 11 problem in my case. If I can isolate this problem >to a single patch, I will then apply all the subsequent CTM deltas and >reverse that one patch. If all goes well, I'll post a diff to the list. >Has anyone else attempted this? The CTM deltas are available on freefall >for the taking! It's an excellent way to see which changes were made >when, without requiring a program like CVS. Unfortunately many of the changes are related and have to be taken as a complete step in order for the system to work. -DG From owner-freebsd-current Thu Sep 14 00:30:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA29021 for current-outgoing; Thu, 14 Sep 1995 00:30:23 -0700 Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA29008 for ; Thu, 14 Sep 1995 00:30:18 -0700 Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id AAA00756; Thu, 14 Sep 1995 00:29:39 -0700 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: Jake Hamby cc: current@freebsd.org Subject: Re: Finding solve to severe sig11 problem: In-reply-to: Your message of "Wed, 13 Sep 1995 23:40:41 PDT." Date: Thu, 14 Sep 1995 00:29:38 -0700 Message-ID: <754.811063778@critter.tfs.com> From: Poul-Henning Kamp Sender: current-owner@freebsd.org Precedence: bulk > Thanks to CTM, I've discovered I can produce any version of > FreeBSD-current from Aug. 15 until today! I built a kernel from the Call it a planned for feature :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-current Thu Sep 14 05:01:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA07511 for current-outgoing; Thu, 14 Sep 1995 05:01:56 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA07503 for ; Thu, 14 Sep 1995 05:01:54 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id FAA27059; Thu, 14 Sep 1995 05:02:08 -0700 Date: Thu, 14 Sep 1995 05:02:08 -0700 Message-Id: <199509141202.FAA27059@silvia.HIP.Berkeley.EDU> To: faulkner@mpd.tandem.com CC: paul@FreeBSD.org, jkh@time.cdrom.com, current@freefall.freebsd.org In-reply-to: <9509131935.AA08745@olympus> (faulkner@mpd.tandem.com) Subject: Re: libforms - thumbs up or down? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: current-owner@FreeBSD.org Precedence: bulk * From: faulkner@mpd.tandem.com (Boyd Faulkner) * Would it be retired to the ports? Then it would be available if * anyone wanted it. Don't mean to nit-pick, but if it's broken or not used at all, it's not welcome in ports either. The ports tree is not a retirement home for old source. :) If someone really wants it, and someone (doesn't have to be the same "someone") is committed to make sure it is going to work now and in the future, that's fine, of course. Satoshi From owner-freebsd-current Thu Sep 14 05:56:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA09418 for current-outgoing; Thu, 14 Sep 1995 05:56:06 -0700 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA09412 ; Thu, 14 Sep 1995 05:56:01 -0700 Received: from wup-gate.UUCP (uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) with UUCP id OAA26604; Thu, 14 Sep 1995 14:55:50 +0200 Received: from wup.de by wup-gate with smtp (Smail3.1.28.1 #2) id m0stDtH-0007rLC; Thu, 14 Sep 95 14:59 MET DST Received: from sunny.wup.de by wup.de (4.1/SMI-4.1) id AA18065; Thu, 14 Sep 95 14:50:15 +0200 Received: by sunny.wup.de (5.x/SMI-SVR4) id AA10430; Thu, 14 Sep 1995 14:53:08 +0200 Date: Thu, 14 Sep 1995 14:53:08 +0200 From: Andreas Klemm Message-Id: <9509141253.AA10430@sunny.wup.de> To: larry@seminole.iag.net Subject: SCSI problems with FreeBSD 2.0.5 using AHA 2940 and Quantum Grand Prix Cc: jhk@freebsd.org, hackers@freebsd.org, current@freebsd.org Content-Type: X-sun-attachment Sender: current-owner@freebsd.org Precedence: bulk ---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Charset: us-ascii X-Sun-Content-Lines: 100 Subject: Re: SCSI errors 2.0.5 FreeBSD "sd0 timed out" Newsgroups: comp.periphs.scsi,comp.unix.bsd.freebsd.misc In article <42o73m$6vr@news.iag.net> you wrote: : I have an Opti based Pentium 100 Mhz motherboard with 32 : megs of RAM. The PCI controller is a 2940 and the hard : drive is a Quantum XP series 2 gig drive. The OS is Free : BSD 2.0.5. : With heavy DiskIO I see: : ahc0: target 0, lun 0, (sd0) timed out This happens to me, too, sometimes. : on the console. all diskIO is stopped, and the LED on : the SCSI host adapter and hard drive are on solid Yes ! : this happens with heavy disk IO with the configuration : supporting 10 mhz transfers rates and sync transfers : enabled My scenario: Asus P/I 55TP4XE board, P90, 256k synchr. cache, AHA 2940 BIOS V1.16, Toshiba 3601 CD-Rom, Quantum Grand Prix 4GB 7200U/min. Parity enabled on all devices, as well as 10MB synchr. My problems started with Termination pronlems. Here how I solved it, but problems remain ... The system locked up more frequently under FreeBSD and Linux, when I had the following order on the scsi bus: 2940-----------Hd-------------CD-Rom Termin. X X Putting the harddisk onto the end of the scsi bus I have much less problems: 2940-----------CD-------------HD Termin. X X Before that I tried nearly every combination of SCSI - Termination ;-) But still somethimes seems to break ... I had 4 OS on the Harddisk Slice 1 primary DOS - 250 MB DOS Slice 2 other - 3 GB FreeBSD Slice 3 Ext. Part - 500 MB Win NT 351 AS Slice 4 " - 400 MB Linux Slackware 2.3 - accessable via boot disk The FreeBSD bootmanager is _the_ boot manager on my system. So I have to take care to use this order during installation: DOS, FreeBSD partitioning, Windows NT, Linux, FreeBSD installation. When I had the disk in the middle of the scsi bus, then the Linux distrib with 1.2.12 kernel fucked up after installing about 75% of the packages. Now it works nearly flawlessly. But then after a few days again some drawbacks ... The Extended partition couldn't be accessed any more. The first warnings about a bad extended partition I received during the FreeBSD startup. After that I installed everything new ... But I left out Linux. So I have now DOS,NT,FreeBSD, to speed up installing everything again... But working for a while I get strange results again.... Under FreeBSD I noticed in /usr 1 dir and one file with control characters. When trying to boot WinNT I can't boot NT from one day to another, because ntdetect was screwed up ... I should install this file new ... Is the hardware so weak, that it can't drive 10MB/sec synchronously without loosing data ????? Or is it due to driver problems ???? The only OS, where I have no crashes in the moment is DOS/Windows 3.11. BTW: Everything is terminated properly, and I enabled Parity checking on all devices !! Hope, that -stable will help me out of this situation, if it should be a driver problem. BTW: I made a copy for thr freebsd mailinglists ... Since I'm not reading these lists currently, please write a cc: to my e-mail address, too Best regards Andreas /// -- andreas@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: .signature X-Sun-Charset: us-ascii X-Sun-Content-Lines: 2 andreas@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - From owner-freebsd-current Thu Sep 14 06:00:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA09581 for current-outgoing; Thu, 14 Sep 1995 06:00:11 -0700 Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.35.13]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA09575 for ; Thu, 14 Sep 1995 06:00:10 -0700 Received: (from james@localhost) by miller.cs.uwm.edu (8.6.10/8.6.10) id IAA08573; Thu, 14 Sep 1995 08:00:08 -0500 Date: Thu, 14 Sep 1995 08:00:08 -0500 From: Jim Lowe Message-Id: <199509141300.IAA08573@miller.cs.uwm.edu> To: current@freebsd.org, sysseh@devetir.qld.gov.au Subject: Re: More in sig11 & VM problem. Sender: current-owner@freebsd.org Precedence: bulk Just a little more information on the problem: I was compiling a program yesterday and received ld:/usr/local/lib/libtk.a: read_file_symbols(header): premature EOF''. It did this continuously. I reboot the system and the problem went away. Seems that the cache wasn't consistant with the disk. -Jim From owner-freebsd-current Thu Sep 14 06:46:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA10714 for current-outgoing; Thu, 14 Sep 1995 06:46:54 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA10708 for ; Thu, 14 Sep 1995 06:46:50 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id JAA29978; for ; Thu, 14 Sep 1995 09:46:48 -0400 Date: Thu, 14 Sep 95 09:44:41 PDT From: "Ugen J.S.Antsilevich" Subject: RE: Yet another severe Sig 11 problem with -current To: current@FreeBSD.ORG, Jake Hamby X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: current-owner@FreeBSD.ORG Precedence: bulk >I just upgraded to -current (as of 10:00 pm Sept. 12 PDT) and compiled it >on my Micron 90MHz Pentium at work to see if my machine could shed any >light on the Sig-11 problem so many people have reported. I built a >custom kernel and rebooted, and sure enough, sig 11's on the two sed's in >rc.local and sig 11's on login which locked my out of the system! This >is a severe problem, and not at all like the occasional sig 11's that >some people have reported. Here is some information on my system if this >might help solve the problem: Yep..yep..that's the same thing which happening to me... >Micron 90MHz Pentium PCI/ISA w/ 32MB RAM >BusLogic PCI SCSI controller with Conner 1GB hard drive & Plextor CDROM >3COM 3c509 ISA Ethernet card Nai 75MHz Pentium PCI/ISA w/ 16MB RAM No SCSI adaptors, EIDE disk adaptor onboard... --Ugen From owner-freebsd-current Thu Sep 14 07:00:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA11095 for current-outgoing; Thu, 14 Sep 1995 07:00:35 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA11089 for ; Thu, 14 Sep 1995 07:00:33 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id KAA01973; for ; Thu, 14 Sep 1995 10:00:26 -0400 Date: Thu, 14 Sep 95 09:57:34 PDT From: "Ugen J.S.Antsilevich" Subject: What is where... To: freebsd-current@FreeBSD.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Hi guys..sorta lame question but forgive me, i was out of business for so long: so i c the last released version was 2.0.5 -stable = 2.1.0 -current = 2.2.0 (???) So if i am going to write something and i want it into 2.1.0 release i should put it into stable? OR there is not any development on stable? If there is what's the policy of commits etc...? If i put something in 2.2.0 (suppose for a minute, it works :^))) it is going to be only there, right? Thanx! --Ugen From owner-freebsd-current Thu Sep 14 07:30:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA11746 for current-outgoing; Thu, 14 Sep 1995 07:30:39 -0700 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA11740 ; Thu, 14 Sep 1995 07:30:37 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id HAA22861; Thu, 14 Sep 1995 07:29:48 -0700 Message-Id: <199509141429.HAA22861@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Andreas Klemm cc: larry@seminole.iag.net, jhk@freebsd.org, hackers@freebsd.org, current@freebsd.org Subject: Re: SCSI problems with FreeBSD 2.0.5 using AHA 2940 and Quantum Grand Prix In-reply-to: Your message of "Thu, 14 Sep 1995 14:53:08 +0200." <9509141253.AA10430@sunny.wup.de> Date: Thu, 14 Sep 1995 07:29:48 -0700 From: "Justin T. Gibbs" Sender: current-owner@freebsd.org Precedence: bulk >In article <42o73m$6vr@news.iag.net> you wrote: >: I have an Opti based Pentium 100 Mhz motherboard with 32 >: megs of RAM. The PCI controller is a 2940 and the hard >: drive is a Quantum XP series 2 gig drive. The OS is Free >: BSD 2.0.5. > >: With heavy DiskIO I see: > >: ahc0: target 0, lun 0, (sd0) timed out > >This happens to me, too, sometimes. > >: on the console. all diskIO is stopped, and the LED on >: the SCSI host adapter and hard drive are on solid > >Yes ! > >: this happens with heavy disk IO with the configuration >: supporting 10 mhz transfers rates and sync transfers >: enabled > >My scenario: Asus P/I 55TP4XE board, P90, 256k synchr. cache, AHA 2940 >BIOS V1.16, Toshiba 3601 CD-Rom, Quantum Grand Prix 4GB 7200U/min. You should be running the driver in -stable if you have a grand prix. The driver is most likely your problem. >andreas@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH >Andreas Klemm ___/\/\/ - Support Unix - -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Thu Sep 14 08:02:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA12650 for current-outgoing; Thu, 14 Sep 1995 08:02:48 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA12644 for ; Thu, 14 Sep 1995 08:02:46 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id QAA06224; Thu, 14 Sep 1995 16:01:47 +0100 From: Paul Richards Message-Id: <199509141501.QAA06224@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: asami@cs.berkeley.edu (Satoshi Asami) Date: Thu, 14 Sep 1995 16:01:46 +0100 (BST) Cc: faulkner@mpd.tandem.com, paul@FreeBSD.org, jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199509141202.FAA27059@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Sep 14, 95 05:02:08 am Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1245 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Satoshi Asami who said > > * From: faulkner@mpd.tandem.com (Boyd Faulkner) > > * Would it be retired to the ports? Then it would be available if > * anyone wanted it. > > Don't mean to nit-pick, but if it's broken or not used at all, it's > not welcome in ports either. The ports tree is not a retirement > home for old source. :) > > If someone really wants it, and someone (doesn't have to be the same > "someone") is committed to make sure it is going to work now and in > the future, that's fine, of course. Well, someone's contacted me about using it so I'll let them decide where they think it should go and what to do with it. As far as I'm concerned, you can do what you want with it. It's not going to be a mainstream part of FreeBSD so if I or someone else continue to work on it then it will be as an independant project, much like any other add-in functionality and can probably be "ported" when it's ready for use. It's not actually going anywhere anyway, since it'll always be available in the Attic should someone feel a burning desire to look at the code. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Thu Sep 14 08:44:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA13940 for current-outgoing; Thu, 14 Sep 1995 08:44:17 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA13934 for ; Thu, 14 Sep 1995 08:44:13 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id KAA28858; Thu, 14 Sep 1995 10:43:58 -0500 Received: by olympus (4.1/TSS2.1) id AA10094; Thu, 14 Sep 95 10:43:54 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9509141543.AA10094@olympus> Subject: Re: libforms - thumbs up or down? To: asami@cs.berkeley.edu (Satoshi Asami) Date: Thu, 14 Sep 1995 10:43:54 -0500 (CDT) Cc: faulkner@devnull, paul@FreeBSD.org, jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199509141202.FAA27059@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Sep 14, 95 05:02:08 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 921 Sender: current-owner@FreeBSD.org Precedence: bulk > > * From: faulkner@mpd.tandem.com (Boyd Faulkner) > > * Would it be retired to the ports? Then it would be available if > * anyone wanted it. > > Don't mean to nit-pick, but if it's broken or not used at all, it's > not welcome in ports either. The ports tree is not a retirement > home for old source. :) > > If someone really wants it, and someone (doesn't have to be the same > "someone") is committed to make sure it is going to work now and in > the future, that's fine, of course. > > Satoshi > But didn't I just see that it is used in xfmail (or was that fxmail)? All I know now is that is not used by the base system. I agree it should be fixed before it goes into ports. Boyd -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Thu Sep 14 08:55:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA14247 for current-outgoing; Thu, 14 Sep 1995 08:55:58 -0700 Received: from tserv.lodgenet.com (root@dial4.iw.net [204.157.148.53]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA14144 for ; Thu, 14 Sep 1995 08:53:12 -0700 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id KAA17216; Thu, 14 Sep 1995 10:54:14 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.12/8.6.9) with SMTP id KAA26568; Thu, 14 Sep 1995 10:58:07 -0500 Message-Id: <199509141558.KAA26568@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: faulkner@mpd.tandem.com (Boyd Faulkner) cc: asami@cs.berkeley.edu (Satoshi Asami), faulkner@devnull.lodgenet.com, paul@FreeBSD.org, jkh@time.cdrom.com, current@freefall.freebsd.org Subject: Re: libforms - thumbs up or down? In-reply-to: Your message of "Thu, 14 Sep 1995 10:43:54 CDT." <9509141543.AA10094@olympus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 1995 10:58:06 -0500 From: "Eric L. Hernes" Sender: current-owner@FreeBSD.org Precedence: bulk > > > > * From: faulkner@mpd.tandem.com (Boyd Faulkner) > > > > * Would it be retired to the ports? Then it would be available if > > * anyone wanted it. > > > > Don't mean to nit-pick, but if it's broken or not used at all, it's > > not welcome in ports either. The ports tree is not a retirement > > home for old source. :) > > > > If someone really wants it, and someone (doesn't have to be the same > > "someone") is committed to make sure it is going to work now and in > > the future, that's fine, of course. > > > > Satoshi > > > But didn't I just see that it is used in xfmail (or was that fxmail)? no that was a different `libforms', it (xfmail) uses xforms available from ftp://bloch.phys.uwm.edu/pub/xforms/freeBSD/. In fact for this, It would be *preferable* to remove /usr/lib/libforms.a from the tree, 'cause then I could do a fairly clean port of xforms, which is used by xfmail (and possibly others). At present, I haven't figured out how to resolve the conflict between the FBSD libforms and xforms. > All I know now is that is not used by the base system. I agree it should > be fixed before it goes into ports. > > Boyd > > -- > _______________________________________________________________________ > > Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner > _______________________________________________________________________ > eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-current Thu Sep 14 09:39:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15333 for current-outgoing; Thu, 14 Sep 1995 09:39:45 -0700 Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA15323 for ; Thu, 14 Sep 1995 09:39:27 -0700 Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.144.4]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id SAA13129 for ; Thu, 14 Sep 1995 18:29:53 +0200 From: Wolfram Schneider Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.12/8.6.9) id SAA28249; Thu, 14 Sep 1995 18:29:47 +0200 Date: Thu, 14 Sep 1995 18:29:47 +0200 Message-Id: <199509141629.SAA28249@caramba.cs.tu-berlin.de> To: current@freebsd.org Subject: /usr/libexec/locate.* MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: current-owner@freebsd.org Precedence: bulk [next try, I don't see this mail in mailinglist] o locate.bigram.c Bigram does not remove newline at end of filename. This break particulary the bigram algorithm and /var/db/locate.database grow up 15 %. It's really a bug!!! The bigram output is silly and need ~1/2 CPU time of database rebuilding. old: locate.bigram < $filelist | sort | uniq -c | sort -T /$TMPDIR -nr ^^^^^^^^^^^^^^ this can easy make bigram new: locate.bigram < $filelist | sort -T /$TMPDIR -nr o locate.code.c Use a lookup array instead a function. 3 x faster o local.updatedb.csh # search locally or everything # find ${SRCHPATHS} -print | \ find ${SRCHPATHS} \! -fstype local -prune -or -print | \ tr '/' '\001' | \ ^^^^^^^^^^^^^^^^^^ Superfluously. Nobody need it. (sort -T $TMPDIR -f; echo $status > $errs) | tr '\001' '/' > $filelist ^^ wrong, made database 0.5% bigger ^^^^^^^^^^^^^^^^^^^^^^^^ Superfluously, see above. It double the disk space for filenames. The filenames are in a temp sort file and at the same time in $filelist. sort -T $TMPDIR -o $filelist avoid this by renaming temp sort file to $filelist. My database is 115MB big ... $LIBDIR/locate.bigram < $filelist | \ (sort -T /$TMPDIR; echo $status >> $errs) | uniq -c | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ see locate.bigram.c --- /usr/src/usr.bin/locate/bigram/locate.bigram.c Fri May 27 14:32:02 1994 +++ locate.bigram.c Tue Sep 12 14:24:56 1995 @@ -53,32 +53,51 @@ #include #include /* for MAXPATHLEN */ +#include /* memchr */ -char buf1[MAXPATHLEN] = " "; -char buf2[MAXPATHLEN]; +u_char buf1[MAXPATHLEN] = " "; +u_char buf2[MAXPATHLEN]; +unsigned int bigram[UCHAR_MAX][UCHAR_MAX]; -main ( ) + +void main ( ) { - register char *cp; - register char *oldpath = buf1, *path = buf2; + register u_char *cp; + register u_char *oldpath = buf1, *path = buf2; + register int i, j; + + /* init bigram buffer */ + for (i = 0; i < UCHAR_MAX; i++) + for (j = 0; j < UCHAR_MAX; j++) + bigram[i][j] = 0; while ( fgets ( path, sizeof(buf2), stdin ) != NULL ) { + /* chop newline */ + if ((cp = memchr(path, '\n', sizeof(buf2))) != NULL) + *cp = NULL; + /* skip longest common prefix */ - for ( cp = path; *cp == *oldpath; cp++, oldpath++ ) - if ( *oldpath == NULL ) - break; + for (cp = path; (*cp == *oldpath) != NULL; cp++, oldpath++); + /* * output post-residue bigrams only */ + while ( *cp != NULL && *(cp + 1) != NULL ) { - putchar ( *cp++ ); - putchar ( *cp++ ); - putchar ( '\n' ); + bigram[*cp][*(cp+1)]++; + cp += 2; } + if ( path == buf1 ) /* swap pointers */ path = buf2, oldpath = buf1; else path = buf1, oldpath = buf2; } + + /* output */ + for (i = 0; i < UCHAR_MAX; i++) + for (j = 0; j < UCHAR_MAX; j++) + if (bigram[i][j] != 0) + fprintf(stdout, "%4d %c%c\n", bigram[i][j], i, j); } --- 1.1 1995/09/12 16:40:45 +++ locate.code.c 1995/09/12 18:07:57 @@ -93,8 +93,20 @@ char buf2[MAXPATHLEN]; char bigrams[BGBUFSIZE + 1] = { 0 }; +#if 1 +#define BGINDEX(x) (big[(int)*x][(int)*(x+1)]) +typedef u_char bg_t; +bg_t big[UCHAR_MAX][UCHAR_MAX]; + +#else +#define BGINDEX(x) bgindex(x) +typedef int bg_t; +#endif + int bgindex __P((char *)); void usage __P((void)); +extern int optind; +extern int optopt; int main(argc, argv) @@ -104,6 +116,7 @@ register char *cp, *oldpath, *path; int ch, code, count, diffcount, oldcount; FILE *fp; + register int i, j; while ((ch = getopt(argc, argv, "")) != EOF) switch(ch) { @@ -126,14 +139,22 @@ err(1, "stdout"); (void)fclose(fp); + /* init lookup table */ + for (i = 0; i < UCHAR_MAX; i++) + for (j = 0; j < UCHAR_MAX; j++) + big[i][j] = (bg_t)-1; + + for (cp = bigrams, i = 0; *cp != NULL; i += 2, cp += 2) + big[(int)*cp][(int)*(cp + 1)] = (bg_t)i; + oldpath = buf1; path = buf2; oldcount = 0; while (fgets(path, sizeof(buf2), stdin) != NULL) { - /* Truncate newline. */ - cp = path + strlen(path) - 1; - if (cp > path && *cp == '\n') - *cp = '\0'; + + /* chop newline */ + if ((cp = memchr(path, '\n', sizeof(buf2))) != NULL) + *cp = NULL; /* Squelch characters that would botch the decoding. */ for (cp = path; *cp != NULL; cp++) { @@ -144,9 +165,9 @@ } /* Skip longest common prefix. */ - for (cp = path; *cp == *oldpath; cp++, oldpath++) - if (*oldpath == NULL) - break; + for (cp = path; (*cp == *oldpath) != NULL; cp++, oldpath++) + ; + count = cp - path; diffcount = count - oldcount + OFFSET; oldcount = count; @@ -164,7 +185,7 @@ err(1, "stdout"); break; } - if ((code = bgindex(cp)) < 0) { + if ((code = BGINDEX(cp)) == (bg_t)-1) { if (putchar(*cp++) == EOF || putchar(*cp++) == EOF) err(1, "stdout"); --- /usr/libexec/locate.updatedb.old Sun Jan 1 05:36:58 1995 +++ /usr/libexec/locate.updatedb Tue Sep 12 14:33:32 1995 @@ -58,12 +58,10 @@ # search locally or everything # find ${SRCHPATHS} -print | \ find ${SRCHPATHS} \! -fstype local -prune -or -print | \ - tr '/' '\001' | \ - (sort -T $TMPDIR -f; echo $status > $errs) | tr '\001' '/' > $filelist + sort -T $TMPDIR -o $filelist; echo $status > $errs -$LIBDIR/locate.bigram < $filelist | \ - (sort -T /$TMPDIR; echo $status >> $errs) | \ - uniq -c | sort -T /$TMPDIR -nr | \ +$LIBDIR/locate.bigram.new < $filelist | \ + sort -T $TMPDIR -nr | \ awk '{ if (NR <= 128) print $2 }' | tr -d '\012' > $bigrams # code the file list From owner-freebsd-current Thu Sep 14 09:45:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15500 for current-outgoing; Thu, 14 Sep 1995 09:45:12 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA15494 for ; Thu, 14 Sep 1995 09:45:10 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA04049; Thu, 14 Sep 1995 12:44:38 -0400 Date: Thu, 14 Sep 1995 12:44:38 -0400 From: "Garrett A. Wollman" Message-Id: <9509141644.AA04049@halloran-eldar.lcs.mit.edu> To: Mark Murray Cc: current@freebsd.org Subject: Re: New DES library for secure/ In-Reply-To: <199509141615.SAA15579@grumble.grondar.za> References: <199509141615.SAA15579@grumble.grondar.za> Sender: current-owner@freebsd.org Precedence: bulk < said: > Going back to my proposal - I see how it can be inconvenient, but in this > case I am proposing quite a large shift, and I hope I am creating > something that can be built on for a long while. The name lib_des_ > seems to have outlived its usefulness, as my original poroposal pointed > out, and I would rather not create historically bad names if we do > not have to. How many applications are there _now_, installed > and dependant on libdes? I would say very few. The important point is that the DES library associated with Kerberos v4 has been called `libdes' from time immemorial, and that to break this would be a rather gratuitous change for absolutely no benefit. (The DES libraries associated with Kerberos v5 are called `libcrypto' and `libdes425'.) Now, I have no objection if you want to call it `libfoo' and then create `libdes' links (assuming that the new code is call-compatible with what we have now), but it is important to me that we avoid ``change for change's sake'', as it does bad things for our public image and irritates people trying to port and manage software on our platform. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Sep 14 09:52:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15730 for current-outgoing; Thu, 14 Sep 1995 09:52:16 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA15653 for ; Thu, 14 Sep 1995 09:51:09 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id SAA17579; Thu, 14 Sep 1995 18:50:29 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id SAA15940; Thu, 14 Sep 1995 18:50:28 +0200 Message-Id: <199509141650.SAA15940@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: "Garrett A. Wollman" cc: Mark Murray , current@freebsd.org Subject: Re: New DES library for secure/ Date: Thu, 14 Sep 1995 18:50:28 +0200 From: Mark Murray Sender: current-owner@freebsd.org Precedence: bulk > The important point is that the DES library associated with Kerberos > v4 has been called `libdes' from time immemorial, and that to break > this would be a rather gratuitous change for absolutely no benefit. > (The DES libraries associated with Kerberos v5 are called `libcrypto' > and `libdes425'.) The library that I am talking about is called [ hopefully ;-) ] libcrypto. I have seen the Kerberos5 DES, and it requires Eric Youngs library, which is the one that I am going to import. Looks like we are (sort of) compatible with the future to start with! > Now, I have no objection if you want to call it `libfoo' and then > create `libdes' links (assuming that the new code is call-compatible > with what we have now), but it is important to me that we avoid > ``change for change's sake'', as it does bad things for our public > image and irritates people trying to port and manage software on our > platform. I can live with that... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key From owner-freebsd-current Thu Sep 14 11:23:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA17552 for current-outgoing; Thu, 14 Sep 1995 11:23:50 -0700 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA17493 for ; Thu, 14 Sep 1995 11:22:28 -0700 Received: from olympus by devnull (8.6.8/8.6.6) id NAA10475; Thu, 14 Sep 1995 13:19:49 -0500 Received: by olympus (4.1/TSS2.1) id AA11203; Thu, 14 Sep 95 13:19:58 CDT From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9509141819.AA11203@olympus> Subject: Re: libforms - thumbs up or down? To: erich@lodgenet.com (Eric L. Hernes) Date: Thu, 14 Sep 1995 13:19:57 -0500 (CDT) Cc: faulkner@devnull, asami@cs.berkeley.edu, faulkner@devnull.lodgenet.com, paul@FreeBSD.org, jkh@time.cdrom.com, current@freefall.freebsd.org In-Reply-To: <199509141558.KAA26568@jake.lodgenet.com> from "Eric L. Hernes" at Sep 14, 95 10:58:06 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1774 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > > > * From: faulkner@mpd.tandem.com (Boyd Faulkner) > > > > > > * Would it be retired to the ports? Then it would be available if > > > * anyone wanted it. > > > > > > Don't mean to nit-pick, but if it's broken or not used at all, it's > > > not welcome in ports either. The ports tree is not a retirement > > > home for old source. :) > > > > > > If someone really wants it, and someone (doesn't have to be the same > > > "someone") is committed to make sure it is going to work now and in > > > the future, that's fine, of course. > > > > > > Satoshi > > > > > But didn't I just see that it is used in xfmail (or was that fxmail)? > > no that was a different `libforms', it (xfmail) uses xforms available > from ftp://bloch.phys.uwm.edu/pub/xforms/freeBSD/. In fact for this, > It would be *preferable* to remove /usr/lib/libforms.a from the tree, > 'cause then I could do a fairly clean port of xforms, which is used > by xfmail (and possibly others). At present, I haven't figured out > how to resolve the conflict between the FBSD libforms and xforms. Never mind, then. Boyd > > > All I know now is that is not used by the base system. I agree it should > > be fixed before it goes into ports. > > > > Boyd > > > > -- > > _______________________________________________________________________ > > > > Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner > > _______________________________________________________________________ > > > > eric. > -- > erich@lodgenet.com > erich@rrnet.com > > -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Thu Sep 14 13:06:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA20267 for current-outgoing; Thu, 14 Sep 1995 13:06:08 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA20219 for ; Thu, 14 Sep 1995 13:05:54 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA22150 ; Thu, 14 Sep 1995 22:05:31 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA18446 ; Thu, 14 Sep 1995 22:05:30 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id UAA26870; Thu, 14 Sep 1995 20:49:35 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509141849.UAA26870@keltia.Freenix.FR> Subject: Re: Finding solve to severe sig11 problem: To: jehamby@lightside.com (Jake Hamby) Date: Thu, 14 Sep 1995 20:49:34 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: from "Jake Hamby" at Sep 13, 95 11:40:41 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@freebsd.org Precedence: bulk It seems that Jake Hamby said: > plan is to slowly step forward and see exactly which patch in which file > is causing the Sig 11 problem in my case. If I can isolate this problem > to a single patch, I will then apply all the subsequent CTM deltas and > reverse that one patch. If all goes well, I'll post a diff to the list. As David said, the patches are related and the one that cause the sig11 will not be easely pointed out. Here are the patches you'll have to look for if you want to try anyway: Even with that, it will probably be hard to find because (a wild guess) it is either a long-time-well-hidden bug discovered by some new way to do things or a new bug. My knowledge on VM stuff is unfortunately slim :-( dyson 95/09/03 12:56:16 Modified: sys/kern vfs_bio.c vfs_cluster.c Log: Improvements to the cluster code, minor vfs_bio efficiency: Better performance -- more aggressive read-ahead under certain circumstanses. Mods to support clustering on small ( < PAGE_SIZE) block size filesystems (e.g. ext2fs, msdosfs.) dyson 95/09/03 12:57:26 Modified: sys/vm vm_page.c Log: New subroutine "vm_page_set_validclean" for a vfs_bio improvement. dyson 95/09/03 13:11:29 Modified: sys/vm vm_page.h Log: Added prototype for new routine "vm_page_set_validclean" and initial declarations for the prezeroed pages mechanism. dyson 95/09/03 13:32:53 Modified: sys/kern vfs_cluster.c Log: VOP_BMAP will eventually need an additional argument, but not yet. This backs out that modification to minimize the window during which this is not yet correct. dyson 95/09/03 13:39:23 Modified: sys/i386/i386 swtch.s vm_machdep.c Log: Machine dependent routines to support pre-zeroed free pages. This significantly improves demand zero performance. dyson 95/09/03 13:40:44 Modified: sys/vm vm_kern.c vm_fault.c vm_page.c Log: Machine independent changes to support pre-zeroed free pages. This significantly improves demand-zero performance. dyson 95/09/03 21:44:28 Modified: sys/vm swap_pager.c vnode_pager.c vm_fault.c Log: Allow the fault code to use additional clustering info from both bmap and the swap pager. Improved fault clustering performance. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Thu Sep 14 13:06:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA20283 for current-outgoing; Thu, 14 Sep 1995 13:06:10 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA20210 for ; Thu, 14 Sep 1995 13:05:44 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id WAA22162 ; Thu, 14 Sep 1995 22:05:38 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id WAA18452 ; Thu, 14 Sep 1995 22:05:37 +0200 Received: (from roberto@localhost) by keltia.Freenix.FR (8.7.Beta.14/keltia-uucp-2.4) id VAA27453; Thu, 14 Sep 1995 21:15:23 +0200 (MET DST) From: Ollivier Robert Message-Id: <199509141915.VAA27453@keltia.Freenix.FR> Subject: Re: Is nullfs broken in -current? To: terry@lambert.org (Terry Lambert) Date: Thu, 14 Sep 1995 21:15:23 +0200 (MET DST) Cc: wollman@lcs.mit.edu, terry@lambert.org, current@freefall.freebsd.org In-Reply-To: <199509131752.KAA07769@phaeton.artisoft.com> from "Terry Lambert" at Sep 13, 95 10:52:16 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1085 X-Mailer: ELM [version 2.4 PL24 ME7a+] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: current-owner@FreeBSD.org Precedence: bulk It seems that Terry Lambert said: > > You are replacing the /usr/src vnode (potentially on cdrom) with the > /src/src vnode from a writeable media? My goal in this was to avoid the long directory names generated my make obj (i.e. having /src/src generate /usr/obj/src/src/* instead of /usr/obj/*) but the result is the same. > This seems more useful and applicable. Yep :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.Freenix.FR 2.2-CURRENT #1: Sun Sep 10 18:50:19 MET DST 1995 From owner-freebsd-current Thu Sep 14 13:30:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA21439 for current-outgoing; Thu, 14 Sep 1995 13:30:25 -0700 Received: from chemserv.umd.edu (chemserv.umd.edu [129.2.64.40]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA21426 for ; Thu, 14 Sep 1995 13:30:15 -0700 Received: from espresso.eng.umd.edu (espresso.eng.umd.edu [129.2.98.13]) by chemserv.umd.edu (8.7.Beta.14/8.7.Beta.14) with ESMTP id QAA01042; Thu, 14 Sep 1995 16:29:45 -0400 (EDT) Received: (chuckr@localhost) by espresso.eng.umd.edu (8.7.Beta.14/8.6.4) id QAA09755; Thu, 14 Sep 1995 16:29:44 -0400 (EDT) Date: Thu, 14 Sep 1995 16:29:43 -0400 (EDT) From: Chuck Robey To: "Ugen J.S.Antsilevich" cc: freebsd-current@freebsd.org Subject: Re: What is where... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Thu, 14 Sep 1995, Ugen J.S.Antsilevich wrote: > Hi guys..sorta lame question but forgive me, i was out of business for > so long: > > so i c the last released version was 2.0.5 > -stable = 2.1.0 > -current = 2.2.0 (???) > > So if i am going to write something and i want it into 2.1.0 release > i should put it into stable? OR there is not any development on stable? > If there is what's the policy of commits etc...? > If i put something in 2.2.0 (suppose for a minute, it works :^))) it is > going to be only there, right? Way I understand it, the idea is no new functionality in 2.1 (STABLE), just bug fixes. I think it's been violated, but only for stuff that's gone thru testing by sitting in 2.2 (CURRENT) for awhile, and even then, there's some argument. The idea is for the 2.1 release to approach the kind of reputation for reliability that our old, revered 1.1.5.1 release has. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Thu Sep 14 13:35:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA21643 for current-outgoing; Thu, 14 Sep 1995 13:35:37 -0700 Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA21637 for ; Thu, 14 Sep 1995 13:35:34 -0700 Received: from ugen (ugen-tr.worldbank.org [138.220.101.58]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id QAA00379; for ; Thu, 14 Sep 1995 16:33:45 -0400 Date: Thu, 14 Sep 95 16:32:38 PDT From: "Ugen J.S.Antsilevich" Subject: Re: What is where... To: "Ugen J.S.Antsilevich" , Chuck Robey Cc: freebsd-current@freebsd.org X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk The idea is for the 2.1 release to approach the >kind of reputation for reliability that our old, revered 1.1.5.1 release >has. Is that possible...ohh... i am dreamin about such a time...1.1.5.1 is far ahead froam all what happening now.. --Ugen From owner-freebsd-current Thu Sep 14 14:45:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA25220 for current-outgoing; Thu, 14 Sep 1995 14:45:20 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA25214 for ; Thu, 14 Sep 1995 14:45:18 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.6.11/8.6.11) with ESMTP id OAA23553 for ; Thu, 14 Sep 1995 14:44:50 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA19290 for ; Thu, 14 Sep 1995 23:25:17 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA17223 for freebsd-current@FreeBSD.org; Thu, 14 Sep 1995 23:25:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id WAA11000 for freebsd-current@FreeBSD.org; Thu, 14 Sep 1995 22:29:07 +0200 From: J Wunsch Message-Id: <199509142029.WAA11000@uriah.heep.sax.de> Subject: Re: What is where... To: freebsd-current@FreeBSD.org Date: Thu, 14 Sep 1995 22:29:05 +0200 (MET DST) Reply-To: freebsd-current@FreeBSD.org In-Reply-To: from "Ugen J.S.Antsilevich" at Sep 14, 95 09:57:34 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 777 Sender: current-owner@FreeBSD.org Precedence: bulk As Ugen J.S.Antsilevich wrote: > so i c the last released version was 2.0.5 > -stable = 2.1.0 > -current = 2.2.0 (???) Da. (Dobro, 2.2.0 is 2.2) > So if i am going to write something and i want it into 2.1.0 release You are not allowed. > i should put it into stable? OR there is not any development on stable? Yes, no more development, and only hand-selected bugfixes. > If i put something in 2.2.0 (suppose for a minute, it works :^))) it is > going to be only there, right? Yes. If it's clearly an important bugfix (or something harmless like documentation cleanup), send it to David Greenman for inclusion into 2.1. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Sep 14 15:44:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA28505 for current-outgoing; Thu, 14 Sep 1995 15:44:11 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA28499 for ; Thu, 14 Sep 1995 15:44:07 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA19250 for ; Thu, 14 Sep 1995 23:25:02 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA17217 for current@freefall.freebsd.org; Thu, 14 Sep 1995 23:25:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id XAA11305 for current@freefall.freebsd.org; Thu, 14 Sep 1995 23:12:01 +0200 From: J Wunsch Message-Id: <199509142112.XAA11305@uriah.heep.sax.de> Subject: Re: libforms - thumbs up or down? To: current@freefall.freebsd.org Date: Thu, 14 Sep 1995 23:12:00 +0200 (MET DST) Reply-To: current@freefall.freebsd.org In-Reply-To: <199509141501.QAA06224@server.netcraft.co.uk> from "Paul Richards" at Sep 14, 95 04:01:46 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 825 Sender: current-owner@FreeBSD.org Precedence: bulk As Paul Richards wrote: > > Well, someone's contacted me about using it so I'll let them decide where > they think it should go and what to do with it. As far as I'm concerned, > you can do what you want with it. Do you have an idea _how_ to fix it? Your last commit didn't get it back into a working state. I have no idea how it's supposed to work: i can find a (wrong wrt. -lncurses) prototype for draw_box(), but no actual implementation inside libforms. Hence the draw_box() from libncurses will be linked, which expects a totally different arg list. I'm stuck here since i've got no idea how it was _intented_ to work. (Btw., libncurses apparently lacks documentation.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Sep 14 16:46:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA03625 for current-outgoing; Thu, 14 Sep 1995 16:46:10 -0700 Received: from Wit401402.student.utwente.nl (Wit401402.student.utwente.nl [130.89.236.162]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA03614 for ; Thu, 14 Sep 1995 16:46:09 -0700 Received: (from alain@localhost) by Wit401402.student.utwente.nl (8.6.12/8.6.9) id BAA01451; Fri, 15 Sep 1995 01:45:49 +0200 Date: Fri, 15 Sep 1995 01:45:49 +0200 (MET DST) From: Alain Kalker Reply-To: A.C.P.M.Kalker@student.utwente.nl To: "Jordan K. Hubbard" cc: current@freefall.freebsd.org Subject: Re: Sound code: Anyone for -current code in 2.1? In-Reply-To: <324.810867210@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Mon, 11 Sep 1995, Jordan K. Hubbard wrote: > Well, I've proven to my satisfaction that the GUS MAX doesn't really > work correctly in 2.1-STABLE (at least not with `maplay', at it's > documented as broken in 2.1's LINT) so I just need to know whether or > not all the soundblaster et al users out there are happier with the > -current sound code, or the 2.1-STABLE stuff. > > If it's 2.1-STABLE then I'll bow to the needs of the many and take a > broken GUS MAX for the time being. If it's 2.2, then I'll do the work > to integrate it into 2.1. You folks decide. Feedback please? > > Jordan > Please hold your horses! Ther may be coming a patch to fix the playing of stereo files on the GF1 chip (via /dev/dsp0) on the GUS/GUS MAX real soon now! --- Alain From owner-freebsd-current Thu Sep 14 16:53:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA04339 for current-outgoing; Thu, 14 Sep 1995 16:53:27 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA04330 for ; Thu, 14 Sep 1995 16:53:25 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id QAA06864; Thu, 14 Sep 1995 16:53:07 -0700 To: A.C.P.M.Kalker@student.utwente.nl cc: current@freefall.freebsd.org Subject: Re: Sound code: Anyone for -current code in 2.1? In-reply-to: Your message of "Fri, 15 Sep 1995 01:45:49 +0200." Date: Thu, 14 Sep 1995 16:53:07 -0700 Message-ID: <6862.811122787@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > Please hold your horses! Ther may be coming a patch to fix the playing of > stereo files on the GF1 chip (via /dev/dsp0) on the GUS/GUS MAX real soon > now! Uh.. Well, the v3.0.5 sound code is now part of 2.1! You caught me literally minutes after finishing with this message, but it's no big deal - if your fix works, we'll just add it to both branches! Thanks.. Jordan From owner-freebsd-current Thu Sep 14 23:16:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA26501 for current-outgoing; Thu, 14 Sep 1995 23:16:20 -0700 Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA26495 for ; Thu, 14 Sep 1995 23:16:18 -0700 Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.6.12) id XAA09169; Thu, 14 Sep 1995 23:16:15 -0700 Received: from localhost by newport.ece.uci.edu (8.6.12) id XAA00454; Thu, 14 Sep 1995 23:16:14 -0700 Message-Id: <199509150616.XAA00454@newport.ece.uci.edu> To: "Jordan K. Hubbard" cc: A.C.P.M.Kalker@student.utwente.nl, current@freefall.freebsd.org Subject: Re: Sound code: Anyone for -current code in 2.1? In-reply-to: Your message of "Thu, 14 Sep 1995 16:53:07 PDT." <6862.811122787@time.cdrom.com> Date: Thu, 14 Sep 1995 23:16:12 -0700 From: Steven Wallace Sender: owner-current@FreeBSD.org Precedence: bulk >> Please hold your horses! Ther may be coming a patch to fix the playing of >> stereo files on the GF1 chip (via /dev/dsp0) on the GUS/GUS MAX real soon >> now! > >Uh.. Well, the v3.0.5 sound code is now part of 2.1! You caught >me literally minutes after finishing with this message, but it's >no big deal - if your fix works, we'll just add it to both branches! The current sound code (and I think previous ones) have probs with /dev/dsp and /dev/audio devices for GUS MAX. GUS specific sound (e.g. gmod) works fine though. Also I have some initialization prob with my GUS 'cuz sometimes it comes up and it pretends to be playing but no volume. Steven From owner-freebsd-current Thu Sep 14 23:42:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA28519 for current-outgoing; Thu, 14 Sep 1995 23:42:12 -0700 Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA28513 for ; Thu, 14 Sep 1995 23:42:10 -0700 Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.6.12) id XAA09607; Thu, 14 Sep 1995 23:42:08 -0700 Received: from localhost by newport.ece.uci.edu (8.6.12) id XAA00631; Thu, 14 Sep 1995 23:42:06 -0700 Message-Id: <199509150642.XAA00631@newport.ece.uci.edu> To: Steven Wallace cc: "Jordan K. Hubbard" , A.C.P.M.Kalker@student.utwente.nl, current@freefall.freebsd.org Subject: Re: Sound code: Anyone for -current code in 2.1? In-reply-to: Your message of "Thu, 14 Sep 1995 23:16:12 PDT." <199509150616.XAA00454@newport.ece.uci.edu> Date: Thu, 14 Sep 1995 23:42:05 -0700 From: Steven Wallace Sender: owner-current@FreeBSD.org Precedence: bulk >The current sound code (and I think previous ones) have probs with >/dev/dsp and /dev/audio devices for GUS MAX. GUS specific sound >(e.g. gmod) works fine though. Also I have some initialization prob >with my GUS 'cuz sometimes it comes up and it pretends to be playing >but no volume. > >Steven I take back my statement. I just tried my -current kerenl and /dev/dsp and /dev/audio seem to be working fine. Only problem I'm having is with recording comes out garbled-like. I think I might have a really bad microphone or somethihng. I have been using an August kernel 'cuz -current gives me sig 4, 10, and 11's all the time (VM woes). Steven From owner-freebsd-current Fri Sep 15 05:15:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA22481 for current-outgoing; Fri, 15 Sep 1995 05:15:29 -0700 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA22467 ; Fri, 15 Sep 1995 05:15:25 -0700 Received: from wup-gate.UUCP (uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) with UUCP id OAA23980; Fri, 15 Sep 1995 14:14:57 +0200 Received: from wup.de by wup-gate with smtp (Smail3.1.28.1 #2) id m0stZjE-0007rLC; Fri, 15 Sep 95 14:18 MET DST Received: from sunny.wup.de by wup.de (4.1/SMI-4.1) id AA19949; Fri, 15 Sep 95 14:09:18 +0200 Received: by sunny.wup.de (5.x/SMI-SVR4) id AA11185; Fri, 15 Sep 1995 14:12:12 +0200 Date: Fri, 15 Sep 1995 14:12:12 +0200 From: Andreas Klemm Message-Id: <9509151212.AA11185@sunny.wup.de> To: gibbs@freefall.FreeBSD.org Subject: Re: SCSI problems with FreeBSD 2.0.5 using AHA 2940 and Quantum Grand Prix Cc: larry@seminole.iag.net, jhk@freebsd.org, hackers@freebsd.org, current@freebsd.org X-Sun-Charset: US-ASCII Sender: owner-current@freebsd.org Precedence: bulk > > You should be running the driver in -stable if you have a grand > prix. The driver is most likely your problem. Well, I found the suitable sup file for stable and was surprised, that supping is relatively fast ... So I was able to build a new kernel this morning. Performance has increased a bit (bonnie benchmark), now I'll stress test the system a bit ... I'll let you hear, if it works. Looks good so far. Thanks for your great work and nice support. Andreas /// From owner-freebsd-current Fri Sep 15 06:07:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA27775 for current-outgoing; Fri, 15 Sep 1995 06:07:29 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA27770 for ; Fri, 15 Sep 1995 06:07:26 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id OAA19270 for current@freefall.freebsd.org; Fri, 15 Sep 1995 14:07:09 +0100 From: Paul Richards Message-Id: <199509151307.OAA19270@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: current@freefall.freebsd.org Date: Fri, 15 Sep 1995 14:07:08 +0100 (BST) In-Reply-To: <199509142112.XAA11305@uriah.heep.sax.de> from "J Wunsch" at Sep 14, 95 11:12:00 pm Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1056 Sender: owner-current@FreeBSD.org Precedence: bulk In reply to J Wunsch who said > > As Paul Richards wrote: > > > > Well, someone's contacted me about using it so I'll let them decide where > > they think it should go and what to do with it. As far as I'm concerned, > > you can do what you want with it. > > Do you have an idea _how_ to fix it? Your last commit didn't get it > back into a working state. I have no idea how it's supposed to work: > i can find a (wrong wrt. -lncurses) prototype for draw_box(), but no > actual implementation inside libforms. Hence the draw_box() from > libncurses will be linked, which expects a totally different arg list. > I'm stuck here since i've got no idea how it was _intented_ to work. My libncurses has no draw_box at all. Curses has a box() function, as does ncurses. I wonder if libncurses has been updated recently. My cvs tree doesn't have a draw_box either? Where's the draw_box code you're seeing? -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Fri Sep 15 09:28:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA19718 for current-outgoing; Fri, 15 Sep 1995 09:28:59 -0700 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA19711 for ; Fri, 15 Sep 1995 09:28:56 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id JAA23343 for ; Fri, 15 Sep 1995 09:28:47 -0700 Message-Id: <199509151628.JAA23343@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: current@FreeBSD.org Subject: rkinit added to eBones Date: Fri, 15 Sep 1995 09:28:47 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org Precedence: bulk I've just finished importing rkinit into the U.S. eBones of -current. Rkinit allows you to forward kerberos tickets securely so that you can remotely rlogin or telnet without having to type a password. For those of you who are going to use rkinit to pass tickets to non FreeBSD machines, just a few words of warning. The original rkinit didn't handle the case when multiple rkinit messages arived in a single packet. During one portion of the protocol, the client sends three messages back to back without requiring a response from the server. FreeBSD seems to always deliver these in one packet. The old rkinit would just hang at this point since the server would skip a portion of the protocol and close up shop. The version I imported includes a re-write of the main rpc routine to avoid this problem, but it still cannot work with the older, broken servers. The FreeBSD code will complain about the premature EOF so you can identify machines still running the old code. UC Berkeley, for example is still running the broken code, but I have submitted the patch to their Software Warehouse so that condition may change. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Fri Sep 15 09:59:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA22368 for current-outgoing; Fri, 15 Sep 1995 09:59:32 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA22350 for ; Fri, 15 Sep 1995 09:59:27 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id NAA20912 for current@freebsd.org; Fri, 15 Sep 1995 13:04:31 -0400 From: Mark Hittinger Message-Id: <199509151704.NAA20912@ns1.win.net> Subject: new pci setup on EISA box :-) To: current@freebsd.org Date: Fri, 15 Sep 1995 13:04:31 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 194 Sender: owner-current@freebsd.org Precedence: bulk The latest -current sup kernel as of 11 am eastern time today has an adjustment in the handling of the pci bus. Just FYI - it hangs on my EISA test box. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Fri Sep 15 10:51:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA25928 for current-outgoing; Fri, 15 Sep 1995 10:51:35 -0700 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA25920 for ; Fri, 15 Sep 1995 10:51:25 -0700 Received: (from uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) with UUCP id TAA09099 for current@freebsd.org; Fri, 15 Sep 1995 19:51:15 +0200 Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.6.11/8.6.9) with SMTP id QAA14861 for ; Sun, 10 Sep 1995 16:03:55 +0200 Date: Sun, 10 Sep 1995 16:03:55 +0200 (MET DST) From: Andreas Klemm To: current@freebsd.org Subject: Which SUP files are available and where ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi ! I'm currently supping the -current release using sup and the supfile /usr/share/FAQ/extras/standard-supfile. What source code do I get using this sup file ? Is this the _latest_ code oder the latest code from -STABLE ? Could someone please explain that to me ? I would like to sup both, the latest stable current-sources (if yuch a beast exists) and parts of the newest code ... Thanks Andreas /// Andreas Klemm You have lpd and need an intelligent print filter ?!! Ok, this might help: "apsfilter ... irgendwie clever" ftp it from ------> ftp://sunsite.unc.edu/pub/Linux/Incoming/aps-491.tgz From owner-freebsd-current Fri Sep 15 11:00:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA26438 for current-outgoing; Fri, 15 Sep 1995 11:00:18 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA26430 for ; Fri, 15 Sep 1995 11:00:14 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id NAA11569 for current@freebsd.org; Fri, 15 Sep 1995 13:53:18 -0400 From: Mark Hittinger Message-Id: <199509151753.NAA11569@ns1.win.net> Subject: Re: new pci setup on EISA box :-) (fwd) To: current@freebsd.org Date: Fri, 15 Sep 1995 13:53:18 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 849 Sender: owner-current@freebsd.org Precedence: bulk Re: new -current EISA hangs in pci probe: > Stefan Esser writes; > 1) Is this a PCI + EISA box, or pure EISA ? Pure EISA with above 16mb DMA bug > 2) Does it seem to find a PCI bus (though there is none) before hanging ? The last thing printed is the probe for NPX16 > 3) What exact version is this ($Id: line of the following files): > /sys/i386/isa/pcibus.c /sys/pci/pci.c /sys/pci/pcisupport.c pcibus.c, v 1.12 1995/09/14 20:27:31 pci/c, v 1/31 1995/09/14 23:24:29 pcisupport.c,v 1.22 1995/09/14 17:26:24 > Could you please add printf() statements... Will do this and report later in the day. > Sorry for the inconvenience No inconvenience - this is on a test box! The production boxes are running -stable and I'm a happy FreeBSD camper. Regards, Mark Hittinger Internet Manager WinNET Communications, Inc. bugs@win.net From owner-freebsd-current Fri Sep 15 11:25:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA28621 for current-outgoing; Fri, 15 Sep 1995 11:25:35 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA28614 for ; Fri, 15 Sep 1995 11:25:18 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id OAA18272; Fri, 15 Sep 1995 14:17:02 -0400 Date: Fri, 15 Sep 1995 14:17:02 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: Which SUP files are available and where ? To: Andreas Klemm cc: current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sun, 10 Sep 1995, Andreas Klemm wrote: > Hi ! > > I'm currently supping the -current release using sup and the > supfile /usr/share/FAQ/extras/standard-supfile. > > What source code do I get using this sup file ? Is this the > _latest_ code oder the latest code from -STABLE ? -current is the leading bleeding edge. beware of sig 11's will become 2.2 -stable is looking real good. a 1.1.5.1 quality release will become 2.1 sup -stable using supfile-stable Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Fri Sep 15 11:50:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA29329 for current-outgoing; Fri, 15 Sep 1995 11:50:52 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA29312 for ; Fri, 15 Sep 1995 11:50:47 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA26611; Fri, 15 Sep 1995 20:50:31 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA26443; Fri, 15 Sep 1995 20:50:31 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id UAA21610; Fri, 15 Sep 1995 20:12:11 +0200 From: J Wunsch Message-Id: <199509151812.UAA21610@uriah.heep.sax.de> Subject: Re: libforms - thumbs up or down? To: paul@FreeBSD.org Date: Fri, 15 Sep 1995 20:12:10 +0200 (MET DST) Cc: current@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199509151307.OAA19270@server.netcraft.co.uk> from "Paul Richards" at Sep 15, 95 02:07:08 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1034 Sender: owner-current@FreeBSD.org Precedence: bulk yes As Paul Richards wrote: > > My libncurses has no draw_box at all. Curses has a box() function, as does > ncurses. Sorry, libdialog was it actually: j@uriah 520% nm /usr/lib/libdialog.a | fgrep draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box U _draw_box 00000a00 T _draw_box j@uriah 521% fgrep draw_box /usr/include/dialog.h void draw_box(WINDOW *win, int y, int x, int height, int width,\ ^^^^^^^^^^^^^^^^^^^^^^^^^^^... chtype box, chtype border); j@uriah 522% fgrep draw_box /tmp/libforms/*.[ch] /tmp/libforms/forms.c: {"draw_box", &draw_box}, /tmp/libforms/forms.h:void draw_box(OBJECT *); ^^^^^^^^^^^^^^^^^^ /tmp/libforms/ncurses.c:ncurses_draw_box(OBJECT *object) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Sep 15 12:56:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA01334 for current-outgoing; Fri, 15 Sep 1995 12:56:30 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA01329 for ; Fri, 15 Sep 1995 12:56:20 -0700 Received: (from root@localhost) by ns1.win.net (8.6.11/8.6.9) id QAA13126 for current@freebsd.org; Fri, 15 Sep 1995 16:02:03 -0400 From: Mark Hittinger Message-Id: <199509152002.QAA13126@ns1.win.net> Subject: re: more EISA pci probe hang info To: current@freebsd.org Date: Fri, 15 Sep 1995 16:02:02 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1539 Sender: owner-current@freebsd.org Precedence: bulk More info on pci probe hang on pure EISA box: It doesn't do it every time. Starting out with a powered off/then on sequence seems to increase the probability of a hang. If you reboot without powering off the hang doesn't occur as often. This is with several iterations. I have an ep0 at 0x2000 and an ahc1 at 0x4000. I've seen the ep0 device act weird with FreeBSD probes before. I put in printfs and got "past probe 2" every time but on a hang did not see the "past conf1_enable_res2" printf. So the hang is somewhere in the code below. Strangely enough when I put printf's between the inl/outl instructions I cannot cause a hang. I have run out of time today to fool with this but I wanted to pass the information along in case it narrows the scope of the problem down. I will be able to play with this more tommorrow. Stefan sent me some patches I will try those tommorrow also. pcibus.c: printf("Past probe 2\n") ; /*----------------------------------------------------- ** Well, is it Configuration mode 1, after all ? **----------------------------------------------------- */ oldval = inl (CONF1_ADDR_PORT); outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK2); result = inl (CONF1_ADDR_PORT); outl (CONF1_ADDR_PORT, oldval); if (result == CONF1_ENABLE_RES2) { pci_mechanism = 1; pci_maxdevice = 32; if (pcibus_check()) { return; } } printf("Past CONF1_ENABLE_RES2\n") ; Regards, Mark Hittinger Internet Manager WinNET Communications, Inc. bugs@win.net From owner-freebsd-current Fri Sep 15 13:21:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA02212 for current-outgoing; Fri, 15 Sep 1995 13:21:48 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA02207 for ; Fri, 15 Sep 1995 13:21:42 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA01692; Fri, 15 Sep 1995 13:20:36 -0700 From: Terry Lambert Message-Id: <199509152020.NAA01692@phaeton.artisoft.com> Subject: Re: new pci setup on EISA box :-) (fwd) To: bugs@ns1.win.net (Mark Hittinger) Date: Fri, 15 Sep 1995 13:20:36 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199509151753.NAA11569@ns1.win.net> from "Mark Hittinger" at Sep 15, 95 01:53:18 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 660 Sender: owner-current@FreeBSD.org Precedence: bulk > Re: new -current EISA hangs in pci probe: > > > Stefan Esser writes; > > 1) Is this a PCI + EISA box, or pure EISA ? > > Pure EISA with above 16mb DMA bug FYI: The EISA spec requires DMA above 16M to work correctly. If your EISA box doesn't do this, it's not an EISA box. Period. The connectors do not define EISA, the spec does. I'm betting this is a NiCE or other motherboard with a HiNT chipset. I think you will have to build a new kernel to work around the problem (by forcing the use of bounce buffers). 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-current Fri Sep 15 13:47:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA03404 for current-outgoing; Fri, 15 Sep 1995 13:47:00 -0700 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA03390 for ; Fri, 15 Sep 1995 13:46:45 -0700 Received: by Sysiphos id AA10991 (5.67b/IDA-1.5 for current@freebsd.org); Fri, 15 Sep 1995 22:46:36 +0200 Message-Id: <199509152046.AA10991@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 15 Sep 1995 22:46:35 +0200 In-Reply-To: Mark Hittinger "re: more EISA pci probe hang info" (Sep 15, 16:02) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Mark Hittinger Subject: re: more EISA pci probe hang info Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk On Sep 15, 16:02, Mark Hittinger wrote: } Subject: re: more EISA pci probe hang info } More info on pci probe hang on pure EISA box: } } It doesn't do it every time. Starting out with a powered off/then on } sequence seems to increase the probability of a hang. If you reboot } without powering off the hang doesn't occur as often. This is with } several iterations. I have an ep0 at 0x2000 and an ahc1 at 0x4000. } I've seen the ep0 device act weird with FreeBSD probes before. } } I put in printfs and got "past probe 2" every time but on a hang did } not see the "past conf1_enable_res2" printf. So the hang is somewhere } in the code below. The hang is most probably in pcibus_check(), invoked only after the correct value (CONF1_ENABLE_RES2) has been read back from the CONF1_ADDR_PORT. Seems that your system returns the last value written to any address, in case there is no I/O device driving the data lines at the inl() ... } Strangely enough when I put printf's between the inl/outl instructions } I cannot cause a hang. I have run out of time today to fool with this } but I wanted to pass the information along in case it narrows the scope } of the problem down. I will be able to play with this more tommorrow. Well, I was afraid, that the second loop was causing the problem (though I couldn't understand how). But now I understand, what's going on and I know how to solve it. } Stefan sent me some patches I will try those tommorrow also. Knowing what's going on, I'll send a different patch later today ... } printf("Past probe 2\n") ; } /*----------------------------------------------------- } ** Well, is it Configuration mode 1, after all ? } **----------------------------------------------------- } */ } oldval = inl (CONF1_ADDR_PORT); } outl (CONF1_ADDR_PORT, CONF1_ENABLE_CHK2); } result = inl (CONF1_ADDR_PORT); Seems that the previously written value is either read back from some latch or has been held stored due to the bus line capacities. The EISA system for sure doesn't have any I/O port at address 0x0cf8 (CONF1_ADDR_PORT). } outl (CONF1_ADDR_PORT, oldval); } } if (result == CONF1_ENABLE_RES2) { } pci_mechanism = 1; } pci_maxdevice = 32; } if (pcibus_check()) } { } return; } } } } } printf("Past CONF1_ENABLE_RES2\n") ; Thanks a lot for doing those tests ! Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/staff/esser/esser.html From owner-freebsd-current Fri Sep 15 13:52:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA03589 for current-outgoing; Fri, 15 Sep 1995 13:52:55 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA03582 for ; Fri, 15 Sep 1995 13:52:51 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id QAA06743 for current@freebsd.org; Fri, 15 Sep 1995 16:58:22 -0400 From: Mark Hittinger Message-Id: <199509152058.QAA06743@ns1.win.net> Subject: Re: new pci setup on EISA box :-) (fwd) To: current@freebsd.org Date: Fri, 15 Sep 1995 16:58:20 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 994 Sender: owner-current@freebsd.org Precedence: bulk > From: Terry Lambert > > Pure EISA with above 16mb DMA bug > I think you will have to build a new kernel to work around the problem > (by forcing the use of bounce buffers). I've been using bounce buffers on this box since around December when the box became a FreeBSD box. It tripped me up then and the list was very helpful about telling me where the problem was. The box serves as a testbed for our Internet services in the -current environment. I test the web servers, the uucp servers, inn, ect on -current because someday -current will be -stable.....or maybe -performance? :-) It has been doing ok up until recently. The sig 11 thing is outstanding and now the pci probe seems to have a glitch. I am not complaining or demanding an instant fix or anything. Just trying to be in a helpful FYI mode here. Some of my hardware does suck, but that is why it is the test box :-) Regards, Mark Hittinger Internet Manager WinNET Communications, Inc. bugs@win.net From owner-freebsd-current Fri Sep 15 14:26:38 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA05653 for current-outgoing; Fri, 15 Sep 1995 14:26:38 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA05645 for ; Fri, 15 Sep 1995 14:26:34 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id OAA05181; Fri, 15 Sep 1995 14:23:57 -0700 Message-Id: <199509152123.OAA05181@precipice.shockwave.com> To: "Jonathan M. Bresler" cc: Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Fri, 15 Sep 1995 14:17:02 EDT." Date: Fri, 15 Sep 1995 14:23:56 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk I thought a couple of people were reporting sig 11 problems on -stable. Is it true that there are NO sig 11 problems that we're aware of? Paul From: "Jonathan M. Bresler" Subject: Re: Which SUP files are available and where ? On Sun, 10 Sep 1995, Andreas Klemm wrote: > Hi ! > > I'm currently supping the -current release using sup and the > supfile /usr/share/FAQ/extras/standard-supfile. > > What source code do I get using this sup file ? Is this the > _latest_ code oder the latest code from -STABLE ? -current is the leading bleeding edge. beware of sig 11's will become 2.2 -stable is looking real good. a 1.1.5.1 quality release will become 2.1 sup -stable using supfile-stable Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. >> FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Fri Sep 15 14:53:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA08020 for current-outgoing; Fri, 15 Sep 1995 14:53:21 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA08005 for ; Fri, 15 Sep 1995 14:53:16 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA17570; Fri, 15 Sep 1995 15:55:10 -0600 Date: Fri, 15 Sep 1995 15:55:10 -0600 From: Nate Williams Message-Id: <199509152155.PAA17570@rocky.sri.MT.net> To: Paul Traina Cc: current@freebsd.org Subject: Re: Which SUP files are available and where ? In-Reply-To: <199509152123.OAA05181@precipice.shockwave.com> References: <199509152123.OAA05181@precipice.shockwave.com> Sender: owner-current@freebsd.org Precedence: bulk Paul Traina writes: > I thought a couple of people were reporting sig 11 problems on -stable. > Is it true that there are NO sig 11 problems that we're aware of? AFAIK, all of the problems have been reported in -current. Nate From owner-freebsd-current Fri Sep 15 15:08:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA10503 for current-outgoing; Fri, 15 Sep 1995 15:08:24 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA10488 for ; Fri, 15 Sep 1995 15:08:13 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id PAA02087; Fri, 15 Sep 1995 15:06:58 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id PAA02115; Fri, 15 Sep 1995 15:09:15 -0700 Message-Id: <199509152209.PAA02115@corbin.Root.COM> To: Paul Traina cc: "Jonathan M. Bresler" , Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Fri, 15 Sep 95 14:23:56 PDT." <199509152123.OAA05181@precipice.shockwave.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 15 Sep 1995 15:08:58 -0700 Sender: owner-current@freebsd.org Precedence: bulk >I thought a couple of people were reporting sig 11 problems on -stable. >Is it true that there are NO sig 11 problems that we're aware of? There are no known reliability problems with -stable. All of the people that I'm aware of that reported (any sort of) problems have since figured out what was causing them and have fixed them. There was one bug which Rod found that was causing a "CMAP busy" panic, but this isn't a new problem and has been with us since last year. It is caused by an attempt to read from /dev/kmem in an area that has no currently mapped page. This results in a page fault and subsequantly messed up 'CMAP' page table entry. The problem will normally only be seen when you have an out of date /var/db/kvm_kernel.foo.db file. It only happens at boot time and it's actually quite rare. -DG From owner-freebsd-current Fri Sep 15 15:37:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA12478 for current-outgoing; Fri, 15 Sep 1995 15:37:49 -0700 Received: from mozart.american.com (mozart.american.com [204.253.96.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA12473 for ; Fri, 15 Sep 1995 15:37:45 -0700 Received: from localhost (localhost [127.0.0.1]) by mozart.american.com (8.6.12/8.6.9) with SMTP id SAA19750; Fri, 15 Sep 1995 18:37:05 -0400 Message-Id: <199509152237.SAA19750@mozart.american.com> X-Authentication-Warning: mozart.american.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.5.3 12/28/94 To: jdl@chromatic.com cc: current@freebsd.org Subject: Re: more ATAPI CD issues In-reply-to: Your message of "Wed, 13 Sep 1995 22:59:26 CDT." <199509140359.WAA02589@chrome.onramp.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Sep 1995 18:37:04 -0400 From: Josh Littlefield Sender: owner-current@freebsd.org Precedence: bulk >> The 3 trials of ATA you must pass are 1) writable byte count / cyl. address >> registers, >> >> The first test is reasonable, for what its worth. > > Hmm. Not sure I agree here. My POS NEC 260 fails this test badly. > Not sure why. I (w)hacked it out to get even vague functionality... Wow. Writable byte count registers are pretty much mandatory for atapi to work at all, since they are the way of communicating ATAPI packet sizes and data lengths. The best explanation I can think of is that this is not really a good test. I'm not sure there is really any guarantee that this register will read the same as its written. For ATAPI, one writes it to indicate the size of data desired to be read or written. One reads it AFTER SENDING A PACKET COMMAND, and when BSY is gone to find out about the subsequent device needs for data transfer. Even the length of time the register is supposed to contain info the device has generated is only until the first data register access. Other parts of the spec indicate that the device should place its "signature" (0xEB14) in the cnt_hi/lo registers and maintain it until the first ATAPI command is recieved, which might explain the need to generalize this test to checking for != 0xFF after the write. All in all, sounds like a bogus "test". > Hmm.. You may need Serge's latest and greates patch that I alude to above. > With minor work, I could dredge this up for you if you don't have it. I don't have this, and it doesn't appear that -current does either. Could you send it? >From some behavior I've noticed where the drive gets stuck in an aborted command state (and stays there across a reboot), I'm wondering why there appears to be no code which ever issues an ATAPI SRST command. Seems like that might be a good thing to do, both initially during probe or attach, and maybe also during ioctl reset. -josh ======================================================================== Josh Littlefield American Internet Corporation josh@american.com 4 Preston Court tel: 617-271-9200 fax: 617-275-4930 Bedford, MA 01730-2334 From owner-freebsd-current Fri Sep 15 15:59:50 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA13237 for current-outgoing; Fri, 15 Sep 1995 15:59:50 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA13232 for ; Fri, 15 Sep 1995 15:59:46 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id SAA25481; Fri, 15 Sep 1995 18:52:05 -0400 Date: Fri, 15 Sep 1995 18:52:03 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: Which SUP files are available and where ? To: Paul Traina cc: Andreas Klemm , current@freebsd.org In-Reply-To: <199509152123.OAA05181@precipice.shockwave.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Fri, 15 Sep 1995, Paul Traina wrote: > I thought a couple of people were reporting sig 11 problems on -stable. > Is it true that there are NO sig 11 problems that we're aware of? > > Paul i have been running -stable for 4 days now, doing a sup and make world everyday as well as my usual activity. i have not had a sig 11 during this entire time. period. -stable looks to be the release that will replace the 1.1.5.1 boxes that i still have running here. (in addition to the 2.0, 2.0.5 etc) jmb > > From: "Jonathan M. Bresler" > Subject: Re: Which SUP files are available and where ? > On Sun, 10 Sep 1995, Andreas Klemm wrote: > > > Hi ! > > > > I'm currently supping the -current release using sup and the > > supfile /usr/share/FAQ/extras/standard-supfile. > > > > What source code do I get using this sup file ? Is this the > > _latest_ code oder the latest code from -STABLE ? > > -current is the leading bleeding edge. beware of sig 11's > will become 2.2 > > -stable is looking real good. a 1.1.5.1 quality release > will become 2.1 > > sup -stable using supfile-stable > > > Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. > >> > FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy > play go. | Arlington, VA 22202 > ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 > > Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Fri Sep 15 16:05:09 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13475 for current-outgoing; Fri, 15 Sep 1995 16:05:09 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13468 for ; Fri, 15 Sep 1995 16:05:04 -0700 Received: by haven.uniserve.com id <30749>; Fri, 15 Sep 1995 16:06:40 +0100 Date: Fri, 15 Sep 1995 16:06:37 -0700 (PDT) From: Tom Samplonius To: "Jonathan M. Bresler" cc: Paul Traina , Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Fri, 15 Sep 1995, Jonathan M. Bresler wrote: > i have been running -stable for 4 days now, doing a sup and make > world everyday as well as my usual activity. i have not had a sig 11 > during this entire time. period. > > -stable looks to be the release that will replace the 1.1.5.1 > boxes that i still have running here. (in addition to the 2.0, 2.0.5 etc) Ok, if this is the general consensus, when will 2.1 be available? Tom From owner-freebsd-current Fri Sep 15 16:08:47 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13602 for current-outgoing; Fri, 15 Sep 1995 16:08:47 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13594 for ; Fri, 15 Sep 1995 16:08:45 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id QAA06428; Fri, 15 Sep 1995 16:06:26 -0700 Message-Id: <199509152306.QAA06428@precipice.shockwave.com> To: davidg@Root.COM cc: "Jonathan M. Bresler" , Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Fri, 15 Sep 1995 15:08:58 PDT." <199509152209.PAA02115@corbin.Root.COM> Date: Fri, 15 Sep 1995 16:06:25 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk Thanks for the update, ok, then one of my machines is going to switch over to -stable. Paul From: David Greenman Subject: Re: Which SUP files are available and where ? >I thought a couple of people were reporting sig 11 problems on -stable. >Is it true that there are NO sig 11 problems that we're aware of? There are no known reliability problems with -stable. All of the people that I'm aware of that reported (any sort of) problems have since figured out what was causing them and have fixed them. There was one bug which Rod found that was causing a "CMAP busy" panic, but this isn't a new problem and has been with us since last year. It is caused by an attempt to read from /dev/kmem in an area that has no currently mapped page. This results in a page fault and subsequantly messed up 'CMAP' page table entry. The problem will normally only be seen when you have an out of date /var/db/kvm_kernel.foo.db file. It only happens at boot time and it's actuall >>y quite rare. -DG From owner-freebsd-current Fri Sep 15 16:09:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13678 for current-outgoing; Fri, 15 Sep 1995 16:09:41 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13673 for ; Fri, 15 Sep 1995 16:09:38 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id TAA25740; Fri, 15 Sep 1995 19:01:45 -0400 Date: Fri, 15 Sep 1995 19:01:43 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: Which SUP files are available and where ? To: Tom Samplonius cc: Paul Traina , Andreas Klemm , current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Fri, 15 Sep 1995, Tom Samplonius wrote: > > On Fri, 15 Sep 1995, Jonathan M. Bresler wrote: > > > i have been running -stable for 4 days now, doing a sup and make > > world everyday as well as my usual activity. i have not had a sig 11 > > during this entire time. period. > > > > -stable looks to be the release that will replace the 1.1.5.1 > > boxes that i still have running here. (in addition to the 2.0, 2.0.5 etc) > > Ok, if this is the general consensus, when will 2.1 be available? now, if you use sup ;) Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 ps. i sent the previous mail at 18:55 and receive tom's response at 18:57. now that's what i call a mailing list ;))))))) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by kryten.atinc.com (8.6.10/8.3) with ESMTP id SAA25716; Fri, 15 Sep 1995 18:57:41 -0400 Received: by haven.uniserve.com id <30749>; Fri, 15 Sep 1995 16:06:40 +0100 Date: Fri, 15 Sep 1995 16:06:37 -0700 (PDT) Sender: Tom Samplonius From: Tom Samplonius To: "Jonathan M. Bresler" cc: Paul Traina , Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From owner-freebsd-current Fri Sep 15 16:16:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13960 for current-outgoing; Fri, 15 Sep 1995 16:16:16 -0700 Received: from chrome.onramp.net (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13947 for ; Fri, 15 Sep 1995 16:16:13 -0700 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.onramp.net (8.6.11/8.6.9) with SMTP id SAA08077; Fri, 15 Sep 1995 18:15:22 -0500 Message-Id: <199509152315.SAA08077@chrome.onramp.net> X-Authentication-Warning: chrome.onramp.net: Host localhost.jdl.com didn't use HELO protocol To: Josh Littlefield cc: current@freebsd.org Subject: More ATAPI CD issues, and some old ones too! In-reply-to: Your message of "Fri, 15 Sep 1995 18:37:04 EDT." <199509152237.SAA19750@mozart.american.com> Reply-To: jdl@chromatic.com Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Fri, 15 Sep 1995 18:15:22 -0500 From: Jon Loeliger Sender: owner-current@freebsd.org Precedence: bulk Apparently, Josh Littlefield scribbled: > > Hmm. Not sure I agree here. My POS NEC 260 fails this test badly. > > Not sure why. I (w)hacked it out to get even vague functionality... > > Wow. Writable byte count registers are pretty much mandatory for atapi to > work at all, since they are the way of communicating ATAPI packet sizes and > data lengths. Yea, I believe it is writable, but... > The best explanation I can think of is that this is not really a good test. Right. > I'm not sure there is really any guarantee that this register will read the > same as its written. For ATAPI, one writes it to indicate the size of data > desired to be read or written. One reads it AFTER SENDING A PACKET COMMAND, > and when BSY is gone to find out about the subsequent device needs for data > transfer. Even the length of time the register is supposed to contain info > the device has generated is only until the first data register access. > > Other parts of the spec indicate that the device should place its "signature" > > (0xEB14) in the cnt_hi/lo registers and maintain it until the first ATAPI > command is recieved, which might explain the need to generalize this test to > checking for != 0xFF after the write. All in all, sounds like a bogus "test" >. And in hackers, Bruce added to the fray: > jdl wrote: > >So who can tell me any details about that lovely weak check for R/W > >registers that appears to be failing for me? Simple things like: > > > - Is this a valid register for a CDROM drive too? Ie, is this check > > tacitly assuming a hard disk beneath it? > > - Is it subject to timing problems? > > - It *claims* to be "too weak", however it appears to be too strong! > > It's too weak for ST506...EIDE controllers with normal drives attached. > These all have read/write registers, so the inb() should return what > was written. That used to be tested for, but someone weakened the > test without documenting why. I don't know what happens for CDROM > drives. > > The point of the test is to attempt to limit the damage if there is > a device other than an ST506...EIDE controller behind the port. It > is far too weak for that (if 0xff wasn't so magic, then the test > would have much less than a 1/256 chance of detecting conflicts). > Even if it tested for `== 0xa5', then any device with a read/write > port at the probed address would pass the test. > > The test is very sloppy. It should do something like: > > int > is_rw_port(port) > u_int_port; > { > u_char in1, in2, was; > > DELAY(5); > was = inb(port); > DELAY(5); > outb(port, 0xa5); > DELAY(5); > (void)inb(0x20); /* attempt to eliminate bus echoes */ > DELAY(5); > in1 = inb(port); > DELAY(5); > outb(port, 0x5a); > DELAY(5); > (void)inb(0x20); > DELAY(5); > in2 = inb(port); > DELAY(5); > outb(port, was); > DELAY(5); > return (in1 == 0xa5 && in2 == 0x5a); > } > ... > if (!is_rw_port(du->dk_port + wd_cyl_lo)) > goto nodevice; > > Then the test would be stronger and your CDROM would be sure to fail :-). Leave it Bruce to be succinct on that final point... :-) So, I'm not sure what to do there yet... If this suddenly clears up, feel free to let me know! Also, it appears that the NEC-260 might have been available before the spec gelled, so I'm apt to expect it to be a tad out of spec with respect to the ATAPI spec. > > Hmm.. You may need Serge's latest and greates patch that I alude to above. > > With minor work, I could dredge this up for you if you don't have it. > > I don't have this, and it doesn't appear that -current does either. Could > you send it? Check. Sent separately to only Josh. If this should be commited, we need to find a committer for it.... Serge may have it wrapped and ready to go too. Dunno. > >From some behavior I've noticed where the drive gets stuck in an aborted > command state (and stays there across a reboot), Ick. Maybe that's part of the reason for the "reset test"? jdl From owner-freebsd-current Fri Sep 15 16:21:57 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA14300 for current-outgoing; Fri, 15 Sep 1995 16:21:57 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA14294 for ; Fri, 15 Sep 1995 16:21:54 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id QAA02195; Fri, 15 Sep 1995 16:20:41 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id QAA00165; Fri, 15 Sep 1995 16:22:59 -0700 Message-Id: <199509152322.QAA00165@corbin.Root.COM> To: Tom Samplonius cc: current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Fri, 15 Sep 95 16:06:37 PDT." From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 15 Sep 1995 16:22:58 -0700 Sender: owner-current@freebsd.org Precedence: bulk > >On Fri, 15 Sep 1995, Jonathan M. Bresler wrote: > >> i have been running -stable for 4 days now, doing a sup and make >> world everyday as well as my usual activity. i have not had a sig 11 >> during this entire time. period. >> >> -stable looks to be the release that will replace the 1.1.5.1 >> boxes that i still have running here. (in addition to the 2.0, 2.0.5 etc) > > Ok, if this is the general consensus, when will 2.1 be available? "Soon". It's looking very good indeed. -DG From owner-freebsd-current Fri Sep 15 17:09:57 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17236 for current-outgoing; Fri, 15 Sep 1995 17:09:57 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA17222 for ; Fri, 15 Sep 1995 17:09:50 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA12149; Fri, 15 Sep 1995 17:07:54 -0700 To: Josh Littlefield cc: jdl@chromatic.com, current@freebsd.org Subject: Re: more ATAPI CD issues In-reply-to: Your message of "Fri, 15 Sep 1995 18:37:04 EDT." <199509152237.SAA19750@mozart.american.com> Date: Fri, 15 Sep 1995 17:07:54 -0700 Message-ID: <12146.811210074@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > > Hmm.. You may need Serge's latest and greates patch that I alude to above. > > With minor work, I could dredge this up for you if you don't have it. > > I don't have this, and it doesn't appear that -current does either. Could yo u > send it? I just uploaded it to freefall.freebsd.org's incoming directory: ftp://freefall.freebsd.org/incoming/wcd13.tgz Jordan From owner-freebsd-current Fri Sep 15 17:13:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17421 for current-outgoing; Fri, 15 Sep 1995 17:13:05 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA17414 for ; Fri, 15 Sep 1995 17:12:59 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id RAA12160; Fri, 15 Sep 1995 17:09:25 -0700 To: Tom Samplonius cc: "Jonathan M. Bresler" , Paul Traina , Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Fri, 15 Sep 1995 16:06:37 PDT." Date: Fri, 15 Sep 1995 17:09:25 -0700 Message-ID: <12158.811210165@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > Ok, if this is the general consensus, when will 2.1 be available? Stock reply: October Developer's reply: "When it's ready, darn it!" :) Jordan From owner-freebsd-current Fri Sep 15 17:15:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA17631 for current-outgoing; Fri, 15 Sep 1995 17:15:55 -0700 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA17622 for ; Fri, 15 Sep 1995 17:15:51 -0700 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA04574; Sat, 16 Sep 95 02:18:42 +0100 Date: Sat, 16 Sep 95 02:18:42 +0100 Message-Id: <9509160118.AA04574@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: freebsd-current@freebsd.org Subject: SCSI bug (possibly in the ncr driver) X-Mailer: Emacs Sender: owner-current@freebsd.org Precedence: bulk I get the following message whenever I do a msf play command on my cdroms: cd1(ncr0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB or cd0(ncr0:3:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB Since the scsi code has not changed recently, and since I never had such errors with an adaptec, I conclude that there is a problem with my ncr driver... Curiously the other cdrom commands work correctly. I also get this error with a -stable kernel. Jean-Marc /kernel: FreeBSD 2.2-CURRENT #3: Tue Sep 12 00:40:58 MET DST 1995 /kernel: jmz@qix:/u3/src/sys/compile/QIX /kernel: CPU: 90-MHz Pentium 735\90 (Pentium-class CPU) /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 /kernel: Features=0x1bf /kernel: real memory = 16777216 (16384K bytes) /kernel: avail memory = 14819328 (14472K bytes) /kernel: Probing for devices on the ISA bus: /kernel: sc0 at 0x60-0x6f irq 1 on motherboard /kernel: sc0: VGA color <8 virtual consoles, flags=0x0> /kernel: ed0 not found at 0x280 /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa /kernel: sio0: type 16550A /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa /kernel: sio1: type 16550A /kernel: lpt0 at 0x378-0x37f irq 7 on isa /kernel: lpt0: Interrupt-driven port /kernel: lp0: TCP/IP capable interface /kernel: lpt1 not found at 0xffffffff /kernel: lpt2 not found at 0xffffffff /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa /kernel: fdc0: NEC 72065B /kernel: fd0: 1.44MB 3.5in /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa /kernel: wdc0: unit 0 (wd0): /kernel: wd0: 234MB (479349 sectors), 723 cyls, 13 heads, 51 S/T, 512 B/S /kernel: aha0 not found at 0x330 /kernel: pas0 at 0x388 irq 10 drq 6 on isa /kernel: pas0: /kernel: sb0 at 0x220 irq 5 drq 1 on isa /kernel: sb0: /kernel: opl0 at 0x388 on isa /kernel: opl0: /kernel: npx0 on motherboard /kernel: npx0: INT 16 interface /kernel: joy0 at 0x201 on isa /kernel: joy0: joystick /kernel: Probing for devices on the pci0 bus: /kernel: chip0 rev 1 on pci0:0 /kernel: chip1 rev 2 on pci0:7 /kernel: vga0 rev 0 int a irq 12 on pci0:9 /kernel: ncr0 rev 2 int a irq 11 on pci0:10 /kernel: (ncr0:0:0): "MICROP 4110-09TBCU0322J HT01" type 0 fixed SCSI 2 /kernel: sd0(ncr0:0:0): Direct-Access /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. /kernel: 1002MB (2053880 512 byte sectors) /kernel: (ncr0:1:0): "MICROP 2210-09MQ1001901 HQ30" type 0 fixed SCSI 2 /kernel: sd1(ncr0:1:0): Direct-Access /kernel: sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. /kernel: 1008MB (2065250 512 byte sectors) /kernel: (ncr0:2:0): "WANGTEK 5150ES SCSI ES41 B170" type 1 removable SCSI 1 /kernel: st0(ncr0:2:0): Sequential-Access density code 0x10, drive empty /kernel: (ncr0:3:0): "SONY CD-ROM CDU-8003A 1.9a" type 5 removable SCSI 2 /kernel: cd0(ncr0:3:0): CD-ROM /kernel: cd0(ncr0:3:0): 250ns (4 Mb/sec) offset 8. /kernel: cd present.[303666 x 2048 byte records] /kernel: (ncr0:4:0): "QUANTUM LIGHTNING 540S 241E" type 0 fixed SCSI 2 /kernel: sd2(ncr0:4:0): Direct-Access /kernel: sd2(ncr0:4:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. /kernel: 525MB (1075649 512 byte sectors) /kernel: (ncr0:5:0): "SONY CD-ROM CDU-55S 1.0f" type 5 removable SCSI 2 /kernel: cd1(ncr0:5:0): CD-ROM /kernel: cd1(ncr0:5:0): 275ns (4 Mb/sec) offset 8. /kernel: /kernel: cd1(ncr0:5:0): UNIT ATTENTION asc:28,0 /kernel: cd1(ncr0:5:0): Not ready to ready transition, medium may have changed /kernel: cd present.[400000 x 2048 byte records] _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-current Fri Sep 15 18:42:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA23800 for current-outgoing; Fri, 15 Sep 1995 18:42:03 -0700 Received: from chrome.onramp.net (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA23795 for ; Fri, 15 Sep 1995 18:42:01 -0700 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.onramp.net (8.6.11/8.6.9) with SMTP id UAA08655; Fri, 15 Sep 1995 20:41:10 -0500 Message-Id: <199509160141.UAA08655@chrome.onramp.net> X-Authentication-Warning: chrome.onramp.net: Host localhost.jdl.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@freebsd.org Subject: Re: more ATAPI CD issues In-reply-to: Your message of "Fri, 15 Sep 1995 17:07:54 PDT." <12146.811210074@time.cdrom.com> Reply-To: jdl@chromatic.com Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Fri, 15 Sep 1995 20:41:10 -0500 From: Jon Loeliger Sender: owner-current@freebsd.org Precedence: bulk Apparently, "Jordan K. Hubbard" scribbled: > > > Hmm. You may need Serge's latest and greates patch that I alude to above. > > > With minor work, I could dredge this up for you if you don't have it. > > > > I don't have this, and it doesn't appear that -current does either. > > Could you send it? > > I just uploaded it to freefall.freebsd.org's incoming directory: > ftp://freefall.freebsd.org/incoming/wcd13.tgz Thanks. I'll upload the 1.3 patch too. jdl From owner-freebsd-current Fri Sep 15 18:52:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA24167 for current-outgoing; Fri, 15 Sep 1995 18:52:12 -0700 Received: from chrome.onramp.net (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA24162 for ; Fri, 15 Sep 1995 18:52:09 -0700 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.onramp.net (8.6.11/8.6.9) with SMTP id UAA08706; Fri, 15 Sep 1995 20:51:11 -0500 Message-Id: <199509160151.UAA08706@chrome.onramp.net> X-Authentication-Warning: chrome.onramp.net: Host localhost.jdl.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: Josh Littlefield , current@freebsd.org Subject: Re: more ATAPI CD issues In-reply-to: Your message of "Fri, 15 Sep 1995 17:07:54 PDT." <12146.811210074@time.cdrom.com> Reply-To: jdl@chromatic.com Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Fri, 15 Sep 1995 20:51:11 -0500 From: Jon Loeliger Sender: owner-current@freebsd.org Precedence: bulk Apparently, "Jordan K. Hubbard" scribbled: > > > Hmm. You may need Serge's latest and greates patch that I alude to above. > > > With minor work, I could dredge this up for you if you don't have it. > > > > I don't have this, and it doesn't appear that -current does either. Could > > you send it? > > I just uploaded it to freefall.freebsd.org's incoming directory: > ftp://freefall.freebsd.org/incoming/wcd13.tgz And I just added the patch file, called wcd13-nec_patch and its README. Enjoy, jdl From owner-freebsd-current Sat Sep 16 00:28:55 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA03518 for current-outgoing; Sat, 16 Sep 1995 00:28:55 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA03506 for ; Sat, 16 Sep 1995 00:28:44 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id AAA01022; Sat, 16 Sep 1995 00:28:06 -0700 From: "Rodney W. Grimes" Message-Id: <199509160728.AAA01022@GndRsh.aac.dev.com> Subject: Re: Which SUP files are available and where ? To: davidg@Root.COM Date: Sat, 16 Sep 1995 00:28:05 -0700 (PDT) Cc: pst@shockwave.com, jmb@kryten.atinc.com, andreas@knobel.gun.de, current@freebsd.org In-Reply-To: <199509152209.PAA02115@corbin.Root.COM> from "David Greenman" at Sep 15, 95 03:08:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1319 Sender: owner-current@freebsd.org Precedence: bulk > > >I thought a couple of people were reporting sig 11 problems on -stable. > >Is it true that there are NO sig 11 problems that we're aware of? > > There are no known reliability problems with -stable. All of the people > that I'm aware of that reported (any sort of) problems have since figured > out what was causing them and have fixed them. There was one bug which Rod > found that was causing a "CMAP busy" panic, but this isn't a new problem > and has been with us since last year. It is caused by an attempt to read > from /dev/kmem in an area that has no currently mapped page. This results > in a page fault and subsequantly messed up 'CMAP' page table entry. The > problem will normally only be seen when you have an out of date > /var/db/kvm_kernel.foo.db file. It only happens at boot time and it's actually > quite rare. And should probably be added to the FAQ under an entry: Q. Why do I get a ``CMAP busy panic during boot just after installing a new kernel? A. The logic that attempts to detect an out of data /var/db/kvm_*.db files sometimes fails and using a mismatched file can sometimes lead to panics. F. rm /var/db/kvm_*.db -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sat Sep 16 01:45:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA06796 for current-outgoing; Sat, 16 Sep 1995 01:45:20 -0700 Received: from silver.sms.fi (silver.sms.fi [194.111.122.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA06789 for ; Sat, 16 Sep 1995 01:45:16 -0700 Received: (from pete@localhost) by silver.sms.fi (8.6.12/8.6.9) id LAA24544; Sat, 16 Sep 1995 11:45:02 +0300 Date: Sat, 16 Sep 1995 11:45:02 +0300 Message-Id: <199509160845.LAA24544@silver.sms.fi> From: Petri Helenius To: davidg@Root.COM Cc: current@freebsd.org Subject: Re: Which SUP files are available and where ? In-Reply-To: <199509152322.QAA00165@corbin.Root.COM> References: <199509152322.QAA00165@corbin.Root.COM> Sender: owner-current@freebsd.org Precedence: bulk David Greenman writes: > > > > Ok, if this is the general consensus, when will 2.1 be available? > > "Soon". It's looking very good indeed. > > -DG Will there be 2.2-STABLE and 2.3-CURRENT after the 2.1-RELEASE happens? I'm for this because I see it very valuable to have two branches of code in addition to releases. -STABLE has proven it's right to exist, IMO. Pete From owner-freebsd-current Sat Sep 16 03:15:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA12748 for current-outgoing; Sat, 16 Sep 1995 03:15:32 -0700 Received: from aristotle.algonet.se (aristotle.algonet.se [193.12.207.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA12738 for ; Sat, 16 Sep 1995 03:15:29 -0700 Received: from sophocles. (mal@sophocles.algonet.se [193.12.207.10]) by aristotle.algonet.se (8.6.9/hdw.1.0) with SMTP id MAA23554 for ; Sat, 16 Sep 1995 12:14:57 +0200 Received: by sophocles. (5.x/SMI-SVR4) id AA09196; Sat, 16 Sep 1995 12:15:17 +0200 Date: Sat, 16 Sep 1995 12:15:17 +0200 From: mal@aristotle.algonet.se (Mats Lofkvist) Message-Id: <9509161015.AA09196@sophocles.> To: current@freebsd.org Subject: 2.1-stable: /sys/i386/conf/Makefile.i386 problem? Sender: owner-current@freebsd.org Precedence: bulk When I did a "config GENERIC" on a source tree sup'ed today, the following lines made make barf: .if exists(./@/.) S= ./@ .else S= ../.. .endif (The lines appear as is in the compile/GENERIC/Makefile.) _ Mats Lofkvist mal@algonet.se From owner-freebsd-current Sat Sep 16 03:19:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA13320 for current-outgoing; Sat, 16 Sep 1995 03:19:14 -0700 Received: from aristotle.algonet.se (aristotle.algonet.se [193.12.207.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA13302 for ; Sat, 16 Sep 1995 03:19:09 -0700 Received: from sophocles. (mal@sophocles.algonet.se [193.12.207.10]) by aristotle.algonet.se (8.6.9/hdw.1.0) with SMTP id MAA24171 for ; Sat, 16 Sep 1995 12:18:36 +0200 Received: by sophocles. (5.x/SMI-SVR4) id AA09484; Sat, 16 Sep 1995 12:18:57 +0200 Date: Sat, 16 Sep 1995 12:18:57 +0200 From: mal@aristotle.algonet.se (Mats Lofkvist) Message-Id: <9509161018.AA09484@sophocles.> To: current@freebsd.org Subject: Re: 2.1-stable: /sys/i386/conf/Makefile: forget it, my fault Sender: owner-current@freebsd.org Precedence: bulk I was using gmake :-( From owner-freebsd-current Sat Sep 16 03:48:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA15169 for current-outgoing; Sat, 16 Sep 1995 03:48:22 -0700 Received: from merlin.nando.net (root@merlin.nando.net [152.52.2.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA15152 for ; Sat, 16 Sep 1995 03:48:12 -0700 Received: from nando.net.nando.net (parsifal.nando.net) by merlin.nando.net (4.1/davel-nando/dec93) id AA06173; Sat, 16 Sep 95 06:48:08 EDT Received: by nando.net.nando.net (4.1/SMI-4.1) id AA06366; Sat, 16 Sep 95 06:48:08 EDT From: kmitch@nando.net (kmitch) Message-Id: <9509161048.AA06366@nando.net.nando.net> Subject: pci bus and current?? To: current@freebsd.org Date: Sat, 16 Sep 1995 06:48:08 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 166 Sender: owner-current@freebsd.org Precedence: bulk I just upgraded to the current (9-15), and now my kernel does not probe my pci bus anymore, and thus can't find my hard drives. has anyone else had this problem?? From owner-freebsd-current Sat Sep 16 08:10:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA02267 for current-outgoing; Sat, 16 Sep 1995 08:10:14 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA02260 for ; Sat, 16 Sep 1995 08:10:07 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA08149 for current@freebsd.org; Sun, 17 Sep 1995 01:06:20 +1000 From: michael butler Message-Id: <199509161506.BAA08149@asstdc.scgt.oz.au> Subject: rmail and brain-dead mail systems .. patch enclosed To: current@freebsd.org Date: Sun, 17 Sep 1995 01:06:18 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 713 Sender: owner-current@freebsd.org Precedence: bulk Will someone please add this patch to bin/rmail/rmail.c. Some of us have to deal with mail from brain-dead gateways (notably MS-mail) that produce "From " lines without an address .. e.g. .. From Sun Sep 17 01:10:23 1995 Received: from ... .. this throws rmail into a spin :-( The patch recommended by Eric Allman is .. *** rmail.c~ Mon Mar 20 01:06:12 1995 --- rmail.c Tue May 16 03:26:57 1995 *************** *** 211,216 **** --- 211,218 ---- /* Save off from user's address; the last one wins. */ for (p = addrp; *p && !isspace(*p); ++p); *p = '\0'; + if (*addrp == '\0') + addrp = "<>"; if (from_user != NULL) free(from_user); if ((from_user = strdup(addrp)) == NULL) From owner-freebsd-current Sat Sep 16 08:51:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA05483 for current-outgoing; Sat, 16 Sep 1995 08:51:49 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA05473 for ; Sat, 16 Sep 1995 08:51:46 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id QAA02952; Sat, 16 Sep 1995 16:49:58 +0100 From: Paul Richards Message-Id: <199509161549.QAA02952@server.netcraft.co.uk> Subject: Re: Which SUP files are available and where ? To: pete@sms.fi (Petri Helenius) Date: Sat, 16 Sep 1995 16:49:58 +0100 (BST) Cc: davidg@Root.COM, current@FreeBSD.org In-Reply-To: <199509160845.LAA24544@silver.sms.fi> from "Petri Helenius" at Sep 16, 95 11:45:02 am Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 991 Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Petri Helenius who said > > David Greenman writes: > > > > > > Ok, if this is the general consensus, when will 2.1 be available? > > > > "Soon". It's looking very good indeed. > > > > -DG > > Will there be 2.2-STABLE and 2.3-CURRENT after the 2.1-RELEASE happens? > I'm for this because I see it very valuable to have two branches of code > in addition to releases. -STABLE has proven it's right to exist, IMO. > Me too. I know it's more work for David (or someone anyway) but it allows bug smashing to be done over a longer period and also, I'm running some critical machines now and the sig 11 problem would have floored me but I'm happy to run -stable branches and put up with occasional glitches. It means we can run the next potential release in real environemnts for longer periods than we have in the past. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Sat Sep 16 09:09:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA06473 for current-outgoing; Sat, 16 Sep 1995 09:09:05 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA06466 for ; Sat, 16 Sep 1995 09:09:02 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id RAA03192; Sat, 16 Sep 1995 17:08:06 +0100 From: Paul Richards Message-Id: <199509161608.RAA03192@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 16 Sep 1995 17:08:06 +0100 (BST) Cc: paul@FreeBSD.org, current@freefall.freebsd.org In-Reply-To: <199509151812.UAA21610@uriah.heep.sax.de> from "J Wunsch" at Sep 15, 95 08:12:10 pm Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 538 Sender: owner-current@FreeBSD.org Precedence: bulk In reply to J Wunsch who said > > Sorry, libdialog was it actually: > How are you getting libdialog linked with libforms? I guess there's no reason not to have this be possible but it was not intended to be that way. Libforms is meant to ultimately replace libdialog. The example certainly doesn't link with libdialog, are you trying to use something you've knocked together yourself? -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Sat Sep 16 09:20:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA06775 for current-outgoing; Sat, 16 Sep 1995 09:20:07 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA06758 for ; Sat, 16 Sep 1995 09:19:56 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id SAA23653; Sat, 16 Sep 1995 18:19:51 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id SAA04619; Sat, 16 Sep 1995 18:19:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id SAA01383; Sat, 16 Sep 1995 18:18:37 +0200 From: J Wunsch Message-Id: <199509161618.SAA01383@uriah.heep.sax.de> Subject: Re: libforms - thumbs up or down? To: paul@FreeBSD.org Date: Sat, 16 Sep 1995 18:18:37 +0200 (MET DST) Cc: joerg_wunsch@uriah.heep.sax.de, current@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199509161608.RAA03192@server.netcraft.co.uk> from "Paul Richards" at Sep 16, 95 05:08:06 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 751 Sender: owner-current@FreeBSD.org Precedence: bulk As Paul Richards wrote: > > > Sorry, libdialog was it actually: > > > > How are you getting libdialog linked with libforms? I guess there's no reason > not to have this be possible but it was not intended to be that way. > Libforms is meant to ultimately replace libdialog. The example certainly > doesn't link with libdialog, are you trying to use something you've knocked > together yourself? All i did was a cvs checkout, followed by a make. So it must be in the checked in version of example/Makefile. Also, i cannot see where any other draw_box() would be defined (only declared, in the header). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Sep 16 09:27:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07624 for current-outgoing; Sat, 16 Sep 1995 09:27:21 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA07619 for ; Sat, 16 Sep 1995 09:27:16 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id RAA03380; Sat, 16 Sep 1995 17:26:42 +0100 From: Paul Richards Message-Id: <199509161626.RAA03380@server.netcraft.co.uk> Subject: Re: libforms - thumbs up or down? To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 16 Sep 1995 17:26:41 +0100 (BST) Cc: paul@FreeBSD.org, current@freefall.freebsd.org In-Reply-To: <199509161618.SAA01383@uriah.heep.sax.de> from "J Wunsch" at Sep 16, 95 06:18:37 pm Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 910 Sender: owner-current@FreeBSD.org Precedence: bulk In reply to J Wunsch who said > > > > > How are you getting libdialog linked with libforms? I guess there's no reason > > not to have this be possible but it was not intended to be that way. > > Libforms is meant to ultimately replace libdialog. The example certainly > > doesn't link with libdialog, are you trying to use something you've knocked > > together yourself? > > All i did was a cvs checkout, followed by a make. So it must be in > the checked in version of example/Makefile. Also, i cannot see where > any other draw_box() would be defined (only declared, in the header). Hmm, OK. Clear bit rot taken place I think. I've removed libdialog from the example and it now compiles and runs. Not a very interesting example really but it works now. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Sat Sep 16 10:19:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA11591 for current-outgoing; Sat, 16 Sep 1995 10:19:29 -0700 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA11584 ; Sat, 16 Sep 1995 10:19:28 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id KAA05758; Sat, 16 Sep 1995 10:19:18 -0700 Message-Id: <199509161719.KAA05758@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: paul@FreeBSD.org cc: pete@sms.fi (Petri Helenius), davidg@Root.COM, current@FreeBSD.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Sat, 16 Sep 1995 16:49:58 BST." <199509161549.QAA02952@server.netcraft.co.uk> Date: Sat, 16 Sep 1995 10:19:18 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org Precedence: bulk >Me too. I know it's more work for David (or someone anyway) but it allows >bug smashing to be done over a longer period and also, I'm running some >critical machines now and the sig 11 problem would have floored me but I'm >happy to run -stable branches and put up with occasional glitches. It means >we can run the next potential release in real environemnts for longer >periods than we have in the past. > >-- > Paul Richards, Netcraft Ltd. > Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk > Phone: 0370 462071 (Mobile), +44 1225 447500 (work) The only problem is that 2.2 may not be very "stable" at the time 2.1 is released. We'll have to figure out a strategy for how we do the switch over after a release so that people who are relying on -stable don't get hosed. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sat Sep 16 10:40:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12930 for current-outgoing; Sat, 16 Sep 1995 10:40:15 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA12921 for ; Sat, 16 Sep 1995 10:40:12 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id KAA00498; Sat, 16 Sep 1995 10:39:06 -0700 Message-Id: <199509161739.KAA00498@precipice.shockwave.com> To: michael butler cc: current@freebsd.org Subject: Re: rmail and brain-dead mail systems .. patch enclosed In-reply-to: Your message of "Sun, 17 Sep 1995 01:06:18 +1000." <199509161506.BAA08149@asstdc.scgt.oz.au> Date: Sat, 16 Sep 1995 10:39:05 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk This seems backwards. Why would you want a null address in there, rather than just fix the one or two clients that don't do the right thing if no address is present (which has been legal for years)? Paul From: michael butler Subject: rmail and brain-dead mail systems .. patch enclosed Will someone please add this patch to bin/rmail/rmail.c. Some of us have to deal with mail from brain-dead gateways (notably MS-mail) that produce "From " lines without an address .. e.g. .. From Sun Sep 17 01:10:23 1995 Received: from ... .. this throws rmail into a spin :-( The patch recommended by Eric Allman is .. *** rmail.c~ Mon Mar 20 01:06:12 1995 --- rmail.c Tue May 16 03:26:57 1995 *************** *** 211,216 **** --- 211,218 ---- /* Save off from user's address; the last one wins. */ for (p = addrp; *p && !isspace(*p); ++p); *p = '\0'; + if (*addrp == '\0') + addrp = "<>"; if (from_user != NULL) free(from_user); if ((from_user = strdup(addrp)) == NULL) From owner-freebsd-current Sat Sep 16 10:51:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA15170 for current-outgoing; Sat, 16 Sep 1995 10:51:18 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA15149 for ; Sat, 16 Sep 1995 10:51:15 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id KAA02205; Sat, 16 Sep 1995 10:50:10 -0700 Message-Id: <199509161750.KAA02205@precipice.shockwave.com> To: michael butler , current@freebsd.org Subject: Re: rmail and brain-dead mail systems .. patch enclosed In-reply-to: Your message of "Sat, 16 Sep 1995 10:39:05 PDT." <199509161739.KAA00498@precipice.shockwave.com> Date: Sat, 16 Sep 1995 10:50:09 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk In case I'm not clear, I think that this patch will cause more harm than good, as it changes the expected syntax. I doubt very much that MUAs are going to expect a null from address. Paul From: Paul Traina Subject: Re: rmail and brain-dead mail systems .. patch enclosed This seems backwards. Why would you want a null address in there, rather than just fix the one or two clients that don't do the right thing if no address is present (which has been legal for years)? Paul From: michael butler Subject: rmail and brain-dead mail systems .. patch enclosed Will someone please add this patch to bin/rmail/rmail.c. Some of us have to deal with mail from brain-dead gateways (notably MS-mail >>) that produce "From " lines without an address .. e.g. .. From Sun Sep 17 01:10:23 1995 Received: from ... .. this throws rmail into a spin :-( The patch recommended by Eric Allman is .. *** rmail.c~ Mon Mar 20 01:06:12 1995 --- rmail.c Tue May 16 03:26:57 1995 *************** *** 211,216 **** --- 211,218 ---- /* Save off from user's address; the last one wins. */ for (p = addrp; *p && !isspace(*p); ++p); *p = '\0'; + if (*addrp == '\0') + addrp = "<>"; if (from_user != NULL) free(from_user); if ((from_user = strdup(addrp)) == NULL) From owner-freebsd-current Sat Sep 16 10:52:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA15489 for current-outgoing; Sat, 16 Sep 1995 10:52:32 -0700 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA15476 for ; Sat, 16 Sep 1995 10:52:29 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id DAA14200; Sun, 17 Sep 1995 03:52:16 +1000 From: michael butler Message-Id: <199509161752.DAA14200@asstdc.scgt.oz.au> Subject: Re: rmail and brain-dead mail systems .. patch enclosed To: pst@shockwave.com (Paul Traina) Date: Sun, 17 Sep 1995 03:52:16 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <199509161739.KAA00498@precipice.shockwave.com> from "Paul Traina" at Sep 16, 95 10:39:05 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1111 Sender: owner-current@freebsd.org Precedence: bulk Paul Traina writes: > This seems backwards. Why would you want a null address in there, rather > than just fix the one or two clients that don't do the right thing if no > address is present (which has been legal for years)? The client(s) that don't do the right thing are rmail in combination with sendmail. The thing generating the "no from address" mail is MS own SMTP gateway. No way are you going to get them to change that ... rmail, as it is, instead of forwarding the bounce message generated by MS-Mail, provokes sendmail into sending *me* the mail (effectively) saying that it doesn't comprehend it and that a "recipient address must be specified". The resulting command-line is "/usr/sbin/sendmail -f dest_addr". The angle-bracket form, as produced by the patch, becomes a place-holder to convince sendmail to do the Right Thing by producing .. "/usr/sbin/sendmail -f <> dest_addr". sendmail then courteously substitutes the string "MAILER-DAEMON" for the null address and everything works. As I stated, this *is* Eric's "standard" patch for it .. what other options are there ? michael From owner-freebsd-current Sat Sep 16 11:17:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA19795 for current-outgoing; Sat, 16 Sep 1995 11:17:22 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA19786 for ; Sat, 16 Sep 1995 11:17:19 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id LAA06117; Sat, 16 Sep 1995 11:16:12 -0700 Message-Id: <199509161816.LAA06117@precipice.shockwave.com> To: michael butler cc: current@freebsd.org Subject: Re: rmail and brain-dead mail systems .. patch enclosed In-reply-to: Your message of "Sun, 17 Sep 1995 03:52:16 +1000." <199509161752.DAA14200@asstdc.scgt.oz.au> Date: Sat, 16 Sep 1995 11:16:11 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk The angle-bracket form, as produced by the patch, becomes a place-holder to convince sendmail to do the Right Thing by producing .. "/usr/sbin/sendmail -f <> dest_addr". sendmail then courteously substitutes the string "MAILER-DAEMON" for the null address and everything works. As I stated, this *is* Eric's "standard" patch for it .. what other options are there ? Ahh, I looked more carefully at the source code. You're absolutely right. The way I read it from you was going the "other" way, that mail was coming in via a remote SMTP site and you wanted the delivery agent to mung the headers. I was completely full of shit, sorry...I'm used to the bad old days when /bin/mail and /bin/rmail were the same piece of code. What does make me curious is how does rmail enter into the picture at all? Who is invoking it? Does the MS mail gateway software run on a FreeBSD machine and feed its mail into sendmail via /bin/rmail? From owner-freebsd-current Sat Sep 16 11:26:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA21604 for current-outgoing; Sat, 16 Sep 1995 11:26:05 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA21583 ; Sat, 16 Sep 1995 11:26:02 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id LAA07664; Sat, 16 Sep 1995 11:25:31 -0700 Message-Id: <199509161825.LAA07664@precipice.shockwave.com> To: hackers@freebsd.org cc: current@freebsd.org Subject: looking for REALLY good hardware diagnostics Date: Sat, 16 Sep 1995 11:25:30 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk I've got two systems, one an early-model pentium, the other a Cx486DLC both experiencing the occasional odd failure when running under FreeBSD and I want to double-check the hardware on these machines. (Yes, I know about the cache weirdness on the 486DLC, I've even disabled the internal cache completely as part of my testing). I think the Pentium either has a bad CPU (likely) or a bad cache chip (unlikely) and the DLC either has a bad cache chip (likely) or bad dram (unlikely). Does anyone have ANY pointers whatsoever to a really really really good and thorough set of diagnostics that could be used to check for hardware faults? Specificly, anything that can be used to diagnose external caches, memory, (and in the case of the pentium, perform cpu diagnostics) would be cool. Paul From owner-freebsd-current Sat Sep 16 12:38:31 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA03148 for current-outgoing; Sat, 16 Sep 1995 12:38:31 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA03137 ; Sat, 16 Sep 1995 12:38:28 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA01662; Sat, 16 Sep 1995 12:38:21 -0700 From: "Rodney W. Grimes" Message-Id: <199509161938.MAA01662@GndRsh.aac.dev.com> Subject: Re: Which SUP files are available and where ? To: paul@FreeBSD.org Date: Sat, 16 Sep 1995 12:38:20 -0700 (PDT) Cc: pete@sms.fi, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <199509161549.QAA02952@server.netcraft.co.uk> from "Paul Richards" at Sep 16, 95 04:49:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1640 Sender: owner-current@FreeBSD.org Precedence: bulk > > In reply to Petri Helenius who said > > > > David Greenman writes: > > > > > > > > Ok, if this is the general consensus, when will 2.1 be available? > > > > > > "Soon". It's looking very good indeed. > > > > > > -DG > > > > Will there be 2.2-STABLE and 2.3-CURRENT after the 2.1-RELEASE happens? > > I'm for this because I see it very valuable to have two branches of code > > in addition to releases. -STABLE has proven it's right to exist, IMO. > > > > Me too. I know it's more work for David (or someone anyway) but it allows > bug smashing to be done over a longer period and also, I'm running some > critical machines now and the sig 11 problem would have floored me but I'm > happy to run -stable branches and put up with occasional glitches. It means > we can run the next potential release in real environemnts for longer > periods than we have in the past. Not only that, part of the intent of doing the release work on branches means FreeBSD now has a place to commit critical but fixes (after the ``RELENG_2_1_0_RELEASE'' tag, and can produce small ``critical fix'' upgrade kits for the 2.1.0 release (actually create a 2.1.1) easily and without impacting developement or 2.2 work. If the tags are maintained as I had been doing them it should also be quite easy to produce 2.0.5 vs 2.1.0 diffs (though they are going to be _HUGE_.) And even things like 2.1.0 vs -current diffs (which due to Davids Massive work is actuall not that bad of a diff). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sat Sep 16 12:50:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA04474 for current-outgoing; Sat, 16 Sep 1995 12:50:48 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA04469 ; Sat, 16 Sep 1995 12:50:45 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA01763; Sat, 16 Sep 1995 12:50:34 -0700 From: "Rodney W. Grimes" Message-Id: <199509161950.MAA01763@GndRsh.aac.dev.com> Subject: Re: Which SUP files are available and where ? To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sat, 16 Sep 1995 12:50:33 -0700 (PDT) Cc: paul@FreeBSD.org, pete@sms.fi, davidg@Root.COM, current@FreeBSD.org In-Reply-To: <199509161719.KAA05758@aslan.cdrom.com> from "Justin T. Gibbs" at Sep 16, 95 10:19:18 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1761 Sender: owner-current@FreeBSD.org Precedence: bulk > > >Me too. I know it's more work for David (or someone anyway) but it allows > >bug smashing to be done over a longer period and also, I'm running some > >critical machines now and the sig 11 problem would have floored me but I'm > >happy to run -stable branches and put up with occasional glitches. It means > >we can run the next potential release in real environemnts for longer > >periods than we have in the past. > > > >-- > > Paul Richards, Netcraft Ltd. > > Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk > > Phone: 0370 462071 (Mobile), +44 1225 447500 (work) > > The only problem is that 2.2 may not be very "stable" at the time 2.1 > is released. We'll have to figure out a strategy for how we do the > switch over after a release so that people who are relying on -stable > don't get hosed. Don't point the sup file to the 2.2 branch until it has ``stabalized'', and then probably never. I did not have quite enough for thought about names when I set this up and the sup release should probably be called stable-2.1, thus you can change that to stable-2.2 and not hose over the users at end of life for 2.1 and point then cvs update the tree to the 2.2 branch. This can still be made to work, just change the name from ``stable'' to ``stable-2.2'' in the sup control files when that tree gets created ( I suggest YAST (Yet Another Source Tree) for this, as it might be nice to have critical bug fixes go to users via sup who are running 2.1R, just cut the cvs and sup updates down to once every 3 days or something slightly more reasonable for a maintainence mode tree. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sat Sep 16 13:11:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA09652 for current-outgoing; Sat, 16 Sep 1995 13:11:52 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA09629 ; Sat, 16 Sep 1995 13:11:45 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA01803; Sat, 16 Sep 1995 13:11:17 -0700 From: "Rodney W. Grimes" Message-Id: <199509162011.NAA01803@GndRsh.aac.dev.com> Subject: Re: looking for REALLY good hardware diagnostics To: pst@shockwave.com (Paul Traina) Date: Sat, 16 Sep 1995 13:11:16 -0700 (PDT) Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: <199509161825.LAA07664@precipice.shockwave.com> from "Paul Traina" at Sep 16, 95 11:25:30 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2816 Sender: owner-current@freebsd.org Precedence: bulk > > I've got two systems, one an early-model pentium, the other a Cx486DLC both > experiencing the occasional odd failure when running under FreeBSD and I want > to double-check the hardware on these machines. Given that I do this day in day out 7 days a week I can lend some hand in diagnosing hardware related failures, I don't go out of my way to do this for others any longer as I have enought of it to deal with here, but I see you making some assumptions that from my data are incorrect. > (Yes, I know about the cache weirdness on the 486DLC, I've even disabled the > internal cache completely as part of my testing). Good, that eliminates that screwwy mess :-). > I think the Pentium either has a bad CPU (likely) ^^^^^^^^ very unlikely, in the last 2 years I have seen 0 (yes, 0) defects in a Pentium CPU chip, if the thing will power up and load a kernel it is good from my data. > or a bad cache chip (unlikely) Very likely, in the last 120 days I have had to replace 3 SRAM cache chips that would causes system crashes, sig 11's or other strangeness. Infact bad ``cache'' is my #1 failure mode of incoming motherboard products. And my #1 failure during burn in as far as electronic components go (overall #1 is disk drives that die during my 720 minute hour glass seek/random seek pre-burn in test :-(). > and the DLC either has a bad cache chip (likely) or bad dram (unlikely). Dram is my #2 electronic failure, most often occurs during initial incoming inspection during a 3 hour make world pass using a 100Mhz PB Pentium that can really knock snot on the memory subsystem. > Does anyone have ANY pointers whatsoever to a really really really good and > thorough set of diagnostics that could be used to check for hardware faults? There are non other than a VLSI tester for memory chips and simms, and ICE for MB problems, so unless you have access to a multi million dollar test equipment lab it is real tough. Is what I use here is ``make world'', if it fails that I use my years of correlating FreeBSD panics or signals to mostlikely hardware component, and a deep gut feeling for what I have seen over the years. > Specificly, anything that can be used to diagnose external caches, memory, > (and in the case of the pentium, perform cpu diagnostics) would be cool. If it runs ``make world'' it is good, I have found no better test of fucntionality than this as far as MB/CPU/Cache/Memory goes. If it fails I use the big shot gun approach and start replacing each one of those with ``known good'' units (another benifit I have that you may not is I have ``known good'' units around.) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sat Sep 16 13:40:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA17232 for current-outgoing; Sat, 16 Sep 1995 13:40:49 -0700 Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA17202 for ; Sat, 16 Sep 1995 13:40:43 -0700 Received: from [199.183.109.242] by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Sat, 16 Sep 1995 15:40:35 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 16 Sep 1995 15:40:37 -0500 To: "Rodney W. Grimes" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Which SUP files are available and where ? Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk At 2:50 PM 9/16/95, Rodney W. Grimes wrote: >This can still be made to work, just change the name from ``stable'' to >``stable-2.2'' in the sup control files when that tree gets created ( >I suggest YAST (Yet Another Source Tree) for this, as it might be nice >to have critical bug fixes go to users via sup who are running 2.1R, >just cut the cvs and sup updates down to once every 3 days or something >slightly more reasonable for a maintainence mode tree. Why bother with "stable" anything. Just call the tree 2.1, 2.2, 2.3, etc. As for the long term support, I think we should consider CTM as the distribution mechanism rather than sup. Comments? ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Sat Sep 16 14:20:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA24986 for current-outgoing; Sat, 16 Sep 1995 14:20:07 -0700 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA24968 for ; Sat, 16 Sep 1995 14:20:03 -0700 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA01903; Sat, 16 Sep 1995 14:19:45 -0700 From: "Rodney W. Grimes" Message-Id: <199509162119.OAA01903@GndRsh.aac.dev.com> Subject: Re: Which SUP files are available and where ? To: rkw@dataplex.net (Richard Wackerbarth) Date: Sat, 16 Sep 1995 14:19:44 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: from "Richard Wackerbarth" at Sep 16, 95 03:40:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1720 Sender: owner-current@FreeBSD.org Precedence: bulk > > At 2:50 PM 9/16/95, Rodney W. Grimes wrote: > > >This can still be made to work, just change the name from ``stable'' to > >``stable-2.2'' in the sup control files when that tree gets created ( > >I suggest YAST (Yet Another Source Tree) for this, as it might be nice > >to have critical bug fixes go to users via sup who are running 2.1R, > >just cut the cvs and sup updates down to once every 3 days or something > >slightly more reasonable for a maintainence mode tree. > > Why bother with "stable" anything. Just call the tree 2.1, 2.2, 2.3, etc. > As for the long term support, I think we should consider CTM as the > distribution mechanism rather than sup. > > Comments? I can live with those names, names are just labels and are not so important to me any more so long as I have a description of what the label means as far as content. On the sup vs ctm, well, when ctm can fix my tree I just splattered all over I'll switch, until then I will leave it to the others to use. CTM is slightly fragile with respect to anyone doing work in there local tree, while sup has documented mechanism to deal with it (backup is a really nice option, as are old and keep :-). Some how I think it will be a long time before CTM can offer that level of fuctionality. Sup could use some protocol rewrites so that it does things like mass tranfer of the inode update information instead of doing it 1 file per 2xRTT and perhaps some smarts about file moves would help cut load down for things like the cvs repository (files going into the Attic are a pain :-(). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Sat Sep 16 15:07:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA00446 for current-outgoing; Sat, 16 Sep 1995 15:07:02 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA00439 ; Sat, 16 Sep 1995 15:06:57 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id PAA05212; Sat, 16 Sep 1995 15:05:36 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id PAA01126; Sat, 16 Sep 1995 15:07:56 -0700 Message-Id: <199509162207.PAA01126@corbin.Root.COM> To: paul@freebsd.org cc: pete@sms.fi (Petri Helenius), current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Sat, 16 Sep 95 16:49:58 BST." <199509161549.QAA02952@server.netcraft.co.uk> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 16 Sep 1995 15:07:55 -0700 Sender: owner-current@freebsd.org Precedence: bulk >In reply to Petri Helenius who said >> >> David Greenman writes: >> > > >> > > Ok, if this is the general consensus, when will 2.1 be available? >> > >> > "Soon". It's looking very good indeed. >> > >> > -DG >> >> Will there be 2.2-STABLE and 2.3-CURRENT after the 2.1-RELEASE happens? >> I'm for this because I see it very valuable to have two branches of code >> in addition to releases. -STABLE has proven it's right to exist, IMO. >> > >Me too. I know it's more work for David (or someone anyway) but it allows >bug smashing to be done over a longer period and also, I'm running some >critical machines now and the sig 11 problem would have floored me but I'm >happy to run -stable branches and put up with occasional glitches. It means >we can run the next potential release in real environemnts for longer >periods than we have in the past. I generally like the idea of having the -stable branch, but as the one who has been maintaining it for about 3 months now, I can say that it is a *lot* of work and has resulted in me spending all of my energy on it. I haven't had any time to do development of my own and I can say that I'll eventually get burnt out if this becomes my singular job. SO: 2.1-stable will have a life that will live beyond the 2.1 release. It will continue to be the "stable" branch until we near the release date of 2.2 (say 6 weeks before the 2.2 release target), or in other words, 2.2-stable will come into existence as soon as we switch new development to 2.3 (i.e. 2.3 becomes the 'HEAD'). I really don't expect much to happen with the 2.1-stable source after the release is made (barring unforeseen critical bugfixes). I'll let other people figure out what we're going to call the SUP targets. -DG From owner-freebsd-current Sat Sep 16 15:47:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA02972 for current-outgoing; Sat, 16 Sep 1995 15:47:02 -0700 Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA02965 for ; Sat, 16 Sep 1995 15:46:58 -0700 Received: from [199.183.109.242] by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Sat, 16 Sep 1995 17:08:48 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 16 Sep 1995 17:08:49 -0500 To: "Rodney W. Grimes" From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Which SUP files are available and where ? Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk At 4:19 PM 9/16/95, Rodney W. Grimes wrote: >On the sup vs ctm, well, when ctm can fix my tree I just splattered >all over I'll switch, until then I will leave it to the others to >use. CTM is slightly fragile with respect to anyone doing work in >there local tree, while sup has documented mechanism to deal with >it (backup is a really nice option, as are old and keep :-). Some >how I think it will be a long time before CTM can offer that level >of fuctionality. The "features" that I like about CTM are 1) the transfer overhead is reduced and 2) the system is event driven rather than polled. This implies that the load on a server is greatly reduced. In particular, I think this can become an advantage when a release becomes "very-stable" and only get occasional bug fixes. Your points about the ability of sup to repair a damaged tree are valid. I tend to forget them because I can easily restore from the (local) mirror site. I am still willing to generate CTM updates for -stable and mail them out just as soon as I can learn the secrets. ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Sat Sep 16 17:43:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA09805 for current-outgoing; Sat, 16 Sep 1995 17:43:36 -0700 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA09795 ; Sat, 16 Sep 1995 17:43:30 -0700 Received: (from uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) with UUCP id CAA23239; Sun, 17 Sep 1995 02:43:13 +0200 Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.6.12/8.6.12) with SMTP id CAA03205; Sun, 17 Sep 1995 02:11:31 +0200 Date: Sun, 17 Sep 1995 02:11:31 +0200 (MET DST) From: Andreas Klemm To: "Justin T. Gibbs" cc: larry@seminole.iag.net, jhk@freebsd.org, hackers@freebsd.org, current@freebsd.org Subject: Re: SCSI problems with FreeBSD 2.0.5 using AHA 2940 and Quantum Grand Prix In-Reply-To: <199509141429.HAA22861@aslan.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Thu, 14 Sep 1995, Justin T. Gibbs wrote: > > You should be running the driver in -stable if you have a grand > prix. The driver is most likely your problem. Hi Justin ! It works ok with FreeBSD-stable. Thanks !!! Andreas /// -- Andreas Klemm You have lpd and need an intelligent print filter ?!! Ok, this might help: "apsfilter ... irgendwie clever" ftp it from ------> ftp://sunsite.unc.edu/pub/Linux/Incoming/aps-491.tgz From owner-freebsd-current Sat Sep 16 18:18:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA11915 for current-outgoing; Sat, 16 Sep 1995 18:18:11 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA11903 ; Sat, 16 Sep 1995 18:18:07 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id SAA21444; Sat, 16 Sep 1995 18:14:11 -0700 To: "Justin T. Gibbs" cc: paul@FreeBSD.org, pete@sms.fi (Petri Helenius), davidg@Root.COM, current@FreeBSD.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Sat, 16 Sep 1995 10:19:18 PDT." <199509161719.KAA05758@aslan.cdrom.com> Date: Sat, 16 Sep 1995 18:14:10 -0700 Message-ID: <21442.811300450@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > The only problem is that 2.2 may not be very "stable" at the time 2.1 > is released. We'll have to figure out a strategy for how we do the > switch over after a release so that people who are relying on -stable > don't get hosed. Well, I don't expect that the "switch will be thrown" quite as neatly as some here might hope. I'm more inclined to suspect that 2.1 will be followed by 2.1.1, 2.1.2, etc. 2.2 will be released with its own experimental enhancements going on point releases of 2.2, etc. The only serious question still to be resolved is just when the "rollover" happens? Does 2.1.x live forever, or does it get abandoned with 2.2.x is "stable?" Does 2.1 just become 2.3 at some point, leaving the odd numbered releases as the "stable" ones and the even numbered ones as "experimental?" When does 2.2.x get abandoned in favor of 2.4 then? In short, we may be digging ourselves a deep hole if we can't decide just how this is all going to work. Jordan From owner-freebsd-current Sat Sep 16 20:41:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA23221 for current-outgoing; Sat, 16 Sep 1995 20:41:49 -0700 Received: from specgw.spec.co.jp (specgw.spec.co.jp [202.32.13.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA23216 ; Sat, 16 Sep 1995 20:41:45 -0700 Received: from localhost (uucp@localhost) by specgw.spec.co.jp (8.6.5/3.3Wb-SPEC) with UUCP id MAA03578; Sun, 17 Sep 1995 12:25:33 +0900 Received: by tama.spec.co.jp (8.6.12/6.4J.5) id MAA26147; Sun, 17 Sep 1995 12:35:57 +0900 From: Atsushi Murai Message-Id: <199509170335.MAA26147@tama.spec.co.jp> Subject: Re: Which SUP files are available and where ? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 17 Sep 1995 12:35:57 +0900 (JST) Cc: gibbs@freefall.freebsd.org, paul@FreeBSD.org, pete@sms.fi, davidg@Root.com, current@FreeBSD.org In-Reply-To: <21442.811300450@time.cdrom.com> from "Jordan K. Hubbard" at Sep 16, 95 06:14:10 pm Reply-To: amurai@spec.co.jp X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1306 Sender: owner-current@FreeBSD.org Precedence: bulk > > The only problem is that 2.2 may not be very "stable" at the time 2.1 > > is released. We'll have to figure out a strategy for how we do the > > switch over after a release so that people who are relying on -stable > > don't get hosed. > > Well, I don't expect that the "switch will be thrown" quite as neatly > as some here might hope. I'm more inclined to suspect that 2.1 will > be followed by 2.1.1, 2.1.2, etc. 2.2 will be released with its own > experimental enhancements going on point releases of 2.2, etc. > > The only serious question still to be resolved is just when the > "rollover" happens? Does 2.1.x live forever, or does it get abandoned > with 2.2.x is "stable?" Does 2.1 just become 2.3 at some point, > leaving the odd numbered releases as the "stable" ones and the even > numbered ones as "experimental?" When does 2.2.x get abandoned in > favor of 2.4 then? > > In short, we may be digging ourselves a deep hole if we can't decide > just how this is all going to work. > > Jordan > I would like to treat release by "odd" and even number. If we make too much branch, it's hard to truck it ;-) Atsushi. -- Atsushi Murai Internet: amurai@spec.co.jp System Planning and Engineering Co,.Ltd. Voice : +81-33833-5341 From owner-freebsd-current Sat Sep 16 22:29:19 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA27717 for current-outgoing; Sat, 16 Sep 1995 22:29:19 -0700 Received: from chrome.onramp.net (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA27712 for ; Sat, 16 Sep 1995 22:29:16 -0700 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.onramp.net (8.6.11/8.6.9) with SMTP id AAA14969; Sun, 17 Sep 1995 00:28:24 -0500 Message-Id: <199509170528.AAA14969@chrome.onramp.net> X-Authentication-Warning: chrome.onramp.net: Host localhost.jdl.com didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@FreeBSD.org Subject: Release numbering In-reply-to: Your message of "Sat, 16 Sep 1995 18:14:10 PDT." <21442.811300450@time.cdrom.com> Reply-To: jdl@chromatic.com Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Sun, 17 Sep 1995 00:28:23 -0500 From: Jon Loeliger Sender: owner-current@FreeBSD.org Precedence: bulk Apparently, "Jordan K. Hubbard" scribbled: > The only serious question still to be resolved is just when the > "rollover" happens? Does 2.1.x live forever, or does it get abandoned > with 2.2.x is "stable?" Personally, I think trying to maintain a strict 2.1 derived base for a very long time will become fairly problematic. You'll likely end up with the nightmare of figuring out which variant of which patch gets applied to which branches and the resulting rev interlock. Been there done that. Wasn't too much fun then either. I sort of think people have a desire to contribute to and subsequently need the "latest and greatest". I think they'd rather do development work into that and generally push the frontier there. My point being: sure bug fix 2.1 to get 2.1.1 if needed, but don't plan on it living long if 2.2 is already under way and people are actively contributing to that. How well this rolls from 2.1 to 2.2 probably depend on the gross-level development cycle time. Waiting 9~12 months for a major release is somewhat painful, especially if there's nothing in between. This is proabably what leads to the snap shot releases that people want. In fact, could we just formalize the snapshots into the series of release numbers? (Yea, I know, this was all discussed a month ago...) > Does 2.1 just become 2.3 at some point, > leaving the odd numbered releases as the "stable" ones and the even > numbered ones as "experimental?" Isn't that what the makers of the Star Trek movies decided to do? :-) Oh wait, no. The odd ones sucked and the even ones were good, right? Yea, this is probably the basic approach to take. As soon as 2.1 goes out the door, people are generally going to breath a huge sigh of relief, take a break, and then be real gung-ho about 2.2. Why not just let everyone work on 2.2 until it too gets to a reasonably stable point and then call it "stable" at the same time introduce 2.3 as the next development release. Just pipeline it, not leapfrog it? > In short, we may be digging ourselves a deep hole if we can't decide > just how this is all going to work. Agreed. jdl From owner-freebsd-current Sat Sep 16 22:45:17 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA28394 for current-outgoing; Sat, 16 Sep 1995 22:45:17 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA28387 for ; Sat, 16 Sep 1995 22:45:15 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id WAA18561; Sat, 16 Sep 1995 22:45:08 -0700 To: jdl@chromatic.com cc: current@FreeBSD.org Subject: Re: Release numbering In-reply-to: Your message of "Sun, 17 Sep 1995 00:28:23 CDT." <199509170528.AAA14969@chrome.onramp.net> Date: Sat, 16 Sep 1995 22:45:08 -0700 Message-ID: <18559.811316708@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > relief, take a break, and then be real gung-ho about 2.2. Why not > just let everyone work on 2.2 until it too gets to a reasonably > stable point and then call it "stable" at the same time introduce 2.3 > as the next development release. Just pipeline it, not leapfrog it? I can see that working, modulo a -STABLE or -DEVEL tag appended so people know which number is which. If we're not going to go for an even/odd scheme then something else needs to be evolved to keep them straight. Jordan From owner-freebsd-current Sat Sep 16 23:48:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA00592 for current-outgoing; Sat, 16 Sep 1995 23:48:26 -0700 Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id XAA00587 for ; Sat, 16 Sep 1995 23:48:23 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <25787-0@bunyip.cc.uq.oz.au>; Sun, 17 Sep 1995 16:47:58 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id QAA23608 for ; Sun, 17 Sep 1995 16:52:46 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id GAA25324 for ; Sun, 17 Sep 1995 06:54:19 GMT Message-Id: <199509170654.GAA25324@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.2 7/18/95 To: current@freebsd.org Subject: Poul's new malloc changes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Sep 1995 16:54:18 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org Precedence: bulk Phew! It sure aggravates the sig11/10/4 problem! Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that!