From owner-freebsd-current Sun Apr 21 02:02:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA10073 for current-outgoing; Sun, 21 Apr 1996 02:02:24 -0700 (PDT) Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA10067 for ; Sun, 21 Apr 1996 02:02:18 -0700 (PDT) Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.6.12/8.6.12) id CAA26829; Sun, 21 Apr 1996 02:06:00 -0700 Date: Sun, 21 Apr 1996 02:06:00 -0700 Message-Id: <199604210906.CAA26829@sunrise.cs.berkeley.edu> To: jkh@time.cdrom.com CC: current@FreeBSD.ORG In-reply-to: <245.829962579@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Anyone else notice NFS broken in -current? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Running the latest 2.2 kernels on two boxes here, I can only use NFS * for a short time before any process doing NFS I/O hangs. After awhile * of this, one of the systems will then reset to the BIOS. * * This and other reports now leads me to say that NFS is very, very * broken. The only question is - who broke it, and when? I don't see crashes (well I do (reported to -current awhile back) but they are not NFS related) but I noticed that if I redirect the output of a program to an NFS-mounted disk under heavy (local ccd) load, the output gets mangled with the environment of the process. If the output is redirected to a local file, it works fine. Satoshi From owner-freebsd-current Sun Apr 21 03:00:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA11898 for current-outgoing; Sun, 21 Apr 1996 03:00:51 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA11893 for ; Sun, 21 Apr 1996 03:00:49 -0700 (PDT) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <14759-0@bunyip.cc.uq.oz.au>; Sun, 21 Apr 1996 20:00:33 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id QAA02473 for ; Sun, 21 Apr 1996 16:48:25 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id GAA19816 for ; Sun, 21 Apr 1996 06:51:39 GMT Message-Id: <199604210651.GAA19816@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: mmap vs malloc - what gives? X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Apr 1996 16:51:38 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mixing mmap & malloc appears to be a recipe for much grief. mmap doesn't seem to take much notice of what's already malloced and occasionally drops its region over the top of some already malloced space. I've tried with the addr parameter set to something which is malloced to be the same size as the file being mmaped in, I've tried it set to zero, I've tried doing my mallocing all before the mmap and (where possible) all after. No dice. (For the curious, the application in question is a re-implementation of the doom soundserver which gropes through the wadfile using mmap. I'm re-implementing it so I can send the sounds off to the NAS soundserver) Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Sun Apr 21 08:32:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA22741 for current-outgoing; Sun, 21 Apr 1996 08:32:12 -0700 (PDT) Received: from pegasus.isr.uc.pt (pegasus.isr.uc.pt [193.136.230.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA22735 for ; Sun, 21 Apr 1996 08:32:07 -0700 (PDT) Received: from pioneer (pioneer.isr.uc.pt) by pegasus.isr.uc.pt (5.x/SMI-SVR4) id AA21494; Sun, 21 Apr 1996 16:26:55 +0100 Date: Sun, 21 Apr 1996 16:31:27 +0100 (WET DST) From: Paulo Menezes X-Sender: paulo@pioneer To: "Justin T. Gibbs" Cc: current@FreeBSD.org Subject: Re: Another problem with Adaptec 2940 and S3TRIO64 In-Reply-To: <199604141634.JAA18995@freefall.freebsd.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Apr 1996, Justin T. Gibbs wrote: > The aic7xxx driver in 2.1R has problems. Upgrade to 2.1-STABLE and > see if your problems go away. > Well, I did... and it still shows the same problem :( I installed the stable-kernel and started a "make world"... and after installing the libs, it hang, with lots of messages related with the scsi controller. One of the messages was :"BUS DEVICE RESET message queued" I realy need this machine working because it was bought to support our web server... Thanks again Paulo ---- ener1000# dmesg FreeBSD 2.1-STABLE #0: Fri Apr 19 01:23:17 1996 root@ener1000.dee.uc.pt:/usr/src/sys/compile/LOCAL CPU: 99-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30539776 (29824K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 ahc0 rev 3 int a irq 9 on pci0:6 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "MICROP 4221-09SC21020AV TN05" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1955MB (4004219 512 byte sectors) vga0 rev 0 int a irq 255 on pci0:13 chip1 rev 2 on pci0:15 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 ed1 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff lpt2 not found at 0xffffffff mse0: wrong signature ff mse0 not found at 0x23c psm0 at 0x60-0x63 irq 12 on motherboard fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 bt0 not found at 0x330 uha0 not found at 0x330 aha0 not found at 0x330 aic0 not found at 0x340 nca0 not found at 0x1f88 nca1 not found at 0x350 sea0 not found wt0 not found at 0x300 mcd0 not found at 0x300 mcd1: timeout getting status mcd1 not found at 0x340 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0 not found at 0x360 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:c3:4e:2fix0 not probed due to I/O address conflict with ep0 at 0x300 le0 not probed due to I/O address conflict with ep0 at 0x300 lnc0 not found at 0x280 lnc1 not probed due to I/O address conflict with ep0 at 0x300 ze0 not probed due to I/O address conflict with ep0 at 0x300 zp0 not probed due to I/O address conflict with ep0 at 0x300 npx0 on motherboard npx0: INT 16 interface changing root device to sd0a > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > From owner-freebsd-current Sun Apr 21 08:41:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23105 for current-outgoing; Sun, 21 Apr 1996 08:41:07 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23082 for ; Sun, 21 Apr 1996 08:41:05 -0700 (PDT) Message-Id: <199604211541.IAA23082@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol Date: Sun, 21 Apr 1996 08:41:04 -0700 From: "Justin T. Gibbs" Subject: Re: Another problem with Adaptec 2940 and S3TRIO64 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- Blind-Carbon-Copy To: Paulo Menezes cc: stable@FreeBSD.org Subject: Re: Another problem with Adaptec 2940 and S3TRIO64 In-reply-to: Your message of "Sun, 21 Apr 1996 16:31:27 BST." Date: Sun, 21 Apr 1996 08:41:04 -0700 From: "Justin T. Gibbs" Moved to -stable. >On Sun, 14 Apr 1996, Justin T. Gibbs wrote: > >> The aic7xxx driver in 2.1R has problems. Upgrade to 2.1-STABLE and >> see if your problems go away. >> > >Well, I did... and it still shows the same problem :( >I installed the stable-kernel and started a "make world"... and after >installing the libs, it hang, with lots of messages related with the scsi >controller. >One of the messages was :"BUS DEVICE RESET message queued" As a first step, remove the entries for every device in your kernel config file that you do not need, and recompile your kernel. As a second step, make sure that the termination on your hard drive is active and powered from the drive (not the SCSI bus), use a short cable, and ensure that termination is turned on with your 2940. >Thanks again > >Paulo >---- - -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== ------- End of Blind-Carbon-Copy From owner-freebsd-current Sun Apr 21 08:59:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23654 for current-outgoing; Sun, 21 Apr 1996 08:59:52 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA23647 for ; Sun, 21 Apr 1996 08:59:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id IAA05328 for ; Sun, 21 Apr 1996 08:59:40 -0700 (PDT) To: current@freebsd.org Subject: Another 2.2-SNAP soon, folks? Date: Sun, 21 Apr 1996 08:59:39 -0700 Message-ID: <5325.830102379@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Modulo the problem with ip_output.c that I expect Garrett will want to work on, and my own final attempts to repair sysinstall (now that I've gone to the new menuing scheme), does anyone else have any objection to a 2.2-SNAP being done sometime within the next 7 days? I'm thinking something like 2.2-960428-SNAP, assuming, of course, that -current is stable enough to snapshot on that date. Goals of this snapshot are to: 1. Get Justin's latest Adaptec support code out in bootable/installable form. 2. See what people think of the cosmetic changes to sysinstall. 3. Get John's latest VM enhancements out there. 4. Get the rundos stuff out in what's at least an experimental form. 5. Whatever other justifications I manage to come up with in the next 7 days.. :-) Any objections / reports of known brokenness which would make this a bad time for a SNAP? Jordan From owner-freebsd-current Sun Apr 21 09:40:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA25069 for current-outgoing; Sun, 21 Apr 1996 09:40:19 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA25064 for ; Sun, 21 Apr 1996 09:40:16 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) with ESMTP id JAA25438; Sun, 21 Apr 1996 09:40:10 -0700 (PDT) Message-Id: <199604211640.JAA25438@austin.polstra.com> To: jkh@time.cdrom.com Cc: freebsd-current@freebsd.org Subject: Re: Another 2.2-SNAP soon, folks? In-reply-to: <5325.830102379@time.cdrom.com> Date: Sun, 21 Apr 1996 09:40:10 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Any objections / reports of known brokenness which would make this > a bad time for a SNAP? I would very much like to see gzipped executables working again. Without them, you can't use the fixit disk. (I know, I know, you can use it with an older install disk. But that's not quite the same.) I realize that the proper answer to a statement like this is, "Feel free to fix it yourself." I tried for almost a whole day. But I don't know the kernel well at all, and gzipped executables crash it without so much as a complaint on the console, let alone a bona-fide panic. So I was limited to the time-honored technique of sprinkling printfs throughout the offending code. I got some clues that way, but the results were very anomalous. In fact, they would seem to support Terry's hypothesis about the processor cache. (This was on a 486DX2, by the way.) I'd be happy to share what I learned, FWIW, with anyone who wants to try and fix gzipped executables. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sun Apr 21 11:31:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA29149 for current-outgoing; Sun, 21 Apr 1996 11:31:42 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA29143 for ; Sun, 21 Apr 1996 11:31:39 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id EAA32380; Mon, 22 Apr 1996 04:30:03 +1000 Date: Mon, 22 Apr 1996 04:30:03 +1000 From: Bruce Evans Message-Id: <199604211830.EAA32380@godzilla.zeta.org.au> To: jdp@polstra.com, jkh@time.cdrom.com Subject: Re: Another 2.2-SNAP soon, folks? Cc: freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I would very much like to see gzipped executables working again. >Without them, you can't use the fixit disk. (I know, I know, you can >use it with an older install disk. But that's not quite the same.) I sent this to the wrong list: --- I have been debugging the kernel gzip and rebooting the test systems a lot. exec_gzip_imgact() works fine if the final vm_map_remove() is omitted. Otherwise it hangs in various places in vm_map_remove() doing harmless-looking memory accesses, except the vm_map_remove() works OK if it is called only on every second gzip exec (after the previous one has left suitable garbage). It looks like a reference counting problem. The mapping that causes the problem is particularly simple. --- It might be acceptable to simply skip the vm_map_remove() for the fixit version. The vm_map_remove() is for a 4K mmapped window on the input file. There seems to be no problem removing and reallocating this window every 4K for input files larger than 4K. Bruce From owner-freebsd-current Sun Apr 21 13:37:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05369 for current-outgoing; Sun, 21 Apr 1996 13:37:06 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05347 for ; Sun, 21 Apr 1996 13:36:58 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26339 for ; Sun, 21 Apr 1996 22:36:49 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00274 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 22:36:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA14692 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 20:15:43 +0200 (MET DST) From: J Wunsch Message-Id: <199604211815.UAA14692@uriah.heep.sax.de> Subject: Re: Another 2.2-SNAP soon, folks? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 21 Apr 1996 20:15:42 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <5325.830102379@time.cdrom.com> from "Jordan K. Hubbard" at Apr 21, 96 08:59:39 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > Goals of this snapshot are to: > > 1. Get Justin's latest Adaptec support code out in bootable/installable > form. This would leave the question whether we should enable it on the install floppy or not. I'd say not, to prevent people from running into a chicken-and-egg problem, but i realize that it won't be tested very extensively then. Many people seem to run the GENERIC kernel now that we've got UserConfig and dset(8). :-/ I could try to see if i can come up with some better fdisk (or replacement tool), but i don't make any promises. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 21 13:37:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05392 for current-outgoing; Sun, 21 Apr 1996 13:37:11 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05373 for ; Sun, 21 Apr 1996 13:37:06 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26343 for ; Sun, 21 Apr 1996 22:36:51 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00277 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 22:36:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA14717 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 20:19:19 +0200 (MET DST) From: J Wunsch Message-Id: <199604211819.UAA14717@uriah.heep.sax.de> Subject: Re: Another 2.2-SNAP soon, folks? To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 21 Apr 1996 20:19:18 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604211640.JAA25438@austin.polstra.com> from "John Polstra" at Apr 21, 96 09:40:10 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As John Polstra wrote: > I would very much like to see gzipped executables working again. > Without them, you can't use the fixit disk. As a short-term solution, i think we could turn off gzipping. The stuff should fit (though it will become tight then). This would at least make the fixit floppy usable at all. It has the additional advantage that the fixit floppy would become much faster then (in particular, consider the pagein times from a floppy). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 21 13:37:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05554 for current-outgoing; Sun, 21 Apr 1996 13:37:49 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05510 for ; Sun, 21 Apr 1996 13:37:42 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26392 for ; Sun, 21 Apr 1996 22:37:38 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00304 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 22:37:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA15228 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 21:33:27 +0200 (MET DST) From: J Wunsch Message-Id: <199604211933.VAA15228@uriah.heep.sax.de> Subject: Re: gzipped executables To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 21 Apr 1996 21:33:27 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604192030.NAA08890@phaeton.artisoft.com> from "Terry Lambert" at Apr 19, 96 01:30:31 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Terry Lambert wrote: > > If this is the case, why did it used to work on Pentium processors? > > Because it's circumstantial based on where the code is loaded -- and now > it's loaded at a new place and you see the problem -- an optimized loop > is wholly in cache. > > I'm suprised, given the size of the cache, that it worked at all > on Pentium boxes, ever. It even breaks on a 386sx/16 now, and i would be really surprised to learn that this one has suddenly grown cache memory. :-) Nope, Terry, your point explained some rare cases where people couldn't boot zipped kernels unless they turned off their caches, but for the zipped binaries: try again. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 21 13:37:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05572 for current-outgoing; Sun, 21 Apr 1996 13:37:51 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05530 for ; Sun, 21 Apr 1996 13:37:46 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA26396 for ; Sun, 21 Apr 1996 22:37:40 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA00305 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 22:37:39 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA15263 for freebsd-current@FreeBSD.org; Sun, 21 Apr 1996 21:37:16 +0200 (MET DST) From: J Wunsch Message-Id: <199604211937.VAA15263@uriah.heep.sax.de> Subject: Re: gzipped executables To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 21 Apr 1996 21:37:16 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <2993.829958579@time.cdrom.com> from "Jordan K. Hubbard" at Apr 19, 96 05:02:59 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > This doesn't lead me to believe that the > failure is related to any particular processor or cache architecture > so much as it is a simple bug which has crept in and whacked the gzip > emulator. The bug might have been there forever, but it only got apparent due to some unrelated (most likely: VM) changes. The sad thing is that it ain't easy to debug. The symptom is that the machine is hard-resetting without a whisper, instead of falling back into DDB. The only method i could think of were single-stepping or ``breakpointing forward'' through the imgact_gzip code, but oh well, this will most likely require slightly more than an hour... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Apr 21 14:13:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA07569 for current-outgoing; Sun, 21 Apr 1996 14:13:12 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA07564 for ; Sun, 21 Apr 1996 14:13:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id OAA06027; Sun, 21 Apr 1996 14:11:34 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Another 2.2-SNAP soon, folks? In-reply-to: Your message of "Sun, 21 Apr 1996 20:15:42 +0200." <199604211815.UAA14692@uriah.heep.sax.de> Date: Sun, 21 Apr 1996 14:11:34 -0700 Message-ID: <6024.830121094@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > This would leave the question whether we should enable it on the > install floppy or not. I'd say not, to prevent people from running > into a chicken-and-egg problem, but i realize that it won't be tested > very extensively then. Many people seem to run the GENERIC kernel now > that we've got UserConfig and dset(8). :-/ I think you may be speaking about something else - I was just referring to his changes which support more members of the Adaptec family (th 7890 I think? Some weird on-board thing anyway). > I could try to see if i can come up with some better fdisk (or > replacement tool), but i don't make any promises. I wouldn't fight you on this one.. :-) Jordan From owner-freebsd-current Sun Apr 21 14:40:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08762 for current-outgoing; Sun, 21 Apr 1996 14:40:07 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA08744 Sun, 21 Apr 1996 14:40:05 -0700 (PDT) Message-Id: <199604212140.OAA08744@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: Another 2.2-SNAP soon, folks? In-reply-to: Your message of "Sun, 21 Apr 1996 20:15:42 +0200." <199604211815.UAA14692@uriah.heep.sax.de> Date: Sun, 21 Apr 1996 14:40:05 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >As Jordan K. Hubbard wrote: > >> Goals of this snapshot are to: >> >> 1. Get Justin's latest Adaptec support code out in bootable/installable >> form. > >This would leave the question whether we should enable it on the >install floppy or not. I'd say not, to prevent people from running >into a chicken-and-egg problem, but i realize that it won't be tested >very extensively then. Many people seem to run the GENERIC kernel now >that we've got UserConfig and dset(8). :-/ I believe Jordan is talking about the aic7850 support which was added since the last snap, not the SCB paging code. >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Apr 21 16:17:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15235 for current-outgoing; Sun, 21 Apr 1996 16:17:55 -0700 (PDT) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA15230 Sun, 21 Apr 1996 16:17:52 -0700 (PDT) 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 BAA03521 ; Mon, 22 Apr 1996 01:17:44 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id BAA08548 ; Mon, 22 Apr 1996 01:17:43 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.7) id BAA01087; Mon, 22 Apr 1996 01:06:00 +0200 (MET DST) From: Ollivier Robert Message-Id: <199604212306.BAA01087@keltia.freenix.fr> Subject: IIJ PPP and subnetting To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Date: Mon, 22 Apr 1996 01:06:00 +0200 (MET DST) Cc: freebsd-bugs@FreeBSD.ORG (FreeBSD Bugs' list) X-Operating-System: FreeBSD 2.2-CURRENT ctm#1889 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, My machine is on a /28 subnet in the range of 193.56.58.65-78. I have a PPP address of 193.56.58.46 (in another subnet) pointing to a machine on the side with a 193.56.58.33 address. Giving: ed0: flags=8843 mtu 1500 inet 193.56.58.65 netmask 0xfffffff0 broadcast 193.56.58.79 ether 00:00:c0:7c:66:48 tun0: flags=8051 mtu 1500 inet 193.56.58.46 --> 193.56.58.33 netmask 0xfffffff0 and: 242 [19:31] root@keltia:~# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 193.56.58.33 UGc 0 0 tun0 127.0.0.1 127.0.0.1 UH 0 0 lo0 193.56.58.33 193.56.58.46 UH 1 14 tun0 193.56.58.64/28 link#1 UC 0 0 224/4 link#1 UCS 0 0 When using IIJPPP, routing doesn't work at all: 258 [19:31] root@keltia:~# ping 193.56.58.33 PING 193.56.58.33 (193.56.58.33): 56 data bytes ^C --- 193.56.58.33 ping statistics --- 15 packets transmitted, 0 packets received, 100% packet loss It seems unable to cope with a subnetted network even if I define my address in ppp.conf, I can't even ping its own interface 193.56.58.46: 250 [19:32] root@keltia:~# ping 193.56.58.46 PING 193.56.58.46 (193.56.58.46): 56 data bytes ping: sendto: No route to host ping: wrote 193.56.58.46 64 chars, ret=-1 ping: sendto: No route to host /etc/ppp/ppp.conf ------------------------------------------------------------ brasil: set timeout 0 set phone XXXXXXXX set ifaddr 193.56.58.46 193.56.58.33 255.255.255.240 login ... add 0 0 HISADDR ------------------------------------------------------------ Kernel PPP works fine with the same setup: ppp0: flags=8051 mtu 1500 inet 193.56.58.46 --> 193.56.58.33 netmask 0xfffffff0 282 [19:44] root@keltia:~# ping 193.56.58.33 PING 193.56.58.33 (193.56.58.33): 56 data bytes 64 bytes from 193.56.58.33: icmp_seq=0 ttl=63 time=177.546 ms 64 bytes from 193.56.58.33: icmp_seq=1 ttl=63 time=169.326 ms Is this a bug in IIJ PPP ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #12: Sun Apr 14 16:01:04 MET DST 1996 From owner-freebsd-current Sun Apr 21 16:54:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA22185 for current-outgoing; Sun, 21 Apr 1996 16:54:06 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA22179 for ; Sun, 21 Apr 1996 16:54:03 -0700 (PDT) Received: (from jkh@localhost) by time.cdrom.com (8.7.5/8.6.9) id QAA06576 for current@freebsd.org; Sun, 21 Apr 1996 16:53:51 -0700 (PDT) Date: Sun, 21 Apr 1996 16:53:51 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199604212353.QAA06576@time.cdrom.com> To: current@freebsd.org Subject: What do folks think of the following patch? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It seems like world, update, all and install should be targets which include an optional sub-make in /etc/Makefile for the corresponding target (only the diff to world: is shown here). This would give us a nice way of doing site-specific stuff which is preserved across changes to /usr/src/Makefile. One person is already using it to build and install a new kernel at the end of each world build. Comments? Jordan From owner-freebsd-current Sun Apr 21 18:02:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA27250 for current-outgoing; Sun, 21 Apr 1996 18:02:18 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA27244 for ; Sun, 21 Apr 1996 18:02:15 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id TAA07674; Sun, 21 Apr 1996 19:02:03 -0600 Date: Sun, 21 Apr 1996 19:02:03 -0600 From: Nate Williams Message-Id: <199604220102.TAA07674@rocky.sri.MT.net> To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: What do folks think of the following patch? In-Reply-To: <199604212353.QAA06576@time.cdrom.com> References: <199604212353.QAA06576@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It seems like world, update, all and install should be targets which > include an optional sub-make in /etc/Makefile for the corresponding > target (only the diff to world: is shown here). This would give us > a nice way of doing site-specific stuff which is preserved across changes > to /usr/src/Makefile. Since both /etc/make.conf and /usr/src/Makefile are generated by us, what does adding it in the tree vs. having them add buy us? In either case, the end-user has to edit the files. (I'm not against the idea, but I don't see any purpose for it.) nate From owner-freebsd-current Sun Apr 21 18:17:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA28238 for current-outgoing; Sun, 21 Apr 1996 18:17:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA28231 for ; Sun, 21 Apr 1996 18:17:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA16344; Sun, 21 Apr 1996 18:12:21 -0700 From: Terry Lambert Message-Id: <199604220112.SAA16344@phaeton.artisoft.com> Subject: Re: Changes for vfork() To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Sun, 21 Apr 1996 18:12:21 -0700 (MST) Cc: peter@jhome.DIALix.COM, current@FreeBSD.ORG In-Reply-To: from "Sujal Patel" at Apr 21, 96 02:19:20 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Note that there are some programs still using these features.. tcsh, > > for one, uses the shared address space semantics to update some statistics > > in the parent. > > This is an absolutely horrible thing for a user program to do. The > vfork() call was never intended to allow you to update the parent's > address space and as the man page states, should never be used in such a > way. Besides, FreeBSD doesn't have an implementation that supports this > anyway :) If tcsh (I think it's actually csh) *really* wants to update > some of the parents address space on FreeBSD, it should use rfork() > instead IMO. The inevitble response to "you aren't supposed to use that interface to do that thing" is "how then am I supposed to do that thing", where "you are not supposed to" is not an acceptable answer. 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 Sun Apr 21 18:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA28396 for current-outgoing; Sun, 21 Apr 1996 18:18:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA28389 for ; Sun, 21 Apr 1996 18:18:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA16357; Sun, 21 Apr 1996 18:15:34 -0700 From: Terry Lambert Message-Id: <199604220115.SAA16357@phaeton.artisoft.com> Subject: Re: gzipped executables To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 21 Apr 1996 18:15:33 -0700 (MST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199604211933.VAA15228@uriah.heep.sax.de> from "J Wunsch" at Apr 21, 96 09:33:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It even breaks on a 386sx/16 now, and i would be really surprised to > learn that this one has suddenly grown cache memory. :-) > > Nope, Terry, your point explained some rare cases where people > couldn't boot zipped kernels unless they turned off their caches, but > for the zipped binaries: try again. Oh well, back to the "explain the fix working" theory drawing board, I suppose. 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 Sun Apr 21 18:55:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29840 for current-outgoing; Sun, 21 Apr 1996 18:55:58 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA29833 for ; Sun, 21 Apr 1996 18:55:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id SAA06804; Sun, 21 Apr 1996 18:55:37 -0700 (PDT) To: Nate Williams cc: current@freebsd.org Subject: Re: What do folks think of the following patch? In-reply-to: Your message of "Sun, 21 Apr 1996 19:02:03 MDT." <199604220102.TAA07674@rocky.sri.MT.net> Date: Sun, 21 Apr 1996 18:55:37 -0700 Message-ID: <6802.830138137@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /etc is not updated across upgrades, nor is it vulnerable to src smashing. Jordan > > It seems like world, update, all and install should be targets which > > include an optional sub-make in /etc/Makefile for the corresponding > > target (only the diff to world: is shown here). This would give us > > a nice way of doing site-specific stuff which is preserved across changes > > to /usr/src/Makefile. > > Since both /etc/make.conf and /usr/src/Makefile are generated by us, > what does adding it in the tree vs. having them add buy us? > > In either case, the end-user has to edit the files. > > (I'm not against the idea, but I don't see any purpose for it.) > > > > nate From owner-freebsd-current Sun Apr 21 22:13:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA10361 for current-outgoing; Sun, 21 Apr 1996 22:13:15 -0700 (PDT) Received: from neon.Glock.COM (neon.glock.com [198.82.228.159]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA10356 Sun, 21 Apr 1996 22:13:12 -0700 (PDT) Received: from neon.Glock.COM (localhost [127.0.0.1]) by neon.Glock.COM (8.7.5/8.7.3) with SMTP id BAA01330; Mon, 22 Apr 1996 01:13:10 -0400 (EDT) Message-ID: <317B1566.41C67EA6@Glock.COM> Date: Mon, 22 Apr 1996 01:13:10 -0400 From: "matthew c. mead" Organization: Glock Telecommunications X-Mailer: Mozilla 3.0b2 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: smpatel@freebsd.org CC: current@freebsd.org Subject: possible 4th option? [Re: kern/1102] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was looking through your discussion on the difficulties of differentiating a Linux ELF binary from a FreeBSD ELF binary. The 2nd option you mention is the one in which you would use currently unused bytes in the ELF e_ident tag. What you proposed for this method of distinguishing the two different systems' binaries was to modify each Linux executable so that it has an identification byte in it. Since at this point we only (am I wrong here?) support Linux and FreeBSD ELF binaries, wouldn't it be sufficient to have our ELF binary generation utilities put an identifier for FreeBSD into the ELF binary as mentioned above, and if that is detected, use the FreeBSD sysvec set, otherwise assume the Linux sysvec set? -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/ From owner-freebsd-current Mon Apr 22 04:38:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA00577 for current-outgoing; Mon, 22 Apr 1996 04:38:23 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA00571 for ; Mon, 22 Apr 1996 04:38:18 -0700 (PDT) Received: from gmarco.eclipse.org (ts1port10d.masternet.it [194.184.65.32]) by masternet.it (8.6.12/8.6.9) with SMTP id MAA05513 for ; Mon, 22 Apr 1996 12:36:32 +0200 Message-ID: <317B8B62.41C67EA6@masternet.it> Date: Mon, 22 Apr 1996 13:36:34 +0000 From: Gianmarco Giovannelli X-Mailer: Mozilla 3.0b2 (X11; I; FreeBSD 2.2-960323-SNAP i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Begin the ctm process... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am trying to begin the ctm upgrades of my FreeBSD 2.2-960323-SNAP taken by Walnut Creek Cdrom... Mr. Hubbard said to me that I need for beginning the next delta which is not in the CD rom distribution... So I downloaded from src-cur.1610.gz (because src-cur.1609.gz was the last in the CD) to src-cur.1706.gz but when I try to apply it return me first a warning about the lack of the .ctm-status, and then it exit with an error 72 here is the output : Warning: .ctm_status not found. FS: .ctm_status doesn't exist. Exit(72) Now please can you tell me the way to begin the ctm steps ? -- Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | Fidonet : 2:332/113.0@fidonet | __ | | Amiganet: 39:102/507@amiganet | __/// Gianmarco | | http://www.masternet.it/dsc/gmarco | \XX/ | +-------------------------------------+--------------------+ From owner-freebsd-current Mon Apr 22 05:06:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA01136 for current-outgoing; Mon, 22 Apr 1996 05:06:35 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA01128 for ; Mon, 22 Apr 1996 05:06:33 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uBKNx-0003wCC; Mon, 22 Apr 96 05:06 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id MAA06161; Mon, 22 Apr 1996 12:06:21 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Gianmarco Giovannelli cc: current@FreeBSD.org Subject: Re: Begin the ctm process... In-reply-to: Your message of "Mon, 22 Apr 1996 13:36:34 GMT." <317B8B62.41C67EA6@masternet.it> Date: Mon, 22 Apr 1996 12:06:20 +0000 Message-ID: <6159.830174780@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I am trying to begin the ctm upgrades of my > FreeBSD 2.2-960323-SNAP taken by Walnut Creek Cdrom... > > Mr. Hubbard said to me that I need for beginning the next delta which is > not in the CD rom distribution... > > So I downloaded from src-cur.1610.gz (because src-cur.1609.gz was the > last in the CD) to src-cur.1706.gz but when I try to apply it return me > first a warning about the lack of the .ctm-status, and then it exit with > an error 72 rm -rf /usr/src mkdir /usr/src cd /usr/src ctm < /cdrom/CTM/src-cur/src-cur.1500A.gz ctm < /cdrom/CTM/src-cur/src-cur.????.gz # expect a couple of warnings about src-cur.1500.gz src-cur.1500A.gz -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Apr 22 05:34:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA01845 for current-outgoing; Mon, 22 Apr 1996 05:34:52 -0700 (PDT) Received: from s1.GANet.NET (s1.GANet.NET [199.18.201.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA01840 Mon, 22 Apr 1996 05:34:50 -0700 (PDT) Received: (from ec0@localhost) by s1.GANet.NET (8.6.11/8.6.11) id IAA09784; Mon, 22 Apr 1996 08:33:30 -0400 Date: Mon, 22 Apr 1996 08:33:29 -0400 (EDT) From: Eric Chet To: "matthew c. mead" cc: smpatel@freebsd.org, current@freebsd.org Subject: Re: possible 4th option? [Re: kern/1102] In-Reply-To: <317B1566.41C67EA6@Glock.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, matthew c. mead wrote: > I was looking through your discussion on the difficulties of > differentiating a Linux ELF binary from a FreeBSD ELF binary. The 2nd > option you mention is the one in which you would use currently unused > bytes in the ELF e_ident tag. What you proposed for this method of > distinguishing the two different systems' binaries was to modify each > Linux executable so that it has an identification byte in it. Since at > this point we only (am I wrong here?) support Linux and FreeBSD ELF > binaries, wouldn't it be sufficient to have our ELF binary generation > utilities put an identifier for FreeBSD into the ELF binary as mentioned > above, and if that is detected, use the FreeBSD sysvec set, otherwise > assume the Linux sysvec set? > Hello Well how about Slowaris ELF binaries? Eric J. Chet (ejc@nasvr1.cb.att.com || ec0@ganet.net) Lucent Technologies, Bell Labs Innovations > > -matt > > -- > Matthew C. Mead > > mmead@Glock.COM > http://www.Glock.COM/~mmead/ > From owner-freebsd-current Mon Apr 22 05:47:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA02407 for current-outgoing; Mon, 22 Apr 1996 05:47:46 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA02402 for ; Mon, 22 Apr 1996 05:47:44 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id IAA04134; Mon, 22 Apr 1996 08:44:20 -0400 (EDT) Date: Mon, 22 Apr 1996 08:44:18 -0400 (EDT) From: Kim Culhan To: Joerg Wunsch cc: current@FreeBSD.org Subject: Re: more -current build failure In-Reply-To: <199604220534.HAA17747@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, J Wunsch wrote: > As Kim Culhan wrote: > > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ > > > > The above series of characters begins on line 531 and repeats a few hundred > > to the end of the file. > > Your file is damaged. My CVS master is okay, it hasn't been touched > for ages (October 1995). > > You might have serious disk/controller problems. I re-supped and this time the problem was gone, now just the mispelling of 'smrsh' in the sendmail makefile remains. kim -- kimc@w8hd.org From owner-freebsd-current Mon Apr 22 08:17:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA10948 for current-outgoing; Mon, 22 Apr 1996 08:17:21 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA10942 Mon, 22 Apr 1996 08:17:12 -0700 (PDT) Received: from mx10.netvision.net.il (mx10.NetVision.net.il [194.90.1.51]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id IAA09078; Mon, 22 Apr 1996 08:17:06 -0700 (PDT) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mx10.netvision.net.il (8.7.5/8.7.1) with SMTP id SAA02831; Mon, 22 Apr 1996 18:18:56 +0300 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Message-ID: X-Mailer: XFMail 0.4-beta [p0] on FreeBSD In-Reply-To: <199604210432.VAA22374@freefall.freebsd.org> Date: Mon, 22 Apr 1996 16:30:19 +0200 (IST) 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: "Justin T. Gibbs" Subject: RE: Aic7xxx driver update in current Cc: current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello! I tried the recent driver with and without the new option and my system refused to boot. At the fsck stage i got: (i copied it from the screen so it's not 100% correct) sd(...): unexpected targ_status: ff error code 1 , retries 4 timed out in common phase, SCSISIGI=3D0x84 asserted ATN - device reset in message buffer ahc0 Issued Channel A Bus Reset #1. 4 SCBs aborted And 3 last messages are being repeated only with number afters SCSISIGI being to changed to: 0x94 0xa4 0xb4 0xa4 0xb4 .... an so on. Here are boot messages from kernel built about 10 days ago: --------------------------------------------------------------------- FreeBSD 2.2-CURRENT #0: Fri Apr 12 13:34:07 IST 1996 root@Burka.NetVision.net.il:/usr/src/sys/compile/BURKA CPU: Pentium (89.98-MHz 586-class CPU) Origin =3D "GenuineIntel" Id =3D 0x525 Stepping=3D5 Features=3D0x1bf real memory =3D 41943040 (40960K bytes) avail memory =3D 39464960 (38540K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0 rev 64 on pci0:0 chip1 rev 1 on pci0:1 pci0:8: CMD, device=3D0x0640, class=3Dstorage (ide) int a irq 14 [no driver assigned] vga0 rev 0 int a irq ?? on pci0:9 ahc0 rev 0 int a irq 9 on pci0:12 pcibus_ihandler_attach: counting pci irq9's as clk0 irqs ahc0: aic7870 Single Channel, SCSI Id=3D7, 16 SCBs (ahc0:0:0): "HP C3725S 4299" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=3D0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pca0 on isa pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp[*UTP*] address 00:60:8c:b6:f8:b1 npx0 on motherboard npx0: INT 16 interface devfs ready to run new masks: bio c0000240, tty c003009a, net c003049a WARNING: / was not properly dismounted. --------------------------------------------------------------------- Boot messages from the latest kernel look the same except of ahc driver saying something about Tagged queueing. Here is my kernel configuration: --------------------------------------------------------------------- # # BURKA -- my desktop machine # # $Id: BURKA,v 1.1 1995/01/26 11:38:00 gena Exp $ # machine "i386" cpu "I586_CPU" maxusers 30 ident BURKA options INET #InterNETworking options GATEWAY #Host is a Gateway (forwards packets) options FFS #Berkeley Fast File System options NFS #Network File System options NFS_NOSERVER #Just client options MFS #Memory File System options PROCFS #Process File System options QUOTA #enable disk quotas options MSDOSFS #MS DOS File System options DEVFS #devices filesystem options "COMPAT_43" #Compatible with BSD 4.3 options LINUX #Linux compatibility options SYSVSHM options SYSVSEM options SYSVMSG options UCONSOLE #X Console support config kernel root on sd0 swap on sd0 dumps on sd0 controller isa0 controller scbus0 controller pci0 controller ahc1 device sd0 device cd0 #SCSI CD-ROMs controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ep0 at isa? port 0x300 net irq 10 vector epintr device pca0 at isa? tty pseudo-device snp 1 #Snoop device - to look at pty/vty/etc.. pseudo-device loop pseudo-device ether pseudo-device log pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device speaker pseudo-device bpfilter 4 #berkeley packet filter pseudo-device gzip #Exec gzipped a.out's pseudo-device vn --------------------------------------------------------------------- Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena This message was sent at 04/22/96 16:30:19 by XF-Mail From owner-freebsd-current Mon Apr 22 09:22:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15269 for current-outgoing; Mon, 22 Apr 1996 09:22:32 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA15260 Mon, 22 Apr 1996 09:22:27 -0700 (PDT) Message-Id: <199604221622.JAA15260@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Gennady Sorokopud cc: current@freefall.freebsd.org Subject: Re: Aic7xxx driver update in current In-reply-to: Your message of "Mon, 22 Apr 1996 16:30:19 +0200." Date: Mon, 22 Apr 1996 09:22:27 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hello! > >I tried the recent driver with and without the new option and >my system refused to boot. >At the fsck stage i got: (i copied it from the screen so it's not 100% correct >) Have you ever used tagged queuing with this drive before? That would have been options AHC_TAGENABLE in previous kernels. To ensure that this is the problem, #if 0 out the block of code starting on line 1535 and ending on line 1568 in i386/scsi/aic7xxx.c. If this does cure your problem, please try the original driver again and send me *exactly* what the error messages on the screen are. >Best regards. >-------- > Gennady B. Sorokopud - System programmer at NetVision Israel. > E-Mail: Gennady Sorokopud > Homepage: http://www.netvision.net.il/~gena > > This message was sent at 04/22/96 16:30:19 by XF-Mail > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Mon Apr 22 10:32:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA20913 for current-outgoing; Mon, 22 Apr 1996 10:32:54 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA20908 for ; Mon, 22 Apr 1996 10:32:51 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA09137; Mon, 22 Apr 1996 11:32:45 -0600 Date: Mon, 22 Apr 1996 11:32:45 -0600 From: Nate Williams Message-Id: <199604221732.LAA09137@rocky.sri.MT.net> To: "JULIAN Elischer" Cc: jkh@time.cdrom.com (Jordan K. Hubbard), nate@sri.MT.net, current@freebsd.org Subject: Re: What do folks think of the following patch? In-Reply-To: <199604221727.KAA19763@ref.tfs.com> References: <6802.830138137@time.cdrom.com> <199604221727.KAA19763@ref.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I would like a make world to also install etc if the DESTDIR is not / > I often make images of systems and want /etc to be rebuilt as well, but > it never is.. Except that almost *no-one* sets DESTDIR. This would cause virtually everyone to have their /etc files wiped out because they didn't hard-code DESTDIR. Now, installing the /etc files if DESTDIR is set would be acceptable, but it has never been part of the 'make world' process, and would need someone willing to take the time to make sure it fits in the current setup. Nate From owner-freebsd-current Mon Apr 22 10:41:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21530 for current-outgoing; Mon, 22 Apr 1996 10:41:57 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21525 Mon, 22 Apr 1996 10:41:53 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id DAA13067; Tue, 23 Apr 1996 03:39:57 +1000 Date: Tue, 23 Apr 1996 03:39:57 +1000 From: Bruce Evans Message-Id: <199604221739.DAA13067@godzilla.zeta.org.au> To: current@freebsd.org Subject: gzip bug Cc: dyson@freebsd.org, phk@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The gzip bug was introduced in the big vm patch on 1996/01/19. It seems to have nothing to do with any of the vm things in imgact_gzip.c. I replaced the input file accesses in NextByte() by accesses to an array of bytes and Flush() by return (ENOEXEC). This made inflate() do nothing fancier than malloc() and free(), but it still sometimes hung and sometimes rebooted. A user mode version of this worked fine. Some of the reboots went through the double fault handler but none of them stopped in ddb. Bruce From owner-freebsd-current Mon Apr 22 10:52:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22266 for current-outgoing; Mon, 22 Apr 1996 10:52:29 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA22261 for ; Mon, 22 Apr 1996 10:52:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id KAA09832; Mon, 22 Apr 1996 10:51:46 -0700 (PDT) To: "JULIAN Elischer" cc: nate@sri.MT.net, current@freebsd.org Subject: Re: What do folks think of the following patch? In-reply-to: Your message of "Mon, 22 Apr 1996 10:27:23 PDT." <199604221727.KAA19763@ref.tfs.com> Date: Mon, 22 Apr 1996 10:51:46 -0700 Message-ID: <9830.830195506@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I would like a make world to also install etc if the DESTDIR is not / > I often make images of systems and want /etc to be rebuilt as well, but > it never is.. Maybe once a little more work is done to "localize" the contents of /etc a bit more, I'll endorse this idea. Right now, however, there are a few too many /etc files that are often locally hacked and for which I wouldn't want to see the local changes go away. A successful automated merge would also take someone writing a script smart enough to do the job safely and reliably every single time, something I'm not going to hold my breath on - it's hard. Similarly, not updating your /etc/sysconfig but updating your /etc/netstart (say) can also get you into grief when some calling convention changes and you've now just broken yourself by updating only one half of the equation. However, here's another instance where my /etc/Makefile idea would help you - you could use it for keeping your own /etc migrated with each make world by hooking in some custom Elischer script to do the deed. :-) Jordan From owner-freebsd-current Mon Apr 22 11:43:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25842 for current-outgoing; Mon, 22 Apr 1996 11:43:16 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA25836 Mon, 22 Apr 1996 11:43:14 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uBQZj-0003w7C; Mon, 22 Apr 96 11:43 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id SAA06765; Mon, 22 Apr 1996 18:42:56 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Bruce Evans cc: current@FreeBSD.org, dyson@FreeBSD.org Subject: Re: gzip bug In-reply-to: Your message of "Tue, 23 Apr 1996 03:39:57 +1000." <199604221739.DAA13067@godzilla.zeta.org.au> Date: Mon, 22 Apr 1996 18:42:55 +0000 Message-ID: <6763.830198575@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The gzip bug was introduced in the big vm patch on 1996/01/19. I would like to get on the record that I have never fully convinced myself that the gzip did the right thing to the vm system, in particular I just called functions I could find usage of that did what I kindda needed, not quite knowing if I needed to do more than I did. What I wanted to say with that was, don't expect the version prior to that patch to have been >correct< maybe the vm system just was more tolerant before... -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Apr 22 11:56:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA26759 for current-outgoing; Mon, 22 Apr 1996 11:56:46 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA26754 Mon, 22 Apr 1996 11:56:42 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id EAA14944; Tue, 23 Apr 1996 04:54:51 +1000 Date: Tue, 23 Apr 1996 04:54:51 +1000 From: Bruce Evans Message-Id: <199604221854.EAA14944@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.tfs.com Subject: Re: gzip bug Cc: current@FreeBSD.org, dyson@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> The gzip bug was introduced in the big vm patch on 1996/01/19 >... >What I wanted to say with that was, don't expect the version prior to >that patch to have been >correct< maybe the vm system just was more >tolerant before... My cut down version doesn't use the vm system apart from malloc() and free() and initialization and cleanup in the higher level exec function. If inflate() is trashing something then it must be fairly subtle to have not been found by phkmalloc. I'll try inflate() as an lkm. Bruce From owner-freebsd-current Mon Apr 22 12:02:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27062 for current-outgoing; Mon, 22 Apr 1996 12:02:25 -0700 (PDT) Received: (from mpp@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27056 Mon, 22 Apr 1996 12:02:24 -0700 (PDT) From: Mike Pritchard Message-Id: <199604221902.MAA27056@freefall.freebsd.org> Subject: Re: What do folks think of the following patch? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 22 Apr 1996 12:02:23 -0700 (PDT) Cc: julian@ref.tfs.com, nate@sri.MT.net, current@freebsd.org In-Reply-To: <9830.830195506@time.cdrom.com> from "Jordan K. Hubbard" at Apr 22, 96 10:51:46 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > [...] > Similarly, not updating your /etc/sysconfig but updating your > /etc/netstart (say) can also get you into grief when some calling > convention changes and you've now just broken yourself by updating > only one half of the equation. /etc/sysconfig is the one thing I modify in /etc that I think is a pain in the ass to upgrade. Perhaps sysconfig should be created by a shell script, along the lines of: #!/bin/sh # # gensysconfig - generate a skeleton /etc/sysconfig, possibly # using the currently installed version to obtain current settings. nfs_client=NO nfs_server=NO [...all of the default sysconfig variables would be set here...] if [ $1 = "upgrade" ] then . /etc/sysconfig #get our current values fi cat <<__EOF__ # This is sysconfig - a file full of useful variables that you can set # to change the default startup behavior of your system. [...] # Set to YES if this machine will be an NFS client nfs_client=$nfs_client # Set to YES if this machine will be an NFS server nfs_server=$nfs_server [...] __EOF__ This would make upgrading to a new sysconfig trivial when new configuration options are added. Things get trickier when the meaning of an existing option changes somehow, but I can live with that, since I usually look at the diffs before deciding when I want to upgrade my /etc files anyways. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Mon Apr 22 12:11:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA27707 for current-outgoing; Mon, 22 Apr 1996 12:11:02 -0700 (PDT) Received: from epprod.elsevier.co.uk (epprod.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA27243 for ; Mon, 22 Apr 1996 12:04:04 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by epprod.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id UAA12648 for ; Mon, 22 Apr 1996 20:03:14 +0100 Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 22 Apr 1996 20:02:47 +0100 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id UAA10237; Mon, 22 Apr 1996 20:02:29 +0100 From: Paul Richards Message-Id: <199604221902.UAA10237@cadair.elsevier.co.uk> Subject: Re: What do folks think of the following patch? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 22 Apr 1996 20:02:28 +0100 (BST) Cc: julian@ref.tfs.com, nate@sri.MT.net, current@FreeBSD.org In-Reply-To: <9830.830195506@time.cdrom.com> from "Jordan K. Hubbard" at Apr 22, 96 10:51:46 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > > Right now, however, there are a few too many /etc files that are often > locally hacked and for which I wouldn't want to see the local changes > go away. A successful automated merge would also take someone writing > a script smart enough to do the job safely and reliably every single > time, something I'm not going to hold my breath on - it's hard. > Similarly, not updating your /etc/sysconfig but updating your > /etc/netstart (say) can also get you into grief when some calling > convention changes and you've now just broken yourself by updating > only one half of the equation. How about simply installing a .new file so the user realises something needs merging or even printing out a diff report. Even better would be a diff of the new version against the previous version of the file so that the user can see what's been changed in the FreeBSD default version and merge it in by hand. Something along those lines would be usefull. -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155 From owner-freebsd-current Mon Apr 22 12:35:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28969 for current-outgoing; Mon, 22 Apr 1996 12:35:34 -0700 (PDT) Received: from nauplius.rsmas.miami.edu (nauplius.rsmas.miami.edu [129.171.102.27]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28951 for ; Mon, 22 Apr 1996 12:35:28 -0700 (PDT) Received: (from ivan@localhost) by nauplius.rsmas.miami.edu (8.6.12/8.6.12) id PAA08676 for freebsd-current@freebsd.org; Mon, 22 Apr 1996 15:35:11 -0400 From: Ivan Lima Message-Id: <199604221935.PAA08676@nauplius.rsmas.miami.edu> Subject: shared library To: freebsd-current@freebsd.org Date: Mon, 22 Apr 1996 15:35:11 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Where can I find shared libraries like libc.so.3.0? -- /| Ivan Lima | O __/ |_ Rosenstiel School of Marine and Atmospheric Science | o /o \_/| Division of Marine Biology and Fisheries | ( < _ | ivan@nauplius.rsmas.miami.edu | \__ _/ \| http://nauplius.rsmas.miami.edu/homepage/home.html | \_| From owner-freebsd-current Mon Apr 22 13:18:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA04256 for current-outgoing; Mon, 22 Apr 1996 13:18:07 -0700 (PDT) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA04248 for ; Mon, 22 Apr 1996 13:18:00 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id KAA19763; Mon, 22 Apr 1996 10:27:23 -0700 (PDT) Message-Id: <199604221727.KAA19763@ref.tfs.com> Subject: Re: What do folks think of the following patch? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 22 Apr 1996 10:27:23 -0700 (PDT) From: "JULIAN Elischer" Cc: nate@sri.MT.net, current@freebsd.org In-Reply-To: <6802.830138137@time.cdrom.com> from "Jordan K. Hubbard" at Apr 21, 96 06:55:37 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I would like a make world to also install etc if the DESTDIR is not / I often make images of systems and want /etc to be rebuilt as well, but it never is.. > > > /etc is not updated across upgrades, nor is it vulnerable to src > smashing. > > Jordan > > > > > It seems like world, update, all and install should be targets which > > > include an optional sub-make in /etc/Makefile for the corresponding > > > target (only the diff to world: is shown here). This would give us > > > a nice way of doing site-specific stuff which is preserved across changes > > > to /usr/src/Makefile. > > > > Since both /etc/make.conf and /usr/src/Makefile are generated by us, > > what does adding it in the tree vs. having them add buy us? > > > > In either case, the end-user has to edit the files. > > > > (I'm not against the idea, but I don't see any purpose for it.) > > > > > > > > nate > > From owner-freebsd-current Mon Apr 22 13:26:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05013 for current-outgoing; Mon, 22 Apr 1996 13:26:27 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA05002 Mon, 22 Apr 1996 13:26:18 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA00276; Mon, 22 Apr 1996 16:26:02 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA16309; Mon, 22 Apr 1996 16:26:33 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 16:26:32 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: stable@freebsd.org Subject: request for a new "feature" as regards DDB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... After *almost* 10 days uptime, my system just died. That fact, in itself, doesn't bother me *too* much, or at least, not as much as the fact that I don't know why :( I happened to be off of vt0 when it died, with no way to switch to vt0 and see what ddb was showing, and since I had to cold boot the machine as a result, couldn't even get a core dump :( So...any way of having an auto-switch to vt0 if the system crashes with DDB enabled? Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Mon Apr 22 13:56:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09016 for current-outgoing; Mon, 22 Apr 1996 13:56:42 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA08995 for ; Mon, 22 Apr 1996 13:56:35 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id NAA01408; Mon, 22 Apr 1996 13:56:17 -0700 From: "Rodney W. Grimes" Message-Id: <199604222056.NAA01408@GndRsh.aac.dev.com> Subject: Re: What do folks think of the following patch? To: julian@ref.tfs.com (JULIAN Elischer) Date: Mon, 22 Apr 1996 13:56:17 -0700 (PDT) Cc: jkh@time.cdrom.com, nate@sri.MT.net, current@FreeBSD.org In-Reply-To: <199604221727.KAA19763@ref.tfs.com> from JULIAN Elischer at "Apr 22, 96 10:27:23 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I would like a make world to also install etc if the DESTDIR is not / > I often make images of systems and want /etc to be rebuilt as well, but > it never is.. Your so lazy you cant say: (make DESTDIR=/foo/bar install && cd etc; make DESTDIR=/foo/bar distribution) I've been doing it for 4 years now... > > /etc is not updated across upgrades, nor is it vulnerable to src > > smashing. > > > > Jordan > > > > > > > > It seems like world, update, all and install should be targets which > > > > include an optional sub-make in /etc/Makefile for the corresponding > > > > target (only the diff to world: is shown here). This would give us > > > > a nice way of doing site-specific stuff which is preserved across changes > > > > to /usr/src/Makefile. > > > > > > Since both /etc/make.conf and /usr/src/Makefile are generated by us, > > > what does adding it in the tree vs. having them add buy us? > > > > > > In either case, the end-user has to edit the files. > > > > > > (I'm not against the idea, but I don't see any purpose for it.) > > > > > > > > > > > > nate > > > > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Mon Apr 22 15:03:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17336 for current-outgoing; Mon, 22 Apr 1996 15:03:13 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA17328 for ; Mon, 22 Apr 1996 15:03:11 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id SAA05494; Mon, 22 Apr 1996 18:02:57 -0400 (EDT) Date: Mon, 22 Apr 1996 18:02:56 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: "Marc G. Fournier" cc: current@freebsd.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Marc G. Fournier wrote: > I happened to be off of vt0 when it died, with no way to > switch to vt0 and see what ddb was showing, and since I had to > cold boot the machine as a result, couldn't even get a core dump :( > > So...any way of having an auto-switch to vt0 if the system > crashes with DDB enabled? While we're talking about DDB, can't we have it timeout in 30s if you don't hit a key (and then generate a core dump). What about making DDB a LKM also? Whenever I find myself using DDB, I know that the system is going to panic, not everyone needs DDB loaded at all times (and rebuilding kernels is such a pain). Sujal From owner-freebsd-current Mon Apr 22 15:44:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21687 for current-outgoing; Mon, 22 Apr 1996 15:44:33 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA21675 for ; Mon, 22 Apr 1996 15:44:28 -0700 (PDT) Received: from gmarco.eclipse.org (ts1port4d.masternet.it [194.184.65.26]) by masternet.it (8.6.12/8.6.9) with SMTP id XAA07633; Mon, 22 Apr 1996 23:42:26 +0200 Message-ID: <317C2775.41C67EA6@masternet.it> Date: Tue, 23 Apr 1996 00:42:29 +0000 From: Gianmarco Giovannelli X-Mailer: Mozilla 3.0b2 (X11; I; FreeBSD 2.2-960323-SNAP i386) MIME-Version: 1.0 To: Poul-Henning Kamp CC: current@freebsd.org Subject: Re: Begin the ctm process... References: <6159.830174780@critter.tfs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > rm -rf /usr/src > mkdir /usr/src > cd /usr/src > ctm < /cdrom/CTM/src-cur/src-cur.1500A.gz > ctm < /cdrom/CTM/src-cur/src-cur.????.gz > # expect a couple of warnings about src-cur.1500.gz src-cur.1500A.gz > and then please ? :-) ^^^^^^^^^^^^^^^^ This because I use ctm to arrive till delta 1710 without any problems, but when I tried to do from /usr/src a make world or make && make install (that works like a charm in -stable :-) I receive error complaing something about files that are missing... (If my memory is right , the first fails on something about sendmail, the second on something missing like libc*, Is there a log ?) Thanks in advance (and again) for your attention.... Any hints are welcome... -- Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | Fidonet : 2:332/113.0@fidonet | __ | | Amiganet: 39:102/507@amiganet | __/// Gianmarco | | http://www.masternet.it/dsc/gmarco | \XX/ | +-------------------------------------+--------------------+ From owner-freebsd-current Mon Apr 22 15:47:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21942 for current-outgoing; Mon, 22 Apr 1996 15:47:17 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA21936 for ; Mon, 22 Apr 1996 15:47:15 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id PAA06258 for ; Mon, 22 Apr 1996 15:46:40 -0700 (PDT) Message-Id: <199604222246.PAA06258@precipice.shockwave.com> To: current@freebsd.org Subject: socks support native in freebsd? Date: Mon, 22 Apr 1996 15:46:40 -0700 From: Paul Traina Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I know I'm the "let's not bloat things out" guy, but I want to get some feedback on this idea. It seems like a big gain. I'd like to bring socks4 (and later socks5) into the FreeBSD source tree directly. The reason for doing so is that minor modifications to our utilities, such as telnet, ftp, et al need to be performed. I figure it would be more useful to the user community if we just make these changes /and/ ship our default binaries with socks support included. Everything will behave as normal, unless the user creates /etc/socks.conf which will then enable socks functionality. Comments? Paul p.s. for those who don't know, SOCKS is an application relay system for handling clients behind a firewall. Because SOCKS operates on TCP connections directly, it also means that you can do things that would otherwise require globally routable network addresses (e.g. SOCKS lets you do away with network address translators and use RFC 1597 addresses). From owner-freebsd-current Mon Apr 22 16:02:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA23769 for current-outgoing; Mon, 22 Apr 1996 16:02:13 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA23738 Mon, 22 Apr 1996 16:02:01 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id SAA01943; Mon, 22 Apr 1996 18:01:11 -0500 (EST) From: "John S. Dyson" Message-Id: <199604222301.SAA01943@dyson.iquest.net> Subject: Re: gzip bug To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Mon, 22 Apr 1996 18:01:11 -0500 (EST) Cc: bde@zeta.org.au, current@freebsd.org, dyson@freebsd.org In-Reply-To: <6763.830198575@critter.tfs.com> from "Poul-Henning Kamp" at Apr 22, 96 06:42:55 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > The gzip bug was introduced in the big vm patch on 1996/01/19. > Is it still broken with the latest pmap fix? There was a mega-major bogon there. John From owner-freebsd-current Mon Apr 22 16:04:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA24050 for current-outgoing; Mon, 22 Apr 1996 16:04:21 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA24045 for ; Mon, 22 Apr 1996 16:04:18 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uBUeU-0003xTC; Mon, 22 Apr 96 16:04 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id XAA07220; Mon, 22 Apr 1996 23:04:04 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Gianmarco Giovannelli cc: current@FreeBSD.org Subject: Re: Begin the ctm process... In-reply-to: Your message of "Tue, 23 Apr 1996 00:42:29 GMT." <317C2775.41C67EA6@masternet.it> Date: Mon, 22 Apr 1996 23:04:00 +0000 Message-ID: <7218.830214240@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Poul-Henning Kamp wrote: > > rm -rf /usr/src > > mkdir /usr/src > > cd /usr/src > > ctm < /cdrom/CTM/src-cur/src-cur.1500A.gz > > ctm < /cdrom/CTM/src-cur/src-cur.????.gz > > # expect a couple of warnings about src-cur.1500.gz src-cur.1500A.gz > > > > and then please ? :-) > ^^^^^^^^^^^^^^^^ > > This because I use ctm to arrive till delta 1710 without any problems, > but when I tried to do from /usr/src a > > make world > > or > > make && make install (that works like a charm in -stable :-) > > I receive error complaing something about files that are missing... > (If my memory is right , the first fails on something about sendmail, > the second on something missing like libc*, Is there a log ?) (Uhm, sounds like you need to read the handbook a bit) Try this: cd /usr/src make world >& w.x and then send me the last 200 lines of the /usr/src/w.x file -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Apr 22 16:15:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA25404 for current-outgoing; Mon, 22 Apr 1996 16:15:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA25386 Mon, 22 Apr 1996 16:15:07 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA22374; Tue, 23 Apr 1996 09:08:09 +1000 Date: Tue, 23 Apr 1996 09:08:09 +1000 From: Bruce Evans Message-Id: <199604222308.JAA22374@godzilla.zeta.org.au> To: phk@critter.tfs.com, toor@dyson.iquest.net Subject: Re: gzip bug Cc: bde@zeta.org.au, current@FreeBSD.org, dyson@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> > The gzip bug was introduced in the big vm patch on 1996/01/19. >> >Is it still broken with the latest pmap fix? There was a mega-major >bogon there. Yes. The fix seemed to delay the failure sometimes. Bruce From owner-freebsd-current Mon Apr 22 16:24:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA26504 for current-outgoing; Mon, 22 Apr 1996 16:24:18 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA26499 for ; Mon, 22 Apr 1996 16:24:15 -0700 (PDT) Received: from ole.cs.tu-berlin.de (wosch@ole.cs.tu-berlin.de [130.149.28.1]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id BAA14091 for ; Tue, 23 Apr 1996 01:24:12 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id AAA09484; Tue, 23 Apr 1996 00:03:21 +0200 Date: Tue, 23 Apr 1996 00:03:21 +0200 From: Wolfram Schneider Message-Id: <199604222203.AAA09484@campa.panke.de> To: current@freebsd.org Subject: Re: What do folks think of the following patch? In-Reply-To: <199604221732.LAA09137@rocky.sri.MT.net> References: <6802.830138137@time.cdrom.com> <199604221727.KAA19763@ref.tfs.com> <199604221732.LAA09137@rocky.sri.MT.net> Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk BTW, `make DESTDIR=/tmp/foo world' install bsd.*.mk files in /tmp/foo/usr/share/mk but use the old (and maybe wrong) *.mk files from /usr/share/mk. Wolfram Nate Williams writes: >> I would like a make world to also install etc if the DESTDIR is not / >> I often make images of systems and want /etc to be rebuilt as well, but >> it never is.. > >Except that almost *no-one* sets DESTDIR. This would cause virtually >everyone to have their /etc files wiped out because they didn't >hard-code DESTDIR. > >Now, installing the /etc files if DESTDIR is set would be acceptable, >but it has never been part of the 'make world' process, and would need >someone willing to take the time to make sure it fits in the current >setup. From owner-freebsd-current Mon Apr 22 16:35:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA27924 for current-outgoing; Mon, 22 Apr 1996 16:35:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA27912 Mon, 22 Apr 1996 16:35:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18124; Mon, 22 Apr 1996 16:29:55 -0700 From: Terry Lambert Message-Id: <199604222329.QAA18124@phaeton.artisoft.com> Subject: Re: possible 4th option? [Re: kern/1102] To: ec0@s1.GANet.NET (Eric Chet) Date: Mon, 22 Apr 1996 16:29:55 -0700 (MST) Cc: mmead@Glock.COM, smpatel@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "Eric Chet" at Apr 22, 96 08:33:29 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I was looking through your discussion on the difficulties of > > differentiating a Linux ELF binary from a FreeBSD ELF binary. The 2nd > > option you mention is the one in which you would use currently unused > > bytes in the ELF e_ident tag. What you proposed for this method of > > distinguishing the two different systems' binaries was to modify each > > Linux executable so that it has an identification byte in it. Since at > > this point we only (am I wrong here?) support Linux and FreeBSD ELF > > binaries, wouldn't it be sufficient to have our ELF binary generation > > utilities put an identifier for FreeBSD into the ELF binary as mentioned > > above, and if that is detected, use the FreeBSD sysvec set, otherwise > > assume the Linux sysvec set? This is unnecessary (hint: look at the Linux ELF binary load location, vs. the FreeBSD/SVR4 load location). > Hello > Well how about Slowaris ELF binaries? This is one of the fundamental flaws in using the EABI/ABI spec to constrain the ELF format (as SEF has pointed out). There is some possiblity of recognizing known crt0.o code; this is easily generalized, since there is no specific compatability requirements for keeping the existing FreeBSD ELF crt0.o (since ELF has not yet been deployed -- now you are glad we waited. 8-)). I suspect we will want the loader to load ld.so at 0x80001000 (or higher) to allow segment identifier based paging to take place. This type of paging would be necessary if we wanted to, for instance, migrate to the University of Utah OMOS implementation in place of the ELF/BSD shared library implementation. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Apr 22 16:39:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28464 for current-outgoing; Mon, 22 Apr 1996 16:39:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28453 for ; Mon, 22 Apr 1996 16:39:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18150; Mon, 22 Apr 1996 16:35:07 -0700 From: Terry Lambert Message-Id: <199604222335.QAA18150@phaeton.artisoft.com> Subject: Re: What do folks think of the following patch? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 22 Apr 1996 16:35:07 -0700 (MST) Cc: julian@ref.tfs.com, nate@sri.MT.net, current@FreeBSD.org In-Reply-To: <9830.830195506@time.cdrom.com> from "Jordan K. Hubbard" at Apr 22, 96 10:51:46 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I would like a make world to also install etc if the DESTDIR is not / > > I often make images of systems and want /etc to be rebuilt as well, but > > it never is.. > > Maybe once a little more work is done to "localize" the contents of > /etc a bit more, I'll endorse this idea. > > Right now, however, there are a few too many /etc files that are often > locally hacked and for which I wouldn't want to see the local changes > go away. A successful automated merge would also take someone writing > a script smart enough to do the job safely and reliably every single > time, something I'm not going to hold my breath on - it's hard. I agree with Jordan. The data needs to be better divorced from the implementation. There is too much information encoded in the /etc directory file contents that should really be elsewhere to allow automatic update to not shoot you in the foot (or crotch). 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 Apr 22 16:42:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28887 for current-outgoing; Mon, 22 Apr 1996 16:42:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28852 Mon, 22 Apr 1996 16:41:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18168; Mon, 22 Apr 1996 16:37:52 -0700 From: Terry Lambert Message-Id: <199604222337.QAA18168@phaeton.artisoft.com> Subject: Re: request for a new "feature" as regards DDB To: scrappy@ki.net (Marc G. Fournier) Date: Mon, 22 Apr 1996 16:37:52 -0700 (MST) Cc: current@FreeBSD.org, stable@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 22, 96 04:26:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > So...any way of having an auto-switch to vt0 if the system > crashes with DDB enabled? Assuming you aren't in X, yes, it's possible. If you are in X, after the panic, the console driver would need to send a signal to the X server process to get it to restore the console state. Obviously, the X server process can't run if your machine has paniced. 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 Mon Apr 22 16:48:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA29568 for current-outgoing; Mon, 22 Apr 1996 16:48:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA29559 for ; Mon, 22 Apr 1996 16:48:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18180; Mon, 22 Apr 1996 16:44:00 -0700 From: Terry Lambert Message-Id: <199604222344.QAA18180@phaeton.artisoft.com> Subject: Re: socks support native in freebsd? To: pst@shockwave.com (Paul Traina) Date: Mon, 22 Apr 1996 16:44:00 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199604222246.PAA06258@precipice.shockwave.com> from "Paul Traina" at Apr 22, 96 03:46:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I know I'm the "let's not bloat things out" guy, but I want to get some > feedback on this idea. It seems like a big gain. > > I'd like to bring socks4 (and later socks5) into the FreeBSD source tree > directly. The reason for doing so is that minor modifications to our > utilities, such as telnet, ftp, et al need to be performed. I figure it > would be more useful to the user community if we just make these changes > /and/ ship our default binaries with socks support included. > > Everything will behave as normal, unless the user creates /etc/socks.conf > which will then enable socks functionality. > > Comments? Socks functionality should be implemented via an IP tunnel; preferrably in a user space "socksd" process. It is a mistake to rebuild "telnet, ftp, et al" to achieve functionality that belongs at the transport layer, not in the applications. This would also fix the OBA (Only Binary Available) problem with trying to use Netscape or Nettrek clinets against a socks server. For what it's worth, this is the same class of thing that should be done to cause the effect that Linux's "IP Masquerading" gets by blatantly violating the RFC's when it isn't really necessary. 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 Apr 22 17:14:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA02600 for current-outgoing; Mon, 22 Apr 1996 17:14:09 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA02588 Mon, 22 Apr 1996 17:14:04 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id UAA03984; Mon, 22 Apr 1996 20:14:00 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id UAA17374; Mon, 22 Apr 1996 20:14:33 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 20:14:33 -0400 (EDT) From: "Marc G. Fournier" To: Terry Lambert cc: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604222337.QAA18168@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Terry Lambert wrote: > > So...any way of having an auto-switch to vt0 if the system > > crashes with DDB enabled? > > Assuming you aren't in X, yes, it's possible. > Is this one of those "do it yourself if you want it" sort of "possibles"? *grin* Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Mon Apr 22 17:49:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA05969 for current-outgoing; Mon, 22 Apr 1996 17:49:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA05925 Mon, 22 Apr 1996 17:49:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA18373; Mon, 22 Apr 1996 17:45:34 -0700 From: Terry Lambert Message-Id: <199604230045.RAA18373@phaeton.artisoft.com> Subject: Re: request for a new "feature" as regards DDB To: scrappy@ki.net (Marc G. Fournier) Date: Mon, 22 Apr 1996 17:45:34 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.org, stable@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 22, 96 08:14:33 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > So...any way of having an auto-switch to vt0 if the system > > > crashes with DDB enabled? > > > > Assuming you aren't in X, yes, it's possible. > > > Is this one of those "do it yourself if you want it" sort > of "possibles"? *grin* Possible, but not yet implemented by a cheerful volunteer. 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 Mon Apr 22 18:04:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA07947 for current-outgoing; Mon, 22 Apr 1996 18:04:23 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA07934 for ; Mon, 22 Apr 1996 18:04:19 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id SAA00857; Mon, 22 Apr 1996 18:07:36 -0700 Date: Mon, 22 Apr 1996 18:07:36 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Ivan Lima cc: freebsd-current@freebsd.org Subject: Re: shared library In-Reply-To: <199604221935.PAA08676@nauplius.rsmas.miami.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Ivan Lima wrote: > Where can I find shared libraries like libc.so.3.0? /usr/lib Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-current Mon Apr 22 18:37:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA11943 for current-outgoing; Mon, 22 Apr 1996 18:37:34 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA11935 Mon, 22 Apr 1996 18:37:29 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) with ESMTP id SAA03252; Mon, 22 Apr 1996 18:35:47 -0700 (PDT) Message-Id: <199604230135.SAA03252@austin.polstra.com> To: terry@lambert.org Cc: mmead@Glock.COM, smpatel@freebsd.org, current@freebsd.org, ec0@s1.GANet.NET Subject: Re: possible 4th option? [Re: kern/1102] In-reply-to: <199604222329.QAA18124@phaeton.artisoft.com> Date: Mon, 22 Apr 1996 18:35:47 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry wrote: > > > Since at > > > this point we only (am I wrong here?) support Linux and FreeBSD ELF > > > binaries, wouldn't it be sufficient to have our ELF binary generation > > > utilities put an identifier for FreeBSD into the ELF binary as mentioned > > > above, and if that is detected, use the FreeBSD sysvec set, otherwise > > > assume the Linux sysvec set? > > This is unnecessary (hint: look at the Linux ELF binary load location, > vs. the FreeBSD/SVR4 load location). That won't work any more. Linux and GNU have changed their binary load location to agree with FreeBSD/SVR4. > > > The 2nd > > > option you mention is the one in which you would use currently unused > > > bytes in the ELF e_ident tag. They're not unused -- they're _reserved_. If you stick anything other than 0 in them, you're technically no longer producing a valid ELF file. The analogous objection applies also to other ELF header fields such as e_type, e_machine, and e_flags. This may seem like a minor nit, but it's not. Suppose somebody else, say Sun, also decides to identify their executables using the extra bytes of the e_ident tag. Suppose their choice of values collides with yours. Too bad, you're out of luck. The ELF specification defines a mechanism for adding extra identifying information to an executable file: the PT_NOTE program header, and associated SHT_NOTE section. That's how I think that different kinds of ELF executables should be recognized. The good thing about NOTE sections is that each chunk of information contains, among other things, a "vendor tag" which is a string. It's not that likely that Sun is going to collide with a vendor tag of, say, "FreeBSD, Inc." or "Free Software Foundation". I'm going to try to add this kind of identification to our FreeBSD ELF executables, and fix the kernel to recognize them. (Unfortunately, as usual, the binutils code maze is doing its best to make this difficult for me.) I'd like to coordinate this with the Linux people, if they're interested. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Mon Apr 22 19:03:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA14815 for current-outgoing; Mon, 22 Apr 1996 19:03:55 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA14803 for ; Mon, 22 Apr 1996 19:03:52 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id WAA01003; Mon, 22 Apr 1996 22:03:41 -0400 (EDT) Date: Mon, 22 Apr 1996 22:03:41 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: John Polstra cc: current@freebsd.org Subject: Re: possible 4th option? [Re: kern/1102] In-Reply-To: <199604230135.SAA03252@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, John Polstra wrote: > They're not unused -- they're _reserved_. If you stick anything other > than 0 in them, you're technically no longer producing a valid ELF file. > The analogous objection applies also to other ELF header fields such as > e_type, e_machine, and e_flags. > > This may seem like a minor nit, but it's not. Suppose somebody else, > say Sun, also decides to identify their executables using the extra > bytes of the e_ident tag. Suppose their choice of values collides with > yours. Too bad, you're out of luck. You are absolutely correct here. Unless it's in the standard, it's a hack. > I'm going to try to add this kind of identification to our FreeBSD ELF > executables, and fix the kernel to recognize them. (Unfortunately, as > usual, the binutils code maze is doing its best to make this difficult > for me.) I'd like to coordinate this with the Linux people, if they're > interested. If you can coordinate with the Linux people, then I think this would be worthwhile; otherwise we may be the only ones using this technique. I still think that we will need a method for the user to specify EXACTLY what type of binary we're dealing with (for those "slip through the crack" cases). I think that a variation of my original patch (moving all environment parsing to libc), would work very well for this. Sujal From owner-freebsd-current Mon Apr 22 19:55:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA21377 for current-outgoing; Mon, 22 Apr 1996 19:55:38 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA21366 Mon, 22 Apr 1996 19:55:34 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id WAA05890; Mon, 22 Apr 1996 22:55:34 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id WAA17688; Mon, 22 Apr 1996 22:56:08 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 22:56:07 -0400 (EDT) From: "Marc G. Fournier" To: Terry Lambert cc: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604230045.RAA18373@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Terry Lambert wrote: > > > > So...any way of having an auto-switch to vt0 if the system > > > > crashes with DDB enabled? > > > > > > Assuming you aren't in X, yes, it's possible. > > > > > Is this one of those "do it yourself if you want it" sort > > of "possibles"? *grin* > > Possible, but not yet implemented by a cheerful volunteer. > Urmm...guess I'll volunteer then...*gets chainsaw tuned up* *laughs maniacally* Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Mon Apr 22 20:00:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA22250 for current-outgoing; Mon, 22 Apr 1996 20:00:20 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA22179 for ; Mon, 22 Apr 1996 20:00:10 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA07445; Tue, 23 Apr 1996 12:23:47 +0930 From: Michael Smith Message-Id: <199604230253.MAA07445@genesis.atrad.adelaide.edu.au> Subject: Re: socks support native in freebsd? To: terry@lambert.org (Terry Lambert) Date: Tue, 23 Apr 1996 12:23:47 +0930 (CST) Cc: pst@shockwave.com, current@FreeBSD.org In-Reply-To: <199604222344.QAA18180@phaeton.artisoft.com> from "Terry Lambert" at Apr 22, 96 04:44:00 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > Socks functionality should be implemented via an IP tunnel; > preferrably in a user space "socksd" process. This is total crap. How can you possibly implement what Socks does using a "tunnel"? Socks provides a standards-friendly means of hiding unroutable hosts behind a routed firewall. It provides healthy amounts of logging, and good configuration flexibility. > It is a mistake to rebuild "telnet, ftp, et al" to achieve > functionality that belongs at the transport layer, not in the > applications. The functionality is correctly implemented in the _library_ functions that telnet, ftp et. al call. Incorporating Socks proxy support in the system libraries would instantly Socksify _all_ of the system, including any ports built, as well as Perl and so forth. Given the popularity of firewalls these days, this would be a Big Plus. > This would also fix the OBA (Only Binary Available) problem with > trying to use Netscape or Nettrek clinets against a socks server. ...except that Netscape (at the least) already supports Socks, and in fact goes so far as to support making TCP DNS queries so that a UDP proxy isn't required. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Mon Apr 22 21:11:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA00846 for current-outgoing; Mon, 22 Apr 1996 21:11:30 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA00840 for ; Mon, 22 Apr 1996 21:11:26 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id VAA06842; Mon, 22 Apr 1996 21:10:03 -0700 (PDT) Message-Id: <199604230410.VAA06842@precipice.shockwave.com> To: Terry Lambert cc: current@FreeBSD.org Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Mon, 22 Apr 1996 16:44:00 PDT." <199604222344.QAA18180@phaeton.artisoft.com> Date: Mon, 22 Apr 1996 21:10:03 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From: Terry Lambert Subject: Re: socks support native in freebsd? > I know I'm the "let's not bloat things out" guy, but I want to get some > feedback on this idea. It seems like a big gain. > > I'd like to bring socks4 (and later socks5) into the FreeBSD source tree > directly. The reason for doing so is that minor modifications to our > utilities, such as telnet, ftp, et al need to be performed. I figure it > would be more useful to the user community if we just make these changes > /and/ ship our default binaries with socks support included. > > Everything will behave as normal, unless the user creates /etc/socks.conf > which will then enable socks functionality. > > Comments? Socks functionality should be implemented via an IP tunnel; preferrably in a user space "socksd" process. In theory, I agree with you 100%. I believe that individualized NAT technology is a wonderfully ugly and evil kludge that is going to stay. However, the proponents of application layer gateways like SOCKS want SOCKS functionality precicely because it happens at the application layer. My desire is to solve a problem. I'm not motivated by one technology or the other, as I've written both NAT code and application layer gateway code before. The problem I'm trying to solve is making FTP work in firewall environments, everything else is just a nice bonus. I've already produced two solutions for FreeBSD (passive mode and quarantine mode) and am just adding a useful third for folks who dislike either. From owner-freebsd-current Mon Apr 22 21:21:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01725 for current-outgoing; Mon, 22 Apr 1996 21:21:19 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA01716 for ; Mon, 22 Apr 1996 21:21:15 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA20182; Tue, 23 Apr 1996 06:21:09 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA06473; Tue, 23 Apr 1996 06:21:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id FAA21475; Tue, 23 Apr 1996 05:47:58 +0200 (MET DST) From: J Wunsch Message-Id: <199604230347.FAA21475@uriah.heep.sax.de> Subject: Re: request for a new "feature" as regards DDB To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 05:47:57 +0200 (MET DST) Cc: scrappy@ki.net (Marc G. Fournier) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Marc G. Fournier" at Apr 22, 96 08:14:33 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Marc G. Fournier wrote: > > > So...any way of having an auto-switch to vt0 if the system > > > crashes with DDB enabled? > > > > Assuming you aren't in X, yes, it's possible. > > > Is this one of those "do it yourself if you want it" sort > of "possibles"? *grin* It's not too easy, since the console drivers don't export the VT switch functions (or at least, they should not export them), and DDB provides no hook for the console drivers to be called when DDB is entered. Please, don't add another crock, rather implement a generic ``ddb_enter'' (or whatever) hook. I'm sure Bruce will have an opinion about this, too. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Apr 22 21:21:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01744 for current-outgoing; Mon, 22 Apr 1996 21:21:21 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA01724 for ; Mon, 22 Apr 1996 21:21:19 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA20186 for ; Tue, 23 Apr 1996 06:21:10 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA06475 for freebsd-current@FreeBSD.org; Tue, 23 Apr 1996 06:21:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id FAA21363 for freebsd-current@FreeBSD.org; Tue, 23 Apr 1996 05:38:33 +0200 (MET DST) From: J Wunsch Message-Id: <199604230338.FAA21363@uriah.heep.sax.de> Subject: Re: gzip bug To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 05:38:33 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <6763.830198575@critter.tfs.com> from "Poul-Henning Kamp" at Apr 22, 96 06:42:55 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Poul-Henning Kamp wrote: > I would like to get on the record that I have never fully convinced > myself that the gzip did the right thing to the vm system, in particular > I just called functions I could find usage of that did what I kindda > needed, not quite knowing if I needed to do more than I did. Time for somebody to write vm(9)? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Apr 22 21:21:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01762 for current-outgoing; Mon, 22 Apr 1996 21:21:24 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA01723 for ; Mon, 22 Apr 1996 21:21:18 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA20177; Tue, 23 Apr 1996 06:21:08 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA06470; Tue, 23 Apr 1996 06:21:07 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id FAA21385; Tue, 23 Apr 1996 05:39:40 +0200 (MET DST) From: J Wunsch Message-Id: <199604230339.FAA21385@uriah.heep.sax.de> Subject: Re: shared library To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 05:39:39 +0200 (MET DST) Cc: ivan@nauplius.rsmas.miami.edu (Ivan Lima) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604221935.PAA08676@nauplius.rsmas.miami.edu> from "Ivan Lima" at Apr 22, 96 03:35:11 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Ivan Lima wrote: > > Where can I find shared libraries like libc.so.3.0? In FreeBSD-current. Try ftp.freebsd.org, somewhere you should find `FreeBSD-current'. The shared libs are in usr/lib/. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Apr 22 22:44:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06016 for current-outgoing; Mon, 22 Apr 1996 22:44:33 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA06011 for ; Mon, 22 Apr 1996 22:44:30 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id WAA19305; Mon, 22 Apr 1996 22:44:02 -0700 (PDT) Date: Mon, 22 Apr 1996 22:44:02 -0700 (PDT) Message-Id: <199604230544.WAA19305@silvia.HIP.Berkeley.EDU> To: ivan@nauplius.rsmas.miami.edu CC: freebsd-current@freebsd.org In-reply-to: <199604221935.PAA08676@nauplius.rsmas.miami.edu> (message from Ivan Lima on Mon, 22 Apr 1996 15:35:11 -0400 (EDT)) Subject: Re: shared library From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Where can I find shared libraries like libc.so.3.0? If you are running -current, it's in /usr/lib. ("/sbin/ldconfig -r" will tell you where all the shared libraries are on your system.) If you are not, and are trying to run the packages you picked up from packages-current, just do an "ln -s libc.so.2.2 libc.so.3.0". That will probably work for most applications, the differences so far are only a few deleted functions so running libc.so.3.0 binaries that way won't cause any problems. Note that everything you compile from now on will be linked to that version of libc, and you can no longer give binaries to your friends running 2.1R, for instance. Also, the ports are tracking -current, so some of them will not work on 2.1R or -stable. Satoshi From owner-freebsd-current Mon Apr 22 23:38:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA08250 for current-outgoing; Mon, 22 Apr 1996 23:38:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA08245 for ; Mon, 22 Apr 1996 23:38:34 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id XAA18930; Mon, 22 Apr 1996 23:33:29 -0700 From: Terry Lambert Message-Id: <199604230633.XAA18930@phaeton.artisoft.com> Subject: Re: socks support native in freebsd? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 22 Apr 1996 23:33:29 -0700 (MST) Cc: terry@lambert.org, pst@shockwave.com, current@FreeBSD.org In-Reply-To: <199604230253.MAA07445@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 23, 96 12:23:47 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Socks functionality should be implemented via an IP tunnel; > > preferrably in a user space "socksd" process. > > This is total crap. How can you possibly implement what Socks does > using a "tunnel"? Socks provides a standards-friendly means of > hiding unroutable hosts behind a routed firewall. It provides > healthy amounts of logging, and good configuration flexibility. By IP tunneling the default route to the socksd that then forwards it to the forwarding host using a static route to the real interface. Local routes can also go to the local linterface statically, by net. Socks *functionality* is the ability to forward packets by proxy through a connection to a proxy agent on the firewall. This has the benefit of *not* implementing the "functionality" of "recompile all socket using programs". > > It is a mistake to rebuild "telnet, ftp, et al" to achieve > > functionality that belongs at the transport layer, not in the > > applications. > > The functionality is correctly implemented in the _library_ functions > that telnet, ftp et. al call. Incorporating Socks proxy support in the > system libraries would instantly Socksify _all_ of the system, including > any ports built, as well as Perl and so forth. > > Given the popularity of firewalls these days, this would be a Big Plus. First, he was talking about implementing it on a per application basis via the makefile hack that is recommended by the socks package. Second, this is an atypical network configuration, and the average user should not have to pay for it in their libc. > > This would also fix the OBA (Only Binary Available) problem with > > trying to use Netscape or Nettrek clinets against a socks server. > > ...except that Netscape (at the least) already supports Socks, and in fact > goes so far as to support making TCP DNS queries so that a UDP proxy isn't > required. Fine. Pick a binary program other than Netscape which does not support socks. 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 Apr 22 23:51:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA08730 for current-outgoing; Mon, 22 Apr 1996 23:51:34 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA08725 for ; Mon, 22 Apr 1996 23:51:31 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id XAA12653; Mon, 22 Apr 1996 23:49:24 -0700 (PDT) Message-Id: <199604230649.XAA12653@precipice.shockwave.com> To: Terry Lambert cc: msmith@atrad.adelaide.edu.au (Michael Smith), current@FreeBSD.org Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Mon, 22 Apr 1996 23:33:29 PDT." <199604230633.XAA18930@phaeton.artisoft.com> Date: Mon, 22 Apr 1996 23:49:23 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk From: Terry Lambert Subject: Re: socks support native in freebsd? By IP tunneling the default route to the socksd that then forwards it to the forwarding host using a static route to the real interface. Local routes can also go to the local linterface statically, by net. Socks *functionality* is the ability to forward packets by proxy through a connection to a proxy agent on the firewall. This has the benefit of *not* implementing the "functionality" of "recompile all socket using programs". > > It is a mistake to rebuild "telnet, ftp, et al" to achieve > > functionality that belongs at the transport layer, not in the > > applications. > > The functionality is correctly implemented in the _library_ functions > that telnet, ftp et. al call. Incorporating Socks proxy support in the > system libraries would instantly Socksify _all_ of the system, including > any ports built, as well as Perl and so forth. > > Given the popularity of firewalls these days, this would be a Big Plus. First, he was talking about implementing it on a per application basis via the makefile hack that is recommended by the socks package. True. Second, this is an atypical network configuration, and the average user should not have to pay for it in their libc. Untrue, however that's what libsocks.so is for. However, the point is moot, since socks5 uses LD_PRELOAD to implement its magic, socks5 can be made a "real" package because there is no need to modify our code to link in the proxy fake-out code. I'm going to back out my changes for socks4, they're irrelevant with socks5. From owner-freebsd-current Tue Apr 23 00:02:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09119 for current-outgoing; Tue, 23 Apr 1996 00:02:29 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA09113 for ; Tue, 23 Apr 1996 00:02:23 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA09490; Tue, 23 Apr 1996 16:26:58 +0930 From: Michael Smith Message-Id: <199604230656.QAA09490@genesis.atrad.adelaide.edu.au> Subject: Re: socks support native in freebsd? To: terry@lambert.org (Terry Lambert) Date: Tue, 23 Apr 1996 16:26:58 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, terry@lambert.org, pst@shockwave.com, current@FreeBSD.org In-Reply-To: <199604230633.XAA18930@phaeton.artisoft.com> from "Terry Lambert" at Apr 22, 96 11:33:29 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > > This is total crap. How can you possibly implement what Socks does > > using a "tunnel"? Socks provides a standards-friendly means of > > hiding unroutable hosts behind a routed firewall. It provides > > healthy amounts of logging, and good configuration flexibility. > > By IP tunneling the default route to the socksd that then forwards > it to the forwarding host using a static route to the real interface. How is this different from the already-deemed-evil Linux "IP Masquerading"? The 'tunnel' approach either requires a socks-like protocol, which requires application (or library) support, or it rewrites packet headers. > Local routes can also go to the local linterface statically, by net. Heh. That's the linterface that uses static to collect dropped routes? 8) > > Given the popularity of firewalls these days, this would be a Big Plus. > > First, he was talking about implementing it on a per application > basis via the makefile hack that is recommended by the socks > package. Actually, Paul was talking about 'whatever is state-of-the-art'. Witness the upcoming back-outs of the initial socks-4 stuff, and the implementation of the (optional) socks-5 shared-library features. > Second, this is an atypical network configuration, and the average > user should not have to pay for it in their libc. *snort*. There are a million warts that the 'average user' pays for already in their libc. I would suggest that any overhead that Socks-awareness would impose on the (small) number of relevant system calls would be noise against interrupt latency on the average network interface. > > ...except that Netscape (at the least) already supports Socks, and in fact > > goes so far as to support making TCP DNS queries so that a UDP proxy isn't > > required. > > Fine. Pick a binary program other than Netscape which does not support > socks. Hmm. Microsoft Explorer, perhaps. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 00:04:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09239 for current-outgoing; Tue, 23 Apr 1996 00:04:14 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA09199 for ; Tue, 23 Apr 1996 00:03:59 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id JAA07879 for current@freebsd.org; Tue, 23 Apr 1996 09:03:30 +0200 Message-Id: <199604230703.JAA07879@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: smpatel@umiacs.umd.edu (Sujal Patel) Date: Tue, 23 Apr 96 9:00:15 MDT From: Greg Lehey Cc: current@freebsd.org, hackers@freebsd.org (FreeBSD hackers) In-Reply-To: ; from "Sujal Patel" at Apr 22, 96 6:02 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 22 Apr 1996, Marc G. Fournier wrote: > >> I happened to be off of vt0 when it died, with no way to >> switch to vt0 and see what ddb was showing, and since I had to >> cold boot the machine as a result, couldn't even get a core dump :( >> >> So...any way of having an auto-switch to vt0 if the system >> crashes with DDB enabled? Good idea. I'll add it to my list. For those who don't know, I had planned to make some major changes to ddb Real Soon Now. > While we're talking about DDB, can't we have it timeout in 30s if you > don't hit a key (and then generate a core dump). Also a good idea. > What about making DDB a LKM also? Whenever I find myself using DDB, I > know that the system is going to panic, not everyone needs DDB loaded at > all times (and rebuilding kernels is such a pain). Yes, I had planned on that. Who can give me info on how to write LKMs? On the other subject, changing out of X into character mode: I believe that a debugger should have as little involvement with the subject being debugged (in this case, the kernel), as possible. I can't see why ddb shouldn't understand enough about generic VGA to be able to put it back in 25x80 mode. Somewhere I have a little program which I used to do this under BSD/386 0.3, where the X server wasn't always successful. It's only a few lines. I'm sure somebody's going to come up with "yes, but that's not completely generic", but I don't think this is an adequate argument. Make it a config option for ddb, and it'll handle 98% of all hardware. If somebody with the other 2% wants, they can do it for that hardware as well. I'm copying hackers on this, since that is where we discussed ddb before. Greg From owner-freebsd-current Tue Apr 23 00:08:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09928 for current-outgoing; Tue, 23 Apr 1996 00:08:58 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09923 for ; Tue, 23 Apr 1996 00:08:57 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uBcCt-0003wCC; Tue, 23 Apr 96 00:08 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id GAA07856; Tue, 23 Apr 1996 06:05:58 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: gzip bug In-reply-to: Your message of "Tue, 23 Apr 1996 05:38:33 +0200." <199604230338.FAA21363@uriah.heep.sax.de> Date: Tue, 23 Apr 1996 06:05:58 +0000 Message-ID: <7854.830239558@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > As Poul-Henning Kamp wrote: > > > I would like to get on the record that I have never fully convinced > > myself that the gzip did the right thing to the vm system, in particular > > I just called functions I could find usage of that did what I kindda > > needed, not quite knowing if I needed to do more than I did. > > Time for somebody to write vm(9)? :) yes please! -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Apr 23 00:09:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA09982 for current-outgoing; Tue, 23 Apr 1996 00:09:20 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09976 for ; Tue, 23 Apr 1996 00:09:19 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uBcCv-0003wFC; Tue, 23 Apr 96 00:08 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id FAA07652; Tue, 23 Apr 1996 05:48:00 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Paul Traina cc: current@FreeBSD.org Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Mon, 22 Apr 1996 15:46:40 MST." <199604222246.PAA06258@precipice.shockwave.com> Date: Tue, 23 Apr 1996 05:47:59 +0000 Message-ID: <7650.830238479@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I know I'm the "let's not bloat things out" guy, but I want to get some > feedback on this idea. It seems like a big gain. > > I'd like to bring socks4 (and later socks5) into the FreeBSD source tree > directly. The reason for doing so is that minor modifications to our > utilities, such as telnet, ftp, et al need to be performed. I figure it > would be more useful to the user community if we just make these changes > /and/ ship our default binaries with socks support included. YES! -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Apr 23 00:24:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA11750 for current-outgoing; Tue, 23 Apr 1996 00:24:37 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA11733 for ; Tue, 23 Apr 1996 00:24:03 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id JAA09548 for current@freebsd.org; Tue, 23 Apr 1996 09:23:27 +0200 Message-Id: <199604230723.JAA09548@nixpbe.pdb.sni.de> Subject: Re: possible 4th option? [Re: kern/1102] To: jdp@polstra.com (John Polstra) Date: Tue, 23 Apr 96 9:23:07 MDT From: Greg Lehey Cc: terry@lambert.org, mmead@Glock.COM, smpatel@freebsd.org, current@freebsd.org, ec0@s1.GANet.NET In-Reply-To: <199604230135.SAA03252@austin.polstra.com>; from "John Polstra" at Apr 22, 96 6:35 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> The 2nd >>>> option you mention is the one in which you would use currently unused >>>> bytes in the ELF e_ident tag. > > They're not unused -- they're _reserved_. If you stick anything other > than 0 in them, you're technically no longer producing a valid ELF file. > The analogous objection applies also to other ELF header fields such as > e_type, e_machine, and e_flags. > > The ELF specification defines a mechanism for adding extra identifying > information to an executable file: the PT_NOTE program header, and > associated SHT_NOTE section. That's how I think that different kinds > of ELF executables should be recognized. The good thing about NOTE > sections is that each chunk of information contains, among other things, > a "vendor tag" which is a string. It's not that likely that Sun is > going to collide with a vendor tag of, say, "FreeBSD, Inc." or "Free > Software Foundation". Sounds reasonable, even if it's a bit tedious. > I'm going to try to add this kind of identification to our FreeBSD ELF > executables, and fix the kernel to recognize them. (Unfortunately, as > usual, the binutils code maze is doing its best to make this difficult > for me.) I'd like to coordinate this with the Linux people, if they're > interested. Good idea. While you're at it, why not give Sun and SCO a chance to cooperate? Greg From owner-freebsd-current Tue Apr 23 02:34:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA21202 for current-outgoing; Tue, 23 Apr 1996 02:34:46 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA21179 Tue, 23 Apr 1996 02:34:30 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id TAA12645; Tue, 23 Apr 1996 19:28:35 +1000 Date: Tue, 23 Apr 1996 19:28:35 +1000 From: Bruce Evans Message-Id: <199604230928.TAA12645@godzilla.zeta.org.au> To: lehey.pad@sni.de, smpatel@umiacs.UMD.EDU Subject: Re: request for a new "feature" as regards DDB Cc: current@freebsd.org, hackers@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>> So...any way of having an auto-switch to vt0 if the system >>> crashes with DDB enabled? Use syscons. >Good idea. I'll add it to my list. For those who don't know, I had >planned to make some major changes to ddb Real Soon Now. >> While we're talking about DDB, can't we have it timeout in 30s if you >> don't hit a key (and then generate a core dump). >Also a good idea. Bad idea. You should make sure that ddb is never entered if you're not around to watch it. >> What about making DDB a LKM also? Whenever I find myself using DDB, I >Yes, I had planned on that. Who can give me info on how to write >LKMs? Begin with /usr/src/share/examples/lkm. >On the other subject, changing out of X into character mode: I believe >that a debugger should have as little involvement with the subject >being debugged (in this case, the kernel), as possible. I can't see Yes, it shouldn't touch anything that it doesn't fully understand or can't restore. >why ddb shouldn't understand enough about generic VGA to be able to >put it back in 25x80 mode. Somewhere I have a little program which I >used to do this under BSD/386 0.3, where the X server wasn't always >successful. It's only a few lines. I'm sure somebody's going to come >up with "yes, but that's not completely generic", but I don't think >this is an adequate argument. Make it a config option for ddb, and "yes, but that's not completely generic" :-). >it'll handle 98% of all hardware. If somebody with the other 2% >wants, they can do it for that hardware as well. It'll only handle 98% of all hardware that is running in a VGA compatible mode. I guess most X modes aren't VGA compatible. Bruce From owner-freebsd-current Tue Apr 23 03:02:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22134 for current-outgoing; Tue, 23 Apr 1996 03:02:00 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA22106 for ; Tue, 23 Apr 1996 03:01:24 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id MAA20819 for current@freebsd.org; Tue, 23 Apr 1996 12:00:49 +0200 Message-Id: <199604231000.MAA20819@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Tue, 23 Apr 96 12:00:43 MDT From: Greg Lehey Cc: lehey.pad@sni.de, smpatel@umiacs.UMD.EDU, current@freebsd.org, hackers@freebsd.org In-Reply-To: <199604230928.TAA12645@godzilla.zeta.org.au>; from "Bruce Evans" at Apr 23, 96 7:28 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> So...any way of having an auto-switch to vt0 if the system >>>> crashes with DDB enabled? > > Use syscons. I don't understand. Are you saying "syscons auto-switches to vt0 if the system crashes with DDB enabled", or are you saying "if you use syscons, you can still change after entering DDB", or are you saying something else? >> Good idea. I'll add it to my list. For those who don't know, I had >> planned to make some major changes to ddb Real Soon Now. > >>> While we're talking about DDB, can't we have it timeout in 30s if you >>> don't hit a key (and then generate a core dump). > >> Also a good idea. > > Bad idea. You should make sure that ddb is never entered if you're not > around to watch it. I disagree completely. If my machine dies in the middle of the night, I want to come in the next morning and be able to debug the live hardware, not a dump. YMMV, but we should have the option. >>> What about making DDB a LKM also? Whenever I find myself using DDB, I > >> Yes, I had planned on that. Who can give me info on how to write >> LKMs? > > Begin with /usr/src/share/examples/lkm. Thanks. >> On the other subject, changing out of X into character mode: I believe >> that a debugger should have as little involvement with the subject >> being debugged (in this case, the kernel), as possible. I can't see > > Yes, it shouldn't touch anything that it doesn't fully understand or > can't restore. > >> why ddb shouldn't understand enough about generic VGA to be able to >> put it back in 25x80 mode. Somewhere I have a little program which I >> used to do this under BSD/386 0.3, where the X server wasn't always >> successful. It's only a few lines. I'm sure somebody's going to come >> up with "yes, but that's not completely generic", but I don't think >> this is an adequate argument. Make it a config option for ddb, and > > "yes, but that's not completely generic" :-). > >> it'll handle 98% of all hardware. If somebody with the other 2% >> wants, they can do it for that hardware as well. > > It'll only handle 98% of all hardware that is running in a VGA compatible > mode. I guess most X modes aren't VGA compatible. Hmmm. I'd have to check that. We're not interested in the non-compatible modes, we're just interested in whether we can set a VGA compatible mode when we need it. My program ran on an ET4000, and it worked OK, but I suppose it's possible that more modern hardware might not have a simple way to set it back to character mode. I'll enquire. Greg From owner-freebsd-current Tue Apr 23 03:59:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA24209 for current-outgoing; Tue, 23 Apr 1996 03:59:50 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA24061 Tue, 23 Apr 1996 03:56:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA15838; Tue, 23 Apr 1996 20:45:26 +1000 Date: Tue, 23 Apr 1996 20:45:26 +1000 From: Bruce Evans Message-Id: <199604231045.UAA15838@godzilla.zeta.org.au> To: bde@zeta.org.au, lehey.pad@sni.de Subject: Re: request for a new "feature" as regards DDB Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, smpatel@umiacs.UMD.EDU Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> So...any way of having an auto-switch to vt0 if the system >>>>> crashes with DDB enabled? >> >> Use syscons. >I don't understand. Are you saying "syscons auto-switches to vt0 if >the system crashes with DDB enabled", or are you saying "if you use I meant that syscons auto-switches from ttyvn to ttyv0 when DDB is entered. It actually stays on the same ttyvn, just like pcvt, and you have to hit Alt-F1 to switch to it, not quite like in pcvt, where you have to hit Ctr-Alt-F1. Switching from graphics mode of course doesn't work for either syscons or pcvt. >> Bad idea. You should make sure that ddb is never entered if you're not >> around to watch it. >I disagree completely. If my machine dies in the middle of the night, >I want to come in the next morning and be able to debug the live >hardware, not a dump. YMMV, but we should have the option. OK, you should makesure that ddb is never entered if you don't want it to wait. Entering ddb decreases the chance of getting a clean dump and reboot. There is currently no simple way of returning from ddb to continue as if ddb wasn't configured except when ddb was entered via Debugger() (if it was entered via kdb_trap(), then you have to modify some ddb code or variables to get it to return 0). The normal way to quit ddb after a fatal trap is to use the builtin panic, but this complicates the trap frames. >> It'll only handle 98% of all hardware that is running in a VGA compatible >> mode. I guess most X modes aren't VGA compatible. >Hmmm. I'd have to check that. We're not interested in the >non-compatible modes, we're just interested in whether we can set a >VGA compatible mode when we need it. My program ran on an ET4000, and >it worked OK, but I suppose it's possible that more modern hardware >might not have a simple way to set it back to character mode. I'll >enquire. I'm most familiar with the ET400. It has locks to prevent inadvertent access to the special Tseng registers. Some of these locks must be opened to change the bits to enable fairly standard graphics features. E.g., there's one for interlace mode. To work on an ET400, you would have to use the keys for these locks or maybe depend on the X server leaving everything unlocked. I think there are no standards for the keys, and more modern graphics cards have more things to lock, so simply stuffing the VGA registers with standard values is unlikely to work. I've never had any success with using vidcontrol to fix up the state on Et4000/W32 or S3 cards after the X server has crashed. Bruce From owner-freebsd-current Tue Apr 23 04:30:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA25831 for current-outgoing; Tue, 23 Apr 1996 04:30:56 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA25816 Tue, 23 Apr 1996 04:30:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id EAA04676; Tue, 23 Apr 1996 04:28:43 -0700 (PDT) To: Greg Lehey cc: bde@zeta.org.au (Bruce Evans), smpatel@umiacs.UMD.EDU, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for a new "feature" as regards DDB In-reply-to: Your message of "Tue, 23 Apr 1996 12:00:43 MDT." <199604231000.MAA20823@nixpbe.pdb.sni.de> Date: Tue, 23 Apr 1996 04:28:43 -0700 Message-ID: <4674.830258923@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I disagree completely. If my machine dies in the middle of the night, > I want to come in the next morning and be able to debug the live > hardware, not a dump. YMMV, but we should have the option. However, there's a corrolary: If your machine dies in the middle of the night (or when you're in front of it, for that matter) and *you're sitting in the X server* then you should be given a dump if you're not configured for a serial console because we know that there's no way in hell you're going to be debugging any live hardware. A dump is the best you can ask for under those circumstances. Assuming that the same interface which the VT_GETACTIVE ioctl() uses is available for determining if "curvty = vty0", it seems you should be able to avoid going into DDB interaction mode if it's not possible to do anything else. You can simply call panic. Jordan From owner-freebsd-current Tue Apr 23 04:34:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA26045 for current-outgoing; Tue, 23 Apr 1996 04:34:05 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA25977 for ; Tue, 23 Apr 1996 04:33:50 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id NAA26211 for current@FreeBSD.ORG; Tue, 23 Apr 1996 13:33:35 +0200 Message-Id: <199604231133.NAA26211@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 23 Apr 96 13:33:29 MDT From: Greg Lehey Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG (FreeBSD hackers) In-Reply-To: <4674.830258923@time.cdrom.com>; from "Jordan K. Hubbard" at Apr 23, 96 4:28 am X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I disagree completely. If my machine dies in the middle of the night, >> I want to come in the next morning and be able to debug the live >> hardware, not a dump. YMMV, but we should have the option. > > However, there's a corrolary: > > If your machine dies in the middle of the night (or when you're in > front of it, for that matter) and *you're sitting in the X server* > then you should be given a dump if you're not configured for a serial > console because we know that there's no way in hell you're going to be > debugging any live hardware. We haven't done that one to death yet :-) > A dump is the best you can ask for under those circumstances. If a dump is the best you can hope for, then you shouldn't have to even ask. Even if we can only change back to character mode 98% of the time, the other 2% (at least) should give you a dump. Of course, if there's a timeout, that would handle it. > Assuming that the same interface which the VT_GETACTIVE ioctl() > uses is available for determining if "curvty = vty0", it seems you > should be able to avoid going into DDB interaction mode if it's > not possible to do anything else. You can simply call panic. Sounds reasonable. I'll take a look at it. Greg From owner-freebsd-current Tue Apr 23 05:23:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA28025 for current-outgoing; Tue, 23 Apr 1996 05:23:35 -0700 (PDT) Received: from mx10.netvision.net.il (mx10.NetVision.net.il [194.90.1.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA28011 Tue, 23 Apr 1996 05:23:25 -0700 (PDT) Received: from Burka.NetVision.net.il (gena@burka.NetVision.net.il [194.90.6.15]) by mx10.netvision.net.il (8.7.5/8.7.1) with SMTP id PAA27623; Tue, 23 Apr 1996 15:25:32 +0300 Message-ID: X-Mailer: XFMail 0.4-beta [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 In-Reply-To: <199604221622.JAA15260@freefall.freebsd.org> Date: Tue, 23 Apr 1996 15:22:24 +0200 (IST) 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: "Justin T. Gibbs" Subject: Re: Aic7xxx driver update in current Cc: current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello! On 22-Apr-96 "Justin T. Gibbs" wrote: [skip] >Have you ever used tagged queuing with this drive before? That would >have been options AHC_TAGENABLE in previous kernels. To ensure that No i never used it. I tried once (long time ago) but kernel refused to work with messages similair to those i sent you. >this is the problem, #if 0 out the block of code starting on line 1535 >and ending on line 1568 in i386/scsi/aic7xxx.c. > >If this does cure your problem, please try the original driver again and Yeah it does cure my problem and works just great even with this new paging option enabled. >send me *exactly* what the error messages on the screen are. Well, i checked again and messages i sent you are exact ones. (only sd(ahc0:0:0) prefix is missing before each line). > >-- >Justin T. Gibbs >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > FreeBSD: Turning PCs into workstations >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud Homepage: http://www.netvision.net.il/~gena This message was sent at 04/23/96 15:22:24 by XF-Mail From owner-freebsd-current Tue Apr 23 05:48:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA29349 for current-outgoing; Tue, 23 Apr 1996 05:48:55 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA29340 for ; Tue, 23 Apr 1996 05:48:53 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id HAA00629; Tue, 23 Apr 1996 07:47:33 -0500 (EST) From: "John S. Dyson" Message-Id: <199604231247.HAA00629@dyson.iquest.net> Subject: Re: gzip bug To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 23 Apr 1996 07:47:32 -0500 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org In-Reply-To: <7854.830239558@critter.tfs.com> from "Poul-Henning Kamp" at Apr 23, 96 06:05:58 am X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Time for somebody to write vm(9)? :) > > yes please! > If someone else would do the formatting, I'll be glad to put together some raw information perhaps during next weekend. Lemme know... John From owner-freebsd-current Tue Apr 23 06:32:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02634 for current-outgoing; Tue, 23 Apr 1996 06:32:22 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA02616 Tue, 23 Apr 1996 06:32:17 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id JAA00943; Tue, 23 Apr 1996 09:32:08 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id JAA20951; Tue, 23 Apr 1996 09:32:23 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 09:32:22 -0400 (EDT) From: "Marc G. Fournier" To: stable@freebsd.org cc: current@freebsd.org Subject: vm_page_alloc panic, followed by... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Morning... Well, after running nicely for over 9 days straight, my -stable machine has gone down three times in 24hrs :( this morning at approx. 2:30, she went down with in vm_page_alloc(). As per usual, no core dump is possible with this machine, it just locks up, so a DDB trace is the only thing available: vm_page_alloc+0x1b3 vm_hold_load_pages+0x40 allocbuf+0x8a getblk bread ffs_blkatoff ufs_lookup lookup namei vn_open open syscall Xsyscall --- syscall 5, eip = 0x8081465, ebp = 0xefbfd0c4 --- Current process was listed as innd...I believe someone else reported a vm_page_alloc() panic recently with innd also being current process? Then, after resetting the machine after it hung trying to dump, it got to the point of starting up the the system daemons (mountd was being started), when it panic'd again with: panic: pmap_zero_page: CMAP busy Unfortunately, unless there is paging capabilities in ddb that I couldn't find, trace traces right off the screen, so getting anything out of that is near to impossible without a larger screen :( I'm going to sup in a new kernel for this machine today, as the one I have is dated March 26th, but I haven't seen much in the way of commits for the -stable kernel that seems related... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 06:41:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03289 for current-outgoing; Tue, 23 Apr 1996 06:41:14 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA03284 for ; Tue, 23 Apr 1996 06:41:11 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id IAA17091; Tue, 23 Apr 1996 08:39:33 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma017089; Tue Apr 23 08:39:25 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id IAA28364; Tue, 23 Apr 1996 08:43:35 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id IAA18797; Tue, 23 Apr 1996 08:43:34 -0500 (CDT) Message-Id: <199604231343.IAA18797@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Paul Traina cc: current@freebsd.org Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Mon, 22 Apr 1996 15:46:40 PDT." <199604222246.PAA06258@precipice.shockwave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 08:43:33 -0500 From: "Eric L. Hernes" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Paul Traina writes: >I know I'm the "let's not bloat things out" guy, but I want to get some >feedback on this idea. It seems like a big gain. > >I'd like to bring socks4 (and later socks5) into the FreeBSD source tree >directly. The reason for doing so is that minor modifications to our >utilities, such as telnet, ftp, et al need to be performed. I figure it >would be more useful to the user community if we just make these changes >/and/ ship our default binaries with socks support included. > >Everything will behave as normal, unless the user creates /etc/socks.conf >which will then enable socks functionality. > >Comments? At least everyone here at LodgeNet would appreciate it, ever since we replaced all those linux boxes with FreeBSD ones. I've been using socks4 for all my internet accesses here. I've got sup, perl, knews, arena, w3c, ... but it'd be great to not even have to recompile ;) > >Paul > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-current Tue Apr 23 06:47:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03518 for current-outgoing; Tue, 23 Apr 1996 06:47:22 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA03513 Tue, 23 Apr 1996 06:47:20 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id JAA01208; Tue, 23 Apr 1996 09:47:15 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id JAA21002; Tue, 23 Apr 1996 09:47:29 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 09:47:28 -0400 (EDT) From: "Marc G. Fournier" To: Greg Lehey cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604231000.MAA20823@nixpbe.pdb.sni.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Greg Lehey wrote: > >>>> So...any way of having an auto-switch to vt0 if the system > >>>> crashes with DDB enabled? > > > > Use syscons. > > I don't understand. Are you saying "syscons auto-switches to vt0 if > the system crashes with DDB enabled", or are you saying "if you use > syscons, you can still change after entering DDB", or are you saying > something else? > Something I found out with this mornings system panic...even with pcvt, you can switch between vt's. I don't know why yesterday after I couldn't, but I would think that the hang yesterday was something more then just a system panic :( As far as the suggestion to use syscons is concerned...has it recently been modified to support vt100 nicely? Does cons50 have the same functionality? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 09:12:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14693 for current-outgoing; Tue, 23 Apr 1996 09:12:46 -0700 (PDT) Received: (from mpp@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14686 Tue, 23 Apr 1996 09:12:39 -0700 (PDT) From: Mike Pritchard Message-Id: <199604231612.JAA14686@freefall.freebsd.org> Subject: Re: gzip bug To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 23 Apr 1996 09:12:39 -0700 (PDT) Cc: phk@critter.tfs.com, joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org In-Reply-To: <199604231247.HAA00629@dyson.iquest.net> from "John S. Dyson" at Apr 23, 96 07:47:32 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson wrote: > > > > Time for somebody to write vm(9)? :) > > > > yes please! > > > If someone else would do the formatting, I'll be glad to put together some > raw information perhaps during next weekend. > > Lemme know... Give me the text, and I'll get it formatted for you. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-current Tue Apr 23 09:14:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14755 for current-outgoing; Tue, 23 Apr 1996 09:14:18 -0700 (PDT) Received: from gateway.tcsi.com ([137.134.47.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA14750 for ; Tue, 23 Apr 1996 09:14:15 -0700 (PDT) Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by gateway.tcsi.com (8.7.4/8.6.10) with ESMTP id JAA01210; Tue, 23 Apr 1996 09:14:05 -0700 (PDT) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.7.4/8.6.10) with ESMTP id JAA05003; Tue, 23 Apr 1996 09:14:04 -0700 (PDT) From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id JAA00763; Tue, 23 Apr 1996 09:12:09 -0700 Message-Id: <199604231612.JAA00763@cozumel.tcs.com> Subject: Re: socks support native in freebsd? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 23 Apr 1996 09:12:08 -0700 (PDT) Cc: pst@shockwave.com, current@FreeBSD.org In-Reply-To: <7650.830238479@critter.tfs.com> from "Poul-Henning Kamp" at Apr 23, 96 05:47:59 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: | | > I know I'm the "let's not bloat things out" guy, but I want to get some | > feedback on this idea. It seems like a big gain. | > | > I'd like to bring socks4 (and later socks5) into the FreeBSD source tree | > directly. The reason for doing so is that minor modifications to our | > utilities, such as telnet, ftp, et al need to be performed. I figure it | > would be more useful to the user community if we just make these changes | > /and/ ship our default binaries with socks support included. | | YES! NO NO NO NO! We cannot do this for socks5 and we don't really need to anymore (thanks John P. for helping with getting LD_PRELOAD into ld.so which was brought into -current over the weekend and I wouldn't mind seeing it in -stable as I have been running the same code in -current and 2.1R environment). First legally we cannot re-distribute socks5 in source or binary form because of NEC's policy on it. I have been working with Dave Blob, the author of socks5 and have made a port to FreeBSD (however there is one tiny little bug that I haven't updated in the my port that I submitted to FreeBSD), I have had my patches rolled into the socks5 distribution (thanks Dave). FreeBSD is also listed as supported on the Socks5 web page (http://www.socks.nec.com/socks5.html). Second, you don't need to rebuild a binary to socks'ify if it uses shared libs. Dave, designed a intercepting library that can be "preloaded" before all other shared libs and then it will do the socks magic. To set the environment you run this wrapper script with the bin you want socks'ified for example: runsocks ftp runsocks emacs (yes emacs is now socks'fied) runsocks make (in a port directory and now it fetches the dist file via socks! Also this is were the bug is since libsocks5_sh.so was built with -lcompat so sed broke) It should also work if you just set LD_PRELOAD to the special socks lib in you .login and then everything would be socks'ified. So this means we don't need to modify our base telnet, ftp etc. Also Socks5 is way better then Socks4 and is a lot easier to build, it is Socks4 compatible and fully functional for the TCP/IP proxy stuff. This is a great way to share one IP on a home net. The only thing we are missing is socks support for the installation of FreeBSD on the boot floppy. Doug A. From owner-freebsd-current Tue Apr 23 09:59:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA17879 for current-outgoing; Tue, 23 Apr 1996 09:59:24 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA17867 for ; Tue, 23 Apr 1996 09:59:17 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id JAA21586; Tue, 23 Apr 1996 09:58:05 -0700 (PDT) Message-Id: <199604231658.JAA21586@precipice.shockwave.com> X-Mailer: exmh version 1.6.6 3/24/96 To: Douglas Ambrisko cc: phk@critter.tfs.com (Poul-Henning Kamp), current@FreeBSD.org Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Tue, 23 Apr 1996 09:12:08 PDT." <199604231612.JAA00763@cozumel.tcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 09:58:05 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Yes, I know, I found the socks5 code later this evening and went through it. It's in much better shape than that socks4 crud. Socks5 can exist as a port and does not need to be intrusive to FreeBSD, so that's the way I'm going to go. From owner-freebsd-current Tue Apr 23 11:39:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA24342 for current-outgoing; Tue, 23 Apr 1996 11:39:52 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA24324 Tue, 23 Apr 1996 11:39:43 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA20883; Tue, 23 Apr 1996 20:39:40 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA13623; Tue, 23 Apr 1996 20:39:39 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA23556; Tue, 23 Apr 1996 20:20:53 +0200 (MET DST) From: J Wunsch Message-Id: <199604231820.UAA23556@uriah.heep.sax.de> Subject: Re: gzip bug To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 20:20:52 +0200 (MET DST) Cc: toor@dyson.iquest.net, mpp@freefall.freebsd.org (Mike Pritchard) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604231612.JAA14686@freefall.freebsd.org> from "Mike Pritchard" at Apr 23, 96 09:12:39 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Mike Pritchard wrote: > Give me the text, and I'll get it formatted for you. Ok, i leave it to Mike then. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Apr 23 11:54:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25659 for current-outgoing; Tue, 23 Apr 1996 11:54:37 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA25654 for ; Tue, 23 Apr 1996 11:54:33 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA20718; Tue, 23 Apr 1996 20:35:19 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA13589; Tue, 23 Apr 1996 20:35:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA23198; Tue, 23 Apr 1996 19:29:40 +0200 (MET DST) From: J Wunsch Message-Id: <199604231729.TAA23198@uriah.heep.sax.de> Subject: Re: gzip bug To: freebsd-current@freebsd.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 19:29:40 +0200 (MET DST) Cc: toor@dyson.iquest.net (John S. Dyson) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604231247.HAA00629@dyson.iquest.net> from "John S. Dyson" at Apr 23, 96 07:47:32 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As John S. Dyson wrote: > > > Time for somebody to write vm(9)? :) > > > > yes please! > > > If someone else would do the formatting, I'll be glad to put together some > raw information perhaps during next weekend. I volunteer to do the formatting. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Apr 23 12:38:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28678 for current-outgoing; Tue, 23 Apr 1996 12:38:01 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA28642 Tue, 23 Apr 1996 12:37:50 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA22528; Tue, 23 Apr 1996 21:37:26 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id VAA14151; Tue, 23 Apr 1996 21:37:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA23869; Tue, 23 Apr 1996 20:39:13 +0200 (MET DST) From: J Wunsch Message-Id: <199604231839.UAA23869@uriah.heep.sax.de> Subject: Mailer problem To: cstruble@quirk.com, kieber@sax.sax.de, freebsd-hackers@freebsd.org (FreeBSD hackers), freebsd-current@freebsd.org (FreeBSD-current users) Date: Tue, 23 Apr 1996 20:39:12 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ick. ``How can you shoot in your foot?'' -- ``Create a bogus .forward.'' I've lost a dozen mails due to this that have been sent from the adressees of this message. If it's been something important, please resend it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Apr 23 12:41:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA29041 for current-outgoing; Tue, 23 Apr 1996 12:41:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA29012 Tue, 23 Apr 1996 12:41:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA20121; Tue, 23 Apr 1996 12:36:03 -0700 From: Terry Lambert Message-Id: <199604231936.MAA20121@phaeton.artisoft.com> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Tue, 23 Apr 1996 12:36:03 -0700 (MST) Cc: lehey.pad@sni.de, smpatel@umiacs.UMD.EDU, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199604230928.TAA12645@godzilla.zeta.org.au> from "Bruce Evans" at Apr 23, 96 07:28:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >why ddb shouldn't understand enough about generic VGA to be able to > >put it back in 25x80 mode. Somewhere I have a little program which I > >used to do this under BSD/386 0.3, where the X server wasn't always > >successful. It's only a few lines. I'm sure somebody's going to come > >up with "yes, but that's not completely generic", but I don't think > >this is an adequate argument. Make it a config option for ddb, and > > "yes, but that's not completely generic" :-). I can't tell if Bruce is making fun of me or not. 8-). But that's not completely generic. > >it'll handle 98% of all hardware. If somebody with the other 2% > >wants, they can do it for that hardware as well. > > It'll only handle 98% of all hardware that is running in a VGA compatible > mode. I guess most X modes aren't VGA compatible. They aren't. Anything which programs the clocks not through a kernel model is not state-recoverable by kernel code (like DDB). The kernel debugger was almost the primary reason for suggesting a kernel DDX. Now that Plan 9 has abstracted the card specific drivers into the kernel (/dev/vga, /dev/bitblt, etc.) and the Linux community has a "GGI" project in the works, FreeBSD has less and less of an excuse. 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 Apr 23 13:02:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA00753 for current-outgoing; Tue, 23 Apr 1996 13:02:20 -0700 (PDT) Received: from ki.net (ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA00744 Tue, 23 Apr 1996 13:02:09 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA07218; Tue, 23 Apr 1996 16:01:40 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA23237; Tue, 23 Apr 1996 16:02:05 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 16:02:04 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: hackers@freebsd.org Subject: Intelligent Debugging Tools... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... What would it take to either create software for debugging hardware, and/or add appropriate debugging to the kernel that would improve debugging of hardware problems? Erk...as far as software is concerned, maybe something that you could run in single user mode that would completely thrash the RAM, doing read/writes to *all* the memory looking for any corruption? Or something else that could be turned on against /dev/rsd0b to totally thrash the swap space on a drive? As far as the kernel is concerned, I'm getting panics in VM and keep getting told its hardware problems...fine, but there *has* to be a better way of isolating the problem then replacing bits and pieces until the problem seems to go away. For instance, when I get a VM fault...what exactly *is* the problem? Is it a problem with the swap space (ie. hard drives) or RAM? My -stable machine is a 4 month old computer, and all the parts are new in her...last I've been asked is "when am I going to replace the machine"...replace it with what? its all new...if there was some way of narrowing down the offending parts and replacing those, that would be great...but just going out and buying a new machine is not the answer, cause the part that is wrong with *this* machine might exist in the next machine *shrug* Does this make any sense? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 13:06:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA01111 for current-outgoing; Tue, 23 Apr 1996 13:06:23 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA01104 for ; Tue, 23 Apr 1996 13:06:17 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uBoLm-0003wQC; Tue, 23 Apr 96 13:06 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id UAA09460; Tue, 23 Apr 1996 20:05:55 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: current@FreeBSD.org Cc: Jim Fleming Subject: SLIP: Check IP Version (please test) In-reply-to: Your message of "Sun, 07 Apr 1996 00:28:56 CST." <01BB2419.36344C40@webster.unety.net> Date: Tue, 23 Apr 1996 20:05:54 +0000 Message-ID: <9458.830289954@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Somebody running slip with header compression please test this patch. Poul-Henning > I am starting to develop a substantialliy modified version of the IP protocol . > As specified in the IP protocol the ip_v (IP Version) field of the IP header > should be set to 4. (see /usr/src/sys/netinet/ip.h) > > It is not desirable for new versions of IP to "break" existing code. I have n ot > provide this but in studying the SLIP code I see that there is never really > a check done to see of the IP header is of version 4. Index: if_sl.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_sl.c,v retrieving revision 1.37 diff -u -r1.37 if_sl.c --- if_sl.c 1996/04/07 17:39:09 1.37 +++ if_sl.c 1996/04/23 20:03:53 @@ -561,7 +561,8 @@ } while (m1 = m1->m_next); } #endif - if ((ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { + if ((ip = mtod(m, struct ip *))->ip_v == IPVERSION) && + (ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { if (sc->sc_if.if_flags & SC_COMPRESS) *mtod(m, u_char *) |= sl_compress_tcp(m, ip, &sc->sc_comp, 1); -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Apr 23 13:22:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02306 for current-outgoing; Tue, 23 Apr 1996 13:22:00 -0700 (PDT) Received: from doorstep.unety.net (root@[204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA02260 for ; Tue, 23 Apr 1996 13:21:17 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id PAA16305; Tue, 23 Apr 1996 15:14:47 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB3128.0E4B7660@webster.unety.net>; Tue, 23 Apr 1996 15:17:59 -0500 Message-ID: <01BB3128.0E4B7660@webster.unety.net> From: Jim Fleming To: "current@FreeBSD.org" , "'Poul-Henning Kamp'" Cc: Jim Fleming Subject: RE: SLIP: Check IP Version (please test) Date: Tue, 23 Apr 1996 15:17:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tuesday, April 23, 1996 3:05 PM, Poul-Henning Kamp[SMTP:phk@critter.tfs.com] wrote: @ @Somebody running slip with header compression please test this patch. @ @Poul-Henning @ @> I am starting to develop a substantialliy modified version of the IP protocol @. @> As specified in the IP protocol the ip_v (IP Version) field of the IP header @> should be set to 4. (see /usr/src/sys/netinet/ip.h) @> @> It is not desirable for new versions of IP to "break" existing code. I have n @ot @> provide this but in studying the SLIP code I see that there is never really @> a check done to see of the IP header is of version 4. @ @Index: if_sl.c @=================================================================== @RCS file: /home/ncvs/src/sys/net/if_sl.c,v @retrieving revision 1.37 @diff -u -r1.37 if_sl.c @--- if_sl.c 1996/04/07 17:39:09 1.37 @+++ if_sl.c 1996/04/23 20:03:53 @@@ -561,7 +561,8 @@ @ } while (m1 = m1->m_next); @ } @ #endif @- if ((ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { @+ if ((ip = mtod(m, struct ip *))->ip_v == IPVERSION) && @+ (ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { @ if (sc->sc_if.if_flags & SC_COMPRESS) @ *mtod(m, u_char *) |= sl_compress_tcp(m, ip, @ &sc->sc_comp, 1); @-- @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. @Future will arrive by its own means, progress not so. @ @ It looks good here....now SLIP will not compress our IPv8 IP headers...:-) -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-current Tue Apr 23 13:25:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02671 for current-outgoing; Tue, 23 Apr 1996 13:25:03 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA02651 for ; Tue, 23 Apr 1996 13:24:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA20265; Tue, 23 Apr 1996 13:18:32 -0700 From: Terry Lambert Message-Id: <199604232018.NAA20265@phaeton.artisoft.com> Subject: Re: socks support native in freebsd? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 23 Apr 1996 13:18:32 -0700 (MST) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, pst@shockwave.com, current@FreeBSD.org In-Reply-To: <199604230656.QAA09490@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 23, 96 04:26:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > By IP tunneling the default route to the socksd that then forwards > > it to the forwarding host using a static route to the real interface. > > How is this different from the already-deemed-evil Linux "IP Masquerading"? > The 'tunnel' approach either requires a socks-like protocol, which requires > application (or library) support, or it rewrites packet headers. It uses real routing. For masquerading, it would require noting the the socket level abstraction and going back down -- basically, an implementation to layer 4 on the tunnel program that then threw it back down and switch on the "response" bit and a decode of the IP packet contents for TCP packets based on target socket. I think UDP and ICMP echo datagram support could be handled, unlike in the IP masquerading case, but it would be a pretty hairy coding job. ICMP echo datagram (ping/traceroute) would be especially hairy, but might be handled by a monotonically increasing sequence and response LRU queue. Either way, unlike "Linux IP Masquerading", though ugly, it would still be in technical compliance with the RFC's. With the LRU's, it could be significantly more functional than "IP Masquerading". > > Local routes can also go to the local linterface statically, by net. > > Heh. That's the linterface that uses static to collect dropped routes? 8) 8-). "Ain't got a thing if you ain't got that cling"... Naw, just a typo. 8-). > Actually, Paul was talking about 'whatever is state-of-the-art'. Witness > the upcoming back-outs of the initial socks-4 stuff, and the implementation > of the (optional) socks-5 shared-library features. Yes. This makes simple socks implementation much, much nicer. It doesn't fix local socks-unaware Microsoft clients wanting to go through your single too-cheap-to-pay-for-multiple-addresses PPP connection to your provider, like Masquerading does, though. 8-). It does fix everything -- at least everything that's liked shared -- local to the BSD box, though. For HTTP, a cache server would fix the local clients (but then it wouldn't need socks to do it 8-)). > > Second, this is an atypical network configuration, and the average > > user should not have to pay for it in their libc. > > *snort*. There are a million warts that the 'average user' pays for already > in their libc. I would suggest that any overhead that Socks-awareness would > impose on the (small) number of relevant system calls would be noise > against interrupt latency on the average network interface. Well, you know me -- I'm a purist; *all* those warts should be burned off, if only to prevent them from being used as a justification for future warts. 8-). Not that this is really a problem for anything but statically linked code which is not already socks-aware once socks5 is there... > > > ...except that Netscape (at the least) already supports Socks, and in fact > > > goes so far as to support making TCP DNS queries so that a UDP proxy isn't > > > required. > > > > Fine. Pick a binary program other than Netscape which does not support > > socks. > > Hmm. Microsoft Explorer, perhaps. Yeah, that was my first pick too. Didn't want to admit it because it's another example of something not-so-nice that's going to be standard anyway, like it or not. I'm still worried about their non-SSL authentication using licensed RSA code. 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 Apr 23 13:25:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA02707 for current-outgoing; Tue, 23 Apr 1996 13:25:25 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA02652 Tue, 23 Apr 1996 13:24:50 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA20290; Tue, 23 Apr 1996 13:20:06 -0700 From: Terry Lambert Message-Id: <199604232020.NAA20290@phaeton.artisoft.com> Subject: Re: gzip bug To: joerg_wunsch@uriah.heep.sax.de Date: Tue, 23 Apr 1996 13:20:06 -0700 (MST) Cc: freebsd-current@FreeBSD.org, toor@dyson.iquest.net, mpp@freefall.freebsd.org In-Reply-To: <199604231820.UAA23556@uriah.heep.sax.de> from "J Wunsch" at Apr 23, 96 08:20:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > As Mike Pritchard wrote: > > > Give me the text, and I'll get it formatted for you. > > Ok, i leave it to Mike then. :) Ok, leave it to Mike or J"org then. 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 Apr 23 14:45:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09391 for current-outgoing; Tue, 23 Apr 1996 14:45:11 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09364 Tue, 23 Apr 1996 14:45:00 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id OAA23611; Tue, 23 Apr 1996 14:43:25 -0700 Message-Id: <199604232143.OAA23611@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Marc G. Fournier" cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 16:02:04 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 14:43:25 -0700 From: "Amancio Hasty Jr." Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, It will help if you post your hardware configuration. A few months ago there was a nasty PCI interaction in the kernel which caused my system to crash so glad that whatever it was is gone 8) Cheers, Amancio >>> "Marc G. Fournier" said: > > Hi... > > What would it take to either create software for debugging > hardware, and/or add appropriate debugging to the kernel that would > improve debugging of hardware problems? > > Erk...as far as software is concerned, maybe something that > you could run in single user mode that would completely thrash the > RAM, doing read/writes to *all* the memory looking for any corruption? > Or something else that could be turned on against /dev/rsd0b to totally > thrash the swap space on a drive? > > As far as the kernel is concerned, I'm getting panics in VM > and keep getting told its hardware problems...fine, but there *has* > to be a better way of isolating the problem then replacing bits and > pieces until the problem seems to go away. For instance, when I get > a VM fault...what exactly *is* the problem? Is it a problem with > the swap space (ie. hard drives) or RAM? > > My -stable machine is a 4 month old computer, and all the > parts are new in her...last I've been asked is "when am I going to > replace the machine"...replace it with what? its all new...if there > was some way of narrowing down the offending parts and replacing > those, that would be great...but just going out and buying a new machine > is not the answer, cause the part that is wrong with *this* machine > might exist in the next machine *shrug* > > Does this make any sense? > > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org > > From owner-freebsd-current Tue Apr 23 15:00:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA10463 for current-outgoing; Tue, 23 Apr 1996 15:00:23 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA10444 Tue, 23 Apr 1996 15:00:17 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA01865; Tue, 23 Apr 1996 18:00:09 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA02308; Tue, 23 Apr 1996 18:00:07 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 18:00:06 -0400 (EDT) From: "Marc G. Fournier" To: "Amancio Hasty Jr." cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604232143.OAA23611@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Amancio Hasty Jr. wrote: > Hi, > > It will help if you post your hardware configuration. A few months > ago there was a nasty PCI interaction in the kernel which caused > my system to crash so glad that whatever it was is gone 8) > dmesg: FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 scrappy@ki.net:/usr/src/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14835712 (14488K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 12 on pci0:11 (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1222MB (2503872 512 byte sectors) (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 327MB (670506 512 byte sectors) (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 234MB (479350 512 byte sectors) (ncr0:3:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 sd3(ncr0:3:0): Direct-Access sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1013MB (2074880 512 byte sectors) vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 not probed due to I/O address conflict with sio0 at 0x3f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sctarg0(noadapter::): Processor Target The NCR controller is one of the ASUS SC-200 controllers, the vga0 device is an ATI Mach64 4MB PCI, and the sio1 conflict is a misconfiguration on my part in this newest kernel that I have to fix. Oh, the motherboard is an ACER AP43 with a 486DX4-100 CPU, and sio[01] are both onboard serial. The memory is one 16Meg SIMM, and pstat shows: Device 1K-blocks Used Avail Capacity Type /dev/sd0b 51200 6880 44256 13% Interleaved /dev/sd1b 32768 6936 25768 21% Interleaved /dev/sd2b 32768 6960 25744 21% Interleaved /dev/sd3b 102400 6904 95432 7% Interleaved Total 218880 27680 191200 13% Any other information that may be pertinent? helpful? I'm running just about everything on this machine...named, innd, YP, nfs-server and PPP: PID TT STAT TIME COMMAND 0 ?? DLs 0:00.00 (swapper) 1 ?? IWs 0:00.40 /sbin/init -- 2 ?? DL 0:17.60 (pagedaemon) 3 ?? DL 0:05.23 (vmdaemon) 4 ?? DL 0:12.49 (update) 78 ?? Ss 0:00.45 routed -q 102 ?? Ss 0:03.46 syslogd 105 ?? SWs 0:07.72 named 110 ?? IWs 0:00.14 portmap 113 ?? IWs 0:05.73 ypserv 116 ?? IWs 0:00.02 yppasswdd -s -f 120 ?? Ss 0:00.74 rwhod 124 ?? IWs 0:00.09 mountd 126 ?? IWs 0:00.02 nfsd: master (nfsd) 128 ?? S 0:47.11 nfsd: server (nfsd) 129 ?? IW 0:05.28 nfsd: server (nfsd) 130 ?? IW 0:00.85 nfsd: server (nfsd) 131 ?? IW 0:00.25 nfsd: server (nfsd) 138 ?? Ss 0:00.90 inetd 145 ?? Ss 0:00.62 cron 149 ?? IWs 0:00.82 (sendmail) 184 ?? Ss 0:06.29 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 187 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 188 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 208 ?? DNs 12:39.57 /news/admin/etc/innd -p4 -i0 218 ?? IWs 0:00.01 /usr/local/lib/pg95/bin/postmaster -S (postgres) 583 ?? IWN 0:00.91 -204.17.53.78 LIST 860 ?? IWs 0:01.28 SCREEN -R (screen-3.7.1) 999 ?? IW 0:00.09 rshd 1000 ?? IW 0:01.11 /etc/rimapd 1293 ?? IW 0:00.27 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h 1495 ?? DN 0:09.59 /news/bin/overchan 1496 ?? SN 0:09.38 /usr/local/bin/perl /news/stats/bin/flowsum.channel 1551 ?? IW 0:00.18 (ftpd) 1553 ?? IW 0:00.20 (ftpd) 1686 ?? IWN 0:00.25 sh -c \n^IBATCHFILE=${HOST}.nntp\n^ILOCK=${LOCKS}/LOC 1719 ?? SN 0:06.78 innxmit -a -t300 -T1800 news.trends.ca /news/spool/ou 1792 ?? IW 0:00.10 (sendmail) 1808 ?? IW 0:00.06 (sendmail) 1824 ?? IW 0:00.22 (ftpd) 863 p0 IWs+ 0:00.58 -bin/tcsh 911 p1 IWs 0:00.65 -bin/tcsh 921 p1 IW+ 0:00.31 vi filter.c 220 v0 IWs 0:00.84 -tcsh (tcsh) 627 v0 IW+ 0:02.82 rlogin freebsd 628 v0 IW+ 0:04.03 rlogin freebsd 824 v1 IWs 0:00.62 -tcsh (tcsh) 859 v1 IW+ 0:00.06 screen -R (screen-3.7.1) 222 v2 IWs 0:00.66 -tcsh (tcsh) 1786 v2 S 0:01.69 -su (tcsh) 1826 v2 R+ 0:00.07 ps -ax 223 v3 IWs+ 0:00.04 /usr/libexec/getty Pc ttyv3 224 d0 IWs+ 0:00.23 /bin/sh /usr/local/lib/ppp/13 1647 d0 S+ 0:03.58 /usr/sbin/ppp -direct adrenlin My two most recent panics had to do with vm_page_alloc(), which I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of which I've been told no one else is experiencing (and I've gone through the GNaTs database for anything similar to no avail), which I believe. And I have no problems believing that it *may* be a hardware problem, but what would be nice is some non-"trial and error" method of narrowing down the problem. Some way of having the panic that vm_page_alloc() produces send out an error message that states *where* the panic occurred... ie. in RAM or in swap space, or as a result of either. Its difficult to go to the accounting department and ask for more RAM because "that might fix the problem" :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 16:27:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA16300 for current-outgoing; Tue, 23 Apr 1996 16:27:05 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA16274 Tue, 23 Apr 1996 16:26:50 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id QAA00460; Tue, 23 Apr 1996 16:25:20 -0700 Message-Id: <199604232325.QAA00460@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Marc G. Fournier" cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 18:00:06 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Apr 1996 16:25:19 -0700 From: "Amancio Hasty Jr." Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wow, A bunch of stuff to try out: 1. swap out the memory 2. try a different scsi controller 3. check out the scsi cables 4. if the scsi bus does not have an active terminator try to get one 5. make sure that one of the drives is sending the termination power 6. check termination on all drives 7. make sure that scsi drives are good --- this is a tough my last scsi drive loved to crashed my system very similar to your symptoms - to say the least it was a mess. Cured the problem by junking the drive. Since you mentioned swap out problems I would concentrate the drives in which you have a swap partition. 8. Compile a kernel with kgdb so that when the system crashes you can hopefelly pop into the debugger and send us a stack trace. 9. See if you can get hold of another vga card something like an ISA et4000 based. Phew, good luck, Amancio >>> "Marc G. Fournier" said: > On Tue, 23 Apr 1996, Amancio Hasty Jr. wrote: > > > Hi, > > > > It will help if you post your hardware configuration. A few months > > ago there was a nasty PCI interaction in the kernel which caused > > my system to crash so glad that whatever it was is gone 8) > > > > dmesg: > FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 > scrappy@ki.net:/usr/src/sys/compile/kinet > CPU: i486 DX4 (486-class CPU) > Origin = "GenuineIntel" Id = 0x480 Stepping=0 > Features=0x3 > real memory = 16777216 (16384K bytes) > avail memory = 14835712 (14488K bytes) > Probing for devices on PCI bus 0: > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 12 on pci0:11 > (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 1222MB (2503872 512 byte sectors) > (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 > sd1(ncr0:1:0): Direct-Access > sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 327MB (670506 512 byte sectors) > (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 > sd2(ncr0:2:0): Direct-Access > sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 234MB (479350 512 byte sectors) > (ncr0:3:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 > sd3(ncr0:3:0): Direct-Access > sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 1013MB (2074880 512 byte sectors) > vga0 rev 0 on pci0:15 > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa > ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 not probed due to I/O address conflict with sio0 at 0x3f8 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 72065B > fd0: 1.44MB 3.5in > npx0 on motherboard > npx0: INT 16 interface > sctarg0(noadapter::): Processor Target > > > The NCR controller is one of the ASUS SC-200 controllers, > the vga0 device is an ATI Mach64 4MB PCI, and the sio1 conflict is > a misconfiguration on my part in this newest kernel that I have to > fix. > > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > CPU, and sio[01] are both onboard serial. > > The memory is one 16Meg SIMM, and pstat shows: > > Device 1K-blocks Used Avail Capacity Type > /dev/sd0b 51200 6880 44256 13% Interleaved > /dev/sd1b 32768 6936 25768 21% Interleaved > /dev/sd2b 32768 6960 25744 21% Interleaved > /dev/sd3b 102400 6904 95432 7% Interleaved > Total 218880 27680 191200 13% > > Any other information that may be pertinent? helpful? > > I'm running just about everything on this machine...named, > innd, YP, nfs-server and PPP: > > PID TT STAT TIME COMMAND > 0 ?? DLs 0:00.00 (swapper) > 1 ?? IWs 0:00.40 /sbin/init -- > 2 ?? DL 0:17.60 (pagedaemon) > 3 ?? DL 0:05.23 (vmdaemon) > 4 ?? DL 0:12.49 (update) > 78 ?? Ss 0:00.45 routed -q > 102 ?? Ss 0:03.46 syslogd > 105 ?? SWs 0:07.72 named > 110 ?? IWs 0:00.14 portmap > 113 ?? IWs 0:05.73 ypserv > 116 ?? IWs 0:00.02 yppasswdd -s -f > 120 ?? Ss 0:00.74 rwhod > 124 ?? IWs 0:00.09 mountd > 126 ?? IWs 0:00.02 nfsd: master (nfsd) > 128 ?? S 0:47.11 nfsd: server (nfsd) > 129 ?? IW 0:05.28 nfsd: server (nfsd) > 130 ?? IW 0:00.85 nfsd: server (nfsd) > 131 ?? IW 0:00.25 nfsd: server (nfsd) > 138 ?? Ss 0:00.90 inetd > 145 ?? Ss 0:00.62 cron > 149 ?? IWs 0:00.82 (sendmail) > 184 ?? Ss 0:06.29 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 187 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 188 ?? IW 0:00.84 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 208 ?? DNs 12:39.57 /news/admin/etc/innd -p4 -i0 > 218 ?? IWs 0:00.01 /usr/local/lib/pg95/bin/postmaster -S (postgres) > 583 ?? IWN 0:00.91 -204.17.53.78 LIST > 860 ?? IWs 0:01.28 SCREEN -R (screen-3.7.1) > 999 ?? IW 0:00.09 rshd > 1000 ?? IW 0:01.11 /etc/rimapd > 1293 ?? IW 0:00.27 /usr/httpd/bin/httpd -f /usr/httpd/conf/httpd.conf (h > 1495 ?? DN 0:09.59 /news/bin/overchan > 1496 ?? SN 0:09.38 /usr/local/bin/perl /news/stats/bin/flowsum.channe l > 1551 ?? IW 0:00.18 (ftpd) > 1553 ?? IW 0:00.20 (ftpd) > 1686 ?? IWN 0:00.25 sh -c \n^IBATCHFILE=${HOST}.nntp\n^ILOCK=${LOCKS}/ LOC > 1719 ?? SN 0:06.78 innxmit -a -t300 -T1800 news.trends.ca /news/spool /ou > 1792 ?? IW 0:00.10 (sendmail) > 1808 ?? IW 0:00.06 (sendmail) > 1824 ?? IW 0:00.22 (ftpd) > 863 p0 IWs+ 0:00.58 -bin/tcsh > 911 p1 IWs 0:00.65 -bin/tcsh > 921 p1 IW+ 0:00.31 vi filter.c > 220 v0 IWs 0:00.84 -tcsh (tcsh) > 627 v0 IW+ 0:02.82 rlogin freebsd > 628 v0 IW+ 0:04.03 rlogin freebsd > 824 v1 IWs 0:00.62 -tcsh (tcsh) > 859 v1 IW+ 0:00.06 screen -R (screen-3.7.1) > 222 v2 IWs 0:00.66 -tcsh (tcsh) > 1786 v2 S 0:01.69 -su (tcsh) > 1826 v2 R+ 0:00.07 ps -ax > 223 v3 IWs+ 0:00.04 /usr/libexec/getty Pc ttyv3 > 224 d0 IWs+ 0:00.23 /bin/sh /usr/local/lib/ppp/13 > 1647 d0 S+ 0:03.58 /usr/sbin/ppp -direct adrenlin > > > My two most recent panics had to do with vm_page_alloc(), which > I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of > which I've been told no one else is experiencing (and I've gone through > the GNaTs database for anything similar to no avail), which I believe. > > And I have no problems believing that it *may* be a hardware > problem, but what would be nice is some non-"trial and error" method of > narrowing down the problem. Some way of having the panic that vm_page_alloc () > produces send out an error message that states *where* the panic occurred... > ie. in RAM or in swap space, or as a result of either. > > Its difficult to go to the accounting department and ask for more > RAM because "that might fix the problem" :( > > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org > > From owner-freebsd-current Tue Apr 23 16:34:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA16959 for current-outgoing; Tue, 23 Apr 1996 16:34:47 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA16947 for ; Tue, 23 Apr 1996 16:34:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id QAA06375; Tue, 23 Apr 1996 16:32:35 -0700 (PDT) To: Douglas Ambrisko cc: phk@critter.tfs.com (Poul-Henning Kamp), pst@shockwave.com, current@FreeBSD.ORG Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Tue, 23 Apr 1996 09:12:08 PDT." <199604231612.JAA00763@cozumel.tcs.com> Date: Tue, 23 Apr 1996 16:32:35 -0700 Message-ID: <6373.830302355@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The only thing we are missing is socks support for the installation of > FreeBSD on the boot floppy. Hmm, could you perhaps elaborate on this a little? Jordan From owner-freebsd-current Tue Apr 23 17:03:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA20974 for current-outgoing; Tue, 23 Apr 1996 17:03:27 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA20924 Tue, 23 Apr 1996 17:03:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id RAA06541; Tue, 23 Apr 1996 17:02:34 -0700 (PDT) To: "Marc G. Fournier" cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 16:02:04 EDT." Date: Tue, 23 Apr 1996 17:02:34 -0700 Message-ID: <6539.830304154@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What would it take to either create software for debugging > hardware, and/or add appropriate debugging to the kernel that would > improve debugging of hardware problems? A lot. The best you can hope for right now is "CheckIt" from TouchStone software, it runs under DOS and no I haven't even the faintest idea whether or not it will detect your particular problem. Probably not, but it's the best attempt at a software hardware checker that I know of. > As far as the kernel is concerned, I'm getting panics in VM > and keep getting told its hardware problems...fine, but there *has* > to be a better way of isolating the problem then replacing bits and > pieces until the problem seems to go away. For instance, when I get Not really. This is, in fact, how the "big boys" do it. If you're in doubt, swap it out. One component at a time, if necessary, until you find the bad one. I would first target my cache, memory and motherboard, in that order, for replacement if I were in your shoes (and I have been - this is how I fixed it :-). Jordan From owner-freebsd-current Tue Apr 23 17:40:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA24120 for current-outgoing; Tue, 23 Apr 1996 17:40:33 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA24112 Tue, 23 Apr 1996 17:40:30 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id TAA03135; Tue, 23 Apr 1996 19:39:35 -0500 (EST) From: "John S. Dyson" Message-Id: <199604240039.TAA03135@dyson.iquest.net> Subject: Re: gzip bug To: terry@lambert.org (Terry Lambert) Date: Tue, 23 Apr 1996 19:39:35 -0500 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org, mpp@freefall.freebsd.org In-Reply-To: <199604232020.NAA20290@phaeton.artisoft.com> from "Terry Lambert" at Apr 23, 96 01:20:06 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > As Mike Pritchard wrote: > > > > > Give me the text, and I'll get it formatted for you. > > > > Ok, i leave it to Mike then. :) > > Ok, leave it to Mike or J"org then. 8-). > I really don't mean to act lazy, but there is a severe bug in kmem_malloc that BDE has narrowed down, and I am chasing that when I am conscious (I am ill.) Since he has gone to alot of trouble to narrow it down a bit, and it is a severe bug in the system, I HAVE to work that right now. Dealing with mdoc, man or sgml isn't what I want to do right now, it might put me to sleep. :-). So, I'll be sending some stuff to Mike near the end of the weekend. It'll take a few days to figure out what needs to be documented, and then I'll need to fill out some details. John From owner-freebsd-current Tue Apr 23 18:26:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA27680 for current-outgoing; Tue, 23 Apr 1996 18:26:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA27593 Tue, 23 Apr 1996 18:25:31 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA13482; Wed, 24 Apr 1996 10:51:15 +0930 From: Michael Smith Message-Id: <199604240121.KAA13482@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 10:51:15 +0930 (CST) Cc: current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 04:02:04 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > What would it take to either create software for debugging > hardware, and/or add appropriate debugging to the kernel that would > improve debugging of hardware problems? Ah. As someone with a foot in both the hardware and software camps, all I can say is "forget it". Any software has to make a few assumptions about the hardware it runs on. If the hardware fails to meet those assumptions, (eg. random parts of memory change) there's no hope for the software. To answer your question absolutely, this sort of software does exist. You find it in board-level test equipment with price tags starting in the mid six figures. Configuring such software usually requires access to the manufacturer's specification for the DUT. (If such information actually exists in the first place - often it's easier for a board vendor to just throw a prototype together, and if it runs Windows, commit to manufacturing it.) > Erk...as far as software is concerned, maybe something that > you could run in single user mode that would completely thrash the > RAM, doing read/writes to *all* the memory looking for any corruption? "make world". The issue here is that it's not _just_ memory, but the interaction between processor memory accesses, busmastering activity, refresh, chipset timing and random system noise. Simulating such an environment is _impossible_. If the memory was legitimately altered in an incorrect fasion (eg. a bus latch was late and caught data from the master as it transited out of a valid state, and subsequently wrote it into memory), even ECC memory won't help you. > As far as the kernel is concerned, I'm getting panics in VM > and keep getting told its hardware problems...fine, but there *has* > to be a better way of isolating the problem then replacing bits and > pieces until the problem seems to go away. For instance, when I get > a VM fault...what exactly *is* the problem? Is it a problem with > the swap space (ie. hard drives) or RAM? Find a spare $10K or so and buy a _good_ DRAM tester. Discover, much to your surprise, that most of the DRAMs on the market fail to operate to spec. Become Enlightened. Purchase a pile of Triton-II motherboards, fork out _lots_ of money for fast ECC memory, and _maybe_ your problems will go away. What is worth bearing in mind is that other people are doing essentially the same things that you are doing, but aren't having the problems you are. They don't have access to any magical software fixes, it's just that their (our) hardware appears to work OK. > Does this make any sense? Yes. The problem is that PCs are built like toasters, and making a souffle' in a toaster is very difficult. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 18:35:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA28538 for current-outgoing; Tue, 23 Apr 1996 18:35:02 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA28501 Tue, 23 Apr 1996 18:34:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id SAA02806; Tue, 23 Apr 1996 18:34:47 -0700 (PDT) Message-Id: <199604240134.SAA02806@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Amancio Hasty Jr." cc: "Marc G. Fournier" , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Tue, 23 Apr 1996 16:25:19 PDT." <199604232325.QAA00460@rah.star-gate.com> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 23 Apr 1996 18:34:47 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >5. make sure that one of the drives is sending the termination power For external termination, this is normally done by the controller, not any of the drives. Most people terminate the last drive with the drive's termination and configure that drive to supply it's on termination power (which is usually the factory default). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Apr 23 18:43:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29253 for current-outgoing; Tue, 23 Apr 1996 18:43:32 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA29247 for ; Tue, 23 Apr 1996 18:43:29 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id SAA28661; Tue, 23 Apr 1996 18:40:45 -0700 (PDT) Message-Id: <199604240140.SAA28661@precipice.shockwave.com> To: "Jordan K. Hubbard" cc: Douglas Ambrisko , phk@critter.tfs.com (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Tue, 23 Apr 1996 16:32:35 PDT." <6373.830302355@time.cdrom.com> Date: Tue, 23 Apr 1996 18:40:45 -0700 From: Paul Traina Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I think Doug wants a socksified sysinstall ... yuck/ouch (in that order). :-) From: "Jordan K. Hubbard" Subject: Re: socks support native in freebsd? > The only thing we are missing is socks support for the installation of > FreeBSD on the boot floppy. Hmm, could you perhaps elaborate on this a little? Jordan From owner-freebsd-current Tue Apr 23 18:47:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29724 for current-outgoing; Tue, 23 Apr 1996 18:47:59 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA29717 for ; Tue, 23 Apr 1996 18:47:55 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id SAA28795; Tue, 23 Apr 1996 18:47:05 -0700 (PDT) Message-Id: <199604240147.SAA28795@precipice.shockwave.com> To: Poul-Henning Kamp cc: current@FreeBSD.org, Jim Fleming Subject: Re: SLIP: Check IP Version (please test) In-reply-to: Your message of "Tue, 23 Apr 1996 20:05:54 -0000." <9458.830289954@critter.tfs.com> Date: Tue, 23 Apr 1996 18:47:05 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This patch seems to be irrelevant in any case. Only IPv4 packets should be passed to the SLIP driver. SLIP is not a multiprotocol point-to-point protocol, PPP is. IPvX x!=4 is a different protocol. SLIP is not supported in IPv6. Please don't slow down the code path by adding this change. Paul From: Poul-Henning Kamp Subject: SLIP: Check IP Version (please test) Somebody running slip with header compression please test this patch. Poul-Henning > I am starting to develop a substantialliy modified version of the IP protoc >>ol . > As specified in the IP protocol the ip_v (IP Version) field of the IP heade >>r > should be set to 4. (see /usr/src/sys/netinet/ip.h) > > It is not desirable for new versions of IP to "break" existing code. I have >> n ot > provide this but in studying the SLIP code I see that there is never really > a check done to see of the IP header is of version 4. Index: if_sl.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_sl.c,v retrieving revision 1.37 diff -u -r1.37 if_sl.c --- if_sl.c 1996/04/07 17:39:09 1.37 +++ if_sl.c 1996/04/23 20:03:53 @@ -561,7 +561,8 @@ } while (m1 = m1->m_next); } #endif - if ((ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { + if ((ip = mtod(m, struct ip *))->ip_v == IPVERSION) && + (ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { if (sc->sc_if.if_flags & SC_COMPRESS) *mtod(m, u_char *) |= sl_compress_tcp(m, ip, &sc->sc_comp, 1); -- 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, In >>c. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Apr 23 18:48:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA29889 for current-outgoing; Tue, 23 Apr 1996 18:48:50 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA29880 Tue, 23 Apr 1996 18:48:47 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id VAA00596; Tue, 23 Apr 1996 21:48:39 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id VAA03837; Tue, 23 Apr 1996 21:48:44 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 21:48:43 -0400 (EDT) From: "Marc G. Fournier" To: "Amancio Hasty Jr." cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604232325.QAA00460@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Amancio Hasty Jr. wrote: <1 thru 7 removed as I'm working on those ones> > > 8. Compile a kernel with kgdb so that when the system crashes you > can hopefelly pop into the debugger and send us a stack trace. > I have the kernel compiled with DDB & DODUMP enabled, so that I get dropped to ddb and can do a trace...I send them out and get told its a hardware problem and then they seem to drop off the face of the earth :( Is it also a hardware problem that prevents me from getting a coredump after issuing 2xpanic at the ddb> prompt to cause it to reboot? My -current machine reboots and drops core so that I can run kgdb against it, but my -stable machine won't :( > 9. See if you can get hold of another vga card something like an ISA > et4000 based. > Will add that to my "hardware wish list" for a new machine...if I can get *one* machine stable, then this won't be soooo frustrating. Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 18:56:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA00839 for current-outgoing; Tue, 23 Apr 1996 18:56:06 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA00715 Tue, 23 Apr 1996 18:55:55 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA13635; Wed, 24 Apr 1996 11:21:38 +0930 From: Michael Smith Message-Id: <199604240151.LAA13635@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 11:21:37 +0930 (CST) Cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 06:00:06 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 > scrappy@ki.net:/usr/src/sys/compile/kinet > CPU: i486 DX4 (486-class CPU) > Origin = "GenuineIntel" Id = 0x480 Stepping=0 > Features=0x3 > real memory = 16777216 (16384K bytes) > avail memory = 14835712 (14488K bytes) > Probing for devices on PCI bus 0: > chip0 rev 49 on pci0:5 Ok. This guy is known to work pretty well, as long as you avoid ISA busmasters. > sctarg0(noadapter::): Processor Target Wozzis? You have a scanner or something? > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > CPU, and sio[01] are both onboard serial. Jumpered for write-back or write-through? Which cache Tagram are you using? Is the board jumpered correctly for it? > The memory is one 16Meg SIMM, and pstat shows: Speed? Manufacturer? > My two most recent panics had to do with vm_page_alloc(), which > I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of > which I've been told no one else is experiencing (and I've gone through > the GNaTs database for anything similar to no avail), which I believe. The problem, such as it is, is that these pieces of code depend intimately on some _very_ heavily accessed parts of memory, and if there's anything wrong with these parts of memory, they cause a panic. > And I have no problems believing that it *may* be a hardware > problem, but what would be nice is some non-"trial and error" method of > narrowing down the problem. Some way of having the panic that vm_page_alloc() > produces send out an error message that states *where* the panic occurred... > ie. in RAM or in swap space, or as a result of either. Check the source of the panic in the code, and there you have it. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 19:28:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA04290 for current-outgoing; Tue, 23 Apr 1996 19:28:40 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA04279 Tue, 23 Apr 1996 19:28:33 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id WAA01007; Tue, 23 Apr 1996 22:28:31 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id WAA04472; Tue, 23 Apr 1996 22:28:38 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 22:28:37 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240151.LAA13635@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Michael Smith wrote: > Ok. This guy is known to work pretty well, as long as you avoid ISA > busmasters. > Nope, only cards are the NCR SCSI, ATI video and SMC8013 Ethernet > > sctarg0(noadapter::): Processor Target > > Wozzis? You have a scanner or something? > *shrug* nothing else other then those three cards in the machine... > > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > > CPU, and sio[01] are both onboard serial. > > Jumpered for write-back or write-through? Which cache Tagram are you > using? Is the board jumpered correctly for it? > will check the wb/wt...what do you mean by cache Tagram? > > The memory is one 16Meg SIMM, and pstat shows: > > Speed? Manufacturer? > Unknown...will have to shut down to check, but will do so after I send this out... > > My two most recent panics had to do with vm_page_alloc(), which > > I *think* have to do with swap -or- RAM, and pmap_zero_page(), both of > > which I've been told no one else is experiencing (and I've gone through > > the GNaTs database for anything similar to no avail), which I believe. > > The problem, such as it is, is that these pieces of code depend intimately > on some _very_ heavily accessed parts of memory, and if there's anything > wrong with these parts of memory, they cause a panic. > Okay, that part I don't have a problem with, but, if it detects that something is wrong, why doesn't it try (or does it?) to work around the problem? Map out the offending area of memory? As well, does this restrict the problem to cache/RAM vs swap space? I'm don't yet understand how swap space works (I know what it does, just not how), but I presume that the swap space is a psuedo-file system? Since I'm on SCSI, I would assume that it would auto-remap defective areas in the swap space, if my first assumption is correct? I can understand having bad luck with one machine, but I have three machines here, all with different hardware and they all have "hardware related" panics, two are -stable, one is -current (so I kind of expect problems with the third) After getting rid of that bad drive that cause the SCSI locks (which, mind you, is running great in another machine, solo on the SCSI bus...go figure), I've been able to get 7+days uptime on my machines. -current machine == 8+ days (rebooted to install new kernel) -stable machine 1 == 9+ days (panic'd...vm related) -stable machine 2 == 5+ days and still running) So I'm getting *somewhere*...just very slowly :( Will check the RAM/cache and get back to you... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 19:42:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA05558 for current-outgoing; Tue, 23 Apr 1996 19:42:57 -0700 (PDT) Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA05489 for ; Tue, 23 Apr 1996 19:41:47 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.7.5/8.6.5) id IAA17516 for current@freebsd.org; Wed, 24 Apr 1996 08:41:18 +0600 (GMT+0600) From: "Serge A. Babkin" Message-Id: <199604240241.IAA17516@hq.icb.chel.su> Subject: Bug in sendmail Makefile To: current@freebsd.org Date: Wed, 24 Apr 1996 08:41:17 +0600 (ESD) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I have found a bug in the sendmail Makefile (from 2 days old -current): is contains the name "shmrsh" in its subdirectories list although the actual name of the subdirectory is "smrsh". I think it is simpler to fix by hands than by a patch, so there is no patch :-) -SB From owner-freebsd-current Tue Apr 23 20:20:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08904 for current-outgoing; Tue, 23 Apr 1996 20:20:48 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA08876 Tue, 23 Apr 1996 20:20:34 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA14238; Wed, 24 Apr 1996 12:29:49 +0930 From: Michael Smith Message-Id: <199604240259.MAA14238@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 12:29:49 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 10:28:37 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > sctarg0(noadapter::): Processor Target > > > > Wozzis? You have a scanner or something? > > > *shrug* nothing else other then those three cards in the > machine... Hmm. Have you got a 'pt0' in your kernel config? > > Jumpered for write-back or write-through? Which cache Tagram are you > > using? Is the board jumpered correctly for it? > > > will check the wb/wt...what do you mean by cache Tagram? Cache SRAM comes in two parts, the cache itself and the tag ram that keeps track of what's in the cache. The SiS boards we use (Soyo) have jumpers for dealing with two different tag parts. I don't have, and have never used any Acer boards, so I don't know about them. > > The problem, such as it is, is that these pieces of code depend intimately > > on some _very_ heavily accessed parts of memory, and if there's anything > > wrong with these parts of memory, they cause a panic. > > Okay, that part I don't have a problem with, but, if it > detects that something is wrong, why doesn't it try (or does it?) to > work around the problem? Map out the offending area of memory? As How? Has the code followed a bad pointer to the area it's working on? Is the location it just read from bad, or is it comparing it with a bad value it picked up a while ago? Is it the RAM that's bad, or the cache? You can't just "map out" the bits of memory that the code is working with - all the critical data structures that the system depends on are in there - to "map them out" would mean total chaos. Simple by far is to say "this value is impossible" and tell the owner of the losing hardware that it lost. > well, does this restrict the problem to cache/RAM vs swap space? > I'm don't yet understand how swap space works (I know what it does, > just not how), but I presume that the swap space is a psuedo-file > system? Since I'm on SCSI, I would assume that it would auto-remap > defective areas in the swap space, if my first assumption is > correct? You should spend some time at night with the new daemon book, which should be out shortly - "The design and implementation of the 4.4 BSD Unix operating system" and perhaps also "The Magic Garden explained". Once you've digested those two, you'll have an appreciation (if not an understanding) of the issues involved. If they give you a headache, try "Operating systems, design and implementation" by Tanenbaum (the Minix book) first, and then come back. > I can understand having bad luck with one machine, but I have > three machines here, all with different hardware and they all have > "hardware related" panics, two are -stable, one is -current (so I kind > of expect problems with the third) We have anything from a few to about a dozen machines around here at any one time, a mix of 2.1R, -stable and -current. A few have known hardware bogons (old systems), but aside from that (and the machines running some of my less-than-wonderful device drivers), we don't see many problems. (Usually someone else runs across the really nasty ones and I hold off updating the kernel until its fixed.) Having said that, there _was_ a recent commit to the pmap code that could well have some bearing on your problem. Check it out 8) > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 20:30:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA09753 for current-outgoing; Tue, 23 Apr 1996 20:30:35 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA09748 for ; Tue, 23 Apr 1996 20:30:30 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id XAA00596; Tue, 23 Apr 1996 23:30:04 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id XAA05280; Tue, 23 Apr 1996 23:30:12 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 23:30:11 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: Cat Okita , Geoff Davidson Subject: MotherBoard Jumper Settings... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Just need to check some stuff, after Michael's probing questions :( I shutdown the machine and checked through all my jumper settings, to make sure that what was set matched what the manual said should match the CPU... Well... First off, my CPU is an Intel DX4-100 w Write/Thru. CMOS was set for Write/Back...have changed it to Write/Thru... Second of all, one of the jumper that was supposed to be set, wasn't...have set it... Third, the Oscillator Frequency was set for 33Mhz instead of 25Mhz...have fixed it... So, I've fixed those...could *any* of those above have produced the problems I've been seeing? Or are they minor? As far as the cache is concerned, I have: 4x UM61512AK-15/95282/N52049's 1x W24129AK-15/95200 (Tag SRAM) Am I correct in assuming that the -15 is the speed of the cache? If so, and I haven't changed that one yet, my CMOS is set for 20ns... would that produce any of the bugs I've been reporting? The jumpers for the cache are set for 256KB/64kbx4...how do I determine the size of each of the cache chips to determine if *this* is right? What is "the ECP DMA Channel"? Its currently set for DMA 3... is that correct? Oh ya...Flash ROM Type? Its set for "5V EEPROM/Flash ROM"... since I can't seem to find either, nor know what I'm looking for, even the "Board Layout" diagram in the manual doesn't seem to point this out... can someone give me an idea of what I'm looking for here? Once I send this out, I'm going to try and beat the hell out of this machine to see if any of this mis-settings happen to be what has been screwing me up for this long... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 20:38:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA10426 for current-outgoing; Tue, 23 Apr 1996 20:38:42 -0700 (PDT) Received: from ki.net (ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA10408 Tue, 23 Apr 1996 20:38:30 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id XAA00682; Tue, 23 Apr 1996 23:37:55 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id XAA05458; Tue, 23 Apr 1996 23:38:05 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 23:38:05 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240259.MAA14238@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > sctarg0(noadapter::): Processor Target > > > > > > Wozzis? You have a scanner or something? > > > > > *shrug* nothing else other then those three cards in the > > machine... > > Hmm. Have you got a 'pt0' in your kernel config? > Yes > Simple by far is to say "this value is impossible" and tell the owner > of the losing hardware that it lost. > Okay, Understood... > You should spend some time at night with the new daemon book, which > should be out shortly - "The design and implementation of the 4.4 BSD > Unix operating system" and perhaps also "The Magic Garden explained". > I will *definitely* look for these books... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 20:43:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA10979 for current-outgoing; Tue, 23 Apr 1996 20:43:49 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA10943 Tue, 23 Apr 1996 20:43:33 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA14757; Wed, 24 Apr 1996 13:09:40 +0930 From: Michael Smith Message-Id: <199604240339.NAA14757@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 24 Apr 1996 13:09:39 +0930 (CST) Cc: scrappy@ki.net, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <6539.830304154@time.cdrom.com> from "Jordan K. Hubbard" at Apr 23, 96 05:02:34 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > The best you can hope for right now is "CheckIt" from TouchStone > software, it runs under DOS and no I haven't even the faintest idea > whether or not it will detect your particular problem. Probably not, > but it's the best attempt at a software hardware checker that I know > of. Don't waste any money on it. If you get it as a freebie, that's fine, but they're honest enough in the manual to point out that their tests aren't anything compared to the load a mutltitasking VM OS imposes. (We got it Real Cheap when we were having RAM trouble; it didn't find the problem, and this was a RAM error so bad that _Windows_ would barf.) > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 20:47:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA11389 for current-outgoing; Tue, 23 Apr 1996 20:47:15 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA11379 Tue, 23 Apr 1996 20:47:07 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id XAA01669; Tue, 23 Apr 1996 23:46:57 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id XAA05619; Tue, 23 Apr 1996 23:47:01 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 23:46:57 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: "Jordan K. Hubbard" , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240339.NAA14757@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Michael Smith wrote: > Don't waste any money on it. If you get it as a freebie, that's fine, > but they're honest enough in the manual to point out that their tests > aren't anything compared to the load a mutltitasking VM OS imposes. > > (We got it Real Cheap when we were having RAM trouble; it didn't find the > problem, and this was a RAM error so bad that _Windows_ would barf.) > I've got 9 make processes running in /usr/src/lib right now, and will cycle those through for the next little while...that should give it a good test, shouldn't it? That with the rest of its normal load? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Apr 23 20:47:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA11429 for current-outgoing; Tue, 23 Apr 1996 20:47:22 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA11383 Tue, 23 Apr 1996 20:47:12 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA14787; Wed, 24 Apr 1996 13:11:41 +0930 From: Michael Smith Message-Id: <199604240341.NAA14787@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 13:11:40 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 11:38:05 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > You should spend some time at night with the new daemon book, which > > should be out shortly - "The design and implementation of the 4.4 BSD > > Unix operating system" and perhaps also "The Magic Garden explained". > > > I will *definitely* look for these books... Check the handbook, as I think they're on the reading list. If not, check the -hackers archive for Terry Lambert talking about the 'magic garden' book - his reading list was pretty comprehensive. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 20:59:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA12510 for current-outgoing; Tue, 23 Apr 1996 20:59:06 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA12502 Tue, 23 Apr 1996 20:59:01 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) with ESMTP id UAA20804; Tue, 23 Apr 1996 20:57:23 -0700 (PDT) Message-Id: <199604240357.UAA20804@austin.polstra.com> To: lehey.pad@sni.de Cc: terry@lambert.org, mmead@Glock.COM, smpatel@FreeBSD.org, current@FreeBSD.org, ec0@s1.GANet.NET Subject: Re: possible 4th option? [Re: kern/1102] In-reply-to: <199604230723.JAA09548@nixpbe.pdb.sni.de> Date: Tue, 23 Apr 1996 20:57:23 -0700 From: John Polstra Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Greg wrote: > > The ELF specification defines a mechanism for adding extra identifying > > information to an executable file: the PT_NOTE program header, and > > associated SHT_NOTE section... > > Sounds reasonable, even if it's a bit tedious. It's not too bad, really. I've got it working in the compiler+linker now, and I've looked at the kernel code in imgact_elf.c. That code already has to scan and interpret the program headers, so there's not a lot of extra work to be done. > > I'm going to try to add this kind of identification to our FreeBSD ELF > > executables, and fix the kernel to recognize them. (Unfortunately, as > > usual, the binutils code maze is doing its best to make this difficult > > for me.) I'd like to coordinate this with the Linux people, if they're > > interested. > > Good idea. While you're at it, why not give Sun and SCO a chance to > cooperate? I would welcome that, but somebody else is going to have to approach them. Sorry, I'm just not an ambassador by nature. And I only commit unnatural acts in my paying job :-). -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Apr 23 21:05:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA13063 for current-outgoing; Tue, 23 Apr 1996 21:05:59 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA13010 Tue, 23 Apr 1996 21:05:50 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA15067; Wed, 24 Apr 1996 13:28:13 +0930 From: Michael Smith Message-Id: <199604240358.NAA15067@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 13:28:12 +0930 (CST) Cc: hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 09:48:43 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > Is it also a hardware problem that prevents me from getting > a coredump after issuing 2xpanic at the ddb> prompt to cause it to > reboot? My -current machine reboots and drops core so that I can > run kgdb against it, but my -stable machine won't :( This machines has an NCR controller in it IIRC. You should talk to Stefan about this - dumping requires the controller to run in polled mode, and it's possible that's not happening. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 21:10:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA13637 for current-outgoing; Tue, 23 Apr 1996 21:10:40 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA13629 for ; Tue, 23 Apr 1996 21:10:36 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) with ESMTP id VAA20870; Tue, 23 Apr 1996 21:10:28 -0700 (PDT) Message-Id: <199604240410.VAA20870@austin.polstra.com> To: ambrisko@tcsi.com Subject: Re: socks support native in freebsd? In-Reply-To: <199604231612.JAA00763@cozumel.tcs.com> Organization: Polstra & Co., Seattle, WA Cc: freebsd-current@freebsd.org Date: Tue, 23 Apr 1996 21:10:28 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199604231612.JAA00763@cozumel.tcs.com> Doug writes: > (thanks John P. for helping with getting LD_PRELOAD into ld.so which > was brought into -current over the weekend and I wouldn't mind seeing > it in -stable as I have been running the same code in -current and > 2.1R environment). I'll merge it into -stable. But I want to wait a week, at least. It's only just gone into -current. Let's live with it there for a bit, just to make sure there aren't any problems. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Apr 23 21:50:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA15602 for current-outgoing; Tue, 23 Apr 1996 21:50:55 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA15597 for ; Tue, 23 Apr 1996 21:50:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id VAA03207; Tue, 23 Apr 1996 21:50:47 -0700 (PDT) Message-Id: <199604240450.VAA03207@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Marc G. Fournier" cc: current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Tue, 23 Apr 1996 23:30:11 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 23 Apr 1996 21:50:47 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Third, the Oscillator Frequency was set for 33Mhz instead >of 25Mhz...have fixed it... Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't *possibly* have any bad effects. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Apr 23 22:10:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA17789 for current-outgoing; Tue, 23 Apr 1996 22:10:56 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA17780 Tue, 23 Apr 1996 22:10:53 -0700 (PDT) Message-Id: <199604240510.WAA17780@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: davidg@Root.COM cc: "Marc G. Fournier" , current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Tue, 23 Apr 1996 21:50:47 PDT." <199604240450.VAA03207@Root.COM> Date: Tue, 23 Apr 1996 22:10:52 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> Third, the Oscillator Frequency was set for 33Mhz instead >>of 25Mhz...have fixed it... > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't >*possibly* have any bad effects. :-) > >-DG > >David Greenman >Core-team/Principal Architect, The FreeBSD Project DX4s are clock trippled chips. The clock setting was correct the first time. A DX4100 runs at 99.999MHz. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Apr 23 22:13:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA18083 for current-outgoing; Tue, 23 Apr 1996 22:13:46 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA18074 Tue, 23 Apr 1996 22:13:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id WAA03265; Tue, 23 Apr 1996 22:13:47 -0700 (PDT) Message-Id: <199604240513.WAA03265@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: "Marc G. Fournier" , current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Tue, 23 Apr 1996 22:10:52 PDT." <199604240510.WAA17780@freefall.freebsd.org> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 23 Apr 1996 22:13:47 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>> Third, the Oscillator Frequency was set for 33Mhz instead >>>of 25Mhz...have fixed it... >> >> Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't >>*possibly* have any bad effects. :-) >> >>-DG >> >>David Greenman >>Core-team/Principal Architect, The FreeBSD Project > >DX4s are clock trippled chips. The clock setting was correct the >first time. A DX4100 runs at 99.999MHz. Oh, yes, of course - 3 * 33.3 = 100. Okay, so it's been a long day. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Apr 23 23:02:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA20882 for current-outgoing; Tue, 23 Apr 1996 23:02:10 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA20874 Tue, 23 Apr 1996 23:02:04 -0700 (PDT) Received: from pgeoffred (professor.net5a.io.org [199.166.190.38]) by ki.net (8.7.4/8.7.4) with SMTP id CAA02276; Wed, 24 Apr 1996 02:01:53 -0400 (EDT) Message-ID: <317DC476.5C2E@sales.org> Date: Wed, 24 Apr 1996 02:04:38 -0400 From: Geoff Davidson Organization: sales.org Sales, Marketing & Training Effectiveness X-Mailer: Mozilla 2.01 (Win95; I) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: davidg@Root.COM, "Marc G. Fournier" , current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... References: <199604240510.WAA17780@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs wrote: > > >> Third, the Oscillator Frequency was set for 33Mhz instead > >>of 25Mhz...have fixed it... > > > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > >*possibly* have any bad effects. :-) > > > >-DG > > > >David Greenman > >Core-team/Principal Architect, The FreeBSD Project > > DX4s are clock trippled chips. The clock setting was correct the > first time. A DX4100 runs at 99.999MHz. > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== Justin, well caught, you are quite correct on this one. That's what I like about standards, DX4 just intuitively feels like it should stand for triple. I wonder if that means that 8X CD-ROMS are really quad speeds? Geoff -- How do you score as a smart consumer or salesperson? Try one of the Quizes located at: "http://www.sales.org" Email: or Geoff Davidson Personal HomePage: "http://ki.net/~geoff" From owner-freebsd-current Tue Apr 23 23:21:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA21911 for current-outgoing; Tue, 23 Apr 1996 23:21:57 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA21906 for ; Tue, 23 Apr 1996 23:21:55 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA16813; Wed, 24 Apr 1996 15:48:22 +0930 From: Michael Smith Message-Id: <199604240618.PAA16813@genesis.atrad.adelaide.edu.au> Subject: Re: MotherBoard Jumper Settings... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 15:48:22 +0930 (CST) Cc: current@FreeBSD.org, cat@ki.net, geoff@ki.net In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 11:30:11 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > First off, my CPU is an Intel DX4-100 w Write/Thru. CMOS > was set for Write/Back...have changed it to Write/Thru... Ouch. Make sure there were no jumpers relevant to that as well. > Second of all, one of the jumper that was supposed to be > set, wasn't...have set it... Also bad. > Third, the Oscillator Frequency was set for 33Mhz instead > of 25Mhz...have fixed it... Wrong. "DX4" is marketting crap. They're really DX3's, so 33 is correct. > As far as the cache is concerned, I have: > > 4x UM61512AK-15/95282/N52049's UMC. Normal stuff. > 1x W24129AK-15/95200 (Tag SRAM) Winbond. Also normal stuff. If there aren't any jumpers on the board related to the cache tag type then I would assume that that's OK. > Am I correct in assuming that the -15 is the speed of the cache? The cycle time of the SRAM parts, yes. > If so, and I haven't changed that one yet, my CMOS is set for 20ns... > would that produce any of the bugs I've been reporting? No. If the BIOS supports 15ns cycle cache memory then you may be able to improve your performance by frobbing that. > The jumpers for the cache are set for 256KB/64kbx4...how do I > determine the size of each of the cache chips to determine if *this* is > right? Convention in naming memory parts is to put the size in Kbits in the part number; 61512 implies 512kbits or 64kx8 or 128kx4. (I would expect the latter). The setting you have now implies 8 cache parts, not 4. If there's a 256kB/128kbx4 setting, try that. > What is "the ECP DMA Channel"? Its currently set for DMA 3... > is that correct? ECP == Enhanced Capabilities Parallel port. If your're not talking to it, ignore it. > Oh ya...Flash ROM Type? Its set for "5V EEPROM/Flash ROM"... > since I can't seem to find either, nor know what I'm looking for, even > the "Board Layout" diagram in the manual doesn't seem to point this out... > can someone give me an idea of what I'm looking for here? Harmless. Only relevant for saving PnP info at boot time. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 23:24:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA21997 for current-outgoing; Tue, 23 Apr 1996 23:24:17 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA21975 Tue, 23 Apr 1996 23:24:12 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA16847; Wed, 24 Apr 1996 15:49:04 +0930 From: Michael Smith Message-Id: <199604240619.PAA16847@genesis.atrad.adelaide.edu.au> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 15:49:03 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 11:38:05 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > > Hmm. Have you got a 'pt0' in your kernel config? > > > Yes Get rid of it, unless you have a 'processor'-type SCSI device. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Apr 23 23:35:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA22354 for current-outgoing; Tue, 23 Apr 1996 23:35:43 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA22349 for ; Tue, 23 Apr 1996 23:35:41 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uByAm-0003wXC; Tue, 23 Apr 96 23:35 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id GAA10417; Wed, 24 Apr 1996 06:35:30 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Paul Traina cc: current@FreeBSD.org, Jim Fleming Subject: Re: SLIP: Check IP Version (please test) In-reply-to: Your message of "Tue, 23 Apr 1996 18:47:05 MST." <199604240147.SAA28795@precipice.shockwave.com> Date: Wed, 24 Apr 1996 06:35:29 +0000 Message-ID: <10415.830327729@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > This patch seems to be irrelevant in any case. Only IPv4 packets should > be passed to the SLIP driver. SLIP is not a multiprotocol point-to-point > protocol, PPP is. > > IPvX x!=4 is a different protocol. SLIP is not supported in IPv6. Please > don't slow down the code path by adding this change. I agree, the point is that people play with IPv8 and it breaks slip. If SLIP is only for IPv4, it should discard other packets... And hey, how much overhead is this ??? Poul-Henning > > Paul > > From: Poul-Henning Kamp > Subject: SLIP: Check IP Version (please test) > > Somebody running slip with header compression please test this patch. > > Poul-Henning > > > I am starting to develop a substantialliy modified version of the IP prot oc > >>ol > . > > As specified in the IP protocol the ip_v (IP Version) field of the IP hea de > >>r > > should be set to 4. (see /usr/src/sys/netinet/ip.h) > > > > It is not desirable for new versions of IP to "break" existing code. I ha ve > >> n > ot > > provide this but in studying the SLIP code I see that there is never real ly > > a check done to see of the IP header is of version 4. > > Index: if_sl.c > =================================================================== > RCS file: /home/ncvs/src/sys/net/if_sl.c,v > retrieving revision 1.37 > diff -u -r1.37 if_sl.c > --- if_sl.c 1996/04/07 17:39:09 1.37 > +++ if_sl.c 1996/04/23 20:03:53 > @@ -561,7 +561,8 @@ > } while (m1 = m1->m_next); > } > #endif > - if ((ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { > + if ((ip = mtod(m, struct ip *))->ip_v == IPVERSION) && > + (ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { > if (sc->sc_if.if_flags & SC_COMPRESS) > *mtod(m, u_char *) |= sl_compress_tcp(m, ip, > &sc->sc_comp, 1); > -- > 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, In > >>c. > Future will arrive by its own means, progress not so. -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Apr 23 23:42:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA22539 for current-outgoing; Tue, 23 Apr 1996 23:42:19 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA22534 for ; Tue, 23 Apr 1996 23:42:06 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA11028 (5.67a/IDA-1.5 for ); Wed, 24 Apr 1996 09:42:02 +0300 Received: (from count@localhost) by key.hole.fi (8.7.4/8.6.12) id JAA02764; Wed, 24 Apr 1996 09:42:01 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199604240642.JAA02764@key.hole.fi> Subject: Re: MotherBoard Jumper Settings... To: davidg@Root.COM Date: Wed, 24 Apr 1996 09:42:01 +0300 (EET DST) Cc: current@freebsd.org In-Reply-To: <199604240450.VAA03207@Root.COM> from "David Greenman" at Apr 23, 96 09:50:47 pm X-Mailer: ELM [version 2.4 PL24alpha5] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman taisi sanoa: > > Third, the Oscillator Frequency was set for 33Mhz instead > >of 25Mhz...have fixed it... > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > *possibly* have any bad effects. :-) > > -DG AFAIK, DX/4-100 CPU's run only at 3x33MHz _or_ 2x50MHz mode which should be jumper selectable on the motherboard. At least all motherboards (and CPU's, two AMD's and one Intel) have worked like that. So if external clock is changed to 25MHz, it's effectively working with 75MHz internal clock instead of ~100MHz it's supposed to. (I used to have a AMD Am5x86-P75-S 133MHz part overclocked to 160MHz (ie. 4x33MHz -> 4x40MHz) which I used to run FreeBSD on but now I've got a P100 for BSD and that machine runs Windows95 without any problems after I dropped the ISA bus clock down from 13.33MHz to 10MHz so GUS could keep up.) -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Pengerkatu 13b A5 % IRC: Count NIC: BH271 % FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Wed Apr 24 00:05:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA23455 for current-outgoing; Wed, 24 Apr 1996 00:05:52 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA23448 for ; Wed, 24 Apr 1996 00:05:49 -0700 (PDT) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with SMTP id AAA06833; Wed, 24 Apr 1996 00:05:11 -0700 (PDT) Message-Id: <199604240705.AAA06833@precipice.shockwave.com> To: Poul-Henning Kamp cc: current@FreeBSD.org, Jim Fleming Subject: Re: SLIP: Check IP Version (please test) In-reply-to: Your message of "Wed, 24 Apr 1996 06:35:29 -0000." <10415.830327729@critter.tfs.com> Date: Wed, 24 Apr 1996 00:05:10 -0700 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk An IP v8 packet MUST never be forwarded to the slip driver. From: Poul-Henning Kamp Subject: Re: SLIP: Check IP Version (please test) > This patch seems to be irrelevant in any case. Only IPv4 packets should > be passed to the SLIP driver. SLIP is not a multiprotocol point-to-point > protocol, PPP is. > > IPvX x!=4 is a different protocol. SLIP is not supported in IPv6. Please > don't slow down the code path by adding this change. I agree, the point is that people play with IPv8 and it breaks slip. If SLIP is only for IPv4, it should discard other packets... And hey, how much overhead is this ??? Poul-Henning > > Paul > > From: Poul-Henning Kamp > Subject: SLIP: Check IP Version (please test) > > Somebody running slip with header compression please test this patch. > > Poul-Henning > > > I am starting to develop a substantialliy modified version of the IP pr >>ot oc > >>ol > . > > As specified in the IP protocol the ip_v (IP Version) field of the IP h >>ea de > >>r > > should be set to 4. (see /usr/src/sys/netinet/ip.h) > > > > It is not desirable for new versions of IP to "break" existing code. I >>ha ve > >> n > ot > > provide this but in studying the SLIP code I see that there is never re >>al ly > > a check done to see of the IP header is of version 4. > > Index: if_sl.c > =================================================================== > RCS file: /home/ncvs/src/sys/net/if_sl.c,v > retrieving revision 1.37 > diff -u -r1.37 if_sl.c > --- if_sl.c 1996/04/07 17:39:09 1.37 > +++ if_sl.c 1996/04/23 20:03:53 > @@ -561,7 +561,8 @@ > } while (m1 = m1->m_next); > } > #endif > - if ((ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { > + if ((ip = mtod(m, struct ip *))->ip_v == IPVERSION) && > + (ip = mtod(m, struct ip *))->ip_p == IPPROTO_TCP) { > if (sc->sc_if.if_flags & SC_COMPRESS) > *mtod(m, u_char *) |= sl_compress_tcp(m, ip, > &sc->sc_comp, 1); > -- > 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 >>, In > >>c. > Future will arrive by its own means, progress not so. -- 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, In >>c. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Apr 24 00:47:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA25566 for current-outgoing; Wed, 24 Apr 1996 00:47:53 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA25552 for ; Wed, 24 Apr 1996 00:47:38 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA11196; Wed, 24 Apr 1996 09:41:34 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA21278; Wed, 24 Apr 1996 09:41:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA26732; Wed, 24 Apr 1996 09:30:13 +0200 (MET DST) From: J Wunsch Message-Id: <199604240730.JAA26732@uriah.heep.sax.de> Subject: Re: MotherBoard Jumper Settings... To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 24 Apr 1996 09:30:12 +0200 (MET DST) Cc: cat@ki.net, geoff@ki.net, scrappy@ki.net (Marc G. Fournier) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 11:30:11 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Marc G. Fournier wrote: > Third, the Oscillator Frequency was set for 33Mhz instead > of 25Mhz...have fixed it... (Others told you that a DX4 is 3x, so the 33 MHz was right.) > As far as the cache is concerned, I have: > > 4x UM61512AK-15/95282/N52049's > 1x W24129AK-15/95200 (Tag SRAM) > > Am I correct in assuming that the -15 is the speed of the cache? > If so, and I haven't changed that one yet, my CMOS is set for 20ns... > would that produce any of the bugs I've been reporting? I don't think so. The tag RAM is IMHO normally faster than the cache, perhaps that's why they kept the cache timing slower than necessary in the setup. > The jumpers for the cache are set for 256KB/64kbx4...how do I > determine the size of each of the cache chips to determine if *this* is > right? The 61512 suggests a 512 Kbit cache. Seems you are using only half of it with your jumper setting. > What is "the ECP DMA Channel"? Its currently set for DMA 3... > is that correct? This hypermodern parallel channel. We don't use it, and most likely, you don't even have it enabled, but are using it in dumb Centronics compatibility mode. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Wed Apr 24 01:34:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA28739 for current-outgoing; Wed, 24 Apr 1996 01:34:23 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA28713 Wed, 24 Apr 1996 01:34:15 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04088; Wed, 24 Apr 1996 01:32:35 -0700 From: "Rodney W. Grimes" Message-Id: <199604240832.BAA04088@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: davidg@Root.COM Date: Wed, 24 Apr 1996 01:32:35 -0700 (PDT) Cc: hasty@rah.star-gate.com, scrappy@ki.net, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199604240134.SAA02806@Root.COM> from David Greenman at "Apr 23, 96 06:34:47 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >5. make sure that one of the drives is sending the termination power > > For external termination, this is normally done by the controller, not any > of the drives. True. > Most people terminate the last drive with the drive's termination I would disagree with that, most people use an external terminator on an external chain. Turning terminators on inside of external scsi enclosures is a no no in my book, it often leads to multiple termination when someone not so informed adds something to a chain. Or middle termination with a floating end when a chain gets swapped around. > and configure that drive to supply it's on termination power ^^ own For external scsi chains of any length > 3 feet I would _strongly_ encourage the use of drive supplied termination power (preferably from the last drive on the chain) to the scsi bus. > (which is usually the factory default). With the advent of the SCSI PnP spec this and other defaults are rapidly changing, the SCSI PnP spec requires that drives ship with no termination enabled, the use of on drive termination is verboten, you are suppose to use cable end terminators both internally and externally. I don't seem to recally anything about term power though :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 01:46:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA29693 for current-outgoing; Wed, 24 Apr 1996 01:46:46 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA29662 Wed, 24 Apr 1996 01:46:38 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id BAA00464; Wed, 24 Apr 1996 01:45:47 -0700 Message-Id: <199604240845.BAA00464@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: current@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-reply-to: Your message of "Wed, 24 Apr 1996 01:32:35 PDT." <199604240832.BAA04088@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Apr 1996 01:45:47 -0700 From: "Amancio Hasty Jr." Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I hope that all this useful information about scsi goes into the FreeBSD Handbook 8) Cheers, Amancio >>> "Rodney W. Grimes" said: > > >5. make sure that one of the drives is sending the termination power > > > > For external termination, this is normally done by the controller, not any > > of the drives. > > True. > > > Most people terminate the last drive with the drive's termination > > I would disagree with that, most people use an external terminator on > an external chain. Turning terminators on inside of external scsi > enclosures is a no no in my book, it often leads to multiple termination > when someone not so informed adds something to a chain. Or middle > termination with a floating end when a chain gets swapped around. > > > and configure that drive to supply it's on termination power > ^^ own > For external scsi chains of any length > 3 feet I would _strongly_ encourage > the use of drive supplied termination power (preferably from the last > drive on the chain) to the scsi bus. > > > (which is usually the factory default). > > With the advent of the SCSI PnP spec this and other defaults are rapidly > changing, the SCSI PnP spec requires that drives ship with no termination > enabled, the use of on drive termination is verboten, you are suppose to > use cable end terminators both internally and externally. I don't seem > to recally anything about term power though :-(. > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 01:53:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA00385 for current-outgoing; Wed, 24 Apr 1996 01:53:30 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA00361 Wed, 24 Apr 1996 01:53:23 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04106; Wed, 24 Apr 1996 01:51:11 -0700 From: "Rodney W. Grimes" Message-Id: <199604240851.BAA04106@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 01:51:11 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at "Apr 23, 96 11:38:05 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Tue, 23 Apr 1996, Michael Smith wrote: > > > Marc G. Fournier stands accused of saying: > > > > > sctarg0(noadapter::): Processor Target > > > > > > > > Wozzis? You have a scanner or something? > > > > > > > *shrug* nothing else other then those three cards in the > > > machine... > > > > Hmm. Have you got a 'pt0' in your kernel config? > > > Yes Why? And how many changes are there in your kernel config file with respect to the GENERIC kernel? Did you make the fatal mistakes that others have made and started from the LINT config file instead of the GENERIC config? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 01:54:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA00460 for current-outgoing; Wed, 24 Apr 1996 01:54:01 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA00430 Wed, 24 Apr 1996 01:53:54 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04097; Wed, 24 Apr 1996 01:49:05 -0700 From: "Rodney W. Grimes" Message-Id: <199604240849.BAA04097@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 01:49:05 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, jkh@time.cdrom.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at "Apr 23, 96 11:46:57 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 24 Apr 1996, Michael Smith wrote: > > > Don't waste any money on it. If you get it as a freebie, that's fine, > > but they're honest enough in the manual to point out that their tests > > aren't anything compared to the load a mutltitasking VM OS imposes. > > > > (We got it Real Cheap when we were having RAM trouble; it didn't find the > > problem, and this was a RAM error so bad that _Windows_ would barf.) > > > > I've got 9 make processes running in /usr/src/lib right now, > and will cycle those through for the next little while...that should give > it a good test, shouldn't it? That with the rest of its normal load? One of the bests tests I use for doing the divide and conquere (swap parts) in locating hardware related system failures (something I do as a weekly event) is simply repeated ``make worlds''. Unless you have _lots_ of memory (>32MB) multiple builds of /usr/src/lib are just going to thrash the paging/swap area to death. Besides library code compiles easily do to the small sizes of the source and produced object files, use a monster compile like gcc/g++. What you are looking for is signal 6's, 10's and 11's, which generally point to memory (cache or main) related system failures. Panics can be just about anything from the CPU chip to the I/O cards. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 02:07:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA01489 for current-outgoing; Wed, 24 Apr 1996 02:07:16 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA01474 for ; Wed, 24 Apr 1996 02:07:12 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id CAA04133; Wed, 24 Apr 1996 02:06:57 -0700 From: "Rodney W. Grimes" Message-Id: <199604240906.CAA04133@GndRsh.aac.dev.com> Subject: Re: SLIP: Check IP Version (please test) To: pst@Shockwave.COM (Paul Traina) Date: Wed, 24 Apr 1996 02:06:57 -0700 (PDT) Cc: phk@critter.tfs.com, current@FreeBSD.org, JimFleming@unety.net In-Reply-To: <199604240705.AAA06833@precipice.shockwave.com> from Paul Traina at "Apr 24, 96 00:05:10 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > An IP v8 packet MUST never be forwarded to the slip driver. Granted, but to protect one self from losing software ``be conservative in what you send and gaurd yourself from what you might receive''. This patch just protects FreeBSD to make sure what comes down the serial line is marked as an IPV4 packet. I don't care if your not suppose to send v6 or v8 stuff over SLIP, the software should _VALIDATE_ what it received. > From: Poul-Henning Kamp > Subject: Re: SLIP: Check IP Version (please test) > > This patch seems to be irrelevant in any case. Only IPv4 packets should > > be passed to the SLIP driver. SLIP is not a multiprotocol point-to-point > > protocol, PPP is. > > > > IPvX x!=4 is a different protocol. SLIP is not supported in IPv6. Please > > don't slow down the code path by adding this change. > > I agree, the point is that people play with IPv8 and it breaks slip. > If SLIP is only for IPv4, it should discard other packets... ... [the rest trashed] ... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 02:14:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA01918 for current-outgoing; Wed, 24 Apr 1996 02:14:21 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA01911 for ; Wed, 24 Apr 1996 02:14:16 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id CAA04144; Wed, 24 Apr 1996 02:12:52 -0700 From: "Rodney W. Grimes" Message-Id: <199604240912.CAA04144@GndRsh.aac.dev.com> Subject: Re: MotherBoard Jumper Settings... To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 24 Apr 1996 02:12:52 -0700 (PDT) Cc: freebsd-current@FreeBSD.org, cat@ki.net, geoff@ki.net, scrappy@ki.net In-Reply-To: <199604240730.JAA26732@uriah.heep.sax.de> from J Wunsch at "Apr 24, 96 09:30:12 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > As Marc G. Fournier wrote: > > > Third, the Oscillator Frequency was set for 33Mhz instead > > of 25Mhz...have fixed it... > > (Others told you that a DX4 is 3x, so the 33 MHz was right.) > > > As far as the cache is concerned, I have: > > > > 4x UM61512AK-15/95282/N52049's > > 1x W24129AK-15/95200 (Tag SRAM) > > > > Am I correct in assuming that the -15 is the speed of the cache? > > If so, and I haven't changed that one yet, my CMOS is set for 20ns... > > would that produce any of the bugs I've been reporting? > > I don't think so. The tag RAM is IMHO normally faster than the cache, > perhaps that's why they kept the cache timing slower than necessary in > the setup. This is only common when the data RAM is -20ns. The more ``usuall'' conditions are that the TAG is 15nS (though some times it can be safely 20nS) and the DATA is either 15 or 20nS. A few rare boards use 12nS parts for TAG and either 12 or 15nS parts for DATA. > > The jumpers for the cache are set for 256KB/64kbx4...how do I > > determine the size of each of the cache chips to determine if *this* is > > right? > > The 61512 suggests a 512 Kbit cache. Seems you are using only half of > it with your jumper setting. The 61512 is infact a 64k x 8 part, I looked it up as there had been too much speculation on here about just what that chip was. Cache RAM on 486 and later machines is almost always x 8 parts for those who thought this might have been a 128k x 4. Your cache jumper settings are correct at 256K/64Kx8. You may still have a bad cache RAM though. Do you ever get any signal 10's or 11's from the gcc compiler, or do you just get panics? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 02:47:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA03932 for current-outgoing; Wed, 24 Apr 1996 02:47:04 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [205.218.122.51]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA03907 Wed, 24 Apr 1996 02:46:57 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.4/8.7.3) with SMTP id EAA21733; Wed, 24 Apr 1996 04:39:44 -0500 (CDT) Date: Wed, 24 Apr 1996 04:39:44 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: "Marc G. Fournier" cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, Marc G. Fournier wrote: > FreeBSD 2.1-STABLE #0: Tue Apr 23 10:33:56 EDT 1996 > scrappy@ki.net:/usr/src/sys/compile/kinet > CPU: i486 DX4 (486-class CPU) > Origin = "GenuineIntel" Id = 0x480 Stepping=0 > Features=0x3 This isn't an Asus SP3 or SP3G is it? > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 12 on pci0:11 Same contoller here... > ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa > ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) Heh, I've got an NE2000, but it uses the ed driver as well. > Oh, the motherboard is an ACER AP43 with a 486DX4-100 > CPU, and sio[01] are both onboard serial. Ah, ok... But they both use the same SiS chipset. I'm seeing something I've classified as 'slightly weird' but due to the machine and the nature of problem, its a bit difficult to check the console for a panic. In any event, the machine can't stay up for more than 5 or 6 days. I'm going to re-enable crash dumps and make an up to date -stable kernel and see whats up. Due to the similarities between your hardware and mine, this problem MIGHT be hardware related. I've considered replacing the SC-200 with an ah2940 to see if that makes a difference. Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-current Wed Apr 24 02:59:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA04606 for current-outgoing; Wed, 24 Apr 1996 02:59:03 -0700 (PDT) Received: from ra.dkuug.dk ([130.225.204.52]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA04601 for ; Wed, 24 Apr 1996 02:59:01 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA06582 for current@freebsd.org; Wed, 24 Apr 1996 11:51:03 +0200 Message-Id: <199604240951.LAA06582@ra.dkuug.dk> Subject: Anybody playe with ip_filter ?? To: current@freebsd.org (FreeBSD current) Date: Wed, 24 Apr 1996 11:51:03 +0200 (MET DST) From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I seems it'll do what I need, anybody got any experience before I dig in, and should we put in the patches in the kernel, making it easy to use ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Apr 24 03:09:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA05355 for current-outgoing; Wed, 24 Apr 1996 03:09:15 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA05350 for ; Wed, 24 Apr 1996 03:09:13 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uC1VY-0003wZC; Wed, 24 Apr 96 03:09 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id KAA10756; Wed, 24 Apr 1996 10:09:08 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Paul Traina cc: current@FreeBSD.org, Jim Fleming Subject: Re: SLIP: Check IP Version (please test) In-reply-to: Your message of "Wed, 24 Apr 1996 00:05:10 MST." <199604240705.AAA06833@precipice.shockwave.com> Date: Wed, 24 Apr 1996 10:09:07 +0000 Message-ID: <10754.830340547@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > An IP v8 packet MUST never be forwarded to the slip driver. Fine, well, and where in our code do we assign IP protocol versions to interfaces ??? -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Apr 24 03:23:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA06259 for current-outgoing; Wed, 24 Apr 1996 03:23:15 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA06253 Wed, 24 Apr 1996 03:23:12 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uC1j4-0003viC; Wed, 24 Apr 96 03:23 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id KAA10844; Wed, 24 Apr 1996 10:23:06 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: sos@FreeBSD.org cc: current@FreeBSD.org (FreeBSD current) Subject: Re: Anybody playe with ip_filter ?? In-reply-to: Your message of "Wed, 24 Apr 1996 11:51:03 +0200." <199604240951.LAA06582@ra.dkuug.dk> Date: Wed, 24 Apr 1996 10:23:05 +0000 Message-ID: <10842.830341385@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I seems it'll do what I need, anybody got any experience before > I dig in, and should we put in the patches in the kernel, making > it easy to use ?? I have talked with the author, and we kind of agreed to get it in. The present kernel interface to ipfw should fit ip_filter fine, and we should have no need to modify it further I think... -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Apr 24 03:49:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA07625 for current-outgoing; Wed, 24 Apr 1996 03:49:48 -0700 (PDT) Received: from ra.dkuug.dk ([130.225.204.52]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA07613 Wed, 24 Apr 1996 03:49:41 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id MAA07022; Wed, 24 Apr 1996 12:41:43 +0200 Message-Id: <199604241041.MAA07022@ra.dkuug.dk> Subject: Re: Anybody playe with ip_filter ?? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Wed, 24 Apr 1996 12:41:43 +0200 (MET DST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <10842.830341385@critter.tfs.com> from "Poul-Henning Kamp" at Apr 24, 96 10:23:05 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Poul-Henning Kamp who wrote: > > > > > I seems it'll do what I need, anybody got any experience before > > I dig in, and should we put in the patches in the kernel, making > > it easy to use ?? > > I have talked with the author, and we kind of agreed to get it in. > > The present kernel interface to ipfw should fit ip_filter fine, > and we should have no need to modify it further I think... Super, who is going to do that & when :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Apr 24 04:17:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA09300 for current-outgoing; Wed, 24 Apr 1996 04:17:23 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA09295 Wed, 24 Apr 1996 04:17:21 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uC2ZT-0003viC; Wed, 24 Apr 96 04:17 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id LAA10912; Wed, 24 Apr 1996 11:17:17 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: sos@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Anybody playe with ip_filter ?? In-reply-to: Your message of "Wed, 24 Apr 1996 12:41:43 +0200." <199604241041.MAA07022@ra.dkuug.dk> Date: Wed, 24 Apr 1996 11:17:16 +0000 Message-ID: <10910.830344636@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > In reply to Poul-Henning Kamp who wrote: > > > > > > > > I seems it'll do what I need, anybody got any experience before > > > I dig in, and should we put in the patches in the kernel, making > > > it easy to use ?? > > > > I have talked with the author, and we kind of agreed to get it in. > > > > The present kernel interface to ipfw should fit ip_filter fine, > > and we should have no need to modify it further I think... > > Super, who is going to do that & when :) you, now ? :-) -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Wed Apr 24 04:31:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10127 for current-outgoing; Wed, 24 Apr 1996 04:31:20 -0700 (PDT) Received: from ra.dkuug.dk ([130.225.204.52]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA10119 Wed, 24 Apr 1996 04:31:15 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id NAA07538; Wed, 24 Apr 1996 13:23:19 +0200 Message-Id: <199604241123.NAA07538@ra.dkuug.dk> Subject: Re: Anybody playe with ip_filter ?? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Wed, 24 Apr 1996 13:23:19 +0200 (MET DST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <10910.830344636@critter.tfs.com> from "Poul-Henning Kamp" at Apr 24, 96 11:17:16 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Poul-Henning Kamp who wrote: > > > > The present kernel interface to ipfw should fit ip_filter fine, > > > and we should have no need to modify it further I think... > > > > Super, who is going to do that & when :) > > you, now ? :-) I didn't have to ask right :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Apr 24 05:03:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA11947 for current-outgoing; Wed, 24 Apr 1996 05:03:54 -0700 (PDT) Received: from nhj.nlc.net.au (rjm@nhj.nlc.net.au [203.24.133.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA11939 for ; Wed, 24 Apr 1996 05:03:46 -0700 (PDT) Received: (from rjm@localhost) by nhj.nlc.net.au (8.7.1/8.7.1) id WAA02684; Wed, 24 Apr 1996 22:02:24 +1000 Date: Wed, 24 Apr 1996 22:02:24 +1000 (EST) From: Rick Marshall To: "Marc G. Fournier" cc: Ncurses Mailing List , current@freebsd.org Subject: Re: termcap/curses vs ncurses In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK if there's one thing I hate it's religious arguments and this whole terminfo/termcap thing is definitely one of those. I have picked a message at random from the hoard of message to reply through not because I thought it was better or worse, or more or less appropriate than the others. Enough of the crap. I've been doing curses things for however long its been around and maintain a major screen based thing that does lots of hairy terminal window stuff. Here's my reasons for doing things: Switched from termcap to terminfo so I could stop decoding function keys. If termcap does it now that's great, but eons ago fkeys were a pain in the neck and terminfo did it for me. The post polish strings for sgr, csr and their cousins are great if you know how to use a stack machine. The speed of terminfo is good partly because of the small files that don't don't have to be searched, but mostly because un*x caches inodes and blocks so lots of times there is no disk access to get terminal descriptions. BTW, specially for esr, don't beat up the termcap people too much or I won't have a big enough file to cat to the console while I try to work out which way the turbo switch goes. Terminfo printer stuff in conjunction with Sys V lp works really well too. I have ported terminfo code to SysV3&4, HP/Ux, SUNOs, Solaris, Linux, DEC Unix, SCO :-), AIX,, .... with minimal problems. The worst was getting AIX box stuff working. Anyone interested? And finally I do use mc4/mc5 in production environments for print through and it does work. If anyone's interested I'll share the secrets. Now can we get onto something really important to all of us who use modems to maintain sites where full screen operation is normal and get support for the repeat character sequence in the ncurses screen update optimiser and sort out what attributes the screen has after a clear screen. email rjm@nlc.net.au WWW http://www.nlc.net.au/~rjm/ From owner-freebsd-current Wed Apr 24 05:04:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA12002 for current-outgoing; Wed, 24 Apr 1996 05:04:46 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA11996 for ; Wed, 24 Apr 1996 05:04:44 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id VAA19115; Wed, 24 Apr 1996 21:31:22 +0930 From: Michael Smith Message-Id: <199604241201.VAA19115@genesis.atrad.adelaide.edu.au> Subject: Re: MotherBoard Jumper Settings... To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 24 Apr 1996 21:31:22 +0930 (CST) Cc: current@freebsd.org In-Reply-To: <199604240912.CAA04144@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Apr 24, 96 02:12:52 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney W. Grimes stands accused of saying: > > The 61512 is infact a 64k x 8 part, I looked it up as there had been > too much speculation on here about just what that chip was. Cache RAM > on 486 and later machines is almost always x 8 parts for those who thought > this might have been a 128k x 4. Argh, bite me. 4 parts, 32 bits, has to be x8. Sorry about that. > Rod Grimes rgrimes@gndrsh.aac.dev.com -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Apr 24 05:11:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA12173 for current-outgoing; Wed, 24 Apr 1996 05:11:03 -0700 (PDT) Received: from nhj.nlc.net.au (rjm@nhj.nlc.net.au [203.24.133.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA12168 for ; Wed, 24 Apr 1996 05:10:58 -0700 (PDT) Received: (from rjm@localhost) by nhj.nlc.net.au (8.7.1/8.7.1) id WAA03081; Wed, 24 Apr 1996 22:10:33 +1000 Date: Wed, 24 Apr 1996 22:10:33 +1000 (EST) From: Rick Marshall To: Kaz Kylheku cc: Terry Lambert , "Eric S. Raymond" , ache@astral.msk.su, scrappy@ki.net, current@FreeBSD.org, ncurses-list@netcom.com Subject: Re: terminfo-less ncurses In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk email rjm@nlc.net.au WWW http://www.nlc.net.au/~rjm/ On Wed, 10 Apr 1996, Kaz Kylheku wrote: > > Also let's not foget the TERMCAP environment variable! Any curses program that > doesn't recognize this variable is broken. Filling the environment is a great way to slow down program loads... > Today's UNIX systems could crunch through an 8 megabyte /etc/termcap each time > you run a curses program and still start up the program faster than Microsoft > Word. As long as your'e the only user > > If you could show me that the terminfo format had not changed since > > day one, well, then you'd have an argument. > > Haha. Touche. who cares? tic files are what we distribute and compile as required. Now we have ncurses all the earlier porting problems are rapidly dispapearing too. > From owner-freebsd-current Wed Apr 24 06:40:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA15503 for current-outgoing; Wed, 24 Apr 1996 06:40:59 -0700 (PDT) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA15498 Wed, 24 Apr 1996 06:40:57 -0700 (PDT) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id JAA14983; Wed, 24 Apr 1996 09:40:52 -0400 for Date: Wed, 24 Apr 1996 09:40:52 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199604241340.JAA14983@robin.mcnc.org.mcnc.org> To: current@freebsd.org Subject: minor syscons bogon Cc: freebsd-current@freebsd.org X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I posted recently that I was having trouble with console lockups while running X. This problem was a combination of "I'm a stupid" and a minor bug in syscons.c. I'd recompiled my kernel with MAXCONS set to to 4, to save a few bytes of memory and left xdm getty'd to ttyv4 - duh. Only, the bloody thing ran - for a while, until it had tiptoed thru enuf memory ... Would someone kindly commit this patch so others don't fall in the same hole? I believe pcvt has the same bug, but haven't looked at it. - Frank *** syscons.c.orig Thu Feb 8 04:25:44 1996 --- syscons.c Wed Apr 24 05:31:05 1996 *************** *** 305,311 **** if (!init_done) return(NULL); ! if (unit > MAXCONS || unit < 0) return(NULL); if (unit == MAXCONS) return CONSOLE_TTY; --- 305,311 ---- if (!init_done) return(NULL); ! if (unit >= MAXCONS || unit < 0) return(NULL); if (unit == MAXCONS) return CONSOLE_TTY; \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Wed Apr 24 07:08:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA16771 for current-outgoing; Wed, 24 Apr 1996 07:08:55 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA16749 Wed, 24 Apr 1996 07:08:36 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id PAA08249; Wed, 24 Apr 1996 15:59:45 +0200 Message-Id: <199604241359.PAA08249@ra.dkuug.dk> Subject: Re: minor syscons bogon To: fty@mcnc.org (Frank E. Terhaar-Yonkers) Date: Wed, 24 Apr 1996 15:59:44 +0200 (MET DST) Cc: current@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <199604241340.JAA14983@robin.mcnc.org.mcnc.org> from "Frank E. Terhaar-Yonkers" at Apr 24, 96 09:40:52 am From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Frank E. Terhaar-Yonkers who wrote: > > I posted recently that I was having trouble with console lockups while > running X. This problem was a combination of "I'm a stupid" and a minor > bug in syscons.c. > > I'd recompiled my kernel with MAXCONS set to to 4, to save a few bytes of > memory and left xdm getty'd to ttyv4 - duh. Only, the bloody thing > ran - for a while, until it had tiptoed thru enuf memory ... There is no real saving in mucking with MAXCONS, all vty's are dynamically allocated... Besides MAXCONS are to meant to be fooled around with, its a value used as a max value... > Would someone kindly commit this patch so others don't fall in the same > hole? I believe pcvt has the same bug, but haven't looked at it. NO, this breaks the console device /dev/console ! (and its not a bug) > - Frank > > *** syscons.c.orig Thu Feb 8 04:25:44 1996 > --- syscons.c Wed Apr 24 05:31:05 1996 > *************** > *** 305,311 **** > > if (!init_done) > return(NULL); > ! if (unit > MAXCONS || unit < 0) > return(NULL); > if (unit == MAXCONS) > return CONSOLE_TTY; > --- 305,311 ---- > > if (!init_done) > return(NULL); > ! if (unit >= MAXCONS || unit < 0) > return(NULL); > if (unit == MAXCONS) > return CONSOLE_TTY; > > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ > Frank Terhaar-Yonkers, Manager > High Performance Computing and Communications Research > MCNC > PO Box 12889 3021 Cornwallis Road > Research Triangle Park, North Carolina 27709-2889 > fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 > > http://www.mcnc.org/hpcc.html > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Apr 24 07:21:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17456 for current-outgoing; Wed, 24 Apr 1996 07:21:03 -0700 (PDT) Received: from ghost.uunet.ca (ghost.uunet.ca [142.77.1.100]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA17434 Wed, 24 Apr 1996 07:20:52 -0700 (PDT) Received: by ghost.uunet.ca id <52814-3053>; Wed, 24 Apr 1996 10:20:30 -0400 Date: Wed, 24 Apr 1996 10:20:24 -0400 From: Cat Okita To: "Rodney W. Grimes" cc: davidg@Root.COM, hasty@rah.star-gate.com, scrappy@ki.net, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240832.BAA04088@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > I would disagree with that, most people use an external terminator on > an external chain. Turning terminators on inside of external scsi > enclosures is a no no in my book, it often leads to multiple termination > when someone not so informed adds something to a chain. Or middle > termination with a floating end when a chain gets swapped around. I'll second that one - I've had some really unpleasant times trying to find out which device *thinks* that it's terminated, if it's in the case, or on the drive. External termination is right out in front of your eyes. > With the advent of the SCSI PnP spec this and other defaults are rapidly > changing, the SCSI PnP spec requires that drives ship with no termination > enabled, the use of on drive termination is verboten, you are suppose to > use cable end terminators both internally and externally. I don't seem > to recally anything about term power though :-(. Being overly used to the world of unix-designed machines (ie: sun, dec...), it was a really nasty shock to discover that PC's *normally* terminate on the drives... cheers! cat From owner-freebsd-current Wed Apr 24 07:27:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA17985 for current-outgoing; Wed, 24 Apr 1996 07:27:45 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA17962 Wed, 24 Apr 1996 07:27:38 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id HAA25084 ; Wed, 24 Apr 1996 07:27:20 -0700 Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id RAA19922; Wed, 24 Apr 1996 17:21:22 +0300 Date: Wed, 24 Apr 1996 17:21:22 +0300 (EET DST) From: Narvi To: "Rodney W. Grimes" cc: davidg@Root.COM, hasty@rah.star-gate.com, scrappy@ki.net, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240832.BAA04088@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > >5. make sure that one of the drives is sending the termination power > > > > For external termination, this is normally done by the controller, not any > > of the drives. > > True. > > > Most people terminate the last drive with the drive's termination > > I would disagree with that, most people use an external terminator on > an external chain. Turning terminators on inside of external scsi > enclosures is a no no in my book, it often leads to multiple termination > when someone not so informed adds something to a chain. Or middle > termination with a floating end when a chain gets swapped around. > > > and configure that drive to supply it's on termination power > ^^ own > For external scsi chains of any length > 3 feet I would _strongly_ encourage > the use of drive supplied termination power (preferably from the last > drive on the chain) to the scsi bus. > > > (which is usually the factory default). > > With the advent of the SCSI PnP spec this and other defaults are rapidly > changing, the SCSI PnP spec requires that drives ship with no termination > enabled, the use of on drive termination is verboten, you are suppose to > use cable end terminators both internally and externally. I don't seem > to recally anything about term power though :-(. There happen to be devices (at least my HP DAT is of that kind) which always supply termination power - you even can'tr turn it off. > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD > Sander Eat good food, preserve nature, be nice to all nice people :) From owner-freebsd-current Wed Apr 24 07:32:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA18822 for current-outgoing; Wed, 24 Apr 1996 07:32:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA18702 for ; Wed, 24 Apr 1996 07:32:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA11176; Wed, 24 Apr 1996 07:31:44 -0700 (PDT) To: Paul Traina cc: Douglas Ambrisko , phk@critter.tfs.com (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: socks support native in freebsd? In-reply-to: Your message of "Tue, 23 Apr 1996 18:40:45 PDT." <199604240140.SAA28661@precipice.shockwave.com> Date: Wed, 24 Apr 1996 07:31:44 -0700 Message-ID: <11174.830356304@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I rather doubt it would fit anyway - sysinstall is already pushing the boundries of a kernel + crunched binary on a 1.2MB floppy anyway. > I think Doug wants a socksified sysinstall ... yuck/ouch (in that order). :-) > > From: "Jordan K. Hubbard" > Subject: Re: socks support native in freebsd? > > The only thing we are missing is socks support for the installation of > > FreeBSD on the boot floppy. > > Hmm, could you perhaps elaborate on this a little? > > Jordan From owner-freebsd-current Wed Apr 24 07:42:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA21822 for current-outgoing; Wed, 24 Apr 1996 07:42:13 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA21817 for ; Wed, 24 Apr 1996 07:42:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA11238; Wed, 24 Apr 1996 07:40:28 -0700 (PDT) To: "Marc G. Fournier" cc: current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Tue, 23 Apr 1996 23:30:11 EDT." Date: Wed, 24 Apr 1996 07:40:28 -0700 Message-ID: <11236.830356828@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > So, I've fixed those...could *any* of those above have > produced the problems I've been seeing? Or are they minor? Sorry, I'm still picking my jaw up off the floor! I wish you'd taken a picture of your configuration before you fixed what has to be the most amazing stack of bogons in one machine I've ever seen - I'd stick it up on the web pages as "this month's poster child for how to configure your hardware completely and totally incorrectly." If your machine runs correctly after this, you owe lots of people lots of beer! :-) Jordan From owner-freebsd-current Wed Apr 24 07:43:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA21913 for current-outgoing; Wed, 24 Apr 1996 07:43:46 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA21908 for ; Wed, 24 Apr 1996 07:43:44 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id JAA19003; Wed, 24 Apr 1996 09:37:53 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB31C2.28B6B6A0@webster.unety.net>; Wed, 24 Apr 1996 09:41:05 -0500 Message-ID: <01BB31C2.28B6B6A0@webster.unety.net> From: Jim Fleming To: "'Poul-Henning Kamp'" , Paul Traina Cc: "current@FreeBSD.org" , Jim Fleming Subject: RE: SLIP: Check IP Version (please test) Date: Wed, 24 Apr 1996 09:41:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 1:35 AM, Poul-Henning Kamp[SMTP:phk@critter.tfs.com] wrote: @> This patch seems to be irrelevant in any case. Only IPv4 packets should @> be passed to the SLIP driver. SLIP is not a multiprotocol point-to-point @> protocol, PPP is. @> @> IPvX x!=4 is a different protocol. SLIP is not supported in IPv6. Please @> don't slow down the code path by adding this change. @ @I agree, the point is that people play with IPv8 and it breaks slip. @If SLIP is only for IPv4, it should discard other packets... @ Yes...and since IPv8 "slips" between the cracks of IPv4 and IPv6...SLIP can miss the IPv8 packets and crunch the checksum field of IPv8 which is used to encode the StarGate address(es). -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-current Wed Apr 24 07:44:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22036 for current-outgoing; Wed, 24 Apr 1996 07:44:32 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA22031 for ; Wed, 24 Apr 1996 07:44:30 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id JAA19010; Wed, 24 Apr 1996 09:38:37 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB31C2.436DB3E0@webster.unety.net>; Wed, 24 Apr 1996 09:41:50 -0500 Message-ID: <01BB31C2.436DB3E0@webster.unety.net> From: Jim Fleming To: Poul-Henning Kamp , "'Paul Traina'" Cc: "current@FreeBSD.org" , Jim Fleming Subject: RE: SLIP: Check IP Version (please test) Date: Wed, 24 Apr 1996 09:41:49 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 2:05 AM, Paul Traina[SMTP:pst@shockwave.com] wrote: @An IP v8 packet MUST never be forwarded to the slip driver. @ Why not...??? -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-current Wed Apr 24 07:45:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22103 for current-outgoing; Wed, 24 Apr 1996 07:45:11 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA22095 for ; Wed, 24 Apr 1996 07:45:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA11249; Wed, 24 Apr 1996 07:43:21 -0700 (PDT) To: davidg@Root.COM cc: "Marc G. Fournier" , current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Tue, 23 Apr 1996 21:50:47 PDT." <199604240450.VAA03207@Root.COM> Date: Wed, 24 Apr 1996 07:43:21 -0700 Message-ID: <11246.830357001@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Third, the Oscillator Frequency was set for 33Mhz instead > >of 25Mhz...have fixed it... > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > *possibly* have any bad effects. :-) If I wasn't such a nice guy (ha!) I'd add a "Hall of Shame" to our web pages and stick this entry in there as a warning to others who would first blame the software before performing even the most elementary checks to see if their hardware was even configured correctly! :-) Jordan From owner-freebsd-current Wed Apr 24 07:49:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22376 for current-outgoing; Wed, 24 Apr 1996 07:49:04 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA22370 Wed, 24 Apr 1996 07:49:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA11283; Wed, 24 Apr 1996 07:48:39 -0700 (PDT) To: davidg@Root.COM cc: "Justin T. Gibbs" , "Marc G. Fournier" , current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Tue, 23 Apr 1996 22:13:47 PDT." <199604240513.WAA03265@Root.COM> Date: Wed, 24 Apr 1996 07:48:39 -0700 Message-ID: <11281.830357319@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >DX4s are clock trippled chips. The clock setting was correct the > >first time. A DX4100 runs at 99.999MHz. > > Oh, yes, of course - 3 * 33.3 = 100. Okay, so it's been a long day. :-) This was one of the few things that was correct - he still had his cache set wrong and a jumper mis-set. And actually, I would also run this at 75Mhz until I was sure of the chip - my friend Chuck got a "DX4/100" recently which didn't behave at all well with FreeBSD; same symptoms as Marc's. Then we clocked it to 75Mhz and it worked (and has continued to work) smoothly. We looked at the chip again more closely (we had to peel the stupid sticker off of it first before we could read the numbers) and found that he'd been sold a DX4/75 as a DX4/100. A lot of this kinda thing going around. Jordan From owner-freebsd-current Wed Apr 24 07:58:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22935 for current-outgoing; Wed, 24 Apr 1996 07:58:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA22924 for ; Wed, 24 Apr 1996 07:58:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA11320; Wed, 24 Apr 1996 07:55:14 -0700 (PDT) To: "Bror 'Count' Heinola" cc: davidg@Root.COM, current@freebsd.org Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Wed, 24 Apr 1996 09:42:01 +0300." <199604240642.JAA02764@key.hole.fi> Date: Wed, 24 Apr 1996 07:55:14 -0700 Message-ID: <11318.830357714@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > AFAIK, DX/4-100 CPU's run only at 3x33MHz _or_ 2x50MHz mode > which should be jumper selectable on the motherboard. At least > all motherboards (and CPU's, two AMD's and one Intel) have > worked like that. What's the memory clock on these beasts - 60Mhz? I've never owned a DX4/100 and don't ever really plan to, I'm just wondering if the motherboards require 60ns memory or will live happily with the 70ns stuff. Jordan P.S. The Pentiums are cheap enough now that I just can't see investing in 486 technology unless it's for a router or something. > > So if external clock is changed to 25MHz, it's effectively > working with 75MHz internal clock instead of ~100MHz it's > supposed to. > > (I used to have a AMD Am5x86-P75-S 133MHz part overclocked to > 160MHz (ie. 4x33MHz -> 4x40MHz) which I used to run FreeBSD on > but now I've got a P100 for BSD and that machine runs Windows95 > without any problems after I dropped the ISA bus clock down from > 13.33MHz to 10MHz so GUS could keep up.) > > > -- > Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ > Pengerkatu 13b A5 % IRC: Count NIC: BH271 % > FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, > Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Wed Apr 24 07:58:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA22994 for current-outgoing; Wed, 24 Apr 1996 07:58:45 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA22984 for ; Wed, 24 Apr 1996 07:58:41 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA16933; Wed, 24 Apr 1996 10:58:31 -0400 Date: Wed, 24 Apr 1996 10:58:31 -0400 From: Garrett Wollman Message-Id: <9604241458.AA16933@halloran-eldar.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, Jim Fleming Subject: Re: SLIP: Check IP Version (please test) In-Reply-To: <10754.830340547@critter.tfs.com> References: <199604240705.AAA06833@precipice.shockwave.com> <10754.830340547@critter.tfs.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: >> An IP v8 packet MUST never be forwarded to the slip driver. > Fine, well, and where in our code do we assign IP protocol versions > to interfaces ??? We assign addresses (and their associated address families) to interfaces, which amounts to the same thing. Any implementation of IPvX where X != 4 MUST use family values other than [PA]F_INET. -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 Apr 24 07:59:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23045 for current-outgoing; Wed, 24 Apr 1996 07:59:03 -0700 (PDT) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23038 Wed, 24 Apr 1996 07:58:58 -0700 (PDT) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id KAA20962; Wed, 24 Apr 1996 10:58:58 -0400 for Date: Wed, 24 Apr 1996 10:58:58 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199604241458.KAA20962@robin.mcnc.org.mcnc.org> To: sos@FreeBSD.ORG Subject: Re: minor syscons bogon Cc: current@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That's fine .. >There is no real saving in mucking with MAXCONS, all vty's are dynamically >allocated... >Besides MAXCONS are to meant to be fooled around with, its a value >used as a max value... > >> Would someone kindly commit this patch so others don't fall in the same >> hole? I believe pcvt has the same bug, but haven't looked at it. > >NO, this breaks the console device /dev/console ! >(and its not a bug) The fix may not be correct if it does in fact break /dev/console. But the scenario IS A BUG. The kernel should not allow an open/write to an unconfigured device with obviously bad results. > >> - Frank >> >> *** syscons.c.orig Thu Feb 8 04:25:44 1996 >> --- syscons.c Wed Apr 24 05:31:05 1996 >> *************** >> *** 305,311 **** >> >> if (!init_done) >> return(NULL); >> ! if (unit > MAXCONS || unit < 0) >> return(NULL); >> if (unit == MAXCONS) >> return CONSOLE_TTY; >> --- 305,311 ---- >> >> if (!init_done) >> return(NULL); >> ! if (unit >= MAXCONS || unit < 0) >> return(NULL); >> if (unit == MAXCONS) >> return CONSOLE_TTY; >> >> \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ >> Frank Terhaar-Yonkers, Manager >> High Performance Computing and Communications Research >> MCNC >> PO Box 12889 3021 Cornwallis Road >> Research Triangle Park, North Carolina 27709-2889 >> fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 >> >> http://www.mcnc.org/hpcc.html >> > > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > So much code to hack -- so little time. > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Wed Apr 24 08:37:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA26000 for current-outgoing; Wed, 24 Apr 1996 08:37:46 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA25995 for ; Wed, 24 Apr 1996 08:37:42 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id KAA19080; Wed, 24 Apr 1996 10:31:45 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB31C9.AF275A80@webster.unety.net>; Wed, 24 Apr 1996 10:34:57 -0500 Message-ID: <01BB31C9.AF275A80@webster.unety.net> From: Jim Fleming To: Poul-Henning Kamp , "'Garrett Wollman'" Cc: "current@FreeBSD.ORG" , Jim Fleming Subject: RE: SLIP: Check IP Version (please test) Date: Wed, 24 Apr 1996 10:34:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 9:58 AM, Garrett Wollman[SMTP:wollman@lcs.mit.edu] wrote: @< said: @ @>> An IP v8 packet MUST never be forwarded to the slip driver. @> Fine, well, and where in our code do we assign IP protocol versions @> to interfaces ??? @ @We assign addresses (and their associated address families) to @interfaces, which amounts to the same thing. Any implementation of @IPvX where X != 4 MUST use family values other than [PA]F_INET. @ @-GAWollman @ This may be the general case. In the case of IPv8 it was intentionally designed to allow incremental "hacks" to be added to existing stacks without breaking everything in the world. Because of this, a new address family may not be needed. There are several benefits of this incremental approach. 1. It gives "students" the ability to try some simple experiments with their systems. This allows them to gain confidence that they can do kernel work (a lost art) without destroying the system the first time out. 2. It allows sites to use the IPv8 format for security functions in their closed systems that may need extra protection from IPv4 sniffing. 3. It allows developers to test the benefits of having the IPv4 core network still route some traffic while the IPv8 network is being developed around the edges using Protocol 4 IP-in-IP encapsulation. 4. Performance differences can also be tested when IPv8 packets are sent via the same transports as IPv4 with minor tweeking to allow both formats to co-exist. 5. Most importantly, it allows us to evaluate the trade-offs that were made in the current IPv4 implementation of putting upper level protocol decisions in lower levels of the stack for efficiency reasons while sacrificing code clarity. Now that systems are faster, some of these trade-offs may be relaxed in modern IPv8 implementations. ...there are many ways to skin a C+@...IPv4 did it one way...IPv8 builds on that... -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-current Wed Apr 24 09:12:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA27860 for current-outgoing; Wed, 24 Apr 1996 09:12:06 -0700 (PDT) Received: from remote.transarc.com (remote.transarc.com [158.98.16.250]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA27831 for ; Wed, 24 Apr 1996 09:12:00 -0700 (PDT) Received: by remote.transarc.com (5.65/DEC-Ultrix/4.3) id AA23779; Wed, 24 Apr 1996 12:11:14 -0400 Date: Wed, 24 Apr 1996 12:11:26 -0400 (EDT) From: Pat Barron To: freebsd-current@freebsd.org Subject: make -DCLOBBER Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just tried this with the latest FreeBSD-current sources, and it (still) fails (as it did last time I tried it, back in like Sept. '95, for the same reasons....) This time, in libgmp, the build fails because it can't find crt0.o or libgcc.a. Does no one else actually use this? ;-) --Pat. From owner-freebsd-current Wed Apr 24 09:16:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA28110 for current-outgoing; Wed, 24 Apr 1996 09:16:33 -0700 (PDT) Received: from gateway.tcsi.com ([137.134.47.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA28103 for ; Wed, 24 Apr 1996 09:16:30 -0700 (PDT) Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by gateway.tcsi.com (8.7.4/8.6.10) with ESMTP id JAA16623; Wed, 24 Apr 1996 09:15:23 -0700 (PDT) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.7.4/8.6.10) with ESMTP id JAA28090; Wed, 24 Apr 1996 09:15:16 -0700 (PDT) From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id JAA27648; Wed, 24 Apr 1996 09:13:20 -0700 Message-Id: <199604241613.JAA27648@cozumel.tcs.com> Subject: Re: socks support native in freebsd? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 24 Apr 1996 09:13:20 -0700 (PDT) Cc: pst@shockwave.com, ambrisko@tcsi.com, phk@critter.tfs.com, current@FreeBSD.ORG In-Reply-To: <11174.830356304@time.cdrom.com> from "Jordan K. Hubbard" at Apr 24, 96 07:31:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: | | I rather doubt it would fit anyway - sysinstall is already pushing | the boundries of a kernel + crunched binary on a 1.2MB floppy anyway. | | > I think Doug wants a socksified sysinstall ... yuck/ouch (in that order). :-) Yep it would be nice to install through a socks firewall, but I'm not sure the effort would be worth it. I usually ftp stuff local, install through nfs and then setup Socks. So I have very little motivation for this, whereas I had strong motivation to get Socks5 going so I won't have to build socks'ified stuff and then tell my friends what a nice fire wall FreeBSD makes and lets you share one IP. However if a socks'ified sysinstall did happen I wouldn't complain, but hardly use it. Doug A. From owner-freebsd-current Wed Apr 24 09:25:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA28679 for current-outgoing; Wed, 24 Apr 1996 09:25:35 -0700 (PDT) Received: from gateway.tcsi.com ([137.134.47.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA28669 for ; Wed, 24 Apr 1996 09:25:30 -0700 (PDT) Received: from phact.tcs.com (phact.tcs.com [137.134.41.99]) by gateway.tcsi.com (8.7.4/8.6.10) with ESMTP id JAA16768; Wed, 24 Apr 1996 09:24:13 -0700 (PDT) Received: from cozumel.tcs.com (cozumel.tcs.com [137.134.104.12]) by phact.tcs.com (8.7.4/8.6.10) with ESMTP id JAA28335; Wed, 24 Apr 1996 09:24:12 -0700 (PDT) From: Douglas Ambrisko Received: (ambrisko@localhost) by cozumel.tcs.com (8.6.10/8.6.10) id JAA27673; Wed, 24 Apr 1996 09:22:17 -0700 Message-Id: <199604241622.JAA27673@cozumel.tcs.com> Subject: Re: socks support native in freebsd? To: terry@lambert.org (Terry Lambert) Date: Wed, 24 Apr 1996 09:22:16 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: <199604232018.NAA20265@phaeton.artisoft.com> from "Terry Lambert" at Apr 23, 96 01:18:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: | | > > Fine. Pick a binary program other than Netscape which does not support | > > socks. | > | > Hmm. Microsoft Explorer, perhaps. | | Yeah, that was my first pick too. Didn't want to admit it because SocksCap should solve some of these problems on the windows side. It wedges inbetween a winsocks stack and application. I've used it with WFWG and the tcp/ip stuff from Microsoft and it worked, its not totally clean but I was able to ftp/telnet out to the world. The real issue with this stuff is supporting UDP stuff like RealAudio. Doug A. From owner-freebsd-current Wed Apr 24 09:44:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA29997 for current-outgoing; Wed, 24 Apr 1996 09:44:08 -0700 (PDT) Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA29840 for ; Wed, 24 Apr 1996 09:43:29 -0700 (PDT) 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 SAA00819 ; Wed, 24 Apr 1996 18:42:03 +0200 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id SAA20444 ; Wed, 24 Apr 1996 18:42:02 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.7) id IAA19056; Wed, 24 Apr 1996 08:51:34 +0200 (MET DST) From: Ollivier Robert Message-Id: <199604240651.IAA19056@keltia.freenix.fr> Subject: Re: MotherBoard Jumper Settings... To: davidg@Root.COM Date: Wed, 24 Apr 1996 08:51:34 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) In-Reply-To: <199604240450.VAA03207@Root.COM> from David Greenman at "Apr 23, 96 09:50:47 pm" X-Operating-System: FreeBSD 2.2-CURRENT ctm#1916 X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that David Greenman said: > > Third, the Oscillator Frequency was set for 33Mhz instead > >of 25Mhz...have fixed it... > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > *possibly* have any bad effects. :-) Uh? The DX4/100 is a 33 MHz CPU with a 3x multiplier even if it is named _DX4_. Now Marc has just a DX4/100 running at 75 MHz :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #13: Sun Apr 21 18:14:54 MET DST 1996 From owner-freebsd-current Wed Apr 24 09:46:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA00287 for current-outgoing; Wed, 24 Apr 1996 09:46:30 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-189.ut.nl.ibm.net [139.92.42.189]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA00278 Wed, 24 Apr 1996 09:46:18 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.3/8.6.9) id TAA24670; Tue, 23 Apr 1996 19:07:57 +0200 (MET DST) Date: Tue, 23 Apr 1996 19:07:57 +0200 (MET DST) Message-Id: <199604231707.TAA24670@vector.jhs.no_domain> To: current@freebsd.org Cc: jkh@freebsd.org Subject: non drive zero installation From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (pending modem change) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH [version 1.6.5 95 12 11], PGP available Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A tentative suggestion: Whoever keeps a list of pre-release tests/objectives might want to add "Capability to install on drive [non zero ie sd2]." (& there again you might not, or it might be listed already, I have no time to check, but I'll forget to mention it if I don't here & now. (PS FWIW DOS-5 doesnt want to install on non sd0 either.) I mention it as I was trying to install 2.0.5 on sd2, & failed. (Tearing box apart, & adding scsi selectors to front of pc-chassis succeeded ). I know 2.1 is current release, but I've reinstalled 2.0.5 on one of my boxes to match a customer environment (my boxes are normally current-ish + 2.1). Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ (PGP available) From owner-freebsd-current Wed Apr 24 09:47:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA00395 for current-outgoing; Wed, 24 Apr 1996 09:47:57 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA00366 Wed, 24 Apr 1996 09:47:47 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id LAA19232; Wed, 24 Apr 1996 11:41:48 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB31D3.78BC7DE0@webster.unety.net>; Wed, 24 Apr 1996 11:45:01 -0500 Message-ID: <01BB31D3.78BC7DE0@webster.unety.net> From: Jim Fleming To: "'Cat Okita'" , "Rodney W. Grimes" Cc: "current@FreeBSD.org" , "davidg@Root.COM" , "hackers@FreeBSD.org" , "hasty@rah.star-gate.com" , "scrappy@ki.net" Subject: RE: Intelligent Debugging Tools... Date: Wed, 24 Apr 1996 11:45:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 9:20 AM, Cat Okita[SMTP:cat@ghost.uunet.ca] wrote: @On Wed, 24 Apr 1996, Rodney W. Grimes wrote: @or on the drive. External termination is right out in front of your eyes. @ @Being overly used to the world of unix-designed machines (ie: sun, dec...), @it was a really nasty shock to discover that PC's *normally* terminate @on the drives... @ @cheers! @cat @ @ Yes and vacuum tubes had little orange filaments that you could "see" through the glass and this told you they were working. There was a pin with filament voltage and you knew just where to wire it. Life was great. With Integrated Circuits the filament(s) are "hidden" inside. They are so tiny that you can not see them and to top that off, the designers were able to eliminate the pin. The miracles of modern science....;-) -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-current Wed Apr 24 10:09:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA01803 for current-outgoing; Wed, 24 Apr 1996 10:09:31 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA01779 Wed, 24 Apr 1996 10:09:24 -0700 (PDT) Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA28104 ; Wed, 24 Apr 1996 10:09:23 -0700 Received: from oscar.cc.gatech.edu (cau@oscar.cc.gatech.edu [130.207.107.12]) by burdell.cc.gatech.edu (8.7.5/8.6.9) with ESMTP id NAA08418; Wed, 24 Apr 1996 13:07:48 -0400 (EDT) Received: (from cau@localhost) by oscar.cc.gatech.edu (8.7.5/8.6.9) id NAA22678; Wed, 24 Apr 1996 13:07:46 -0400 (EDT) From: cau@cc.gatech.edu (Carlos Ugarte) Message-Id: <199604241707.NAA22678@oscar.cc.gatech.edu> Subject: Re: Intelligent Debugging Tools... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 24 Apr 1996 13:07:44 -0400 (EDT) Cc: scrappy@ki.net, msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: <199604240259.MAA14238@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 96 12:29:49 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You should spend some time at night with the new daemon book, which > should be out shortly - "The design and implementation of the 4.4 BSD > Unix operating system" and perhaps also "The Magic Garden explained". For those who are interested, Addison Wesley has a web page on the new book. The URL is http://heg-school.aw.com/cseng/authors/mckusick/4.4bsd/4.4bsd.html Two bookstores told me that it would take them about a month to get it, as it is so new. The cost would be comparable to that of the 4.3BSD book. It also mentions the BSD T-shirts ("old" models, and how to order the new ones) somewhere around there. I remember someone asked about this a couple of weeks back on one of the lists. Carlos -- Carlos A. Ugarte cau@cc.gatech.edu Author of PageMage, a virtual desktop util for OS/2 http://www.cc.gatech.edu/people/home/cau/ If you understand what you're doing, you are not learning anything From owner-freebsd-current Wed Apr 24 10:40:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03896 for current-outgoing; Wed, 24 Apr 1996 10:40:35 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA03889 Wed, 24 Apr 1996 10:40:33 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199604241740.KAA03889@freefall.freebsd.org> Subject: Unix Books To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 24 Apr 1996 10:40:33 -0700 (PDT) Cc: scrappy@ki.net, msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@freebsd.org, hackers@freebsd.org In-Reply-To: <199604240341.NAA14787@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 96 01:11:40 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > Marc G. Fournier stands accused of saying: > > > > > You should spend some time at night with the new daemon book, which > > > should be out shortly - "The design and implementation of the 4.4 BSD > > > Unix operating system" and perhaps also "The Magic Garden explained". > > > > > I will *definitely* look for these books... > > Check the handbook, as I think they're on the reading list. > > If not, check the -hackers archive for Terry Lambert talking about > the 'magic garden' book - his reading list was pretty comprehensive. it was the book by Uresh Vahalia "Unix Internals: The New Frontiers", ISBN 0131019082, rather than "The Magic Garden explained". look for terry's name in the acknowledgements section. -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ From owner-freebsd-current Wed Apr 24 11:56:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA10023 for current-outgoing; Wed, 24 Apr 1996 11:56:10 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA10018 for ; Wed, 24 Apr 1996 11:56:06 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id LAA05271; Wed, 24 Apr 1996 11:55:02 -0700 From: "Rodney W. Grimes" Message-Id: <199604241855.LAA05271@GndRsh.aac.dev.com> Subject: Re: make -DCLOBBER To: pat@transarc.com (Pat Barron) Date: Wed, 24 Apr 1996 11:55:02 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from Pat Barron at "Apr 24, 96 12:11:26 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Just tried this with the latest FreeBSD-current sources, and it (still) > fails (as it did last time I tried it, back in like Sept. '95, for > the same reasons....) > > This time, in libgmp, the build fails because it can't find crt0.o > or libgcc.a. > > Does no one else actually use this? ;-) Yea, but it gets broken just as fast if not faster than it gets fixed :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 12:56:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA14770 for current-outgoing; Wed, 24 Apr 1996 12:56:57 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA14754 Wed, 24 Apr 1996 12:56:53 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA19518; Thu, 25 Apr 1996 05:51:48 +1000 Date: Thu, 25 Apr 1996 05:51:48 +1000 From: Bruce Evans Message-Id: <199604241951.FAA19518@godzilla.zeta.org.au> To: fty@mcnc.org, sos@FreeBSD.org Subject: Re: minor syscons bogon Cc: current@FreeBSD.org, freebsd-current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The fix may not be correct if it does in fact break /dev/console. But >the scenario IS A BUG. The kernel should not allow an open/write to an >unconfigured device with obviously bad results. > >> if (!init_done) > >> return(NULL); > >> ! if (unit > MAXCONS || unit < 0) > >> return(NULL); > >> if (unit == MAXCONS) > >> return CONSOLE_TTY; > >> --- 305,311 ---- > >> > >> if (!init_done) > >> return(NULL); > >> ! if (unit >= MAXCONS || unit < 0) > >> return(NULL); > >> if (unit == MAXCONS) > >> return CONSOLE_TTY; Note that (unit == MAXCONS) case is handled 2 lines after the patched line, and this handling is always a no-op if the patch is applied. Thus the patch is at best incomplete. There are certainly some bugs here. If /dev/ttyvn exists for n = MAXCONS, then /dev/ttyvn is more or less an alias for /dev/console. This causes security holes if /dev/ttyvn has weaker ownership or permissions than /dev/console. Opening and closing /dev/ttyvn messes up last-close stuff for /dev/console (e.g., last-closing /dev/ttyvn nukes the console tty's pgrp and session pointers). The problem is easy to work around: don't create /dev/ttyvn for n = MAXCONS. I consider requiring this to be acceptable, although the bug is in the kernel. Root should be very careful about the ownerships, permissions and existence of all devices. There are many similar kernel bugs, because many drivers don't fully decode the minor number. E.g., the vn driver with slices disabled only decodes 5 unit bits, so there are 2^27 aliases for each device, 13 of which are created by `sh MAKEDEV vn0'. Bruce From owner-freebsd-current Wed Apr 24 13:36:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20118 for current-outgoing; Wed, 24 Apr 1996 13:36:38 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20088 for ; Wed, 24 Apr 1996 13:36:25 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id WAA14848; Wed, 24 Apr 1996 22:35:29 +0200 (SAT) Message-Id: <199604242035.WAA14848@grumble.grondar.za> To: Pat Barron cc: freebsd-current@FreeBSD.ORG Subject: Re: make -DCLOBBER Date: Wed, 24 Apr 1996 22:35:28 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Pat Barron wrote: > Just tried this with the latest FreeBSD-current sources, and it (still) > fails (as it did last time I tried it, back in like Sept. '95, for > the same reasons....) > > This time, in libgmp, the build fails because it can't find crt0.o > or libgcc.a. > > Does no one else actually use this? ;-) I have a "fix" for this that simply removes clobbering the lib directory. I will commit this in a few days. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Wed Apr 24 13:39:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20520 for current-outgoing; Wed, 24 Apr 1996 13:39:15 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20489 Wed, 24 Apr 1996 13:39:01 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA04680; Wed, 24 Apr 1996 16:38:44 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA00407; Wed, 24 Apr 1996 16:38:41 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 16:38:40 -0400 (EDT) From: "Marc G. Fournier" To: "Rodney W. Grimes" cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604240851.BAA04106@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > Why? And how many changes are there in your kernel config file with > respect to the GENERIC kernel? Did you make the fatal mistakes that > others have made and started from the LINT config file instead of the > GENERIC config? > *groan* What's wrong with using the LINT config file and trimming it down to what you want? Here's my config file (pt0/sctarg0) removed...in case there is something else i shouldn't have configured in? :( ---- machine "i386" cpu "I486_CPU" ident kinet # # The `maxusers' parameter controls the static sizing of a number of # internal system tables by a complicated formula defined in param.c. # maxusers 32 # # Under some circumstances it is necessary to make the default max # number of processes per user and open files per user more than the # defaults on bootup. (an example is a large news server in which # the uid, news, can sometimes need > 100 simultaneous processes running, # or perhaps a user using lots of windows under X). options "CHILD_MAX=128" options "OPEN_MAX=128" config kernel root on sd0 options "COMPAT_43" options SYSVSHM options "SHMMAXPGS=512" # 2048Kb (?) of sharable memory options SYSVSEM options SYSVMSG options DDB options DODUMP options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device tun 1 #Tunnel driver(user process ppp) # One of these is mandatory: options FFS #Fast filesystem options NFS #Network File System options PROCFS #Process filesystem options QUOTA #enable disk quotas controller scbus0 #base SCSI code device sd0 #SCSI disks pseudo-device pty 64 #Pseudo ttys - can go as high as 64 pseudo-device log #Kernel syslog interface (/dev/klog) controller isa0 options BOUNCE_BUFFERS # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options "PCVT_FREEBSD=210" # pcvt running on FreeBSD 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor device npx0 at isa? port "IO_NPX" irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr controller pci0 device ncr0 Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 13:39:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA20594 for current-outgoing; Wed, 24 Apr 1996 13:39:47 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA20589 Wed, 24 Apr 1996 13:39:43 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA04767; Wed, 24 Apr 1996 16:39:45 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA00414; Wed, 24 Apr 1996 16:39:44 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 16:39:43 -0400 (EDT) From: "Marc G. Fournier" To: Cat Okita cc: "Rodney W. Grimes" , davidg@Root.COM, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Cat Okita wrote: > Being overly used to the world of unix-designed machines (ie: sun, dec...), > it was a really nasty shock to discover that PC's *normally* terminate > on the drives... > What? Sun/Dec don't use the same SCSI drives? Weird... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 13:42:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21242 for current-outgoing; Wed, 24 Apr 1996 13:42:38 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21220 Wed, 24 Apr 1996 13:42:32 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA05007; Wed, 24 Apr 1996 16:42:28 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA00427; Wed, 24 Apr 1996 16:42:27 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 16:42:26 -0400 (EDT) From: "Marc G. Fournier" To: "Jordan K. Hubbard" cc: davidg@Root.COM, "Justin T. Gibbs" , current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <11281.830357319@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Jordan K. Hubbard wrote: > This was one of the few things that was correct - he still had his > cache set wrong and a jumper mis-set. > > And actually, I would also run this at 75Mhz until I was sure of the > chip - my friend Chuck got a "DX4/100" recently which didn't behave at > all well with FreeBSD; same symptoms as Marc's. Then we clocked it to > 75Mhz and it worked (and has continued to work) smoothly. We looked > at the chip again more closely (we had to peel the stupid sticker off > of it first before we could read the numbers) and found that he'd been > sold a DX4/75 as a DX4/100. A lot of this kinda thing going around. > No, I'm definitely certain its a DX4/100 *groan* I took the fan off, and DX4/100 is what is stamped on the chip, no sticker over top of it :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 13:42:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21271 for current-outgoing; Wed, 24 Apr 1996 13:42:42 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21208 for ; Wed, 24 Apr 1996 13:42:28 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA05000; Wed, 24 Apr 1996 16:42:25 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id OAA07252; Wed, 24 Apr 1996 14:42:11 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 14:42:11 -0400 (EDT) From: "Marc G. Fournier" To: "Jordan K. Hubbard" cc: current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <11236.830356828@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Jordan K. Hubbard wrote: > > So, I've fixed those...could *any* of those above have > > produced the problems I've been seeing? Or are they minor? > > Sorry, I'm still picking my jaw up off the floor! > > I wish you'd taken a picture of your configuration before you fixed > what has to be the most amazing stack of bogons in one machine I've > ever seen - I'd stick it up on the web pages as "this month's poster > child for how to configure your hardware completely and totally > incorrectly." > Hey...no, I can't blame the person that sold it to me, I should have checked over the configuration myself when I received it *hang head* *sigh* > If your machine runs correctly after this, you owe lots of people > lots of beer! :-) > Ya, that I do...but, I did cause it to panic after changing this, see my posting to stable? :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 13:46:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA22000 for current-outgoing; Wed, 24 Apr 1996 13:46:10 -0700 (PDT) Received: from ghost.uunet.ca (ghost.uunet.ca [142.77.1.100]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21963 Wed, 24 Apr 1996 13:45:59 -0700 (PDT) Received: by ghost.uunet.ca id <52832-26041>; Wed, 24 Apr 1996 16:45:52 -0400 Date: Wed, 24 Apr 1996 16:45:48 -0400 From: Cat Okita To: "Marc G. Fournier" cc: "Rodney W. Grimes" , davidg@Root.COM, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Marc G. Fournier wrote: > What? Sun/Dec don't use the same SCSI drives? Weird... I think that you must have missed the start of this thread. The question wasn't if drives *could* be terminated on the drive, but rather whether it was a better option to terminate *internally* or *externally*. Typically, the drives which I've used in Sun/Dec machines don't arrive with termination set on the drive - it's set externally. In the PC world, drives usually arrive with termination set on the drive, which becomes an awkward and annoying problem when you start adding SCSI devices. If this still isn't clear, drop me a line in private email - no need to try the list with definitions of internal/external... Cat From owner-freebsd-current Wed Apr 24 13:52:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA23121 for current-outgoing; Wed, 24 Apr 1996 13:52:42 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA23105 for ; Wed, 24 Apr 1996 13:52:37 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with SMTP id VAA03753 ; Wed, 24 Apr 1996 21:09:53 +0100 (BST) To: Sujal Patel cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: request for a new "feature" as regards DDB In-reply-to: Your message of "Mon, 22 Apr 1996 18:02:56 EDT." Date: Wed, 24 Apr 1996 21:09:53 +0100 Message-ID: <3751.830376593@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sujal Patel wrote in message ID : > While we're talking about DDB, can't we have it timeout in 30s if you > don't hit a key (and then generate a core dump). Not really ... that would assume that the IRQ handlers were still operational, which may not be the case. DDB should only be running if all interrupts are disabled if I remember right (and if I don't, I won't mind being corrected :-) ) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD - Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info. From owner-freebsd-current Wed Apr 24 14:09:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25252 for current-outgoing; Wed, 24 Apr 1996 14:09:53 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA25244 for ; Wed, 24 Apr 1996 14:09:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id PAA15418; Wed, 24 Apr 1996 15:09:19 -0600 (MDT) Message-Id: <199604242109.PAA15418@rover.village.org> To: Poul-Henning Kamp Subject: Re: SLIP: Check IP Version (please test) Cc: Paul Traina , current@FreeBSD.ORG, Jim Fleming In-reply-to: Your message of Wed, 24 Apr 1996 06:35:29 -0000 Date: Wed, 24 Apr 1996 15:09:18 -0600 From: Warner Losh Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk : I agree, the point is that people play with IPv8 and it breaks slip. There is no IPv8 that the IETF has defined. Others may have co-opted that name. There is no reason to wrorry about it. IPv6, on the other hand, is being actively defined.... That said, will the extra two instructions really cause people grief? Warner From owner-freebsd-current Wed Apr 24 14:16:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA25906 for current-outgoing; Wed, 24 Apr 1996 14:16:18 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA25882 Wed, 24 Apr 1996 14:16:05 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id XAA26948; Wed, 24 Apr 1996 23:16:16 +0200 Received: by uni4nn.iaf.nl with UUCP id AA29128 (5.67b/IDA-1.5); Wed, 24 Apr 1996 23:15:51 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA27881 (5.67b/IDA-1.5); Wed, 24 Apr 1996 23:01:32 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id UAA00617; Wed, 24 Apr 1996 20:15:57 +0200 From: Wilko Bulte Message-Id: <199604241815.UAA00617@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 20:15:57 +0200 (MET DST) Cc: hasty@rah.star-gate.com, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 23, 96 06:00:06 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > real memory = 16777216 (16384K bytes) > avail memory = 14835712 (14488K bytes) > Probing for devices on PCI bus 0: > chip0 rev 49 on pci0:5 > ncr0 rev 2 int a irq 12 on pci0:11 > (ncr0:0:0): "QUANTUM FIREBALL1280S 630C" type 0 fixed SCSI 2 It might also be interesting to disable tagged command queuing on the ncr. Something like '/usr/sbin/ncrcontrol -s tags=0' does this. I had mysterious lockups on my system (not even the mouse cursor or keyboard would do anything) and this TCQ disable made this go away (thanks Stefan for the suggestion). Admittedly it is not a panic but maybe it makes a difference (BTW I flashed new firmware on my drive and now TCQ enabled also works) Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-current Wed Apr 24 14:42:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28636 for current-outgoing; Wed, 24 Apr 1996 14:42:49 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA28581 Wed, 24 Apr 1996 14:42:28 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA05847; Wed, 24 Apr 1996 14:41:00 -0700 From: "Rodney W. Grimes" Message-Id: <199604242141.OAA05847@GndRsh.aac.dev.com> Subject: Re: Intelligent Debugging Tools... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 14:40:59 -0700 (PDT) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Marc G. Fournier" at "Apr 24, 96 04:38:40 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > > Why? And how many changes are there in your kernel config file with > > respect to the GENERIC kernel? Did you make the fatal mistakes that > > others have made and started from the LINT config file instead of the > > GENERIC config? > > > *groan* What's wrong with using the LINT config file and > trimming it down to what you want? Many people don't trim it down enough and end up with strange problems, looks as if you did a good trim job though I really doubt your need for *_MAX=128 and SHMMAXPGS=512. I also thought you had an NCR scsi controller, which means you don't need BOUNCE_BUFFERS. > Here's my config file (pt0/sctarg0) removed...in case there > is something else i shouldn't have configured in? :( ... > # Under some circumstances it is necessary to make the default max > # number of processes per user and open files per user more than the > # defaults on bootup. (an example is a large news server in which > # the uid, news, can sometimes need > 100 simultaneous processes running, > # or perhaps a user using lots of windows under X). > options "CHILD_MAX=128" > options "OPEN_MAX=128" Do you _really_ need these? > config kernel root on sd0 > > options "COMPAT_43" > options SYSVSHM > options "SHMMAXPGS=512" # 2048Kb (?) of sharable memory The default is 1024, you trimming this on purpose? ... > options QUOTA #enable disk quotas Unless you are really using QUOTA's remove it. > > options BOUNCE_BUFFERS Hummmm PCI machine with NCR scsi controller, nope you do not need this, remove it! ... > controller pci0 > device ncr0 -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Apr 24 14:57:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA00527 for current-outgoing; Wed, 24 Apr 1996 14:57:52 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA00516 Wed, 24 Apr 1996 14:57:49 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id RAA01557; Wed, 24 Apr 1996 17:57:47 -0400 (EDT) Date: Wed, 24 Apr 1996 17:57:47 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: Gary Palmer cc: current@FreeBSD.ORG Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <3751.830376593@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Gary Palmer wrote: > > While we're talking about DDB, can't we have it timeout in 30s if you > > don't hit a key (and then generate a core dump). > > Not really ... that would assume that the IRQ handlers were still > operational, which may not be the case. DDB should only be running if > all interrupts are disabled if I remember right (and if I don't, I > won't mind being corrected :-) ) Can we sit in a loop, while polling the keyboard for input? Sujal From owner-freebsd-current Wed Apr 24 15:25:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA03979 for current-outgoing; Wed, 24 Apr 1996 15:25:11 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA03963 Wed, 24 Apr 1996 15:25:06 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA04205; Wed, 24 Apr 1996 18:24:52 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA01890; Wed, 24 Apr 1996 18:24:54 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 18:24:54 -0400 (EDT) From: "Marc G. Fournier" To: "Rodney W. Grimes" cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Intelligent Debugging Tools... In-Reply-To: <199604242141.OAA05847@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > Many people don't trim it down enough and end up with strange problems, > looks as if you did a good trim job though I really doubt your need > for *_MAX=128 and SHMMAXPGS=512. > The *_MAX are for my INND/Web servers...and the SHMMAXPGS is so that I can put in shared memory support in INND (one of these days *sigh*) > I also thought you had an NCR scsi controller, which means you don't > need BOUNCE_BUFFERS. > I had this in because of using an AHA controller in that machine, which I've put in intermediantly, but will take it out... > > options "COMPAT_43" > > options SYSVSHM > > options "SHMMAXPGS=512" # 2048Kb (?) of sharable memory > > The default is 1024, you trimming this on purpose? > Oh...that I *didn't* know :( Will remove this one too... > ... > > options QUOTA #enable disk quotas > > Unless you are really using QUOTA's remove it. > Am using it. Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 15:40:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA05794 for current-outgoing; Wed, 24 Apr 1996 15:40:10 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA05694 for ; Wed, 24 Apr 1996 15:40:02 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23212; Wed, 24 Apr 1996 15:34:07 -0700 From: Terry Lambert Message-Id: <199604242234.PAA23212@phaeton.artisoft.com> Subject: Re: MotherBoard Jumper Settings... To: count@key.hole.fi (Bror 'Count' Heinola) Date: Wed, 24 Apr 1996 15:34:07 -0700 (MST) Cc: davidg@Root.COM, current@FreeBSD.ORG In-Reply-To: <199604240642.JAA02764@key.hole.fi> from "Bror 'Count' Heinola" at Apr 24, 96 09:42:01 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > AFAIK, DX/4-100 CPU's run only at 3x33MHz _or_ 2x50MHz mode > which should be jumper selectable on the motherboard. At least > all motherboards (and CPU's, two AMD's and one Intel) have > worked like that. I haven't seen a 2x50... I would like to. I have a motherboard with a 50 (not clock doubled) with a 50Mhz memory bus, which I intentionally hot-purchased over spec hardware for to run the EISA bus at 50MHz. It has been working fine for about 3 years now; I'd consider DX2/100 as an upgrade... the DX4/100's run the memory and bus too damn slow for me; IMO, L2 cache is near-worthless on anything with a clock tripler (or worse!) for external bus access. 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 Apr 24 15:53:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA06923 for current-outgoing; Wed, 24 Apr 1996 15:53:59 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA06914 for ; Wed, 24 Apr 1996 15:53:54 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA06605; Wed, 24 Apr 1996 18:53:50 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA02014; Wed, 24 Apr 1996 18:53:51 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 18:53:50 -0400 (EDT) From: "Marc G. Fournier" To: David Greenman cc: current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <199604240450.VAA03207@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Apr 1996, David Greenman wrote: > > Third, the Oscillator Frequency was set for 33Mhz instead > >of 25Mhz...have fixed it... > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > *possibly* have any bad effects. :-) > Guess I won't feel *too* bad about being razed for thinking a DX4 == 4xOscillator, eh? :-) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 15:57:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA07202 for current-outgoing; Wed, 24 Apr 1996 15:57:42 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA07195 for ; Wed, 24 Apr 1996 15:57:37 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA06665; Wed, 24 Apr 1996 18:57:37 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA02025; Wed, 24 Apr 1996 18:57:40 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 18:57:39 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: current@FreeBSD.org, cat@ki.net, geoff@ki.net Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <199604240618.PAA16813@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > First off, my CPU is an Intel DX4-100 w Write/Thru. CMOS > > was set for Write/Back...have changed it to Write/Thru... > > Ouch. Make sure there were no jumpers relevant to that as well. > None that I've been able to find, seems to be purely a CMOS setting... > > Second of all, one of the jumper that was supposed to be > > set, wasn't...have set it... > > Also bad. > Yup :( > > Third, the Oscillator Frequency was set for 33Mhz instead > > of 25Mhz...have fixed it... > > Wrong. "DX4" is marketting crap. They're really DX3's, so 33 is correct. > Reverted back again... > > If so, and I haven't changed that one yet, my CMOS is set for 20ns... > > would that produce any of the bugs I've been reporting? > > No. If the BIOS supports 15ns cycle cache memory then you may be > able to improve your performance by frobbing that. > So I should pop this up to 15ns? > Convention in naming memory parts is to put the size in Kbits in the part > number; 61512 implies 512kbits or 64kx8 or 128kx4. (I would expect the > latter). The setting you have now implies 8 cache parts, not 4. > If there's a 256kB/128kbx4 setting, try that. > The highest I have is 128Kb x 8 x 4pcs, so will try that out... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 15:59:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA07243 for current-outgoing; Wed, 24 Apr 1996 15:59:04 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA07238 for ; Wed, 24 Apr 1996 15:59:02 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id SAA06693; Wed, 24 Apr 1996 18:59:06 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA02033; Wed, 24 Apr 1996 18:59:09 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 18:59:09 -0400 (EDT) From: "Marc G. Fournier" To: "Rodney W. Grimes" cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org, cat@ki.net, geoff@ki.net Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <199604240912.CAA04144@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > > The jumpers for the cache are set for 256KB/64kbx4...how do I > > > determine the size of each of the cache chips to determine if *this* is > > > right? > > > > The 61512 suggests a 512 Kbit cache. Seems you are using only half of > > it with your jumper setting. > > The 61512 is infact a 64k x 8 part, I looked it up as there had been > too much speculation on here about just what that chip was. Cache RAM > on 486 and later machines is almost always x 8 parts for those who thought > this might have been a 128k x 4. > > Your cache jumper settings are correct at 256K/64Kx8. You may still have > a bad cache RAM though. Do you ever get any signal 10's or 11's from the > gcc compiler, or do you just get panics? > Forget my last to Michael then...I won't change this :) But since you did look it up...20 or 15ns? :) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 18:34:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA26659 for current-outgoing; Wed, 24 Apr 1996 18:34:20 -0700 (PDT) Received: from doorstep.unety.net (root@usi-00-10.Naperville.unety.net [204.70.107.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA26631 Wed, 24 Apr 1996 18:34:14 -0700 (PDT) Received: from webster.unety.net (webster.unety.net [206.31.202.8]) by doorstep.unety.net (8.6.9/8.6.9) with SMTP id UAA19973; Wed, 24 Apr 1996 20:28:08 -0500 Received: by webster.unety.net with Microsoft Mail id <01BB321C.FFDBF960@webster.unety.net>; Wed, 24 Apr 1996 20:31:21 -0500 Message-ID: <01BB321C.FFDBF960@webster.unety.net> From: Jim Fleming To: "'Warner Losh'" , Poul-Henning Kamp Cc: "'chat@FreeBSD.org'" , "current@FreeBSD.ORG" , Paul Traina Subject: RE: SLIP: Check IP Version (please test) Date: Wed, 24 Apr 1996 20:31:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wednesday, April 24, 1996 4:09 PM, Warner Losh[SMTP:imp@village.org] wrote: @: I agree, the point is that people play with IPv8 and it breaks slip. @ @There is no IPv8 that the IETF has defined. Others may have co-opted @that name. There is no reason to wrorry about it. IPv6, on the other @hand, is being actively defined.... @ @That said, will the extra two instructions really cause people grief? @ @Warner @ @ The IETF has their hands full trying to make the IPv4 system work... and thinking about the wonderful time they are going to have with IPv6...;-) People that want to have some fun with IPv8 and want to help build an OuterInternet using the existing Internet for core transport are welcome to help weave IPv8 into FreeBSD and other platforms. Some people look forward to the day when they can move beyond the Legacy Internet which is developing problems faster than they can be fixed. This is similar to the flight from large cities to the suburbs as a way to avoid problems and congestion. IPv8 provides room to grow without the massive engineering effort required for IPv6. The IPv8 approach creates 2,048 address spaces similar to the current IPv4 space. The challenge now is to link those address spaces using FreeBSD, host-based routers. In many respects it is like creating airplanes as a replacement for the railroads. The IPv8 pilots will not be restricted to flying only over railroad tracks. Instead, IPv8 will carve its own direction using FreeBSD as a base upon which to build. Everyone that has contributed to FreeBSD and who continues to contribute to FreeBSD should be proud of the work they have done. In over 20 years of hacking UNIX kernels, I have not seen a better version of UNIX and a better group of software engineers. I look forward to "meshing with your bits"....:-) -- Jim Fleming UNETY Systems, Inc. Naperville, IL 60563 e-mail: JimFleming@unety.net From owner-freebsd-current Wed Apr 24 20:00:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA06781 for current-outgoing; Wed, 24 Apr 1996 20:00:27 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA06768 Wed, 24 Apr 1996 20:00:13 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA01585; Thu, 25 Apr 1996 12:39:50 +1000 Date: Thu, 25 Apr 1996 12:39:50 +1000 From: Bruce Evans Message-Id: <199604250239.MAA01585@godzilla.zeta.org.au> To: gpalmer@freebsd.org, smpatel@umiacs.umd.edu Subject: Re: request for a new "feature" as regards DDB Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > While we're talking about DDB, can't we have it timeout in 30s if you >> > don't hit a key (and then generate a core dump). >> >> Not really ... that would assume that the IRQ handlers were still >> operational, which may not be the case. DDB should only be running if >> all interrupts are disabled if I remember right (and if I don't, I >> won't mind being corrected :-) ) Here are some corrections :-). 1. ddb should run with all interrupts enabled. It should also normally keep interrupts disabled while tracing. Otherwise the system state may change while you're looking at it. 2. ddb actually doesn't disable interrupts. It even enables them if they were only disabled in the cpu. Thus breakpoints sections protected by `enable_intr(); ... disable_intr();' or early in Xintr*(), or in fastintr handlers don't work right. spl masking works better. Normally ddb spends most of it's time sitting in the console input routine at spltty() or higher. Other interrupts are masked iff they are masked when ddb is entered. tty interrupts aren't masked throughout unless they are masked when ddb is entered. Clock interrupts usually aren't masked when ddb is entered, so the clocks usually keep ticking away. 3. timeout() is unsuitable for use ddb. First, clk0 interrupts might be masked when ddb is entered. Then ddb can't unmask them, so the clk0 won't work. Second, ddb shouldn't depend on the timeout() code to work. >Can we sit in a loop, while polling the keyboard for input? Yes, you can usefully poll the clock(s) while polling the keyboard, provided: a. polling is non-destructive. This makes it difficult to use timer0, timer1 and the RTC. Perhaps they can be read without (destructively) latching the count. Even that steals some state if a non-debugging part of the system has just latched the count. timer2 is probably safe to use, because non-debugging parts of the system never access it. b. the clock hasn't stopped. Bruce From owner-freebsd-current Wed Apr 24 20:15:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA07755 for current-outgoing; Wed, 24 Apr 1996 20:15:10 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA07746 for ; Wed, 24 Apr 1996 20:15:02 -0700 (PDT) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <17517-0@bunyip.cc.uq.oz.au>; Thu, 25 Apr 1996 13:14:43 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id NAA13273 for ; Thu, 25 Apr 1996 13:15:09 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id DAA03156 for ; Thu, 25 Apr 1996 03:18:50 GMT Message-Id: <199604250318.DAA03156@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: current@freebsd.org Subject: Bug in if_sl.c X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Apr 1996 13:18:49 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk BPRO -DBROKEN_BUS_CLOCK -DFDSEEKWAIT=16 -DHARDFONTS -DSCSIDEBUG -DMFS -DFFS -DTC P_COMPAT_42 -DINET -DCOMPAT_43 -DDEVFS -DKERNEL ../../net/if_sl.c ../../net/if_sl.c: In function `slstart': ../../net/if_sl.c:565: parse error before `(' ../../net/if_sl.c:564: warning: empty body in an if-statement ../../net/if_sl.c:565: parse error before `)' ../../net/if_sl.c:595: continue statement not within a loop ../../net/if_sl.c:675: warning: control reaches end of non-void function ../../net/if_sl.c: At top level: ../../net/if_sl.c:676: parse error before `return' *** Error code 1 Stop. *Mumble*! Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Wed Apr 24 20:24:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08317 for current-outgoing; Wed, 24 Apr 1996 20:24:00 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA08310 for ; Wed, 24 Apr 1996 20:23:54 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA22258; Thu, 25 Apr 1996 12:48:45 +0930 From: Michael Smith Message-Id: <199604250318.MAA22258@genesis.atrad.adelaide.edu.au> Subject: Re: MotherBoard Jumper Settings... To: scrappy@ki.net (Marc G. Fournier) Date: Thu, 25 Apr 1996 12:48:44 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@FreeBSD.org, cat@ki.net, geoff@ki.net In-Reply-To: from "Marc G. Fournier" at Apr 24, 96 06:57:39 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > > No. If the BIOS supports 15ns cycle cache memory then you may be > > able to improve your performance by frobbing that. > > > So I should pop this up to 15ns? Not yet. Be conservative until it works. Then get silly. > > Convention in naming memory parts is to put the size in Kbits in the part > > number; 61512 implies 512kbits or 64kx8 or 128kx4. (I would expect the > > latter). The setting you have now implies 8 cache parts, not 4. > > If there's a 256kB/128kbx4 setting, try that. > > > The highest I have is 128Kb x 8 x 4pcs, so will try that out... Hmm. From Rod's data I would say you have 64x8x4pcs. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Apr 24 20:25:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08557 for current-outgoing; Wed, 24 Apr 1996 20:25:52 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA08547 for ; Wed, 24 Apr 1996 20:25:48 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id XAA04194; Wed, 24 Apr 1996 23:25:48 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id SAA02053; Wed, 24 Apr 1996 18:59:57 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 18:59:56 -0400 (EDT) From: "Marc G. Fournier" To: "Jordan K. Hubbard" cc: davidg@Root.COM, current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <11246.830357001@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Jordan K. Hubbard wrote: > > > Third, the Oscillator Frequency was set for 33Mhz instead > > >of 25Mhz...have fixed it... > > > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > > *possibly* have any bad effects. :-) > > If I wasn't such a nice guy (ha!) I'd add a "Hall of Shame" to our web > pages and stick this entry in there as a warning to others who would > first blame the software before performing even the most elementary > checks to see if their hardware was even configured correctly! :-) > *bows head in shame* I don't think a public display of shame is required...honest :) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 20:39:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA09421 for current-outgoing; Wed, 24 Apr 1996 20:39:15 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA09415 Wed, 24 Apr 1996 20:39:10 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id XAA04108; Wed, 24 Apr 1996 23:38:20 -0400 (EDT) Date: Wed, 24 Apr 1996 23:38:20 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: Bruce Evans cc: gpalmer@freebsd.org, current@freebsd.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604250239.MAA01585@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Bruce Evans wrote: [ In reference to implementing a timeout in DDB to dump core and reboot] > >Can we sit in a loop, while polling the keyboard for input? > > Yes, you can usefully poll the clock(s) while polling the keyboard, > provided: > > a. polling is non-destructive. This makes it difficult to use timer0, > timer1 and the RTC. Perhaps they can be read without (destructively) > latching the count. Even that steals some state if a non-debugging If using the timers is difficult, you could record (on boot up) the approximate time that an inb() takes and use that figure to "approximate" the amount of time we should wait for keyboard input. It doesn't have to be exactly the same for each system, just a "good amount" of time. Sujal From owner-freebsd-current Wed Apr 24 20:56:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA10367 for current-outgoing; Wed, 24 Apr 1996 20:56:58 -0700 (PDT) Received: from io.org (io.org [198.133.36.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA10349 for ; Wed, 24 Apr 1996 20:56:45 -0700 (PDT) Received: from pgeoffred (professor.net5a.io.org [199.166.190.38]) by io.org (8.6.12/8.6.12) with SMTP id XAA10894; Wed, 24 Apr 1996 23:53:56 -0400 Message-ID: <317EF7FE.1A1A@sales.org> Date: Wed, 24 Apr 1996 23:56:46 -0400 From: Geoff Davidson Organization: sales.org Sales, Marketing & Training Effectiveness X-Mailer: Mozilla 2.01 (Win95; I) MIME-Version: 1.0 To: "Marc G. Fournier" CC: "Jordan K. Hubbard" , davidg@Root.COM, current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier wrote: > > On Wed, 24 Apr 1996, Jordan K. Hubbard wrote: > > > > > Third, the Oscillator Frequency was set for 33Mhz instead > > > >of 25Mhz...have fixed it... > > > > > > Ugh! ...so your 486/100 was running at 133Mhz. Nah, that couldn't > > > *possibly* have any bad effects. :-) > > > > If I wasn't such a nice guy (ha!) I'd add a "Hall of Shame" to our web > > pages and stick this entry in there as a warning to others who would > > first blame the software before performing even the most elementary > > checks to see if their hardware was even configured correctly! :-) > > > *bows head in shame* I don't think a public display of shame > is required...honest :) > > Marc G. Fournier scrappy@ki.net > Systems Administrator @ ki.net scrappy@freebsd.org It is said, with some truth to its latin (or is that Greek) roots, that humility comes from humiliation. I have found over the years that it is unwise to publicly point out the foibles of others, as no matter how foolish their actions may be, I am capable of even more embarrassing misadventures. And, on that thought and note, here is a quote to find refuge behind: "An expert is a man who has made all the mistakes which can be made in a very narrow field" Niels Bohr. Best regards, Geoff -- How do you score as a smart consumer or salesperson? Try one of the Quizes located at: "http://www.sales.org" Email: or Geoff Davidson Personal HomePage: "http://ki.net/~geoff" From owner-freebsd-current Wed Apr 24 22:03:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA15445 for current-outgoing; Wed, 24 Apr 1996 22:03:53 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA15440 for ; Wed, 24 Apr 1996 22:03:50 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id BAA02756; Thu, 25 Apr 1996 01:03:39 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id BAA01535; Thu, 25 Apr 1996 01:03:37 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Thu, 25 Apr 1996 01:03:36 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: current@FreeBSD.org, cat@ki.net, geoff@ki.net Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <199604250318.MAA22258@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > > > No. If the BIOS supports 15ns cycle cache memory then you may be > > > able to improve your performance by frobbing that. > > > > > So I should pop this up to 15ns? > > Not yet. Be conservative until it works. Then get silly. > Just fixed a Majordomo problem, and don't want to try and panic the machine without me sitting in front of it to watch it do it, so... Tomorrow, I try see how many re-makes of /usr/src/gnu I can do before it panics *muhahaha* > Hmm. From Rod's data I would say you have 64x8x4pcs. > Yup, so if I haven't missed anything *duck and wait for tomatoes*... the motherboard *should* be setup correctly now *sigh*...*cross fingers* Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Wed Apr 24 23:41:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA20029 for current-outgoing; Wed, 24 Apr 1996 23:41:43 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA20016 for ; Wed, 24 Apr 1996 23:41:38 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA12741 (5.67a/IDA-1.5 for ); Thu, 25 Apr 1996 09:41:33 +0300 Received: (from count@localhost) by key.hole.fi (8.7.4/8.6.12) id JAA04622; Thu, 25 Apr 1996 09:41:33 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199604250641.JAA04622@key.hole.fi> Subject: Re: MotherBoard Jumper Settings... To: terry@lambert.org (Terry Lambert) Date: Thu, 25 Apr 1996 09:41:32 +0300 (EET DST) Cc: davidg@root.com, current@freebsd.org In-Reply-To: <199604242234.PAA23212@phaeton.artisoft.com> from "Terry Lambert" at Apr 24, 96 03:34:07 pm X-Mailer: ELM [version 2.4 PL24alpha5] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert taisi sanoa: > > AFAIK, DX/4-100 CPU's run only at 3x33MHz _or_ 2x50MHz mode > > which should be jumper selectable on the motherboard. At least > > all motherboards (and CPU's, two AMD's and one Intel) have=20 > > worked like that.=20 >=20 > I haven't seen a 2x50... I would like to. >=20 > I have a motherboard with a 50 (not clock doubled) with a 50Mhz > memory bus, which I intentionally hot-purchased over spec hardware > for to run the EISA bus at 50MHz. I don't remember the exact part #'s offhand, but Intel Overdrive chips come with two flavours, one with 'R' and one without. The 'R' version can't be run clock-doubled. AMD DX4/100's all run in 'DX2' or clock-doubled modes. You need to patch your motherboard a bit if you don't have a clock multiplier jumper. The 'patch'=20 involved grounding a certain pin on your CPU.=20 I saw the instructions on how to do that in UseNet group comp.sys.ibm.pc.hardware.chips about 9-10 months ago. I've saved one article from that thread, I hope it helps. -- begin included message -- >From: camps@news.eb.ele.tue.nl (Johan Camps) >Newsgroups: comp.sys.ibm.pc.hardware.chips >Subject: AMD DX4: New version !! >Date: 6 Jul 1995 10:17:17 GMT >Organization: Eindhoven University of Technology, Digital Information >Systems Group >Lines: 59 >Message-ID: <3tgd7d$m4v@tuegate.tue.nl> >NNTP-Posting-Host: green.eb.ele.tue.nl >Summary: AMD DX4 exists in two versions >X-Newsreader: TIN =C4version 1.2 PL2=C5 After having several problems with two different computers, both using an AMD DX4 100, I wrote AMD techsupport. The answer I got was quite shocking: AMD has renewed their DX4's, to make them fully Intel compatible. The compete answer was as follows: ----------------------------------------------------------------------- Dear Camps, Thank you for your email. The earliest version of the AM DX4-100 is not totally compatible with the intel processor and the differences are : >One pin difference, Pin B13, which support the clock multiplier and should be left floating to triple the clock or connected to ground to allow a doubling clock mode. >it has no power management (SMM) >its cache type is only write through type with 8K However, the latest version of the AM DX4-100 and DX4-120 which is reffered to as the enhanced parts, is 100% compatible to intel and incorporates the power management as well as the write back with no pin difference to intel processor. This new enhanced version is out in the market at the start of this month. The part number for the enhanced part is: A80486DX4-100SV8B S : Parts with SMM V : 3.45V+/-0.15V 8 : 8K cache B : write back cache type If you require further assistance, please forward your enquiry by fax or email and we will deal with it as soon as possible. Best regards, Mohamed Bara =20 --=20 Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Pengerkatu 13b A5 % IRC: Count NIC: BH271 %=20 FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Thu Apr 25 00:04:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA21262 for current-outgoing; Thu, 25 Apr 1996 00:04:16 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA21251 for ; Thu, 25 Apr 1996 00:04:12 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id XAA07120; Wed, 24 Apr 1996 23:56:27 -0700 From: "Rodney W. Grimes" Message-Id: <199604250656.XAA07120@GndRsh.aac.dev.com> Subject: Re: MotherBoard Jumper Settings... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 23:56:26 -0700 (PDT) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org, cat@ki.net, geoff@ki.net In-Reply-To: from "Marc G. Fournier" at "Apr 24, 96 06:59:09 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 24 Apr 1996, Rodney W. Grimes wrote: > > > > > The jumpers for the cache are set for 256KB/64kbx4...how do I > > > > determine the size of each of the cache chips to determine if *this* is > > > > right? > > > > > > The 61512 suggests a 512 Kbit cache. Seems you are using only half of > > > it with your jumper setting. > > > > The 61512 is infact a 64k x 8 part, I looked it up as there had been > > too much speculation on here about just what that chip was. Cache RAM > > on 486 and later machines is almost always x 8 parts for those who thought > > this might have been a 128k x 4. > > > > Your cache jumper settings are correct at 256K/64Kx8. You may still have > > a bad cache RAM though. Do you ever get any signal 10's or 11's from the > > gcc compiler, or do you just get panics? > > > Forget my last to Michael then...I won't change this :) > > But since you did look it up...20 or 15ns? :) That was the number after the dash as in 61512-15 would be a 15ns Part. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Thu Apr 25 00:24:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA22257 for current-outgoing; Thu, 25 Apr 1996 00:24:08 -0700 (PDT) Received: from lassie.eunet.fi (lassie.eunet.fi [192.26.119.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA22252 for ; Thu, 25 Apr 1996 00:24:05 -0700 (PDT) Received: from key.hole.fi by lassie.eunet.fi with SMTP id AA20459 (5.67a/IDA-1.5 for ); Wed, 24 Apr 1996 21:22:25 +0300 Received: (from count@localhost) by key.hole.fi (8.7.4/8.6.12) id VAA03459; Wed, 24 Apr 1996 21:22:24 +0300 (EET DST) From: "Bror 'Count' Heinola" Message-Id: <199604241822.VAA03459@key.hole.fi> Subject: Re: MotherBoard Jumper Settings... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 24 Apr 1996 21:22:18 +0300 (EET DST) Cc: current@freebsd.org In-Reply-To: <11318.830357714@time.cdrom.com> from "Jordan K. Hubbard" at Apr 24, 96 07:55:14 am X-Mailer: ELM [version 2.4 PL24alpha5] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard taisi sanoa: > > AFAIK, DX/4-100 CPU's run only at 3x33MHz _or_ 2x50MHz mode > > which should be jumper selectable on the motherboard. At least > > all motherboards (and CPU's, two AMD's and one Intel) have > > worked like that. > What's the memory clock on these beasts - 60Mhz? I've never owned a > DX4/100 and don't ever really plan to, I'm just wondering if the > motherboards require 60ns memory or will live happily with the 70ns > stuff. DX4/100 = 33MHz external or 50MHz external (clock tripled or clock doubled mode), DX4/120 = 40MHz external (clock tripled) 5x86-P75-S = 33MHz external (clock quadrupled) and it can be run as 4x40MHz too as I'm doing. There's supposed to be a real 160MHz part in existence but I haven't seen any on sale - not that I've looked very hard. > P.S. The Pentiums are cheap enough now that I just can't see investing > in 486 technology unless it's for a router or something. It's not the CPU, it's the RAM. If you plan to get 16M RAM for starters, one 16M 72-pin SIMM costs less than two 8M parts. And you can also drop those new 486-compatible chips on your old motherboard so you don't really have to buy nothing else than the new CPU. Though I haven't seen many 2+ year old motherboards which can take DX4/120 writeback cpu so it would really work in write back mode. -- Bror 'Count' Heinola % count@key.hole.fi % http://pobox.com/~count/ Pengerkatu 13b A5 % IRC: Count NIC: BH271 % FI-00530 HELSINKI % Work: bror@sms.fi % Roads? Where we're going, Cell: +358-40-5533-554 % Santa Monica Software % we don't need roads. From owner-freebsd-current Thu Apr 25 02:29:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA27761 for current-outgoing; Thu, 25 Apr 1996 02:29:53 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA27726 for ; Thu, 25 Apr 1996 02:29:38 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id LAA21653 for current@freebsd.org; Thu, 25 Apr 1996 11:29:24 +0200 Message-Id: <199604250929.LAA21653@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Thu, 25 Apr 96 11:29:17 MDT From: Greg Lehey Cc: gpalmer@freebsd.org, smpatel@umiacs.umd.edu, current@freebsd.org In-Reply-To: <199604250239.MAA01585@godzilla.zeta.org.au>; from "Bruce Evans" at Apr 25, 96 12:39 pm X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had tried to take this thread off line. If you agree, please include Terry and erich@lodgenet.com (Eric L. Hernes) on the reply. >>>> While we're talking about DDB, can't we have it timeout in 30s if you >>>> don't hit a key (and then generate a core dump). >>> >>> Not really ... that would assume that the IRQ handlers were still >>> operational, which may not be the case. DDB should only be running if >>> all interrupts are disabled if I remember right (and if I don't, I >>> won't mind being corrected :-) ) > > Here are some corrections :-). > > 1. ddb should run with all interrupts enabled. It should also normally > keep interrupts disabled while tracing. Otherwise the system state > may change while you're looking at it. May I assume that you mean "disabled" above? Then I agree. > 2. ddb actually doesn't disable interrupts. It even enables them if > they were only disabled in the cpu. Thus breakpoints sections > protected by `enable_intr(); ... disable_intr();' or early in > Xintr*(), or in fastintr handlers don't work right. spl masking > works better. Normally ddb spends most of it's time sitting in the > console input routine at spltty() or higher. Other interrupts are > masked iff they are masked when ddb is entered. tty interrupts > aren't masked throughout unless they are masked when ddb is entered. > Clock interrupts usually aren't masked when ddb is entered, so the > clocks usually keep ticking away. I don't think I agree with this approach. This makes it impossible to debug interrupt handlers. I think that it's usually acceptable for the clocks to stop during a debugging session. Possibly we could include an option to restart them where necessary, but I think that having all interrupts enabled is asking for trouble. In Lowbug I took a rather simplistic approach to interrupts: I had a mask of the interrupts that I wanted to block, and another mask of the interrupts that I wanted passed to Lowbug. It caused problems, particularly with breakpoints. This is one of the areas I want to rethink. > 3. timeout() is unsuitable for use ddb. First, clk0 interrupts might be > masked when ddb is entered. Then ddb can't unmask them, so the > clk0 won't work. Second, ddb shouldn't depend on the timeout() code > to work. > >> Can we sit in a loop, while polling the keyboard for input? > > Yes, you can usefully poll the clock(s) while polling the keyboard, > provided: > > a. polling is non-destructive. This makes it difficult to use timer0, > timer1 and the RTC. Perhaps they can be read without (destructively) > latching the count. Even that steals some state if a non-debugging > part of the system has just latched the count. timer2 is probably > safe to use, because non-debugging parts of the system never access > it. The way I propose it, you're going to have to poll the keyboard. That's the tradeoff. > b. the clock hasn't stopped. Or that you can read the counters. I believe this to be the case. Is it? Greg From owner-freebsd-current Thu Apr 25 04:13:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA02332 for current-outgoing; Thu, 25 Apr 1996 04:13:59 -0700 (PDT) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA02326 Thu, 25 Apr 1996 04:13:56 -0700 (PDT) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id HAA02980; Thu, 25 Apr 1996 07:13:55 -0400 for Date: Thu, 25 Apr 1996 07:13:55 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199604251113.HAA02980@robin.mcnc.org.mcnc.org> To: bde@zeta.org.au, sos@FreeBSD.org Subject: Re: minor syscons bogon Cc: current@FreeBSD.org, freebsd-current@FreeBSD.org X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Does anything actually use this kludge? Like, how would an application even know that /dev/ttyv[MAXCONS] == /dev/console ? This is very ugly. - Frank >> >> if (unit == MAXCONS) >> >> return CONSOLE_TTY; > >Note that (unit == MAXCONS) case is handled 2 lines after the patched >line, and this handling is always a no-op if the patch is applied. Thus >the patch is at best incomplete. > >There are certainly some bugs here. If /dev/ttyvn exists for n = >MAXCONS, then /dev/ttyvn is more or less an alias for /dev/console. >This causes security holes if /dev/ttyvn has weaker ownership or >permissions than /dev/console. Opening and closing /dev/ttyvn messes up >last-close stuff for /dev/console (e.g., last-closing /dev/ttyvn nukes >the console tty's pgrp and session pointers). > >The problem is easy to work around: don't create /dev/ttyvn for n = >MAXCONS. I consider requiring this to be acceptable, although the bug >is in the kernel. Root should be very careful about the ownerships, >permissions and existence of all devices. There are many similar kernel >bugs, because many drivers don't fully decode the minor number. E.g., >the vn driver with slices disabled only decodes 5 unit bits, so there >are 2^27 aliases for each device, 13 of which are created by `sh MAKEDEV >vn0'. > >Bruce > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Thu Apr 25 04:41:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA03453 for current-outgoing; Thu, 25 Apr 1996 04:41:22 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA03443 for ; Thu, 25 Apr 1996 04:41:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id EAA19018; Thu, 25 Apr 1996 04:40:29 -0700 (PDT) To: Geoff Davidson cc: "Marc G. Fournier" , davidg@Root.COM, current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-reply-to: Your message of "Wed, 24 Apr 1996 23:56:46 EDT." <317EF7FE.1A1A@sales.org> Date: Thu, 25 Apr 1996 04:40:28 -0700 Message-ID: <19016.830432428@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It is said, with some truth to its latin (or is that Greek) roots, that > humility comes from humiliation. Yes, and perhaps I was a little hard on Marc. But there is, nonetheless, a very valid lesson to be learned here and that's that it really isn't a good idea to bombard the developers with messages and PRs (I think we have about 10 open ones from Marc which are related to this problem) until you've really checked everything else, first. The alternative is that you burn up all your bug reporting "credit" on something stupid and have people then whap `delete' on all your future stuff because they don't want to be sent on any more wild goose chases. Sort of a twist on the boy who cried wolf.. :) Jordan From owner-freebsd-current Thu Apr 25 05:39:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA06098 for current-outgoing; Thu, 25 Apr 1996 05:39:59 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA06084 Thu, 25 Apr 1996 05:39:49 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id OAA17467; Thu, 25 Apr 1996 14:28:35 +0200 Message-Id: <199604251228.OAA17467@ra.dkuug.dk> Subject: Re: minor syscons bogon To: fty@mcnc.org (Frank E. Terhaar-Yonkers) Date: Thu, 25 Apr 1996 14:28:35 +0200 (MET DST) Cc: bde@zeta.org.au, sos@FreeBSD.org, current@FreeBSD.org, freebsd-current@FreeBSD.org In-Reply-To: <199604251113.HAA02980@robin.mcnc.org.mcnc.org> from "Frank E. Terhaar-Yonkers" at Apr 25, 96 07:13:55 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Frank E. Terhaar-Yonkers who wrote: > > Does anything actually use this kludge? Like, how would an application > even know that /dev/ttyv[MAXCONS] == /dev/console ? This is very ugly. NO vty is the same as /dev/console, period. But by changing the MAXCONS define you break the logic in syscons that deals with this. NO application is supposed to know ANYTHING about MAXCONS, its an internal define to syscons, and it shouldn't be tampered with (except you know EXACTLY what you are doing). It is a hack that solves an old problem in the way interaction with the console is done internally in the kernel. There was a time when it defined the number of consoles available, but that is long gone, as that is done dynamically now. It has nothing to do with the physical /dev/console device which is alwas on the same major/minor no matter what MAXCONS is set to. So don't change MAXCONS, and don't make more than the 16 vty's that MAKEDEV allows you to, or something VERY UGLY is going to happen. I wouldn't advise that you go change random defines all over the place or you are in for some REAL trouble. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Thu Apr 25 06:03:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA07798 for current-outgoing; Thu, 25 Apr 1996 06:03:18 -0700 (PDT) Received: from robin.mcnc.org.mcnc.org (robin.mcnc.org [128.109.130.29]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA07792 Thu, 25 Apr 1996 06:03:16 -0700 (PDT) Received: by robin.mcnc.org.mcnc.org (8.6.9/MCNC/8-10-92) id JAA09174; Thu, 25 Apr 1996 09:03:15 -0400 for Date: Thu, 25 Apr 1996 09:03:15 -0400 From: "Frank E. Terhaar-Yonkers" Message-Id: <199604251303.JAA09174@robin.mcnc.org.mcnc.org> To: sos@FreeBSD.org Subject: Re: minor syscons bogon Cc: bde@zeta.org.au, current@FreeBSD.org, freebsd-current@FreeBSD.org X-Face: ,fjtWiMPydUaSQl%8[eTg`u:^BXt&T)Sny(6w\*U"5D9H[Z$kG%Q/z;Z=NwrPiXf-aMF3R) Rsand$,]26-8>5@HD(A3A79gN|0%NHsdek4mT8E,>j+\w!~d2#nH;~NV!5a0"`5$Cj8d\or(Jy/JQ_ |uc;C[filmZ(~#lre*l:|O%d/PJFy`.5w8)sMZ-)QI3TaV"j'k Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> Does anything actually use this kludge? Like, how would an application >> even know that /dev/ttyv[MAXCONS] == /dev/console ? This is very ugly. > Obviously. >NO vty is the same as /dev/console, period. But by changing the MAXCONS >define you break the logic in syscons that deals with this. Exactly my point. Tying a kernel define to a minor device # is stupid. >NO application is supposed to know ANYTHING about MAXCONS, its an internal >define to syscons, and it shouldn't be tampered with (except you know Then document it as such. >EXACTLY what you are doing). It is a hack that solves an old problem >in the way interaction with the console is done internally in the kernel. >There was a time when it defined the number of consoles available, but >that is long gone, as that is done dynamically now. >It has nothing to do with the physical /dev/console device which is >alwas on the same major/minor no matter what MAXCONS is set to. >So don't change MAXCONS, and don't make more than the 16 vty's >that MAKEDEV allows you to, or something VERY UGLY is going to happen. It's not unreasonable to whittle down defines to say, get a kernel (and enuf utils) to fit on a 1.44 floppy for "fixit" purposes. This define seemed to fit the bill. A "few bytes" here and there makes a huge difference not only here but in a production system where it may make the difference between a process page thrashing or not. >I wouldn't advise that you go change random defines all over the >place or you are in for some REAL trouble. > > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > So much code to hack -- so little time. > \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////\\\\////\\\\////\\\\////\\\\ Frank Terhaar-Yonkers, Manager High Performance Computing and Communications Research MCNC PO Box 12889 3021 Cornwallis Road Research Triangle Park, North Carolina 27709-2889 fty@mcnc.org voice (919)248-1417 FAX (919)248-1455 http://www.mcnc.org/hpcc.html From owner-freebsd-current Thu Apr 25 06:56:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA10755 for current-outgoing; Thu, 25 Apr 1996 06:56:37 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA10742 for ; Thu, 25 Apr 1996 06:56:35 -0700 (PDT) Received: from Early-Bird-1.Think.COM by mail.think.com; Thu, 25 Apr 96 09:56:32 -0400 Received: from by Early-Bird.Think.COM; Thu, 25 Apr 96 09:56:26 EDT Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id BAA01844; Thu, 25 Apr 1996 01:42:32 -0500 (CDT) Date: Thu, 25 Apr 1996 01:42:32 -0500 (CDT) Message-Id: <199604250642.BAA01844@compound.Think.COM> From: Tony Kimball To: current@freebsd.org Subject: running out of swap Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Striding through a very large mmap, I discovered that FreeBSD will lock up when it runs out of swap. It would be nicer to terminate the offending process. From owner-freebsd-current Thu Apr 25 07:41:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA13831 for current-outgoing; Thu, 25 Apr 1996 07:41:55 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA13826 for ; Thu, 25 Apr 1996 07:41:52 -0700 (PDT) Received: (from jmacd@localhost) by paris.CS.Berkeley.EDU (8.6.11/8.6.9) id HAA25347 for freebsd-current@freebsd.org; Thu, 25 Apr 1996 07:41:51 -0700 Date: Thu, 25 Apr 1996 07:41:51 -0700 From: Josh MacDonald Message-Id: <199604251441.HAA25347@paris.CS.Berkeley.EDU> To: freebsd-current@freebsd.org Subject: kernel config Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to compile in the ed0 device and I geT: if_ed.o: Undefined symbol `_ether_output' referenced from text segment if_ed.o: Undefined symbol `_ether_ifattach' referenced from text segment if_ed.o: Undefined symbol `_arp_ifinit' referenced from text segment if_ed.o: Undefined symbol `_ether_addmulti' referenced from text segment if_ed.o: Undefined symbol `_ether_delmulti' referenced from text segment if_ed.o: Undefined symbol `_ether_input' referenced from text segment when it tries to link a new kernel. Its not compiling net/if_ethersubr.c or netinet/if_ether.c Did I goof, or what? I just uncommented the line: device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr and when I linked in those two files the kernel ran fine. -josh From owner-freebsd-current Thu Apr 25 09:13:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA19303 for current-outgoing; Thu, 25 Apr 1996 09:13:38 -0700 (PDT) Received: from super.tku.edu.tw ([163.13.241.203]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA19293 for ; Thu, 25 Apr 1996 09:13:28 -0700 (PDT) Received: (from bear@localhost) by super.tku.edu.tw (8.7.5/8.7.3) id AAA11377 for freebsd-current@freebsd.org; Fri, 26 Apr 1996 00:08:44 +0800 (CST) From: "Bear S. Hung" Message-Id: <199604251608.AAA11377@super.tku.edu.tw> Subject: cur-ctm-1929: adjkerntz : make error To: freebsd-current@freebsd.org Date: Fri, 26 Apr 1996 00:08:44 +0800 (CST) Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get the cvs tree from ctm-1800A to ctm-1929, ctm export -r HEAD src/sbin any file I missing ?? ftponly:[bear][11:42pm][Thu][Apr.25.96][/usr/src/sbin/adjkerntz] [391]% pwd /home/src-cvs/src/sbin/adjkerntz ftponly:[bear][11:43pm][Thu][Apr.25.96][/usr/src/sbin/adjkerntz] [392]% make cc -O -Wall -c adjkerntz.c adjkerntz.c: In function `main': adjkerntz.c:321: `CPU_WALLCLOCK' undeclared (first use this function) adjkerntz.c:321: (Each undeclared identifier is reported only once adjkerntz.c:321: for each function it appears in.) *** Error code 1 Stop. bear bear@super.tku.edu.tw From owner-freebsd-current Thu Apr 25 09:35:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA20464 for current-outgoing; Thu, 25 Apr 1996 09:35:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA20456 Thu, 25 Apr 1996 09:35:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id CAA31199; Fri, 26 Apr 1996 02:24:29 +1000 Date: Fri, 26 Apr 1996 02:24:29 +1000 From: Bruce Evans Message-Id: <199604251624.CAA31199@godzilla.zeta.org.au> To: bde@zeta.org.au, lehey.pad@sni.de Subject: Re: request for a new "feature" as regards DDB Cc: current@freebsd.org, gpalmer@freebsd.org, smpatel@umiacs.umd.edu Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> 1. ddb should run with all interrupts enabled. It should also normally >> keep interrupts disabled while tracing. Otherwise the system state >> may change while you're looking at it. >May I assume that you mean "disabled" above? Then I agree. Yes. >> 2. ddb actually doesn't disable interrupts. It even enables them if >I don't think I agree with this approach. This makes it impossible to >debug interrupt handlers. I think that it's usually acceptable for It's a bug. >In Lowbug I took a rather simplistic approach to interrupts: I had a >mask of the interrupts that I wanted to block, and another mask of the >interrupts that I wanted passed to Lowbug. It caused problems, >particularly with breakpoints. This is one of the areas I want to >rethink. The debugger has to work when it is entered with all interrupts enabled, so it sometimes can't depend on interrupts. Whatever it does to handle that cause should work in all cases. >> a. polling is non-destructive. This makes it difficult to use timer0, >> timer1 and the RTC. Perhaps they can be read without (destructively) >The way I propose it, you're going to have to poll the keyboard. >That's the tradeoff. Polling the keyboard is destructive too. It took me many hours over many months to learn how to poll the keyboard on XTs. Early attempts used the 8259 to poll for interrupts. This didn't work well because it changed the state of the 8259. AT keyboards are much easier. >> b. the clock hasn't stopped. >Or that you can read the counters. I believe this to be the case. Is >it? And that you can read the counters. The counters for timer0-3 are always readable. Only the counters for periods >= 1 second in the RTC are readable. Bruce From owner-freebsd-current Thu Apr 25 09:40:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA20709 for current-outgoing; Thu, 25 Apr 1996 09:40:03 -0700 (PDT) Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA20654 for ; Thu, 25 Apr 1996 09:39:56 -0700 (PDT) Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.6.12/8.6.12) id SAA20877 for current@freebsd.org; Thu, 25 Apr 1996 18:39:39 +0200 Message-Id: <199604251639.SAA20877@nixpbe.pdb.sni.de> Subject: Re: request for a new "feature" as regards DDB To: bde@zeta.org.au (Bruce Evans) Date: Thu, 25 Apr 96 18:39:39 MDT From: Greg Lehey Cc: current@freebsd.org In-Reply-To: <199604251624.CAA31199@godzilla.zeta.org.au>; from "Bruce Evans" at Apr 26, 96 2:24 am X-Mailer: xmail 2.4 (based on ELM 2.2 PL16) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >>> 1. ddb should run with all interrupts enabled. It should also normally >>> keep interrupts disabled while tracing. Otherwise the system state >>> may change while you're looking at it. > >> May I assume that you mean "disabled" above? Then I agree. > > Yes. > >>> 2. ddb actually doesn't disable interrupts. It even enables them if > >> I don't think I agree with this approach. This makes it impossible to >> debug interrupt handlers. I think that it's usually acceptable for > > It's a bug. > >> In Lowbug I took a rather simplistic approach to interrupts: I had a >> mask of the interrupts that I wanted to block, and another mask of the >> interrupts that I wanted passed to Lowbug. It caused problems, >> particularly with breakpoints. This is one of the areas I want to >> rethink. > > The debugger has to work when it is entered with all interrupts enabled, > so it sometimes can't depend on interrupts. Whatever it does to handle > that cause should work in all cases. I think we're agreed on all this. >>> a. polling is non-destructive. This makes it difficult to use timer0, >>> timer1 and the RTC. Perhaps they can be read without (destructively) > >> The way I propose it, you're going to have to poll the keyboard. >> That's the tradeoff. > > Polling the keyboard is destructive too. It took me many hours over > many months to learn how to poll the keyboard on XTs. Early attempts > used the 8259 to poll for interrupts. This didn't work well because it > changed the state of the 8259. AT keyboards are much easier. Do we still need support for XT keyboards? :-) Lowbug polls the keyboard, and I haven't had any problems with it. >>> b. the clock hasn't stopped. > >> Or that you can read the counters. I believe this to be the case. Is >> it? > > And that you can read the counters. The counters for timer0-3 are > always readable. Only the counters for periods >= 1 second in the RTC > are readable. We're really only talking about a 30 second (or whatever) timeout here. The RTC counters would do just fine for that. Greg From owner-freebsd-current Thu Apr 25 10:09:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22388 for current-outgoing; Thu, 25 Apr 1996 10:09:37 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA22383 for ; Thu, 25 Apr 1996 10:09:35 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA26189; Thu, 25 Apr 1996 13:09:18 -0400 Date: Thu, 25 Apr 1996 13:09:18 -0400 From: Garrett Wollman Message-Id: <9604251709.AA26189@halloran-eldar.lcs.mit.edu> To: Peter Wemm Cc: current@freebsd.org Subject: Re: cvs commit: ports/net/socks5 Makefile In-Reply-To: <199604251458.WAA01049@jhome.DIALix.COM> References: <199604251351.OAA22261@cadair.elsevier.co.uk> <199604251458.WAA01049@jhome.DIALix.COM> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Discussion redirected.] < said: > BTW: I would not at all distressed to see a few subdirs in /etc.. Eg: (to > borrow a lead from some other OS's) /etc/inet (contains tcp/ip stuff), > /etc/mail (contains mail stuff), /etc/lpd, /etc/nfs (including amd, exports), > and you get the idea. :-) Unfortunately, there are statically linked binaries > to deal with. Since you have to specify the full pathname, there's no reason why you can't put your AMD map files anywhere you want to; /etc/rc sure doesn't care. I use `-x noinfo /net amd.net /home amd.home'. (I put mine in YP.) -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 Apr 25 10:10:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22452 for current-outgoing; Thu, 25 Apr 1996 10:10:06 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA22414 for ; Thu, 25 Apr 1996 10:09:59 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id CAA32034; Fri, 26 Apr 1996 02:52:49 +1000 Date: Fri, 26 Apr 1996 02:52:49 +1000 From: Bruce Evans Message-Id: <199604251652.CAA32034@godzilla.zeta.org.au> To: bde@zeta.org.au, lehey.pad@sni.de Subject: Re: request for a new "feature" as regards DDB Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Polling the keyboard is destructive too. It took me many hours over >> many months to learn how to poll the keyboard on XTs. Early attempts >> used the 8259 to poll for interrupts. This didn't work well because it >> changed the state of the 8259. AT keyboards are much easier. >Do we still need support for XT keyboards? :-) Lowbug polls the >keyboard, and I haven't had any problems with it. FreeBSD never supported them. My debugger does. I won't break it :-). >> And that you can read the counters. The counters for timer0-3 are >> always readable. Only the counters for periods >= 1 second in the RTC >> are readable. >We're really only talking about a 30 second (or whatever) timeout >here. The RTC counters would do just fine for that. Except they will be stopped when you're tracing resettodr() and any other time RTCSB_HALT happens to be set due to a bug. More importantly, they are can't be read without destroying the state of the (write-only) RTC index register. Bruce From owner-freebsd-current Thu Apr 25 10:13:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA22795 for current-outgoing; Thu, 25 Apr 1996 10:13:37 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA22779 for ; Thu, 25 Apr 1996 10:13:33 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA25923; Thu, 25 Apr 1996 13:12:51 -0400 Date: Thu, 25 Apr 1996 13:12:51 -0400 From: Garrett Wollman Message-Id: <9604251712.AA25923@halloran-eldar.lcs.mit.edu> To: Adam David Cc: current@freebsd.org Subject: Re: cvs commit: ports/net/socks5 Makefile In-Reply-To: <199604251536.PAA17164@veda.is> References: <199604251344.OAA22208@cadair.elsevier.co.uk> <199604251536.PAA17164@veda.is> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Cc fixed. Maybe should go to -ports instead.] < said: >> Who says? /usr/local/share is but not /usr. In fact /usr/local/ is >> suppose to be, well, local. If you want to share that then deal with it >> yourself because it's a site defined area. > Typically (by defacto standard) /usr/local is local to the site, not local to > the individual host. But there are always exceptions. Here, /usr/local is always local to the individual host, and stuff shared by the entire group is in /usr/site. (There is actually a second level of indirection on my OSF/1 machines, where /usr/site contains nothing by symlinks to files in /vol, which is automounted.) -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 Apr 25 10:51:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA24949 for current-outgoing; Thu, 25 Apr 1996 10:51:38 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA24940 for ; Thu, 25 Apr 1996 10:51:31 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA26343; Thu, 25 Apr 1996 19:51:18 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id TAA08439; Thu, 25 Apr 1996 19:51:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA02317; Thu, 25 Apr 1996 19:27:24 +0200 (MET DST) From: J Wunsch Message-Id: <199604251727.TAA02317@uriah.heep.sax.de> Subject: Re: kernel config To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 25 Apr 1996 19:27:24 +0200 (MET DST) Cc: jmacd@CS.Berkeley.EDU (Josh MacDonald) In-Reply-To: <199604251441.HAA25347@paris.CS.Berkeley.EDU> from "Josh MacDonald" at Apr 25, 96 07:41:51 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Josh MacDonald wrote: > > > I'm trying to compile in the ed0 device and I geT: > > if_ed.o: Undefined symbol `_ether_output' referenced from text segment > if_ed.o: Undefined symbol `_ether_ifattach' referenced from text segment > if_ed.o: Undefined symbol `_arp_ifinit' referenced from text segment > if_ed.o: Undefined symbol `_ether_addmulti' referenced from text segment > if_ed.o: Undefined symbol `_ether_delmulti' referenced from text segment > if_ed.o: Undefined symbol `_ether_input' referenced from text segment You should not try to configure an ethernet driver without pseudo- device "ether". -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Apr 25 11:48:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA00471 for current-outgoing; Thu, 25 Apr 1996 11:48:59 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA00466 for ; Thu, 25 Apr 1996 11:48:55 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id OAA16902; Thu, 25 Apr 1996 14:48:44 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id OAA02359; Thu, 25 Apr 1996 14:49:04 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Thu, 25 Apr 1996 14:49:03 -0400 (EDT) From: "Marc G. Fournier" To: "Jordan K. Hubbard" cc: Geoff Davidson , davidg@Root.COM, current@FreeBSD.org, Cat Okita , Geoff Davidson Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <19016.830432428@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Jordan K. Hubbard wrote: > But there is, nonetheless, a very valid lesson to be learned here and > that's that it really isn't a good idea to bombard the developers with > messages and PRs (I think we have about 10 open ones from Marc which > are related to this problem) until you've really checked everything > else, first. The alternative is that you burn up all your bug > reporting "credit" on something stupid and have people then whap > `delete' on all your future stuff because they don't want to be sent > on any more wild goose chases. Sort of a twist on the boy who cried > wolf.. :) > Look for a bunch of closed reports over the next hour or so :( Looking hopefully at Jordan, I wonder if all those closed reports in the database balance out the ones I opened? :) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Apr 25 12:26:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA03138 for current-outgoing; Thu, 25 Apr 1996 12:26:35 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA03133 for ; Thu, 25 Apr 1996 12:26:32 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA19429; Thu, 25 Apr 1996 13:26:16 -0600 Date: Thu, 25 Apr 1996 13:26:16 -0600 From: Nate Williams Message-Id: <199604251926.NAA19429@rocky.sri.MT.net> To: "Marc G. Fournier" Cc: current@FreeBSD.org Subject: Re: MotherBoard Jumper Settings... In-Reply-To: References: <19016.830432428@time.cdrom.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier writes: > Look for a bunch of closed reports over the next hour or so :( Does that mean your box is now stable? If so, that's *great* news. Nate From owner-freebsd-current Thu Apr 25 12:36:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA03928 for current-outgoing; Thu, 25 Apr 1996 12:36:46 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA03923 for ; Thu, 25 Apr 1996 12:36:41 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id PAA18141; Thu, 25 Apr 1996 15:36:32 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id PAA02447; Thu, 25 Apr 1996 15:36:55 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Thu, 25 Apr 1996 15:36:53 -0400 (EDT) From: "Marc G. Fournier" To: Nate Williams cc: current@FreeBSD.org Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <199604251926.NAA19429@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Nate Williams wrote: > Does that mean your box is now stable? If so, that's *great* news. > Nope, just that I'm going to submit new ones now that I think I've gone over everything with a fine toothed comb and caught any hardware mis-configurations I can find :) Until I can get a proper core dump out of this machine, there isn't much use putting in a problem report anyway, since DDB just doesn't seem to produce enough information (or I don't know how to use it well enough to get the right information) Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Apr 25 12:58:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA05184 for current-outgoing; Thu, 25 Apr 1996 12:58:36 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA05179 for ; Thu, 25 Apr 1996 12:58:33 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA19541; Thu, 25 Apr 1996 13:58:20 -0600 Date: Thu, 25 Apr 1996 13:58:20 -0600 From: Nate Williams Message-Id: <199604251958.NAA19541@rocky.sri.MT.net> To: "Marc G. Fournier" Cc: Nate Williams , current@FreeBSD.org Subject: Re: MotherBoard Jumper Settings... In-Reply-To: References: <199604251926.NAA19429@rocky.sri.MT.net> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Does that mean your box is now stable? If so, that's *great* news. > > > Nope, just that I'm going to submit new ones now that I > think I've gone over everything with a fine toothed comb and caught > any hardware mis-configurations I can find :) OK, here's some advice. Generally speaking most folks *shouldn't* have to go through this many steps, but in Marc's case where he's having problems that no-one else is seeing, this might be helpful. Step 0: - Remove *ALL* NFS and DOS mounts from your system. The NFS and DOS filesystems are slightly broken, and can cause weird problems. Step 1: - Disable *ALL* caches on your machine in the BIOS. Set the memory wait states to the higher number and your bus speed to ~8Mhz (for ISA/EISA boxes). Test, test, test, test, test. Do the errors still occur? If so, move onto step 2, else assume it's a hardware problem, probably involving the L2 cache (motherboard and/or memory) or BIOS setup. [ Leave the cache's disabled, just in case they are *also* a problem ] Step 2: - Make *SURE* (!!!!) that your SCSI cables are good and everything is terminated correctly. This means that there should be 2 termination points, one at one end and one at the other. Also, if you have external devices, remove them and terminate your SCSI card, just to rule out bad external SCSI cables (very common). If you've got a scanner, remove it. (Scanner's are notorious for screwing things up under load.) Test, test, test, test, test. Do the problems still occur? If so, move onto step 3, else assume it's a hardware problem with SCSI termination and/or cabling. Step 3: - Remove *ALL* non-essential hardware from the system. This means leaving a disk big enough for the OS and some sources, and necessary cards. Ultimately, this would mean only have a video card, hard/floppy card, and possibly an ethernet card. Test, test, test, test, test. The problems still occur? Then it's still possible that it's hardware, move onto step 4, else assume it's a misconfigured card. Step 4: - Swap out your memory with known-good memory, your disk with a known- good disk, and your controller with a known-good controller. (Heck, go IDE at this point.) Re-install FreeBSD to make sure all the bits aren't corrupted from a previously bad hardware setup. Test, test, test, test, test. It *should* work now, because it was a hardware problem in the first place, given the consistency and frequency of your problems. Quick history note: The original 'interim' (pre-FreeBSD, pre-WC) development was a 486/33 box that hosted the development when I was a student at Montana State University. This box (which is still in service today as my home box) would occasionally get NMI's from faulty hardware under heavy load. Most of the time it worked, but it was annoying. Almost 3 years after I got the box I finally got tired of it, and decided to replace the motherboard. Unfortunately, the board I got was DOA, but I noticed that the new board had faster cache ram than my original motherboard. On a whim, I swapped out the cache on my old (working but NMI) Mboard with the cache from the DOA board, and it seemed to work. From that day one, I have been unable to produce an NMI on that board no matter *what* the load. The machine has been 'rock' stable ever since I re-installed FreeBSD on it. However, before I installed FreeBSD on it I got random crashes b/c of FS corruption. Binaries, directories, inodes, and all sorts of other files were corrupt from the the previous hardware misconfiguration. So, even after I fixed my hardware problems, I still got *random* crashes. I backed up what I could of the data (using tar to avoid FS corruptions), and then re-installed and restored all my previos files and I haven't had a crash on it yet. The only reboots occur when I turn-on my DAT drive to do backups, and then reboot to turn it off since I don't like to leave it on. Nate From owner-freebsd-current Thu Apr 25 13:29:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07501 for current-outgoing; Thu, 25 Apr 1996 13:29:08 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA07493 for ; Thu, 25 Apr 1996 13:29:03 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA19335; Thu, 25 Apr 1996 16:28:54 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA02565; Thu, 25 Apr 1996 16:29:15 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Thu, 25 Apr 1996 16:29:14 -0400 (EDT) From: "Marc G. Fournier" To: Nate Williams cc: current@FreeBSD.org Subject: Re: MotherBoard Jumper Settings... In-Reply-To: <199604251958.NAA19541@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk the following advice given by Nate will be saved and worked through once I get a machine I can do this on :( Right now, my -stable(?) machine is my main server, and having it panic and be down for a few minutes is possible, while I reboot it...but disabling the NFS mounts is something that I can't do on this machine ;( I'm trying to get a machine in that I can put stable onto and then load test that. As far as NFS mounts are concerned...I'm running 3 FreeBSD boxes right now, that are all sharing /usr/httpd from one machine so that I can balance the hits going to each machine instead of it all relying on one...if NFS mounts are so broken that I can't do that, then I'm using the wrong OS (and note...I don't believe I am...) for a production environment (nothing from you, Cat!) Hopefully over the next week or so, I'll be able to take delivery of that machine and can give it an appropriate pounding, which, if it passes, I can move stuff off of the main server onto it and take the main server offline, and pound that until the hardware problem is exorcised from the machine. Until I do take delivery of the new machine, I shall not report any more problems, since each one I report seems to be hardware related, and is generally wasting everyones time :( On Thu, 25 Apr 1996, Nate Williams wrote: > > > Does that mean your box is now stable? If so, that's *great* news. > > > > > Nope, just that I'm going to submit new ones now that I > > think I've gone over everything with a fine toothed comb and caught > > any hardware mis-configurations I can find :) > > OK, here's some advice. Generally speaking most folks *shouldn't* have > to go through this many steps, but in Marc's case where he's having > problems that no-one else is seeing, this might be helpful. > > Step 0: > - Remove *ALL* NFS and DOS mounts from your system. The NFS and DOS > filesystems are slightly broken, and can cause weird problems. > > Step 1: - Disable *ALL* caches on your machine in the BIOS. Set the > memory wait states to the higher number and your bus speed to ~8Mhz (for > ISA/EISA boxes). > > Test, test, test, test, test. > > Do the errors still occur? If so, move onto step 2, else assume it's a > hardware problem, probably involving the L2 cache (motherboard and/or > memory) or BIOS setup. > > [ Leave the cache's disabled, just in case they are *also* a problem ] > > Step 2: > - Make *SURE* (!!!!) that your SCSI cables are good and everything is > terminated correctly. This means that there should be 2 termination > points, one at one end and one at the other. Also, if you have > external devices, remove them and terminate your SCSI card, just to > rule out bad external SCSI cables (very common). If you've got a > scanner, remove it. (Scanner's are notorious for screwing things up > under load.) > > Test, test, test, test, test. > > Do the problems still occur? If so, move onto step 3, else assume it's > a hardware problem with SCSI termination and/or cabling. > > Step 3: > - Remove *ALL* non-essential hardware from the system. This means > leaving a disk big enough for the OS and some sources, and necessary > cards. Ultimately, this would mean only have a video card, hard/floppy > card, and possibly an ethernet card. > > Test, test, test, test, test. > > The problems still occur? Then it's still possible that it's > hardware, move onto step 4, else assume it's a misconfigured card. > > Step 4: > - Swap out your memory with known-good memory, your disk with a known- > good disk, and your controller with a known-good controller. (Heck, > go IDE at this point.) Re-install FreeBSD to make sure all the bits > aren't corrupted from a previously bad hardware setup. > > Test, test, test, test, test. > > It *should* work now, because it was a hardware problem in the first > place, given the consistency and frequency of your problems. > > Quick history note: > > The original 'interim' (pre-FreeBSD, pre-WC) development was a 486/33 > box that hosted the development when I was a student at Montana State > University. This box (which is still in service today as my home box) > would occasionally get NMI's from faulty hardware under heavy load. > Most of the time it worked, but it was annoying. > > Almost 3 years after I got the box I finally got tired of it, and > decided to replace the motherboard. Unfortunately, the board I got was > DOA, but I noticed that the new board had faster cache ram than my > original motherboard. On a whim, I swapped out the cache on my old > (working but NMI) Mboard with the cache from the DOA board, and it > seemed to work. From that day one, I have been unable to produce an NMI > on that board no matter *what* the load. The machine has been 'rock' > stable ever since I re-installed FreeBSD on it. > > However, before I installed FreeBSD on it I got random crashes b/c of FS > corruption. Binaries, directories, inodes, and all sorts of other files > were corrupt from the the previous hardware misconfiguration. So, even > after I fixed my hardware problems, I still got *random* crashes. I > backed up what I could of the data (using tar to avoid FS corruptions), > and then re-installed and restored all my previos files and I haven't > had a crash on it yet. The only reboots occur when I turn-on my DAT > drive to do backups, and then reboot to turn it off since I don't like > to leave it on. > > > > > Nate > Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Thu Apr 25 13:48:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09256 for current-outgoing; Thu, 25 Apr 1996 13:48:36 -0700 (PDT) Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.9.13]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA09249 for ; Thu, 25 Apr 1996 13:48:32 -0700 (PDT) Received: (from james@localhost) by miller.cs.uwm.edu (8.7.3/8.7.3) id PAA21370 for current@freebsd.org; Thu, 25 Apr 1996 15:48:27 -0500 Date: Thu, 25 Apr 1996 15:48:27 -0500 From: Jim Lowe Message-Id: <199604252048.PAA21370@miller.cs.uwm.edu> To: current@freebsd.org Subject: Boot Code Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could kind soul tell me if the boot code in -current is stable? I would like to burn it into about 30 ROMs and don't want to have to burn it again for a while. Thanks much, -Jim From owner-freebsd-current Thu Apr 25 16:27:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA19565 for current-outgoing; Thu, 25 Apr 1996 16:27:42 -0700 (PDT) Received: from maui.com (root@waena.mrtc.maui.com [199.4.33.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA19559 for ; Thu, 25 Apr 1996 16:27:39 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [199.4.33.251]) by maui.com (8.6.10/8.6.6) with ESMTP id NAA26507; Thu, 25 Apr 1996 13:27:56 -1000 Received: (from langfod@localhost) by caliban.dihelix.com (8.7.5/8.6.9) id NAA07217; Thu, 25 Apr 1996 13:27:36 -1000 (HST) Message-Id: <199604252327.NAA07217@caliban.dihelix.com> Subject: Re: Boot Code To: james@miller.cs.uwm.edu (Jim Lowe) Date: Thu, 25 Apr 1996 13:27:36 -1000 (HST) Cc: current@freebsd.org In-Reply-To: <199604252048.PAA21370@miller.cs.uwm.edu> from Jim Lowe at "Apr 25, 96 03:48:27 pm" From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jim Lowe >Could kind soul tell me if the boot code in -current is stable? I >would like to burn it into about 30 ROMs and don't want to have to >burn it again for a while. > >Thanks much, > > -Jim Well we just noticed that the odd changes make fairly recently seem to make the code NOT work in a mixed SCSI/IDE environment. I havent have time to figure out the new code and see why. The HD_BIAS just doesnt seem to work. The old drivers with BOOT_HD works peachy though. -- /-------------------------------\ The past tempts us, | David Langford | the present confuses us, | Kihei, Maui, Hawai | and the future frightens us... | | and our lives slip away, | langfod@dihelix.com | moment by moment, \_______________________________/ lost in that vast, terrible in-between. From owner-freebsd-current Thu Apr 25 17:26:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23355 for current-outgoing; Thu, 25 Apr 1996 17:26:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA23350 for ; Thu, 25 Apr 1996 17:26:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA26021; Thu, 25 Apr 1996 17:22:12 -0700 From: Terry Lambert Message-Id: <199604260022.RAA26021@phaeton.artisoft.com> Subject: Re: running out of swap To: alk@Think.COM (Tony Kimball) Date: Thu, 25 Apr 1996 17:22:11 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199604250642.BAA01844@compound.Think.COM> from "Tony Kimball" at Apr 25, 96 01:42:32 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Striding through a very large mmap, I discovered that > FreeBSD will lock up when it runs out of swap. > It would be nicer to terminate the offending process. Send demonstration code to John, please. 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 Thu Apr 25 17:35:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23771 for current-outgoing; Thu, 25 Apr 1996 17:35:21 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA23766 for ; Thu, 25 Apr 1996 17:35:20 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA26044; Thu, 25 Apr 1996 17:30:25 -0700 From: Terry Lambert Message-Id: <199604260030.RAA26044@phaeton.artisoft.com> Subject: Re: Boot Code To: james@miller.cs.uwm.edu (Jim Lowe) Date: Thu, 25 Apr 1996 17:30:25 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <199604252048.PAA21370@miller.cs.uwm.edu> from "Jim Lowe" at Apr 25, 96 03:48:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Could kind soul tell me if the boot code in -current is stable? I > would like to burn it into about 30 ROMs and don't want to have to > burn it again for a while. Stability is relative to change. The easiet yardstick to use would be to SUP the CVS tree and do as "cvs log" on the files to see how recently they had been revised -- this will give you some idea of how widely they have been pointed on. >From my reading of things, the files are stable. 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 Thu Apr 25 18:16:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA25616 for current-outgoing; Thu, 25 Apr 1996 18:16:30 -0700 (PDT) Received: from mail.ucsd.edu (ucsd.edu [132.239.254.201]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA25610 for ; Thu, 25 Apr 1996 18:16:28 -0700 (PDT) Received: from sceard.UUCP by mail.ucsd.edu; id SAA00218 sendmail 8.6.12/UCSD-2.2-sun via UUCP Thu, 25 Apr 1996 18:16:27 -0700 for FreeBSD.ORG!current Received: by Sceard.COM (smail2.5/deliver1.5) id AA14191; 25 Apr 96 18:18:58 PDT (Thu) To: scrappy@ki.net Subject: Re: MotherBoard Jumper Settings... Cc: current@FreeBSD.ORG Message-Id: <9604251818.AA14180@Sceard.COM> Date: 25 Apr 96 18:18:56 PDT (Thu) From: mrm@Sceard.COM (M.R.Murphy) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Good advice from Nate to test, test, ... deleted] Make sure that the CPU's are cool enough. -- Mike Murphy mrm@Sceard.COM ucsd!sceard!mrm +1 619 598 5874 Better is the enemy of Good From owner-freebsd-current Thu Apr 25 19:03:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA28697 for current-outgoing; Thu, 25 Apr 1996 19:03:08 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA28684 for ; Thu, 25 Apr 1996 19:03:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id TAA07131; Thu, 25 Apr 1996 19:02:58 -0700 (PDT) Message-Id: <199604260202.TAA07131@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: Tony Kimball cc: current@freebsd.org Subject: Re: running out of swap In-reply-to: Your message of "Thu, 25 Apr 1996 01:42:32 CDT." <199604250642.BAA01844@compound.Think.COM> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 25 Apr 1996 19:02:58 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Striding through a very large mmap, I discovered that >FreeBSD will lock up when it runs out of swap. >It would be nicer to terminate the offending process. A run-out-of-swapspace test is one of the regression tests that we regularly do. It's not _supposed_ to hang the machine (see code in vm_fault.c and vm_pageout.c that finds kills off the process). If you have a test case that does cause a hang, then please send me or John the code. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Apr 25 19:17:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA29781 for current-outgoing; Thu, 25 Apr 1996 19:17:35 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA29775 for ; Thu, 25 Apr 1996 19:17:30 -0700 (PDT) Received: from pgeoffred (professor.net5a.io.org [199.166.190.38]) by ki.net (8.7.4/8.7.4) with SMTP id WAA25387; Thu, 25 Apr 1996 22:13:19 -0400 (EDT) Message-ID: <318031CD.6E1E@sales.org> Date: Thu, 25 Apr 1996 22:15:41 -0400 From: Geoff Davidson Organization: sales.org Sales, Marketing & Training Effectiveness X-Mailer: Mozilla 2.01 (Win95; I) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: scrappy@ki.net, davidg@Root.COM, current@FreeBSD.org, cat@ki.net Subject: Re: MotherBoard Jumper Settings... References: <19016.830432428@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > It is said, with some truth to its latin (or is that Greek) roots, that > > humility comes from humiliation. > > Yes, and perhaps I was a little hard on Marc. > Not at all Jordan, I think your point was made, RTFM includes a caveat of checking the systems out. Unfortunately there is so much confusion over hardware, that it is virtually impossible to keep the development of software and the configuration of hardware as wholly separate entities. > > But there is, nonetheless, a very valid lesson to be learned here and > that's that it really isn't a good idea to bombard the developers with > messages and PRs (I think we have about 10 open ones from Marc which > are related to this problem) until you've really checked everything > else, first. The alternative is that you burn up all your bug > reporting "credit" on something stupid and have people then whap > `delete' on all your future stuff because they don't want to be sent > on any more wild goose chases. Sort of a twist on the boy who cried > wolf.. :) > > Jordan I agree with your observation, mostly. One thing I've found dealing with a number of software/development groups (MS, SCO, IBM, Novell etc.) is that often times the developers weren't aware of the variety and symptoms of hardware/compatability related problems. Users have this naive belief that software and hardware should work together in perfect harmony :) What is scary is that "plug and play" is starting to look like a Microsoft advantage for OS and hardware choices. I kinda like having healthy and credible competition out there to keep them more honest. Hopefully for others in the future this exercise will result in a "have you checked all your hardware settings?" response early on, with perhaps some more suggested conflicts to consider. Anyhow, I thought the handling of all this was patient, professional and well presented. Your chiding was as gentle as we could each hope to receive for those times when we're caught at pedantic and persistent niggling at a problem we can't quite fix by our lonesomes. Regards, Geoff -- How do you score as a smart consumer or salesperson? Try one of the Quizes located at: "http://www.sales.org" Email: or Geoff Davidson Personal HomePage: "http://ki.net/~geoff" From owner-freebsd-current Thu Apr 25 19:25:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA00693 for current-outgoing; Thu, 25 Apr 1996 19:25:16 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA00675 for ; Thu, 25 Apr 1996 19:25:07 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id VAA00237; Thu, 25 Apr 1996 21:24:36 -0500 (EST) From: "John S. Dyson" Message-Id: <199604260224.VAA00237@dyson.iquest.net> Subject: Re: running out of swap To: terry@lambert.org (Terry Lambert) Date: Thu, 25 Apr 1996 21:24:36 -0500 (EST) Cc: alk@Think.COM, current@FreeBSD.ORG In-Reply-To: <199604260022.RAA26021@phaeton.artisoft.com> from "Terry Lambert" at Apr 25, 96 05:22:11 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > Striding through a very large mmap, I discovered that > > FreeBSD will lock up when it runs out of swap. > > It would be nicer to terminate the offending process. > > Send demonstration code to John, please. > > Good idea... dyson@freebsd.org... Thanks John From owner-freebsd-current Thu Apr 25 23:13:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA12012 for current-outgoing; Thu, 25 Apr 1996 23:13:53 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA12004 for ; Thu, 25 Apr 1996 23:13:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id QAA28569 for current@freebsd.org; Fri, 26 Apr 1996 16:10:45 +1000 Date: Fri, 26 Apr 1996 16:10:45 +1000 From: Bruce Evans Message-Id: <199604260610.QAA28569@godzilla.zeta.org.au> To: current@freebsd.org Subject: fixing FSETOWN/SIGIO Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FSETOWN/SIGIO has many bugs. I knew about the following ones yesterday: 1. FSETOWN on ttys interacts badly with POSIX process groups (see an old discussion). 2. FSETOWN on sockets allows sending SIGIO to any processes. I found some more while looking at something else (stat()) for pipes: 3. FSETOWN on pipes is a no-op. The SIGIO handling got lost when pipes were reimplemented as non-sockets. 4. FSETOWN on everything except sockets only works for right for process group ids. Process ids get converted to (positive) process group ids. Negative process group ids also get converted to positive process group ids, so there is no way to tell whether the resulting pgid was for a process. 5. The conversions in (4) break /dev/klog. logwakeup() expects process group ids to be negative and attempts to support process ids. 6. /dev/bpf and /dev/tun are aware of the negations in (4) (see comments in bpf.c) but aren't aware that the process id case is too broken to recover from. 7. The pipe pgid isn't initialized. 8. The /dev/klog pgid is initialized to the process id (a state that can only be reached for process group leaders via FSETOWN, because of (4)). 9. Socket, bpf and tun pgids seem to be initialized to 0. NO_PID would be better since kernel processes have pid == pgid == 0 (this may be another bug). Some of these problems are worked around in the Linux emulator. The pipe problems are new and the Linux emulator doesn't seem to know about them. Fixes: 1. Later. 2. I can't think of anything better than checking the pid or pgid using CANSIGNAL() when FSETOWN is called. This seems obvious, so why isn't it already done? Checking the signaler's pid when the signal is about to be delivered is no good because I/O is not attached to a process - it's asynchronous. The process that requested it may be long dead. 3. Fixed by cloning some simple socket code. 4. Pass the data straight through to the TIOCSPGRP ioctl. 5. Fixed by fix for (4). 6. Remove negations. 7. Fixed by initializing pgid to NO_PID. However, perhaps it should be initialized to the process id. 8. Not a bug. 9. Same as (7). Bruce From owner-freebsd-current Thu Apr 25 23:56:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA15929 for current-outgoing; Thu, 25 Apr 1996 23:56:30 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA15918 for ; Thu, 25 Apr 1996 23:56:27 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id BAA00172; Fri, 26 Apr 1996 01:55:49 -0500 (EST) From: "John S. Dyson" Message-Id: <199604260655.BAA00172@dyson.iquest.net> Subject: Re: fixing FSETOWN/SIGIO To: bde@zeta.org.au (Bruce Evans) Date: Fri, 26 Apr 1996 01:55:49 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <199604260610.QAA28569@godzilla.zeta.org.au> from "Bruce Evans" at Apr 26, 96 04:10:45 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I found some more while looking at something else (stat()) for pipes: > > 3. FSETOWN on pipes is a no-op. The SIGIO handling got lost when pipes > were reimplemented as non-sockets. I intended (all along) to fix this. So, I'll put that one in my basket of things to do. John From owner-freebsd-current Fri Apr 26 00:44:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA20847 for current-outgoing; Fri, 26 Apr 1996 00:44:46 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA20840 for ; Fri, 26 Apr 1996 00:44:25 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA14970; Fri, 26 Apr 1996 09:44:08 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA15531; Fri, 26 Apr 1996 09:44:07 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA04835; Fri, 26 Apr 1996 09:25:39 +0200 (MET DST) From: J Wunsch Message-Id: <199604260725.JAA04835@uriah.heep.sax.de> Subject: Re: Boot Code To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 26 Apr 1996 09:25:38 +0200 (MET DST) Cc: james@miller.cs.uwm.edu (Jim Lowe) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604252048.PAA21370@miller.cs.uwm.edu> from "Jim Lowe" at Apr 25, 96 03:48:27 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jim Lowe wrote: > > Could kind soul tell me if the boot code in -current is stable? I > would like to burn it into about 30 ROMs and don't want to have to > burn it again for a while. Netboot or Biosboot? (I suspect the former.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Fri Apr 26 02:52:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA28346 for current-outgoing; Fri, 26 Apr 1996 02:52:18 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA28341 Fri, 26 Apr 1996 02:52:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id CAA28938; Fri, 26 Apr 1996 02:35:50 -0700 (PDT) To: current@freebsd.org cc: bde@freebsd.org Subject: Anybody else see these in -current? Date: Fri, 26 Apr 1996 02:35:50 -0700 Message-ID: <28936.830511350@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Device vn0a: name slot allocation failed (E=17) Device rvn0a: name slot allocation failed (E=17) Device vn0c: name slot allocation failed (E=17) Device rvn0c: name slot allocation failed (E=17) I also see them for the slice which points at the ext2fs partition on another box - same `E' value though. Jordan From owner-freebsd-current Fri Apr 26 05:07:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA04161 for current-outgoing; Fri, 26 Apr 1996 05:07:10 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA04156 Fri, 26 Apr 1996 05:07:05 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id IAA01395; Fri, 26 Apr 1996 08:06:45 -0400 (EDT) Message-Id: <199604261206.IAA01395@whizzo.transsys.com> X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: current@FreeBSD.org, bde@FreeBSD.org From: "Louis A. Mamakos" Subject: Re: Anybody else see these in -current? References: <28936.830511350@time.cdrom.com> In-reply-to: Your message of "Fri, 26 Apr 1996 02:35:50 PDT." <28936.830511350@time.cdrom.com> Date: Fri, 26 Apr 1996 08:06:44 -0400 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I get the same sort of messages from the PS/2 mouse driver (/sys/i386/isa/psm.c) because it attempts to create devfs nodes each time the device is *opened*, and it fails on the second and subsequent attempt since the names have already been created. I don't know if this is your problem, but that may give you a place to start. louie > Device vn0a: name slot allocation failed (E=17) > Device rvn0a: name slot allocation failed (E=17) > Device vn0c: name slot allocation failed (E=17) > Device rvn0c: name slot allocation failed (E=17) > > I also see them for the slice which points at the ext2fs partition on > another box - same `E' value though. > > Jordan From owner-freebsd-current Fri Apr 26 08:32:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA14000 for current-outgoing; Fri, 26 Apr 1996 08:32:59 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA13993 for ; Fri, 26 Apr 1996 08:32:53 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id BAA15242; Sat, 27 Apr 1996 01:31:14 +1000 Date: Sat, 27 Apr 1996 01:31:14 +1000 From: Bruce Evans Message-Id: <199604261531.BAA15242@godzilla.zeta.org.au> To: bde@zeta.org.au, toor@dyson.iquest.net Subject: Re: fixing FSETOWN/SIGIO Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I found some more while looking at something else (stat()) for pipes: >> >> 3. FSETOWN on pipes is a no-op. The SIGIO handling got lost when pipes >> were reimplemented as non-sockets. >I intended (all along) to fix this. So, I'll put that one in my basket >of things to do. Erm, I've already fixed it to work more or less as (in)correctly as FSETOWN for sockets. See (3) in my list of fixes. Another problem with it: - since it is controlled by fcntl(), you'd expect the pgid to be per-file descriptor. In fact, it is per-device. The docs should at least that it is broken. Similar problem with O_NONBLOCK/FIONBIO: - O_NBONBLOCK is controlled by fcntl(), so you'd expect it to be per-file descriptor. In fact, for pipes, sockets, /dev/snoop, /dev/bpf and /dev/tun, it is implemented by converting it to the per-device ioctl FIONBIO. It is correctly implemented for /dev/log and ttys (the IO_NDELAY flag is passed to read() and write()). Bruce From owner-freebsd-current Fri Apr 26 09:16:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16637 for current-outgoing; Fri, 26 Apr 1996 09:16:59 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA16632 for ; Fri, 26 Apr 1996 09:16:55 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id LAA29959 for ; Fri, 26 Apr 1996 11:14:42 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma029957; Fri Apr 26 11:14:20 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id LAA21718 for ; Fri, 26 Apr 1996 11:18:32 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id LAA00651 for ; Fri, 26 Apr 1996 11:19:07 -0500 (CDT) Message-Id: <199604261619.LAA00651@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: current@freebsd.org Subject: patch for modload Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Apr 1996 11:19:06 -0500 From: "Eric L. Hernes" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I ran across a little problem w/ modload. it seems that modload can't load a module with a . in it's path, you get an error like: (ttyp0@jake)$ sudo /sbin/modload -o linux_mod -elinux_mod ./linux_mod.o modload: module object must end in .o I changed a strchr() to a strrchr() and now it works. Does this break anything? Here's the trivial patch. --- modload.c.orig Fri Apr 26 11:03:12 1996 +++ modload.c Fri Apr 26 11:03:19 1996 @@ -225,7 +225,7 @@ err(3, _PATH_LKM); fileopen |= DEV_OPEN; - p = strchr(modobj, '.'); + p = strrchr(modobj, '.'); if (!p || strcmp(p, ".o")) errx(2, "module object must end in .o"); eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-current Fri Apr 26 09:37:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA17476 for current-outgoing; Fri, 26 Apr 1996 09:37:06 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA17469 Fri, 26 Apr 1996 09:37:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id CAA17153; Sat, 27 Apr 1996 02:32:02 +1000 Date: Sat, 27 Apr 1996 02:32:02 +1000 From: Bruce Evans Message-Id: <199604261632.CAA17153@godzilla.zeta.org.au> To: jkh@time.cdrom.com, louie@TransSys.COM Subject: Re: Anybody else see these in -current? Cc: bde@FreeBSD.org, current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I get the same sort of messages from the PS/2 mouse driver >(/sys/i386/isa/psm.c) because it attempts to create devfs nodes each >time the device is *opened*, and it fails on the second and subsequent >attempt since the names have already been created. Yes, devfs isn't finished yet. Don't use it unless you want to debug it. The vn (actually the slice) driver attempts to remove all the devfs nodes before it re-creates them (it remove and creates everything every time the device is first-opened), but it apparently fails in some cases. Bruce From owner-freebsd-current Fri Apr 26 10:44:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21391 for current-outgoing; Fri, 26 Apr 1996 10:44:35 -0700 (PDT) Received: from utgard.bga.com (utgard.bga.com [205.238.129.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA21386 for ; Fri, 26 Apr 1996 10:44:29 -0700 (PDT) Received: (from faulkner@localhost) by utgard.bga.com (8.7.5/8.7.3) id MAA00629; Fri, 26 Apr 1996 12:43:49 -0500 (CDT) Message-Id: <199604261743.MAA00629@utgard.bga.com> Subject: Re: Anybody else see these in -current? To: bde@zeta.org.au (Bruce Evans) Date: Fri, 26 Apr 1996 12:43:48 -0459 (CDT) From: "Boyd R. Faulkner" Cc: current@freebsd.org In-Reply-To: <199604261632.CAA17153@godzilla.zeta.org.au> from "Bruce Evans" at Apr 27, 96 02:31:45 am X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Bruce Evans: > > > >I get the same sort of messages from the PS/2 mouse driver > >(/sys/i386/isa/psm.c) because it attempts to create devfs nodes each > >time the device is *opened*, and it fails on the second and subsequent > >attempt since the names have already been created. > > Yes, devfs isn't finished yet. Don't use it unless you want to debug it. > > The vn (actually the slice) driver attempts to remove all the devfs nodes > before it re-creates them (it remove and creates everything every time > the device is first-opened), but it apparently fails in some cases. > > Bruce > I tried to use it this morning. I supped current last night. I added a line in /etc/fstab devfs /dev devfs rw 1 1 after /dev/sd1a / ufs rw 1 1 /dev/sd1s1b none swap sw The machine failed to mount my partitions. It even says so. If I mount on /devfs, the devfs mounts fine and the dev entries cited below are seen. What's up? This is my current fstab without the devfs entry. /dev/sd1a / ufs rw 1 1 /dev/sd1s1b none swap sw /dev/sd1s1e /tmp ufs rw 1 2 /dev/sd1s1d /var ufs rw 1 2 /dev/sd1s1f /usr ufs rw 1 2 /dev/sd1s1g /usr/src ufs rw 1 2 /dev/sd1s1h /omni ufs rw 1 2 /dev/sd0s2 /dos/c msdos rw 1 2 /dev/sd0s5 /dos/d msdos rw 1 2 /dev/sd0s6 /dos/e msdos rw 1 2 /dev/sd0s7 /dos/f msdos rw 1 2 /dev/cd0a /cdrom cd9660 ro,noauto 1 2 /dev/cd1a /cdrom1 cd9660 ro,noauto 1 2 proc /proc procfs rw 1 2 Relevant entries in /devfs 0 brw-r----- 2 root operator 4, 0x00010002 Apr 26 09:05 sd0 0 brw-r----- 2 root operator 4, 0x00030002 Apr 26 04:09 sd0s2 0 brw-r----- 2 root operator 4, 0x00060002 Apr 26 04:09 sd0s5 0 brw-r----- 2 root operator 4, 0x00070002 Apr 26 04:09 sd0s6 0 brw-r----- 2 root operator 4, 0x00080002 Apr 26 04:09 sd0s7 0 brw-r----- 2 root operator 4, 0x0001000a Apr 26 09:05 sd1 0 brw-r----- 2 root operator 4, 8 Apr 26 09:05 sd1a 0 brw-r----- 2 root operator 4, 9 Apr 26 09:05 sd1b 0 brw-r----- 2 root operator 4, 10 Apr 26 09:05 sd1c 0 brw-r----- 2 root operator 4, 11 Apr 26 09:05 sd1d 0 brw-r----- 2 root operator 4, 12 Apr 26 09:05 sd1e 0 brw-r----- 2 root operator 4, 13 Apr 26 09:05 sd1f 0 brw-r----- 2 root operator 4, 14 Apr 26 09:05 sd1g 0 brw-r----- 2 root operator 4, 15 Apr 26 09:05 sd1h 0 brw-r----- 2 root operator 4, 0x0002000a Apr 26 04:06 sd1s1 0 brw-r----- 2 root operator 4, 0x00020008 Apr 26 09:05 sd1s1a 0 brw-r----- 2 root operator 4, 0x00020009 Apr 26 09:05 sd1s1b 0 brw-r----- 2 root operator 4, 0x0002000a Apr 26 09:05 sd1s1c 0 brw-r----- 2 root operator 4, 0x0002000b Apr 26 09:05 sd1s1d 0 brw-r----- 2 root operator 4, 0x0002000c Apr 26 09:05 sd1s1e 0 brw-r----- 2 root operator 4, 0x0002000d Apr 26 09:05 sd1s1f 0 brw-r----- 2 root operator 4, 0x0002000e Apr 26 09:05 sd1s1g 0 brw-r----- 2 root operator 4, 0x0002000f Apr 26 09:05 sd1s1h 0 brw-r----- 2 root operator 4, 0x00010012 Apr 26 09:05 sd2 0 brw-r----- 2 root operator 6, 0 Apr 26 09:05 cd0a 0 brw-r----- 2 root operator 6, 2 Apr 26 09:05 cd0c 0 brw-r----- 2 root operator 6, 8 Apr 26 09:05 cd1a 0 brw-r----- 2 root operator 6, 10 Apr 26 09:05 cd1c -- _____________________________________________________________________________ Boyd Faulkner "The fates lead him who will; faulkner@asgard.bga.com Him who won't, they drag." http://asgard.bga.com/~faulkner Old Roman Saying -- Source: Joseph Campbell _____________________________________________________________________________ From owner-freebsd-current Fri Apr 26 11:19:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA23390 for current-outgoing; Fri, 26 Apr 1996 11:19:00 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA23385 for ; Fri, 26 Apr 1996 11:18:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id EAA21005; Sat, 27 Apr 1996 04:07:09 +1000 Date: Sat, 27 Apr 1996 04:07:09 +1000 From: Bruce Evans Message-Id: <199604261807.EAA21005@godzilla.zeta.org.au> To: bde@zeta.org.au, faulkner@asgard.bga.com Subject: Re: Anybody else see these in -current? Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Yes, devfs isn't finished yet. Don't use it unless you want to debug it. >>... >I tried to use it this morning. I supped current last night. >I added a line in /etc/fstab >devfs /dev devfs rw 1 1 >after >/dev/sd1a / ufs rw 1 1 >/dev/sd1s1b none swap sw >The machine failed to mount my partitions. It even says so. >If I mount on /devfs, the devfs mounts fine and the dev entries cited below >are seen. What's up? Mounting on /dev hides the working entries. Some of the devfs entries are invisible until you look at them (in /dev where they are visible) :-). Don't use it unless you want to fix the bugs in it. Bruce From owner-freebsd-current Fri Apr 26 16:03:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA09922 for current-outgoing; Fri, 26 Apr 1996 16:03:57 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA09917 for ; Fri, 26 Apr 1996 16:03:56 -0700 (PDT) Received: by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA12516; Fri, 26 Apr 1996 16:03:58 -0700 Date: Fri, 26 Apr 1996 16:03:58 -0700 (PDT) From: "Brian N. Handy" To: freebsd-current@freebsd.org Subject: CDR support Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey Folks, I've dug and dug and I can't find the answer to this now. Is there a driver in existence that would allow me to use a Phillips CDD522 CD recorder? I have the CDR here at work, I have the -current-snap box at home....is it worth my while to unite the two and see what I can do? Thanks, Brian From owner-freebsd-current Fri Apr 26 16:24:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA10920 for current-outgoing; Fri, 26 Apr 1996 16:24:23 -0700 (PDT) Received: from biblioteca.campus.unal.edu.co ([200.21.26.198]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA10907 for ; Fri, 26 Apr 1996 16:24:06 -0700 (PDT) From: root@biblioteca.campus.unal.edu.co Received: by biblioteca.campus.unal.edu.co (AIX 3.2/UCB 5.64/4.03) id AA07104; Fri, 26 Apr 1996 18:23:16 -0400 Date: Fri, 26 Apr 1996 18:23:16 -0400 (EDT) To: current@FreeBSD.org Subject: MH mail: part II Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, I was out of the network for some time, and couldn`t reply against all (correctly argumented) comentaries against MH. I will be honest: I don`t like, or even use the MH package, in fact I don`t consider it an application by itself. The main reason I proposed it included is that it is a nonsense to install xmh to find out it won`t run unless you add the mh package. It should be an OPTION, right from the start. Even more, it is documented in the original BSD manuals. There is a filosofical problem involved, what kind of system should FreeBSD be? A system that runs by default all the traditional UNIX (including MH), or a linuxed version of that old UNIX. (Don`t feel offended, I like Linux, and it definitely is an example to be followed). The answer, very probably is something in between, but the controversy over the inclusion of MH must be left open. regards, Pedro. From owner-freebsd-current Fri Apr 26 16:27:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA11060 for current-outgoing; Fri, 26 Apr 1996 16:27:39 -0700 (PDT) Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA11055 for ; Fri, 26 Apr 1996 16:27:38 -0700 (PDT) Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.7.4/8.6.5) with ESMTP id QAA14098 for ; Fri, 26 Apr 1996 16:27:01 -0700 (PDT) Received: (from steve@localhost) by delphi.gordian.com (8.7.2/8.6.9) id QAA03029; Fri, 26 Apr 1996 16:27:00 -0700 (PDT) Date: Fri, 26 Apr 1996 16:27:00 -0700 (PDT) Message-Id: <199604262327.QAA03029@delphi.gordian.com> From: Steve Khoo To: freebsd-current@FreeBSD.org Subject: FreeBSD 2.2-CURRENT(sup'd 4/24/96) and XFree86 3.1.2D problem Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Has anyone seen this problem? I'm sending this to freebsd-current because I'm not sure if it's a XFree problem or FreeBSD problem. Please forgive me if it doesn't belong on this list. Thanks! SEK Date: Fri, 26 Apr 1996 11:57:57 -0700 (PDT) From: Steve Khoo To: xfree86-beta@XFree86.org CC: steve Subject: [steve@delphi.gordian.com: XFree86 Beta Test Report] I just reported this to report@XFree86.org. Has anyone seen this problem before? I didn't find anything in the FAQ or the know problem list. I just requested yesterday to be added to the xfree86-beta list and haven't got a response yet. Please reply to me directly. Also, is there an archive of xfree86-beta list that I can browse to see if this problem has been discussed already? Thanks! SEK ------- Start of forwarded message ------- Date: Fri, 26 Apr 1996 11:51:25 -0700 (PDT) From: Steve Khoo To: report@XFree86.org CC: steve Subject: XFree86 Beta Test Report VERSION: 3.1.2D XSERVER: XF86_S3 OPERATING SYSTEM: FreeBSD 2.2-CURRENT sup'd Wed Apr 24th. VIDEO CARD: MODEL: Diamond Stealth Video 2001 GRAPHICS CHIPSET: S3 Trio64V+ RAMDAC: Trio64V+ builtin RAMDAC CLOCKCHIP: Trio64V+ builtin clockchip VIDEO MEMORY: 2MB DRAM BUS TYPE: PCI REPORT: System lockup at xserver startup with 32MB of RAM; not just a video display problem. The entire system hangs with no network, disk or keyboard activity. If RAM is reduced to 16MB all is well. System configuration: ASUS P55TP4XEG(512K PB Cache) 32MB RAM Diamond Stealth Video 2001 (2MB DRAM) ASUS SC-200 PCI SCSI controller(NCR 810 based) DEC 1.6 GB SCSI drive I'd appreciate any help you can provide in resolving this problem. Thanks! SEK ---------------------------------------------------------------------- Steve E. Khoo Gordian Systems Manager 20361 Irvine Ave Internet: steve@gordian.com Santa Ana Heights, CA 92707 Phone: (714)850-0205 FAX: (714)850-0533 ---------------------------------------------------------------------- ------- End of forwarded message ------- From owner-freebsd-current Fri Apr 26 17:43:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA14294 for current-outgoing; Fri, 26 Apr 1996 17:43:43 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA14289 for ; Fri, 26 Apr 1996 17:43:41 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA28476; Fri, 26 Apr 1996 17:37:59 -0700 From: Terry Lambert Message-Id: <199604270037.RAA28476@phaeton.artisoft.com> Subject: Re: FreeBSD 2.2-CURRENT(sup'd 4/24/96) and XFree86 3.1.2D problem To: steve@gordian.com (Steve Khoo) Date: Fri, 26 Apr 1996 17:37:59 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <199604262327.QAA03029@delphi.gordian.com> from "Steve Khoo" at Apr 26, 96 04:27:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Has anyone seen this problem? I'm sending this to freebsd-current > because I'm not sure if it's a XFree problem or FreeBSD problem. > Please forgive me if it doesn't belong on this list. > VIDEO CARD: > > MODEL: > > Diamond Stealth Video 2001 > > GRAPHICS CHIPSET: > > S3 Trio64V+ > > RAMDAC: > > Trio64V+ builtin RAMDAC > > CLOCKCHIP: > > Trio64V+ builtin clockchip > > VIDEO MEMORY: > > 2MB DRAM > > BUS TYPE: > > PCI > > REPORT: > > System lockup at xserver startup with 32MB of RAM; not just a video > display problem. The entire system hangs with no network, disk or > keyboard activity. If RAM is reduced to 16MB all is well. How frigging bizarre! We have several of these video cards (version number 67) that exhibit these same symptoms when used with WINICE in Windows95. If you reduce the system ram to 16M, or if you replace the thing with a version number 89 of the card firmware, the problem goes away. We can get it to lock up after a while pounding on the mode switch registers (in-and-out-and-in-and-out... of WINICE) in 16M. The v89 card doesn't lock up at all. This is on Micron P166 systems. I've been looking for "bus on time" settings, on the thoury that DRAM refresh is being missed when the card grabs the PCI bus, but haven't found anything useful. We're waiting on rev 89 cards now. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Apr 26 17:54:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA15510 for current-outgoing; Fri, 26 Apr 1996 17:54:58 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA15505 for ; Fri, 26 Apr 1996 17:54:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id RAA02139; Fri, 26 Apr 1996 17:54:31 -0700 (PDT) To: "Brian N. Handy" cc: freebsd-current@FreeBSD.ORG Subject: Re: CDR support In-reply-to: Your message of "Fri, 26 Apr 1996 16:03:58 PDT." Date: Fri, 26 Apr 1996 17:54:31 -0700 Message-ID: <2137.830566471@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hey Folks, > > I've dug and dug and I can't find the answer to this now. Is there a > driver in existence that would allow me to use a Phillips CDD522 CD > recorder? I have the CDR here at work, I have the -current-snap box at Mmmmmmmmmaybe.. :-) > home....is it worth my while to unite the two and see what I can do? Sure, why not? See what the worm driver makes of it. Jordan From owner-freebsd-current Fri Apr 26 22:24:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA27435 for current-outgoing; Fri, 26 Apr 1996 22:24:25 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA27430 for ; Fri, 26 Apr 1996 22:24:23 -0700 (PDT) Received: by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA15519; Fri, 26 Apr 1996 22:24:23 -0700 Date: Fri, 26 Apr 1996 22:24:23 -0700 (PDT) From: "Brian N. Handy" To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: CDR support In-Reply-To: <2137.830566471@time.cdrom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I've dug and dug and I can't find the answer to this now. Is there a > > driver in existence that would allow me to use a Phillips CDD522 CD > > recorder? I have the CDR here at work, I have the -current-snap box at > > Mmmmmmmmmaybe.. :-) > > > home....is it worth my while to unite the two and see what I can do? > > Sure, why not? See what the worm driver makes of it. Argh...I've run out of time. I have to get on a plane and spent all next week on the right coast. Next weekend I'll hook this up and report back, I think I understand how to do it. Laterz, Brian From owner-freebsd-current Sat Apr 27 02:34:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA08516 for current-outgoing; Sat, 27 Apr 1996 02:34:29 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA08506 for ; Sat, 27 Apr 1996 02:34:15 -0700 (PDT) Received: by sequent.kiae.su id AA29897 (5.65.kiae-2 ); Sat, 27 Apr 1996 13:23:48 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 27 Apr 96 13:23:48 +0400 Received: (from ache@localhost) by astral.msk.su (8.7.5/8.7.3) id NAA00380; Sat, 27 Apr 1996 13:23:53 +0400 (MSD) Message-Id: <199604270923.NAA00380@astral.msk.su> Subject: local router<->router UDP traffic: log_in_vain stuff error To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), current@freebsd.org (FreeBSD-current) Date: Sat, 27 Apr 1996 13:23:52 +0400 (MSD) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL15 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It was RIP packets from my service provider which cause local router to router UDP traffic. It seems that kernel treats remote UDP traffic as local when udp.log_in_vain used. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sat Apr 27 02:57:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA09280 for current-outgoing; Sat, 27 Apr 1996 02:57:58 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA09275 for ; Sat, 27 Apr 1996 02:57:56 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0uD6km-0003xdC; Sat, 27 Apr 96 02:57 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id JAA02750; Sat, 27 Apr 1996 09:57:06 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), current@FreeBSD.org (FreeBSD-current) Subject: Re: local router<->router UDP traffic: log_in_vain stuff error In-reply-to: Your message of "Sat, 27 Apr 1996 13:23:52 +0400." <199604270923.NAA00380@astral.msk.su> Date: Sat, 27 Apr 1996 09:57:05 +0000 Message-ID: <2748.830599025@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It was RIP packets from my service provider which cause > local router to router UDP traffic. It seems that kernel > treats remote UDP traffic as local when udp.log_in_vain used. Uhm this doesn't make any sense to me, the log_in_vain change was the addition of this bit of code: if (log_in_vain) log(LOG_INFO, "Connection attempt to UDP %s:%d" " from %s:%d\n", inet_ntoa(ip->ip_dst), ntohs(uh->uh_dport), inet_ntoa(ip->ip_src), ntohs(uh->uh_sport)); There is no change in the handling of it. Are you sure you're not looking at syslog sending the log entries to a remote host ??? -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-current Sat Apr 27 06:03:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA15793 for current-outgoing; Sat, 27 Apr 1996 06:03:35 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA15783 for ; Sat, 27 Apr 1996 06:03:24 -0700 (PDT) Received: by sequent.kiae.su id AA08760 (5.65.kiae-2 ); Sat, 27 Apr 1996 16:54:33 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sat, 27 Apr 96 16:54:32 +0400 Received: (from ache@localhost) by astral.msk.su (8.7.5/8.7.3) id QAA07239; Sat, 27 Apr 1996 16:09:50 +0400 (MSD) Message-Id: <199604271209.QAA07239@astral.msk.su> Subject: Re: local router<->router UDP traffic: log_in_vain stuff error To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Sat, 27 Apr 1996 16:09:49 +0400 (MSD) Cc: joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.org In-Reply-To: <2748.830599025@critter.tfs.com> from "Poul-Henning Kamp" at "Apr 27, 96 09:57:05 am" From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL15 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > It was RIP packets from my service provider which cause > > local router to router UDP traffic. It seems that kernel > > treats remote UDP traffic as local when udp.log_in_vain used. > > Uhm this doesn't make any sense to me, the log_in_vain change was the > addition of this bit of code: > > if (log_in_vain) > log(LOG_INFO, "Connection attempt to UDP %s:%d" > " from %s:%d\n", > inet_ntoa(ip->ip_dst), ntohs(uh->uh_dport), > inet_ntoa(ip->ip_src), ntohs(uh->uh_sport)); > Maybe ip->ip_src not properly evaluated there. More detailed info: on each 16:06:38.000523 d1.z194-58-227.relcom.ru.router > d133.z194-58-229.relcom.ru.router: rip-resp 2: 0.0.0.0(3)[|rip] I got Apr 27 16:06:38 astral /kernel: Connection attempt to UDP 194.58.229.133:520 from 194.58.229.133:520 194.58.229.133 is my address. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sat Apr 27 08:49:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA21884 for current-outgoing; Sat, 27 Apr 1996 08:49:17 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA21879 for ; Sat, 27 Apr 1996 08:49:14 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id LAA00183; Sat, 27 Apr 1996 11:46:52 -0400 (EDT) Date: Sat, 27 Apr 1996 11:46:52 -0400 (EDT) From: Kim Culhan To: current@freebsd.org Subject: can't change -current kernel file Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Trying to install a new kernel I find it is impossible to change the name or rm the present kernel file. I can't cp the new kernel to /, can't rm the present one, can't mv the present kernel file, the error returned is: Operation not permitted It is not possible to change the file mode to make it writeable by root. Any help on this one is greatly appreciated. regards kim -- kimc@w8hd.org From owner-freebsd-current Sat Apr 27 09:32:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24119 for current-outgoing; Sat, 27 Apr 1996 09:32:48 -0700 (PDT) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA24114 for ; Sat, 27 Apr 1996 09:32:45 -0700 (PDT) Received: (from alex@localhost) by zen.nash.org (8.7.5/8.6.12) id LAA06567; Sat, 27 Apr 1996 11:34:42 -0500 (CDT) Date: Sat, 27 Apr 1996 11:34:42 -0500 (CDT) Message-Id: <199604271634.LAA06567@zen.nash.org> From: Alex Nash To: kimc@w8hd.org Cc: current@freebsd.org Subject: RE: can't change -current kernel file Reply-to: nash@mcs.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I can't cp the new kernel to /, can't rm the present one, can't mv > the present kernel file, the error returned is: > Operation not permitted You have to turn off the system immutable flag by typing: chflags noschg /kernel Once you've copied the new kernel, you may want to turn it back on with: chflags schg /kernel Alex From owner-freebsd-current Sat Apr 27 09:36:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24223 for current-outgoing; Sat, 27 Apr 1996 09:36:14 -0700 (PDT) Received: from distortion.eng.umd.edu (distortion.eng.umd.edu [129.2.98.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA24217 for ; Sat, 27 Apr 1996 09:36:12 -0700 (PDT) Received: from thurston.eng.umd.edu (thurston.eng.umd.edu [129.2.98.206]) by distortion.eng.umd.edu (8.7.5/8.7.3) with ESMTP id MAA25098; Sat, 27 Apr 1996 12:36:10 -0400 (EDT) Received: (from chuckr@localhost) by thurston.eng.umd.edu (8.7.5/8.7.3) id MAA07238; Sat, 27 Apr 1996 12:36:09 -0400 (EDT) Date: Sat, 27 Apr 1996 12:36:09 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@thurston.eng.umd.edu To: Kim Culhan cc: current@freebsd.org Subject: Re: can't change -current kernel file In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Apr 1996, Kim Culhan wrote: > > Trying to install a new kernel I find it is impossible to change the > name or rm the present kernel file. > > I can't cp the new kernel to /, can't rm the present one, can't mv > the present kernel file, the error returned is: > Operation not permitted > > It is not possible to change the file mode to make it writeable by root. > > Any help on this one is greatly appreciated. The easiest way to install the new kernel (after you build it) is just to do a 'make install' in the kernel build directory. If you want to do this manually, tho, the kernel is protected by file system flags, so go take a look at the chflags manpage. Probably your best bet is to take a look at what the Makefile is doing, actually, when it does an install: chflags noschg /kernel mv /kernel /kernel.old if [ `sysctl -n kern.bootfile` = /kernel ] ; then sysctl -w kern.bootfile=/kernel.old ; mv -f /var/db/kvm_kernel.db /var/db/kvm_kernel.old.db ; fi install -c -m 555 -o root -g wheel -fschg kernel / ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-current Sat Apr 27 09:36:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24261 for current-outgoing; Sat, 27 Apr 1996 09:36:42 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA24254 for ; Sat, 27 Apr 1996 09:36:40 -0700 (PDT) Received: by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA16841; Sat, 27 Apr 1996 09:36:40 -0700 Date: Sat, 27 Apr 1996 09:36:40 -0700 (PDT) From: "Brian N. Handy" To: Kim Culhan Cc: current@freebsd.org Subject: Re: can't change -current kernel file In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Apr 1996, Kim Culhan wrote: > Trying to install a new kernel I find it is impossible to change the > name or rm the present kernel file. The simplest way to do this is after you've done "make depend; make" is to do a "make install". Perusing the Makefile, we have in more detail: chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel / I skipped a couple of steps here...at this point you need to reboot to get your new kernel working. Good luck and Godspeed, Brian From owner-freebsd-current Sat Apr 27 09:44:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24482 for current-outgoing; Sat, 27 Apr 1996 09:44:11 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA24477 for ; Sat, 27 Apr 1996 09:44:08 -0700 (PDT) Received: (from jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) id JAA15205; Sat, 27 Apr 1996 09:44:04 -0700 (PDT) Date: Sat, 27 Apr 1996 09:44:04 -0700 (PDT) From: John Polstra Message-Id: <199604271644.JAA15205@austin.polstra.com> To: kimc@w8hd.org Subject: Re: can't change -current kernel file Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article kimc writes: > > Trying to install a new kernel I find it is impossible to change the > name or rm the present kernel file. > > I can't cp the new kernel to /, can't rm the present one, can't mv > the present kernel file, the error returned is: > Operation not permitted > > It is not possible to change the file mode to make it writeable by root. chflags noschg /kernel -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Apr 27 09:46:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24619 for current-outgoing; Sat, 27 Apr 1996 09:46:45 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA24614 for ; Sat, 27 Apr 1996 09:46:42 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.6.12) with ESMTP id JAA15176; Sat, 27 Apr 1996 09:41:33 -0700 (PDT) Message-Id: <199604271641.JAA15176@austin.polstra.com> To: ache@astral.msk.su, phk@critter.tfs.com Cc: joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.ORG Subject: Re: local router<->router UDP traffic: log_in_vain stuff error In-reply-to: <199604271209.QAA07239@astral.msk.su> Date: Sat, 27 Apr 1996 09:41:33 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Uhm this doesn't make any sense to me, the log_in_vain change was the > > addition of this bit of code: > > > > if (log_in_vain) > > log(LOG_INFO, "Connection attempt to UDP %s:%d" > > " from %s:%d\n", > > inet_ntoa(ip->ip_dst), ntohs(uh->uh_dport), > > inet_ntoa(ip->ip_src), ntohs(uh->uh_sport)); > > > > Maybe ip->ip_src not properly evaluated there. Inet_ntoa formats its result into a static buffer. It doesn't work to have two calls to it in a single expression. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Apr 27 10:29:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26171 for current-outgoing; Sat, 27 Apr 1996 10:29:52 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA26165 for ; Sat, 27 Apr 1996 10:29:48 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with SMTP id OAA13812 ; Sat, 27 Apr 1996 14:16:28 +0100 (BST) To: root@biblioteca.campus.unal.edu.co cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: MH mail: part II In-reply-to: Your message of "Fri, 26 Apr 1996 18:23:16 EDT." Date: Sat, 27 Apr 1996 14:16:27 +0100 Message-ID: <13810.830610987@palmer.demon.co.uk> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk root@biblioteca.campus.unal.edu.co wrote in message ID : > I was out of the network for some time, and couldn`t reply against all > (correctly argumented) comentaries against MH. At a guess, you were proposing that MH should be in the base distribution? *SHUDDER* > The main reason I proposed it included is that it is a nonsense to > install xmh to find out it won`t run unless you add the mh package. That is not something we have much control over. XMH is part of the release from the X Consortium, and hence is in the XFree86 release. Why it is there, I have no idea. > It should be an OPTION, right from the start. Even more, it is documented > in the original BSD manuals. It is an option ... if you go to the package installation screen. Which ``original BSD manuals'' are you referring to? A quick glance through /usr/share/doc shows that MH is treated as CONTRIBUTED software, NOT part of the system, and I am fairly certain that a glance through a 4.4 Lite tape (or CDROM) will show that MH is NOT built or installed by default. How MH got into the USM section is anybodys guess. > There is a filosofical problem involved, what kind of system should > FreeBSD be? A system that runs by default all the traditional UNIX > (including MH), or a linuxed version of that old UNIX. (Don`t feel > offended, I like Linux, and it definitely is an example to be followed). MH is in no way (that I know of) ``traditional UNIX'' ... ``mail'' (found in /usr/bin on FreeBSD) is the ``traditional'' interface to the mail system, not the Rand MH system. As for ``runs by default'', MH is supplied PRE-COMPILED in the packages collection. What more could you ask for? If you are still saying that we should put MH into the main CVS tree and release it as part of FreeBSD proper, rather than a port/package, you're in for a disappointment. That will never happen. We are trying to avoid putting large, un-necessary chunks of source code into the system. Heck, if we put MH in, we'd have people clamouring for their favourite mailer to go in, and we'd shortly have Pine and Elm in there too. And then someone would need their favourite editor in there too, and suddenly Emacs would find its way in, and shortly you'd need to dedicate a 2Gb disk JUST for the bin distribution. Do you want that? And I doubt that any Linux distribution would install MH by default, but (at least for Slackware) it will probably offer you that option in the hundreds of questions it throws at you. FreeBSD pushes all TRULY ``optional'' software into the packages collection. You will not find MH included with any commercial Unix variants that I know of, and I don't see why (in this case) FreeBSD should be any different. I like MH (a lot), and it has been my mailer of choice for well over 3 years, but I am TOTALLY against seeing this (or any other *non-essential* third party software) becoming part of FreeBSD. > The answer, very probably is something in between, but the controversy > over the inclusion of MH must be left open. The answer already exists. It's the packages collection, which since 2.1R (and possibly 2.0.5R, I can't remember) you are offered the opportunity of browsing and installing stuff from AT INSTALL TIME. That is not controversial, and the discussion about inclusion of MH in the base system is at an end. It just won't happen. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD - Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info. From owner-freebsd-current Sat Apr 27 13:27:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05540 for current-outgoing; Sat, 27 Apr 1996 13:27:32 -0700 (PDT) Received: from yoda.fdt.net (root@yoda.fdt.net [205.229.48.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05534 for ; Sat, 27 Apr 1996 13:27:28 -0700 (PDT) Received: from Kryten.nina.com (dyn054-gnv.51.fdt.net [205.229.51.55]) by yoda.fdt.net (8.6.12/8.6.9) with SMTP id QAA15559; Sat, 27 Apr 1996 16:27:29 -0400 Date: Sat, 27 Apr 1996 16:25:41 -0400 (EDT) From: Frank Seltzer X-Sender: frankd@Kryten.nina.com To: Kim Culhan cc: current@FreeBSD.ORG Subject: Re: can't change -current kernel file In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Apr 1996, Kim Culhan wrote: > > Trying to install a new kernel I find it is impossible to change the > name or rm the present kernel file. > > I can't cp the new kernel to /, can't rm the present one, can't mv > the present kernel file, the error returned is: > Operation not permitted > > It is not possible to change the file mode to make it writeable by root. > > Any help on this one is greatly appreciated. Did you try make install to install it? This will rename the old kernel and copy the new one to / Frank From owner-freebsd-current Sat Apr 27 13:56:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA07136 for current-outgoing; Sat, 27 Apr 1996 13:56:13 -0700 (PDT) Received: from moonpie.w8hd.org (moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA07129 for ; Sat, 27 Apr 1996 13:56:10 -0700 (PDT) Received: (from kimc@localhost) by moonpie.w8hd.org (8.7.5/8.6.12) id QAA00586; Sat, 27 Apr 1996 16:53:46 -0400 (EDT) Date: Sat, 27 Apr 1996 16:53:46 -0400 (EDT) From: Kim Culhan To: current@FreeBSD.ORG Subject: Re: can't change -current kernel file In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks to all who answered question about installing a new kernel. Of course the easy answer is "use 'make install'" from the kernel build directory. regards kim -- kimc@w8hd.org From owner-freebsd-current Sat Apr 27 14:03:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA07463 for current-outgoing; Sat, 27 Apr 1996 14:03:09 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA07458 for ; Sat, 27 Apr 1996 14:03:05 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.5/3.4W4-SMTP) with ESMTP id GAA01774; Sun, 28 Apr 1996 06:04:39 +0900 (JST) Message-Id: <199604272104.GAA01774@mail.tky007.tth.expo96.ad.jp> To: freebsd-current@freebsd.org Cc: max@sfc.wide.ad.jp Subject: problems with comconsole of current kernel From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= Reply-To: max@sfc.wide.ad.jp X-Mailer: Mew version 1.05+ on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 28 Apr 1996 06:04:38 +0900 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've been using boot block compiled with FORCE_COMCONSOLE macro defined and it has been working fine until I changed my kernel to the current one. (It works OK with kernel from 04/22.) First, when I boot up the system, message as follows appears on the screen of PC that is connected to the com1 of the FreeBSD box: Serial console forced. >> FreeBSD BOOT @ 0x10000: 640/31744 k of memory Usage: [[[0:][wd](0,a)]/kernel][-abcCdhrsv] Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1 Use ? for file list or press Enter for defaults Boot: dosdev = 80, biosdrive = 0, unit = 0, maj = 0 Booting 0:wd(0,a)/kernel @ 0x100000 text=0xe8000 data=0x14000 bss=0x13cac symbols=[+0x354+0x4+0x109c8+0x4+0x150f2] total=0x235ac2 entry point=0x100000 After showing this message, FreeBSD disconnects the serial line (I think it's dropping the carrier detect.) and no message is displayed. After system boots up, I can login from the com1 OK, but no message to the console is sent to the com1. Also, while I'm logged in, let's say I want to transfer some files using zmodem and executed rz on FreeBSD. Then I execute sz on DOS (on the machine that is connected to the com1.). Usually, this procedure sends files from the PC to the FreeBSD box without problem. However, with the current kernel, sz on DOS box doesn't even start transfering the files and when I abort the transfer and try to get back to FreeBSD prompt, I'm logged out automatically. Does anyone have any idea what I may be doing wrong? Thanks in advance. ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : t94303mn@sfc.keio.ac.jp / max@sfc.wide.ad.jp [URL] : http://www.sfc.keio.ac.jp/~t94303mn From owner-freebsd-current Sat Apr 27 16:06:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA14384 for current-outgoing; Sat, 27 Apr 1996 16:06:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA14378 for ; Sat, 27 Apr 1996 16:06:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id JAA09430; Sun, 28 Apr 1996 09:01:32 +1000 Date: Sun, 28 Apr 1996 09:01:32 +1000 From: Bruce Evans Message-Id: <199604272301.JAA09430@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, max@sfc.wide.ad.jp Subject: Re: problems with comconsole of current kernel Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been using boot block compiled with FORCE_COMCONSOLE macro >defined and it has been working fine until I changed my kernel to the >current one. (It works OK with kernel from 04/22.) What are the kernel and bootblock versions exactly? Not much has changed since 04/22. > First, when I boot up the system, message as follows appears on >the screen of PC that is connected to the com1 of the FreeBSD box: >Serial console forced. >>> FreeBSD BOOT @ 0x10000: 640/31744 k of memory >Usage: [[[0:][wd](0,a)]/kernel][-abcCdhrsv] >Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1 >Use ? for file list or press Enter for defaults >Boot: >dosdev = 80, biosdrive = 0, unit = 0, maj = 0 I broke the BOOTWAIT timeout for the FORCE_COMCONSOLE case some time before the change that introduced printing of the drive numbers, but since the boot didn't hang, this is probably not your problem. >Booting 0:wd(0,a)/kernel @ 0x100000 >text=0xe8000 data=0x14000 bss=0x13cac symbols=[+0x354+0x4+0x109c8+0x4+0x150f2] >total=0x235ac2 entry point=0x100000 >After showing this message, FreeBSD disconnects the serial line (I >think it's dropping the carrier detect.) and no message is displayed. It's certainly a problem in the console part of the serial driver. This part hasn't changed for a year or two :-). Bruce From owner-freebsd-current Sat Apr 27 16:19:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA14938 for current-outgoing; Sat, 27 Apr 1996 16:19:45 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA14933 for ; Sat, 27 Apr 1996 16:19:41 -0700 (PDT) Received: from gmarco (ts1port12d.masternet.it [194.184.65.34]) by masternet.it (8.6.12/8.6.9) with SMTP id AAA28702 for ; Sun, 28 Apr 1996 00:17:21 +0200 Message-Id: <2.2.32.19960427231837.006aa0f0@masternet.it> X-Sender: gmarco@masternet.it X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 28 Apr 1996 01:18:37 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: Atapi kernel or FTP ? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello everybody, I have a little (very little... :-) network of 2 pc that I usually use to play network games with friends... The first (all scsi device) runs Freebsd current (delta #1721) without any problems now (thanks to some of you for the hints on the ctm)... The second is another pentium , but with HD & CD rom IDE (Sony cdu 77e). I have the cd with the snap, but there isn't there a kernel ready for the Atapi. So I install firstly the 2.1.0 release (with the atapi floppy), then with ftp I got from the other machine (the scsi one) the ctm src-current.1500A and the others ctm files and began the ctm process. ctm, make world && make install... Is it right ? I receive this error on boot : screensaver : Undefined entry symbol '_saver_init' ld: Spurious undefined symbols: # undefined symbols 1, reported 0 modload : /usr/bin/ld : return code 1 Now I ask : 1) Is it possible to find a atapi.flp for the -current too... So I can reinstall it again using directly the snap cdrom ? I looked for it in Walnut creek ftp site without succeded.. 2) If the previous answer will be no, is it possible to use the other machine's Cdrom scsi to install ? They see perfectly each other ... 10.0.0.(1|2) 3) If I do a make world I need a make install too ? And when I receive a new ctm is correct make && make install or there is a better way to do things ? Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | Fidonet : 2:332/113.0@fidonet | __ | | Amiganet: 39:102/507@amiganet | __/// Gianmarco | | http://www.masternet.it/dsc/gmarco | \XX/ | +-------------------------------------+--------------------+ From owner-freebsd-current Sat Apr 27 16:32:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15642 for current-outgoing; Sat, 27 Apr 1996 16:32:00 -0700 (PDT) Received: from mail.tky007.tth.expo96.ad.jp (root@tky007.tth.expo96.ad.jp [133.246.32.58]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA15637 for ; Sat, 27 Apr 1996 16:31:57 -0700 (PDT) Received: from tky007.tth.expo96.ad.jp (masafumi@localhost [127.0.0.1]) by mail.tky007.tth.expo96.ad.jp (8.7.5/3.4W4-SMTP) with ESMTP id IAA01119; Sun, 28 Apr 1996 08:33:06 +0900 (JST) Message-Id: <199604272333.IAA01119@mail.tky007.tth.expo96.ad.jp> To: bde@zeta.org.au Cc: freebsd-current@FreeBSD.ORG, max@sfc.wide.ad.jp Subject: Re: problems with comconsole of current kernel From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= Reply-To: max@sfc.wide.ad.jp In-Reply-To: Your message of "Sun, 28 Apr 1996 09:01:32 +1000" References: <199604272301.JAA09430@godzilla.zeta.org.au> X-Mailer: Mew version 1.05+ on Emacs 19.28.1, Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 28 Apr 1996 08:33:05 +0900 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Bruce Evans Subject: Re: problems with comconsole of current kernel Date: Sun, 28 Apr 1996 09:01:32 +1000 > What are the kernel and bootblock versions exactly? Not much has > changed since 04/22. Sorry for silly question, but, how do you find out the versions of them? I know each file has revision ID, though. ----------------------------------------------------------------------- Masafumi NAKANE, Keio Univ., Dept. of Environmental Information E-Mail : t94303mn@sfc.keio.ac.jp / max@sfc.wide.ad.jp [URL] : http://www.sfc.keio.ac.jp/~t94303mn From owner-freebsd-current Sat Apr 27 17:18:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA19017 for current-outgoing; Sat, 27 Apr 1996 17:18:12 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA19011 for ; Sat, 27 Apr 1996 17:18:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id RAA09096; Sat, 27 Apr 1996 17:17:31 -0700 (PDT) To: Gianmarco Giovannelli cc: current@freebsd.org Subject: Re: Atapi kernel or FTP ? In-reply-to: Your message of "Sun, 28 Apr 1996 01:18:37 +0200." <2.2.32.19960427231837.006aa0f0@masternet.it> Date: Sat, 27 Apr 1996 17:17:31 -0700 Message-ID: <9094.830650651@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is it right ? I receive this error on boot : > > screensaver : Undefined entry symbol '_saver_init' You have to update your /etc files also from /usr/src/etc > 1) Is it possible to find a atapi.flp for the -current too... So I can It's called boot.flp in -current; the atapi driver is part of the standard distribution. Don't forget to set the RELNAME in the Options editor! Jordan From owner-freebsd-current Sat Apr 27 18:36:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23920 for current-outgoing; Sat, 27 Apr 1996 18:36:34 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA23910 for ; Sat, 27 Apr 1996 18:36:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id TAA02941 for ; Sat, 27 Apr 1996 19:36:02 -0600 (MDT) Message-Id: <199604280136.TAA02941@rover.village.org> To: current@freebsd.org Subject: About to make the jump to -current... Date: Sat, 27 Apr 1996 19:36:01 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a couple of questions about -current. Since it takes me about 15 hours to do a checkout, make world, make install, reboot with the new kernel, etc, etc. I was wondering if I could get my feet wet a little more slowly. I want to build a -current kernel on a -stable system. Is that a reasonable thing to do? Will the resulting kernel work with -stable binaries? Will I need to build the config out of -current in order to configure the kernel, or will the one in -stable be good enough? Also, if I upgrade to -current, would it be good enought to grab jordan's next snapshot and just extract all the binaries from it onto my system and reboot with a -current kernel? Or is there a painless upgrade option in the snapshot? Thank you for your reply... Warner From owner-freebsd-current Sat Apr 27 19:03:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA24888 for current-outgoing; Sat, 27 Apr 1996 19:03:02 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA24883 for ; Sat, 27 Apr 1996 19:02:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id TAA09590; Sat, 27 Apr 1996 19:02:23 -0700 (PDT) To: Warner Losh cc: current@freebsd.org Subject: Re: About to make the jump to -current... In-reply-to: Your message of "Sat, 27 Apr 1996 19:36:01 MDT." <199604280136.TAA02941@rover.village.org> Date: Sat, 27 Apr 1996 19:02:23 -0700 Message-ID: <9588.830656943@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I want to build a -current kernel on a -stable system. Is that a > reasonable thing to do? Will the resulting kernel work with -stable Not as a general rule, no. Things like pstat, w, and other kernel grubbing commands tend to break if something has been changed in the system and you've not also updated your libkvm and friends. > binaries? Will I need to build the config out of -current in order to > configure the kernel, or will the one in -stable be good enough? I can't say for sure given arbitrary values for "A" and "B" here, but it's always a good idea to rebuild config before kernel.. ;-) > Also, if I upgrade to -current, would it be good enought to grab > jordan's next snapshot and just extract all the binaries from it onto > my system and reboot with a -current kernel? Or is there a painless > upgrade option in the snapshot? Yes, you could always just try the snapshot upgrade. That's basically all it does anyway! Jordan From owner-freebsd-current Sat Apr 27 21:38:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA04121 for current-outgoing; Sat, 27 Apr 1996 21:38:34 -0700 (PDT) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA04116 for ; Sat, 27 Apr 1996 21:38:31 -0700 (PDT) Received: from cantina.clinet.fi (root@cantina.clinet.fi [194.100.0.15]) by hauki.clinet.fi (8.7.5/8.6.4) with ESMTP id HAA20914 for ; Sun, 28 Apr 1996 07:38:22 +0300 (EET DST) Received: (hsu@localhost) by cantina.clinet.fi (8.7.3/8.6.4) id HAA22181; Sun, 28 Apr 1996 07:38:21 +0300 (EET DST) Date: Sun, 28 Apr 1996 07:38:21 +0300 (EET DST) Message-Id: <199604280438.HAA22181@cantina.clinet.fi> From: Heikki Suonsivu To: freebsd-current@freebsd.org Subject: Flashy panic for todays sup Organization: Clinet Ltd, Espoo, Finland Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sup of -current from tonight produced a kernel which paniced after probing most devices. It happens very quickly, I see a panic message flashing and then the screen is filled with vertical bars and such and the system reboots. This happens too fast to get a copy of what happened. I'll resup tomorrow and if it persists, I'll add DDB in the kernel and see if I can get anything more out of it. The system is a server configuration ASUS-64M-2940-P90. I can boot up an old 486 ide machine with the same kernel. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121