From owner-freebsd-stable Sun Apr 23 0:28:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dart.sr.se (dart.SR.SE [193.12.91.98]) by hub.freebsd.org (Postfix) with ESMTP id 0CE9937B7D6 for ; Sun, 23 Apr 2000 00:28:20 -0700 (PDT) (envelope-from gunnar@pluto.sr.se) Received: from honken.sr.se ([134.25.128.27]) by dart.sr.se (8.9.3/8.9.3) with ESMTP id JAA38889 for ; Sun, 23 Apr 2000 09:28:13 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id JAA56206 for ; Sun, 23 Apr 2000 09:28:13 +0200 (CEST) (envelope-from gunnar@pluto.sr.se) Received: (from gunnar@localhost) by pluto.sr.se (8.9.3/8.9.3) id JAA10046 for freebsd-stable@freebsd.org; Sun, 23 Apr 2000 09:28:13 +0200 (CEST) (envelope-from gunnar) Date: Sun, 23 Apr 2000 09:28:13 +0200 From: Gunnar Flygt To: FreeBSD Stable Subject: Problems with libtool Message-ID: <20000423092812.A9940@sr.se> Reply-To: Gunnar Flygt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am I the only one having problem with the port /usr/ports/devele/libtool? It was some application that needed libtool-1.3.4 Since then no port needing libtool works anymore, The old one I had was 1.3.3 Now all apps that I try to make as "imlib", "gdbm" and so on claims that libtool is of a too old version to be accepted. If I run libtool --version I get the right 1.3.4 Anyone had dimilar problems? And anyone. How do I back it out to 1.3.3, since the new port is for 1.3.4 -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 0:31:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 2547737B7D6 for ; Sun, 23 Apr 2000 00:31:43 -0700 (PDT) (envelope-from sdt@gmx.net) Received: (qmail 8936 invoked by uid 0); 23 Apr 2000 07:31:34 -0000 Received: from as15-94.brunet.bn (HELO stomper.sdtzone) (202.160.15.94) by mail.gmx.net with SMTP; 23 Apr 2000 07:31:34 -0000 Received: from localhost (sdt@localhost) by stomper.sdtzone (8.9.3/8.9.3) with ESMTP id PAA00897 for ; Sun, 23 Apr 2000 15:18:36 +0800 (BNT) (envelope-from sdt@stomper.sdtzone) Date: Sun, 23 Apr 2000 15:18:36 +0800 (BNT) From: Stefanus Du Toit To: freebsd-stable@freebsd.org Subject: SCSI on ATAPI simulation, cdrecord Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, a short while ago I purchased a new IDE/ATAPI CD Rewriter/Recorder from Kodak. Ever since I've been looking all over the web for information on how to get the thing to work with cdrecord in FreeBSD. Unfortunately cdrecord only seems to work with SCSI drives. I know that Linux has a SCSI-on-ATAPI simulation that allows ATAPI devices to be controlled as if they were SCSI devices (which allows one to use cdrecord with ATAPI burners). Does FreeBSD (I'm running 4.0-STABLE) have anything similar, or is there any other way that I might be able to burn CD-Rs using FreeBSD? Any help would be greatly appreciated. Thanks in advance, -- Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 0:50:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id EFC6B37B918 for ; Sun, 23 Apr 2000 00:50:23 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id RAA48057; Sun, 23 Apr 2000 17:20:20 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id RAA01658; Sun, 23 Apr 2000 17:20:17 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 23 Apr 2000 17:20:17 +0930 (CST) From: "Daniel O'Connor" To: Stefanus Du Toit Subject: RE: SCSI on ATAPI simulation, cdrecord Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Apr-00 Stefanus Du Toit wrote: > a short while ago I purchased a new IDE/ATAPI CD Rewriter/Recorder from > Kodak. Ever since I've been looking all over the web for information on > how to get the thing to work with cdrecord in FreeBSD. Unfortunately > cdrecord only seems to work with SCSI drives. Try looking at the stuff in /usr/share/examples/atapi I haven't tried any of it though :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 1:14:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id A357537B6C7 for ; Sun, 23 Apr 2000 01:14:13 -0700 (PDT) (envelope-from sdt@gmx.net) Received: (qmail 28725 invoked by uid 0); 23 Apr 2000 08:14:07 -0000 Received: from as15-94.brunet.bn (HELO stomper.sdtzone) (202.160.15.94) by mail.gmx.net with SMTP; 23 Apr 2000 08:14:07 -0000 Received: from localhost (sdt@localhost) by stomper.sdtzone (8.9.3/8.9.3) with ESMTP id PAA01471 for ; Sun, 23 Apr 2000 15:58:09 +0800 (BNT) (envelope-from sdt@stomper.sdtzone) Date: Sun, 23 Apr 2000 15:58:06 +0800 (BNT) From: Stefanus Du Toit To: freebsd-stable@freebsd.org Subject: Re: SCSI on ATAPI simulation, cdrecord In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all your quick replies, I will be looking at burncd right now. Keep up the good work, -- Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ On Sun, 23 Apr 2000, Stefanus Du Toit wrote: > Hi, > > a short while ago I purchased a new IDE/ATAPI CD Rewriter/Recorder from > Kodak. Ever since I've been looking all over the web for information on > how to get the thing to work with cdrecord in FreeBSD. Unfortunately > cdrecord only seems to work with SCSI drives. > > I know that Linux has a SCSI-on-ATAPI simulation that allows ATAPI devices > to be controlled as if they were SCSI devices (which allows one to use > cdrecord with ATAPI burners). Does FreeBSD (I'm running 4.0-STABLE) have > anything similar, or is there any other way that I might be able to burn > CD-Rs using FreeBSD? > > Any help would be greatly appreciated. Thanks in advance, > > -- > Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic > mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 2:44: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 77E1C37B5C6 for ; Sun, 23 Apr 2000 02:43:58 -0700 (PDT) (envelope-from sdt@gmx.net) Received: (qmail 15361 invoked by uid 0); 23 Apr 2000 09:43:53 -0000 Received: from as15-94.brunet.bn (HELO stomper.sdtzone) (202.160.15.94) by mail.gmx.net with SMTP; 23 Apr 2000 09:43:53 -0000 Received: from localhost (sdt@localhost) by stomper.sdtzone (8.9.3/8.9.3) with ESMTP id RAA20875 for ; Sun, 23 Apr 2000 17:15:07 +0800 (BNT) (envelope-from sdt@stomper.sdtzone) Date: Sun, 23 Apr 2000 17:15:07 +0800 (BNT) From: Stefanus Du Toit To: freebsd-stable@FreeBSD.org Subject: Re: SCSI on ATAPI simulation, cdrecord (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jens/freebsd-stable, well, I just burnt a CD-R with burncd and it worked fine. I had to remake my /dev/acdx entries, which I forgot after upgrading to 4.0-S, but otherwise everything worked just fine. -- Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ This is with a Kodak 4804IDE CD-R/RW btw. Thanks again for your help, -- Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ On Sun, 23 Apr 2000, Jens Fallesen wrote: > Hi Stefanus, > > [...] > > What you are looking for is the burncd utility (do a man burncd for > more information). However, there have been several reports on the > mailing list that people (including me) have had problems making this > work properly. Please try it out and share your experiences with the > list. > > > -- > Jens Fallesen O- > Hedegaardsvej 41 st th, 2300 Copenhagen S, Denmark > Phone: (+45) 32 86 18 99 * Fax: (+45) 32 86 17 99 > CCIE #5470 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 6:58:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 2A84F37B688 for ; Sun, 23 Apr 2000 06:58:55 -0700 (PDT) (envelope-from sdt@gmx.net) Received: (qmail 14830 invoked by uid 0); 23 Apr 2000 13:58:51 -0000 Received: from as9-99.brunet.bn (HELO stomper.sdtzone) (202.160.9.99) by mail.gmx.net with SMTP; 23 Apr 2000 13:58:51 -0000 Received: from localhost (sdt@localhost) by stomper.sdtzone (8.9.3/8.9.3) with ESMTP id VAA01545 for ; Sun, 23 Apr 2000 21:57:48 +0800 (BNT) (envelope-from sdt@stomper.sdtzone) Date: Sun, 23 Apr 2000 21:57:48 +0800 (BNT) From: Stefanus Du Toit To: freebsd-stable@freebsd.org Subject: Copying CDs (with dd?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, sorry for once again asking here, but after much searching I failed to find any help on this anywhere else again. I am able to burn CD-Rs with burncd, but now need to make a copy of an existing CD. What is the easiest way to simply create an image of the disc? I have tried the following: [sdt]# dd if=/dev/acd1c of=image.raw dd: /dev/acd1c: Bad address 0+0 records in 0+0 records out but as you see this didn't work. I would like to avoid using mkisofs on the directory structure, ideally I'd like to be able to create images of bootable CDs etc. Thanks again in advance, -- Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 7:36:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id DC30037B839 for ; Sun, 23 Apr 2000 07:36:27 -0700 (PDT) (envelope-from sdt@gmx.net) Received: (qmail 4369 invoked by uid 0); 23 Apr 2000 14:36:24 -0000 Received: from as9-99.brunet.bn (HELO stomper.sdtzone) (202.160.9.99) by mail.gmx.net with SMTP; 23 Apr 2000 14:36:24 -0000 Received: from localhost (sdt@localhost) by stomper.sdtzone (8.9.3/8.9.3) with ESMTP id WAA01784 for ; Sun, 23 Apr 2000 22:30:23 +0800 (BNT) (envelope-from sdt@stomper.sdtzone) Date: Sun, 23 Apr 2000 22:30:21 +0800 (BNT) From: Stefanus Du Toit To: freebsd-stable@freebsd.org Subject: Re: Copying CDs (with dd?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I feel so bad for sending so many mails to this list... I was unaware of the mailing list archives, where I have found an answer to this problem. I will in future consult these before posting here :). Thanks anyways, -- Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ On Sun, 23 Apr 2000, Stefanus Du Toit wrote: > Hi, > > sorry for once again asking here, but after much searching I failed to > find any help on this anywhere else again. > > I am able to burn CD-Rs with burncd, but now need to make a copy of an > existing CD. What is the easiest way to simply create an image of the > disc? > > I have tried the following: > [sdt]# dd if=/dev/acd1c of=image.raw > dd: /dev/acd1c: Bad address > 0+0 records in > 0+0 records out > > but as you see this didn't work. > > I would like to avoid using mkisofs on the directory structure, ideally > I'd like to be able to create images of bootable CDs etc. > > Thanks again in advance, > > -- > Stefanus Du Toit * WorldForger * Unix Hacker * Open Source Fanatic > mailto:sdt@gmx.net * http://www.worldforge.org/ * http://ultracool.net/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 10:13:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rumiya.misao-unet.ocn.ne.jp (rumiya.misao-unet.ocn.ne.jp [210.232.115.205]) by hub.freebsd.org (Postfix) with ESMTP id C976C37B999 for ; Sun, 23 Apr 2000 10:13:20 -0700 (PDT) (envelope-from shikuma@misao-unet.ocn.ne.jp) Received: from misao-unet.ocn.ne.jp (misao.misao-unet.ocn.ne.jp [210.232.115.203]) by rumiya.misao-unet.ocn.ne.jp (8.8.8/3.7W) with SMTP id CAA21095 for ; Mon, 24 Apr 2000 02:13:18 +0900 (JST) Date: Mon, 24 Apr 2000 02:12:56 +0900 To: freebsd-stable@FreeBSD.org Subject: Message-Id: <20000424021147.121049086.-1634025480@misao-unet.ocn.ne.jp> From: =?ISO-2022-JP?B?GyRCO003J0JZRzcbKEo=?= MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Mailer: WZ MAIL 4.00B Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 11:25:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A22837B9CC for ; Sun, 23 Apr 2000 11:25:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA62883; Sun, 23 Apr 2000 11:25:27 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 11:25:27 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231825.LAA62883@apollo.backplane.com> To: freebsd-stable@FreeBSD.ORG Subject: MFCing SMP cleanups from -current into 4.x on wednesday Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I intend to MFC the preliminary SMP cleanups I did in current a few weeks ago back into 4.x. My current plan is to do this on wednesday. I do not expect there to be any complains since the SMP cleanups appear to have been working wonderfully in -current for some time now but if people have problems with it I can delay the MFC while we discuss it. I also intend to MFC the changes to the write-behind heuristic on wednesday (search for 'Change the write-behind' in the below -current commits for a reference). Since this is a relatively simple patch which solves a degenerate write-stall case in -current as well as fixes one of those silly contrived benchmarks, I do not expect there to be any complaints. My intention is to try to keep the 4.x and 5.x trees synchronized as much as makes sense in regards to my own core work so people doing add-on work can also MFC as much of it as makes sense. It should be reasonable to do this while we are in the early stages of the release cycle. dillon 2000/03/27 23:16:38 PST Modified files: sys/alpha/alpha trap.c sys/i386/i386 exception.s genassym.c globals.s mp_machdep.c mplock.s simplelock.s support.s swtch.s sys_machdep.c trap.c vm86bios.s vm_machdep.c sys/i386/include asnames.h cpu.h globaldata.h globals.h ipl.h lock.h smptests.h sys/i386/isa apic_ipl.s apic_vector.s ipl.s ipl_funcs.c sys/kern init_sysent.c kern_prot.c kern_sig.c kern_switch.c kern_synch.c subr_prof.c vfs_syscalls.c sys/posix4 ksched.c sys/sys ktrace.h proc.h signalvar.h sysent.h Log: Commit major SMP cleanups and move the BGL (big giant lock) in the syscall path inward. A system call may select whether it needs the MP lock or not (the default being that it does need it). A great deal of conditional SMP code for various deadended experiments has been removed. 'cil' and 'cml' have been removed entirely, and the locking around the cpl has been removed. The conditional separately-locked fast-interrupt code has been removed, meaning that interrupts must hold the CPL now (but they pretty much had to anyway). Another reason for doing this is that the original separate-lock for interrupts just doesn't apply to the interrupt thread mechanism being contemplated. Modifications to the cpl may now ONLY occur while holding the MP lock. For example, if an otherwise MP safe syscall needs to mess with the cpl, it must hold the MP lock for the duration and must (as usual) save/restore the cpl in a nested fashion. This is precursor work for the real meat coming later: avoiding having to hold the MP lock for common syscalls and I/O's and interrupt threads. It is expected that the spl mechanisms and new interrupt threading mechanisms will be able to run in tandem, allowing a slow piecemeal transition to occur. This patch should result in a moderate performance improvement due to the considerable amount of code that has been removed from the critical path, especially the simplification of the spl*() calls. The real performance gains will come later. Approved by: jkh Reviewed by: current, bde (exception.s) Some work taken from: luoqi's patch Revision Changes Path 1.27 +4 -4 src/sys/alpha/alpha/trap.c 1.66 +79 -54 src/sys/i386/i386/exception.s 1.88 +2 -1 src/sys/i386/i386/genassym.c 1.14 +5 -3 src/sys/i386/i386/globals.s 1.116 +3 -1 src/sys/i386/i386/mp_machdep.c 1.30 +39 -249 src/sys/i386/i386/mplock.s 1.12 +6 -1 src/sys/i386/i386/simplelock.s 1.68 +14 -2 src/sys/i386/i386/support.s 1.90 +17 -10 src/sys/i386/i386/swtch.s 1.48 +2 -1 src/sys/i386/i386/sys_machdep.c 1.148 +114 -39 src/sys/i386/i386/trap.c 1.16 +2 -7 src/sys/i386/i386/vm86bios.s 1.134 +7 -7 src/sys/i386/i386/vm_machdep.c 1.45 +3 -4 src/sys/i386/include/asnames.h 1.44 +13 -7 src/sys/i386/include/cpu.h 1.12 +2 -1 src/sys/i386/include/globaldata.h 1.6 +3 -1 src/sys/i386/include/globals.h 1.18 +7 -1 src/sys/i386/include/ipl.h 1.12 +6 -74 src/sys/i386/include/lock.h 1.34 +22 -81 src/sys/i386/include/smptests.h 1.28 +20 -30 src/sys/i386/isa/apic_ipl.s 1.48 +11 -265 src/sys/i386/isa/apic_vector.s 1.33 +29 -92 src/sys/i386/isa/ipl.s 1.34 +64 -179 src/sys/i386/isa/ipl_funcs.c 1.80 +5 -5 src/sys/kern/init_sysent.c 1.54 +15 -2 src/sys/kern/kern_prot.c 1.74 +2 -1 src/sys/kern/kern_sig.c 1.4 +3 -1 src/sys/kern/kern_switch.c 1.88 +2 -1 src/sys/kern/kern_synch.c 1.33 +2 -1 src/sys/kern/subr_prof.c 1.152 +3 -1 src/sys/kern/vfs_syscalls.c 1.8 +2 -1 src/sys/posix4/ksched.c 1.20 +2 -2 src/sys/sys/ktrace.h 1.100 +12 -3 src/sys/sys/proc.h 1.35 +15 -4 src/sys/sys/signalvar.h 1.28 +5 -1 src/sys/sys/sysent.h dillon 2000/03/28 10:06:50 PST Modified files: sys/i386/i386 mplock.s sys/i386/include smp.h sys/kern kern_clock.c kern_mib.c kern_shutdown.c kern_sig.c kern_synch.c sys/sys proc.h signalvar.h Log: The SMP cleanup commit broke UP compiles. Make UP compiles work again. Revision Changes Path 1.31 +9 -1 src/sys/i386/i386/mplock.s 1.51 +19 -2 src/sys/i386/include/smp.h 1.107 +2 -4 src/sys/kern/kern_clock.c 1.30 +1 -4 src/sys/kern/kern_mib.c 1.73 +1 -3 src/sys/kern/kern_shutdown.c 1.75 +1 -3 src/sys/kern/kern_sig.c 1.89 +1 -3 src/sys/kern/kern_synch.c 1.101 +2 -1 src/sys/sys/proc.h 1.36 +1 -3 src/sys/sys/signalvar.h dillon 2000/03/28 22:15:44 PST Modified files: sys/i386/i386 exception.s swtch.s vm86bios.s sys/i386/isa apic_vector.s ipl.s Log: The SMP cleanup commit broke need_resched, this fixes that and also removed unncessary MPLOCKED and 'lock' prefixes from the interrupt nesting level, since (A) the MP lock is held at the time, and (B) since the neting level is restored prior to return any interrupted code will see a consistent value. Revision Changes Path 1.67 +2 -2 src/sys/i386/i386/exception.s 1.91 +2 -2 src/sys/i386/i386/swtch.s 1.17 +2 -2 src/sys/i386/i386/vm86bios.s 1.49 +3 -5 src/sys/i386/isa/apic_vector.s 1.34 +4 -4 src/sys/i386/isa/ipl.s dillon 2000/03/29 01:07:47 PST Modified files: sys/i386/isa ipl.s Log: This should fix the lockups people have been experiencing. I muffed up giving astpending two flag bits. A cmpl $0 had to turn into a bit test. Many thanks to: Alain Thivillon Revision Changes Path 1.35 +2 -2 src/sys/i386/isa/ipl.s dillon 2000/04/01 16:55:31 PST Modified files: sys/gnu/ext2fs ext2_readwrite.c sys/kern vfs_cluster.c vfs_vnops.c sys/sys buf.h file.h vnode.h sys/ufs/ufs ufs_readwrite.c Log: Change the write-behind code to take more care when starting async I/O's. The sequential read heuristic has been extended to cover writes as well. We continue to call cluster_write() normally, thus blocks in the file will still be reallocated for large (but still random) I/O's, but I/O will only be initiated for truely sequential writes. This solves a number of annoying situations, especially with DBM (hash method) writes, and also has the side effect of fixing a number of (stupid) benchmarks. Reviewed-by: mckusick Revision Changes Path 1.19 +4 -2 src/sys/gnu/ext2fs/ext2_readwrite.c 1.94 +30 -9 src/sys/kern/vfs_cluster.c 1.88 +37 -28 src/sys/kern/vfs_vnops.c 1.91 +2 -2 src/sys/sys/buf.h 1.23 +3 -3 src/sys/sys/file.h 1.112 +3 -2 src/sys/sys/vnode.h 1.66 +4 -2 src/sys/ufs/ufs/ufs_readwrite.c dillon 2000/04/02 10:52:44 PDT Modified files: sys/i386/i386 support.s sys/kern init_sysent.c kern_prot.c kern_sig.c Log: Make the sigprocmask() and geteuid() system calls MP SAFE. Expand commentary for copyin/copyout to indicate that they are MP SAFE as well. Reviewed by: msmith Revision Changes Path 1.69 +37 -12 src/sys/i386/i386/support.s 1.81 +4 -4 src/sys/kern/init_sysent.c 1.55 +10 -7 src/sys/kern/kern_prot.c 1.76 +14 -7 src/sys/kern/kern_sig.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 11:35:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DF2FC37B9EA; Sun, 23 Apr 2000 11:35:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA62963; Sun, 23 Apr 2000 11:35:14 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 11:35:14 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231835.LAA62963@apollo.backplane.com> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the same patch I put up for review two weeks ago. I got one positive comment back and nothing else, so I presume nobody has a problem with it. I've been running with it for a while but have only tested it with a few linux applications (Java (jre, jdk), and the oracle installer stuff). http://www.backplane.com/FreeBSD4/linux-script-01.diff This patch fixes #! paths in scripts run under linux emulation, causing /compat/linux to be searched for the script binary when the script is exec'd from a program running under emulation. Often linux applications run scripts to do various things. Without this patch these scripts effectively 'break out' of the linux emulation (for example, use the FreeBSD version of /bin/sh instead of the linux version of /bin/sh) which can cause compatibility problems, especially when the scripts run other utilities that they expect to be the linux version rather then FreeBSD version (install, cat, grep, etc...) I intend to commit this to -current and immediately MFC it to -stable. I don't expect there to be any controversy though I'm sure there is a cleaner way to do it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 11:38:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E52FE37B9CC; Sun, 23 Apr 2000 11:38:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA45498; Sun, 23 Apr 2000 20:37:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 11:35:14 PDT." <200004231835.LAA62963@apollo.backplane.com> Date: Sun, 23 Apr 2000 20:37:51 +0200 Message-ID: <45496.956515071@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231835.LAA62963@apollo.backplane.com>, Matthew Dillon writes: > I intend to commit this to -current and immediately MFC it to -stable. > I don't expect there to be any controversy though I'm sure there is a > cleaner way to do it. I don't see anything justifying an immediate MFC in this patch. Please allow the normal waiting period to elapse before you MFC. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 11:46:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C7FC37B9F2; Sun, 23 Apr 2000 11:46:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA63231; Sun, 23 Apr 2000 11:46:34 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 11:46:34 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231846.LAA63231@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <45496.956515071@critter.freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <200004231835.LAA62963@apollo.backplane.com>, Matthew Dillon writes: : :> I intend to commit this to -current and immediately MFC it to -stable. :> I don't expect there to be any controversy though I'm sure there is a :> cleaner way to do it. : :I don't see anything justifying an immediate MFC in this patch. Please :allow the normal waiting period to elapse before you MFC. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 It's such a simple patch, and it fixes problems that would otherwise exist under 4.x's linux emulation, and it only effects the linux emulation. And I've been running it for a while under 5.x already (as I said). And I put it up for a review 2 weeks ago. And it makes no major infrastructure changes to the core system. Unless you can justify a reason for it NOT to be MFC'd immediately, I see no reason to wait for this particular baby. That is, unless you *like* linux applications that use scripts to start running FreeBSD utilities even when you have all the appropriate linux packages installed! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 11:50:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DC55837BA18; Sun, 23 Apr 2000 11:50:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA45596; Sun, 23 Apr 2000 20:50:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 11:46:34 PDT." <200004231846.LAA63231@apollo.backplane.com> Date: Sun, 23 Apr 2000 20:50:09 +0200 Message-ID: <45594.956515809@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231846.LAA63231@apollo.backplane.com>, Matthew Dillon writes: >:I don't see anything justifying an immediate MFC in this patch. Please >:allow the normal waiting period to elapse before you MFC. > > Unless you can justify a reason for it NOT to be MFC'd immediately, I > see no reason to wait for this particular baby. Sorry, Matt, that is not the way it works. Unless there is an overriding issue, things do not get MFC'ed immediately. You have only cited reasons why it would be much more convenient for you personally to MFC right away, that is not enough to justify an immediate MFC. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 11:55:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 79B3637B52A; Sun, 23 Apr 2000 11:55:08 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA63309; Sun, 23 Apr 2000 11:55:08 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 11:55:08 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231855.LAA63309@apollo.backplane.com> To: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <45496.956515071@critter.freebsd.dk> <200004231846.LAA63231@apollo.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's another good reason to MFC the linux patch on wednesday... that is, to do it at the same time the SMP cleanup is MFC'd, and that is because both patch sets require the linux kernel module to be recompiled and I'd rather not force people to do that twice. The SMP patchset, in fact, requires that all kernel modules be recompiled due to the locks that were removed from the spl*() macros. This is something I would contemplate doing for 4.0->4.1, but not something I would consider for 4.1 onward. Even though 4.0 is the most stable .0 release we've ever had, it's still a .0. I wonder if it makes sense to add a release id to the module header and have the module loader refuse (unless forced) to load modules that are out-of-date with the kernel? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12: 0:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D17D137BA2F; Sun, 23 Apr 2000 12:00:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA45657; Sun, 23 Apr 2000 20:59:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 11:55:08 PDT." <200004231855.LAA63309@apollo.backplane.com> Date: Sun, 23 Apr 2000 20:59:48 +0200 Message-ID: <45655.956516388@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231855.LAA63309@apollo.backplane.com>, Matthew Dillon writes: > There's another good reason to MFC the linux patch on wednesday... > that is, to do it at the same time the SMP cleanup is MFC'd, and that > is because both patch sets require the linux kernel module to be > recompiled and I'd rather not force people to do that twice. Matt, this is not a valid reason either. Unless there is *urgent* and *overriding* reasons, and that basically means that the security-officer says so, all changes must be shaken out in -current first. That's just the way it is Matt. Get used to it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12: 1:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F0E5037B90D; Sun, 23 Apr 2000 12:01:49 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63381; Sun, 23 Apr 2000 12:01:46 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:01:46 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231901.MAA63381@apollo.backplane.com> To: Poul-Henning Kamp Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <45594.956515809@critter.freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <200004231846.LAA63231@apollo.backplane.com>, Matthew Dillon writes: : :>:I don't see anything justifying an immediate MFC in this patch. Please :>:allow the normal waiting period to elapse before you MFC. :> :> Unless you can justify a reason for it NOT to be MFC'd immediately, I :> see no reason to wait for this particular baby. : :Sorry, Matt, that is not the way it works. Unless there is an overriding :issue, things do not get MFC'ed immediately. : :You have only cited reasons why it would be much more convenient for you :personally to MFC right away, that is not enough to justify an immediate :MFC. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 I'm sorry, Poul, but you are going to have to come up with better reasoning then that. Not all changes committed to -current require a waiting period before being MFC'd to stable. Specifically, simple and obvious bug fixes certainly do not need a waiting period. My reasoning has nothing to do with what is or is not personally convenient for me, and frankly your insinuation that it is is rather insulting. After all, look how long I've waited for the SMP patches before considering MFCing those? It sure would have been more convenient for me to MFC them a week after 5.0 stabilized and before I began work on other patch sets but I didn't. Due to the gravity of the changes I thought it would be best to give them a really good test run under 5.x (and note: I received permission from Jordan to MFC the SMP stuff weeks ago, and even with that permission I decided to wait). I do not consider the linux scripting patch to be a major infrastructure change, I consider it to be a simple bug fix. If you have a functional issue with the patch I'm all ears. If you disagree with my assessment of the triviality of the linux scripting patch, then I will ask for a second opinion from someone who is not quite so jaded in regards to my commits... say Jordan or DG. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12: 6:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id F3E3237B690; Sun, 23 Apr 2000 12:06:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA45716; Sun, 23 Apr 2000 21:05:41 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 12:01:46 PDT." <200004231901.MAA63381@apollo.backplane.com> Date: Sun, 23 Apr 2000 21:05:41 +0200 Message-ID: <45714.956516741@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231901.MAA63381@apollo.backplane.com>, Matthew Dillon writes: > I'm sorry, Poul, but you are going to have to come up with better > reasoning then that. > > Not all changes committed to -current require a waiting period before > being MFC'd to stable. Specifically, simple and obvious bug fixes > certainly do not need a waiting period. Matt, This does not apply to your patch. The "simple and obvious" loophole applies to spelling fixes and similar, not to anything which changes behaviour of the system. Your current patch does not qualify for immediate MFC status unless the security officer says so. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12: 9:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 665EE37B64A; Sun, 23 Apr 2000 12:09:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63432; Sun, 23 Apr 2000 12:09:18 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:09:18 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231909.MAA63432@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <45655.956516388@critter.freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <200004231855.LAA63309@apollo.backplane.com>, Matthew Dillon writes: : :> There's another good reason to MFC the linux patch on wednesday... :> that is, to do it at the same time the SMP cleanup is MFC'd, and that :> is because both patch sets require the linux kernel module to be :> recompiled and I'd rather not force people to do that twice. : :Matt, this is not a valid reason either. : :Unless there is *urgent* and *overriding* reasons, and that basically :means that the security-officer says so, all changes must be shaken :out in -current first. : :That's just the way it is Matt. Get used to it. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 I think you're confused, Poul. I've gone over the commits made to the tree by people over the last few months and frankly there are dozens of simultanious -current and -stable commits. A quick check shows that most of them are trivial bug fixes. I will also point out that the current STABLE and CURRENT trees are being treated as a special case. Jordan himself said so! And that he has made a specific statement indicating that people could develop in the 4.x tree due to the potential breakage in the 5.x tree. This seems entirely appropriate to me. If the rules have changed since that announcement, then I recommend that core make an official statement to correct it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:10: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B124F37BA74; Sun, 23 Apr 2000 12:09:58 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA09128; Sun, 23 Apr 2000 12:09:36 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004231909.MAA09128@gndrsh.dnsmgr.net> Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: <200004231855.LAA63309@apollo.backplane.com> from Matthew Dillon at "Apr 23, 2000 11:55:08 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 23 Apr 2000 12:09:36 -0700 (PDT) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's another good reason to MFC the linux patch on wednesday... > that is, to do it at the same time the SMP cleanup is MFC'd, and that > is because both patch sets require the linux kernel module to be > recompiled and I'd rather not force people to do that twice. > > The SMP patchset, in fact, requires that all kernel modules be > recompiled due to the locks that were removed from the spl*() macros. In that case I have a strong objection to the SMP patchset being merged to 4.0. I have kernel modules in object format only that are working now, which this would break :-(. Either way, nothing ever should me an immediate MFC, even a blantant security hole should not be MFC'ed immediately, code needs to be tested, and some other person might find a few niglets that need cleaned up before you MFC it. Who knows, you might even break the system, and an immediate MFC would break both at once. Never, ever should anything be immediatly merged. IMHO, no even spelling fixes, as I have seen those done wrong, patched, and MFC'ed again. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:12:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id BE7B337B9F1; Sun, 23 Apr 2000 12:12:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA45768; Sun, 23 Apr 2000 21:11:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 12:09:18 PDT." <200004231909.MAA63432@apollo.backplane.com> Date: Sun, 23 Apr 2000 21:11:38 +0200 Message-ID: <45766.956517098@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, I will say it this last time: Your patch does not qualify for immediate MFC. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:13:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 1934C37B8E4; Sun, 23 Apr 2000 12:13:25 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA09141; Sun, 23 Apr 2000 12:13:02 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004231913.MAA09141@gndrsh.dnsmgr.net> Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: <200004231909.MAA63432@apollo.backplane.com> from Matthew Dillon at "Apr 23, 2000 12:09:18 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 23 Apr 2000 12:13:02 -0700 (PDT) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : > :In message <200004231855.LAA63309@apollo.backplane.com>, Matthew Dillon writes: > : > :> There's another good reason to MFC the linux patch on wednesday... > :> that is, to do it at the same time the SMP cleanup is MFC'd, and that > :> is because both patch sets require the linux kernel module to be > :> recompiled and I'd rather not force people to do that twice. > : > :Matt, this is not a valid reason either. > : > :Unless there is *urgent* and *overriding* reasons, and that basically > :means that the security-officer says so, all changes must be shaken > :out in -current first. > : > :That's just the way it is Matt. Get used to it. > : > :-- > :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > I think you're confused, Poul. I've gone over the commits made > to the tree by people over the last few months and frankly there > are dozens of simultanious -current and -stable commits. A quick > check shows that most of them are trivial bug fixes. And look at how many of them had to be patched, re-merged, etc. IMHO people are getting way way to loose with MFC right after a commit. I don't even want to see a MFC for a 1 character spelling fixed MFC'ed in less than 3 days anymore. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:22:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5AAC837BA43; Sun, 23 Apr 2000 12:22:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63538; Sun, 23 Apr 2000 12:22:00 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:22:00 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231922.MAA63538@apollo.backplane.com> To: "Rodney W. Grimes" Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <200004231913.MAA09141@gndrsh.dnsmgr.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : :> :-- :> :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 :> :> I think you're confused, Poul. I've gone over the commits made :> to the tree by people over the last few months and frankly there :> are dozens of simultanious -current and -stable commits. A quick :> check shows that most of them are trivial bug fixes. : :And look at how many of them had to be patched, re-merged, etc. IMHO :people are getting way way to loose with MFC right after a commit. I :don't even want to see a MFC for a 1 character spelling fixed MFC'ed :in less than 3 days anymore. : :-- :Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net Perfectly acceptable to me ... *IF* core decides to change the rules they've made for the current development trees (stable and current) and makes an official statement that covers everyone rather then just Matt. I think the work required to accomplish the BSDI merger is overrated anyway (in regards to the source tree). I kinda expected the BSDI people to start working on it immediately but obviously the pace is going to be a lot slower. Core should consider reverting the special rules that were originally created with the expectation of major breakage in 5.x back to the set of rules we had for 3.x and 4.x. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:25:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 9B32137B90D for ; Sun, 23 Apr 2000 12:25:49 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id MAA22710; Sun, 23 Apr 2000 12:25:17 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda22708; Sun Apr 23 12:25:11 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id MAA28564; Sun, 23 Apr 2000 12:25:11 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdD28547; Sun Apr 23 12:24:54 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id MAA00521; Sun, 23 Apr 2000 12:24:53 -0700 (PDT) Message-Id: <200004231924.MAA00521@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdoed516; Sun Apr 23 12:24:49 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.0-STABLE X-Sender: cy To: Matthew Dillon Cc: freebsd-stable@freebsd.org Subject: Linux Emulation Root (was: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday) In-reply-to: Your message of "Sun, 23 Apr 2000 11:35:14 PDT." <200004231835.LAA62963@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Apr 2000 12:24:49 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231835.LAA62963@apollo.backplane.com>, Matthew Dillon writes: > I intend to commit this to -current and immediately MFC it to -stable. > I don't expect there to be any controversy though I'm sure there is a > cleaner way to do it. On a semi-related topic, it would be handy to have a feature, environment variable, table in the kernel, a sysctl variable, etc., to set the Linux emulation root to the real root. For example, the backup component of Legato for Linux (nsrexecd and friends) runs nicely on under Linux emulation, however, recovering files in the root directory sees them placed in the Linux emulation root directory. To work around this I've used a union filesystem that mounted / on another mount point and redirected my restores to it. My questions are: Is there a cleaner way to work around this, e.g. some tunable knob to tune Linux emulation? If not, would anyone else see any use for this kind of feature? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:27:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7AAE137BA15; Sun, 23 Apr 2000 12:27:23 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA45853; Sun, 23 Apr 2000 21:24:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 12:22:00 PDT." <200004231922.MAA63538@apollo.backplane.com> Date: Sun, 23 Apr 2000 21:24:35 +0200 Message-ID: <45851.956517875@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004231922.MAA63538@apollo.backplane.com>, Matthew Dillon writes: > Core should consider reverting the special rules that were originally > created with the expectation of major breakage in 5.x back to > the set of rules we had for 3.x and 4.x. I have no idea what special rules you are talking about for 4.x/5.x. 4.x-stable is a -stable tree and shall be treated as such. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:29: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4529737BA0B; Sun, 23 Apr 2000 12:28:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63577; Sun, 23 Apr 2000 12:28:56 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:28:56 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231928.MAA63577@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <45766.956517098@critter.freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Matt, : :I will say it this last time: : : Your patch does not qualify for immediate MFC. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 And I will say this to you for the last time: Under the current rules my patch DOES qualify for an immediate MFC. Hell, by the current rules developers can commit to 4.x FIRST! And unless you can come up with something better then this superior attitude bullshit, that is what is going to happen in this particular case. Frankly, what it comes down to is that if DG or Jordan ask me to delay, I know they will have a damn good reason for doing so and I will of course delay. But you, Poul, have used up all your brownie points and I'm getting tired of you changing the rules to suit your current whims, and then changing them again to justify your own commits. Your duel-standard is getting rather tired and your words simply do not have any weight with me any more. If core wants to change the current rules, that's fine by me. As I said before I think the breakage that we thought would happen with 5.x due to the BSDI merger that prompted the loose rules for 4.x is overrated, and the rules should probably be reverted back to standard. -Matt Matthew Dillon :phk@FreeBSD.ORG | TCP/IP since RFC 956 :FreeBSD coreteam member | BSD since 4.3-tahoe :Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:29:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id CF54C37BA23 for ; Sun, 23 Apr 2000 12:29:52 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id NAA69704 for ; Sun, 23 Apr 2000 13:30:47 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sun, 23 Apr 2000 13:30:47 -0600 (CST) From: Ryan Thompson To: freebsd-stable@freebsd.org Subject: 4.0 buildworld breakage in pam Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Relevant output from a cvsup/buildworld today is shown below. (Updated src-all and src-crypto in RELENG_4). What am I missing, here? I scanned the archives quickly, but wasn't able to pull up a similar problem. As you can see, I haven't done a buildworld on this machine for a while. Thanks - Ryan Thompson Script started on Sun Apr 23 12:47:11 2000 root@stimpy:/usr/src> uname -a FreeBSD stimpy.sasknow.com 4.0-20000307-CURRENT FreeBSD 4.0-20000307-CURRENT #0: Sun Mar 12 20:59:07 GMT 2000 ryan@stimpy.sasknow.com:/usr/src/sys/compile/STIMPY i386 root@stimpy:/usr/src> cat /etc/make.conf USA_RESIDENT=YES NODESCRYPTLINKS=TRUE root@stimpy:/usr/src> time make buildworld -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/i386 mkdir -p /usr/obj/usr/src/i386/usr/bin mkdir -p /usr/obj/usr/src/i386/usr/lib/compat/aout . . . ===> libpam ===> libpam/modules ===> libpam/modules/pam_cleartext_pass_ok rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c cd /usr/src/lib/libpam/modules/pam_cleartext_pass_ok; make _EXTRADEPEND echo pam_cleartext_pass_ok.so: /usr/obj/usr/src/i386/usr/lib/libskey.a >> .depend ===> libpam/modules/pam_deny rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c cd /usr/src/lib/libpam/modules/pam_deny; make _EXTRADEPEND echo pam_deny.so: /usr/obj/usr/src/i386/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_permit rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_permit/../../../../contrib/libpam/libpam/include -I/usr/src/lib/libpam/modules/pam_permit/../../libpam -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/libpam/modules/pam_permit/../../../../contrib/libpam/modules/pam_permit/pam_permit.c cd /usr/src/lib/libpam/modules/pam_permit; make _EXTRADEPEND echo pam_permit.so: /usr/obj/usr/src/i386/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_radius rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/libpam/libpam/include -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/libpam/modules/pam_radius/pam_radius.c cd /usr/src/lib/libpam/modules/pam_radius; make _EXTRADEPEND echo pam_radius.so: /usr/obj/usr/src/i386/usr/lib/libradius.a /usr/obj/usr/src/i386/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_skey rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_skey/../../../../contrib/libpam/libpam/include -I/usr/src/lib/libpam/modules/pam_skey/../../libpam -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/libpam/modules/pam_skey/pam_skey.c cd /usr/src/lib/libpam/modules/pam_skey; make _EXTRADEPEND echo pam_skey.so: /usr/obj/usr/src/i386/usr/lib/libskey.a /usr/obj/usr/src/i386/usr/lib/libgcc_pic.a >> .depend ===> libpam/modules/pam_ssh rm -f .depend mkdep -f .depend -a -I/usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh -I/usr/obj/usr/src/i386/usr/include /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/log-client.c /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c In file included from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/ssh.h:22, from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/log-client.c:21: /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/rsa.h:22: openssl/bn.h: No such file or directory /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/rsa.h:23: openssl/rsa.h: No such file or directory In file included from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/ssh.h:23, from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/log-client.c:21: /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/cipher.h:20: openssl/des.h: No such file or directory /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/cipher.h:21: openssl/blowfish.h: No such file or directory In file included from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c:48: /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/rsa.h:22: openssl/bn.h: No such file or directory /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/rsa.h:23: openssl/rsa.h: No such file or directory In file included from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/ssh.h:23, from /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/pam_ssh/pam_ssh.c:49: /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/cipher.h:20: openssl/des.h: No such file or directory /usr/src/lib/libpam/modules/pam_ssh/../../../../crypto/openssh/cipher.h:21: openssl/blowfish.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_ssh. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 Stop in /usr/src/lib/libpam. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. 686.5u 158.8s 17:49.21 79.0% 1250+1513k 3907+34314io 90pf+0w root@stimpy:/usr/src> exit root@stimpy:/usr/src> exit Script done on Sun Apr 23 13:05:16 2000 -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:30:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B87B737BAF3; Sun, 23 Apr 2000 12:30:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63599; Sun, 23 Apr 2000 12:30:19 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:30:19 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231930.MAA63599@apollo.backplane.com> To: Poul-Henning Kamp Cc: "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <45851.956517875@critter.freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <200004231922.MAA63538@apollo.backplane.com>, Matthew Dillon writes: : :> Core should consider reverting the special rules that were originally :> created with the expectation of major breakage in 5.x back to :> the set of rules we had for 3.x and 4.x. : :I have no idea what special rules you are talking about for 4.x/5.x. : :4.x-stable is a -stable tree and shall be treated as such. Really, then you have a short memory. Why don't we ask Jordan for a clarification. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:34:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 639F737BA68 for ; Sun, 23 Apr 2000 12:34:29 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e3NK3I321271; Sun, 23 Apr 2000 13:03:18 -0700 (PDT) Date: Sun, 23 Apr 2000 13:03:18 -0700 From: Alfred Perlstein To: Matthew Dillon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFCing SMP cleanups from -current into 4.x on wednesday Message-ID: <20000423130318.E204@fw.wintelcom.net> References: <200004231825.LAA62883@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004231825.LAA62883@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Apr 23, 2000 at 11:25:27AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000423 11:57] wrote: > I intend to MFC the preliminary SMP cleanups I did in current a few > weeks ago back into 4.x. My current plan is to do this on wednesday. > I do not expect there to be any complains since the SMP cleanups appear > to have been working wonderfully in -current for some time now but > if people have problems with it I can delay the MFC while we discuss > it. > > I also intend to MFC the changes to the write-behind heuristic on > wednesday (search for 'Change the write-behind' in the below -current > commits for a reference). Since this is a relatively simple patch which > solves a degenerate write-stall case in -current as well as fixes one > of those silly contrived benchmarks, I do not expect there to be any > complaints. > > My intention is to try to keep the 4.x and 5.x trees synchronized as > much as makes sense in regards to my own core work so people doing > add-on work can also MFC as much of it as makes sense. It should be > reasonable to do this while we are in the early stages of the release > cycle. I would like to see this happen and I agree with keeping 4.0 and 5.0 as close as possible. Please don't forget that the SMP deltas had some serious problems, they broke UP kernels (afaik) and you'll need to MFC my makesyscalls.sh hack (the delta directly edited generated files). Because of that they need a couple of days of being available so people can test (I will) before being applied to RELENG_4. I think the change in write behind algorithms should be pushed into RELENG_4 asap, they are stable and if we get negative feedback from the larger userbase they can be re-examined now instead of us scratching our heads a year down the road when we have RELENG_5 and performance problems crop up. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:40:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 070D337BA18 for ; Sun, 23 Apr 2000 12:40:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63647; Sun, 23 Apr 2000 12:39:58 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:39:58 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231939.MAA63647@apollo.backplane.com> To: Alfred Perlstein Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFCing SMP cleanups from -current into 4.x on wednesday References: <200004231825.LAA62883@apollo.backplane.com> <20000423130318.E204@fw.wintelcom.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I would like to see this happen and I agree with keeping 4.0 and :5.0 as close as possible. Please don't forget that the SMP deltas :had some serious problems, they broke UP kernels (afaik) and you'll :need to MFC my makesyscalls.sh hack (the delta directly edited :generated files). Because of that they need a couple of days of being :available so people can test (I will) before being applied to :RELENG_4. : :I think the change in write behind algorithms should be pushed into :RELENG_4 asap, they are stable and if we get negative feedback from :the larger userbase they can be re-examined now instead of us :scratching our heads a year down the road when we have RELENG_5 and :performance problems crop up. : :-Alfred Ach, I did forget about the makesyscalls.sh hack. Your right, I'll put together a big MFC patchset for the SMP stuff and make it available tonight or tomorrow for people to test with first, just to make sure we haven't forgotten anything. That means we will probably have to push the commit off until at least friday. Was it just you and me that committed the SMP stuff or were there others? I'll physically compare the files between 4.x and 5.x just to be sure, but I think it was just you and me doing the commits. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:42:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8E78537B9B9 for ; Sun, 23 Apr 2000 12:42:37 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e3NKBHl21592; Sun, 23 Apr 2000 13:11:17 -0700 (PDT) Date: Sun, 23 Apr 2000 13:11:17 -0700 From: Alfred Perlstein To: Matthew Dillon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MFCing SMP cleanups from -current into 4.x on wednesday Message-ID: <20000423131117.F204@fw.wintelcom.net> References: <200004231825.LAA62883@apollo.backplane.com> <20000423130318.E204@fw.wintelcom.net> <200004231939.MAA63647@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004231939.MAA63647@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Apr 23, 2000 at 12:39:58PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000423 13:08] wrote: > > :I would like to see this happen and I agree with keeping 4.0 and > :5.0 as close as possible. Please don't forget that the SMP deltas > :had some serious problems, they broke UP kernels (afaik) and you'll > :need to MFC my makesyscalls.sh hack (the delta directly edited > :generated files). Because of that they need a couple of days of being > :available so people can test (I will) before being applied to > :RELENG_4. > : > :I think the change in write behind algorithms should be pushed into > :RELENG_4 asap, they are stable and if we get negative feedback from > :the larger userbase they can be re-examined now instead of us > :scratching our heads a year down the road when we have RELENG_5 and > :performance problems crop up. > : > :-Alfred > > Ach, I did forget about the makesyscalls.sh hack. Your right, I'll > put together a big MFC patchset for the SMP stuff and make it available > tonight or tomorrow for people to test with first, just to make sure > we haven't forgotten anything. That means we will probably have to > push the commit off until at least friday. > > Was it just you and me that committed the SMP stuff or were there > others? I'll physically compare the files between 4.x and 5.x just > to be sure, but I think it was just you and me doing the commits. I'm really sorry, I know I did makesyscalls.sh but I don't know who fixed the UP compiles and if anyone else stepped in to 'help' in the meanwhile. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:43:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B10E637B66B for ; Sun, 23 Apr 2000 12:43:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA63679; Sun, 23 Apr 2000 12:42:40 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 12:42:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231942.MAA63679@apollo.backplane.com> To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@freebsd.org Subject: Re: Linux Emulation Root (was: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday) References: <200004231924.MAA00521@cwsys.cwsent.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <200004231835.LAA62963@apollo.backplane.com>, Matthew Dillon :writes: :> I intend to commit this to -current and immediately MFC it to -stable. :> I don't expect there to be any controversy though I'm sure there is a :> cleaner way to do it. : :On a semi-related topic, it would be handy to have a feature, :environment variable, table in the kernel, a sysctl variable, etc., to :set the Linux emulation root to the real root. For example, the backup :component of Legato for Linux (nsrexecd and friends) runs nicely on :under Linux emulation, however, recovering files in the root directory :sees them placed in the Linux emulation root directory. : :To work around this I've used a union filesystem that mounted / on :another mount point and redirected my restores to it. : :My questions are: : :Is there a cleaner way to work around this, e.g. some tunable knob to :tune Linux emulation? If not, would anyone else see any use for this :kind of feature? : : :Regards, Phone: (250)387-8437 :Cy Schubert Fax: (250)387-5766 I had to struggle with this issue during the Oracle install... the fact that under linux emulation the 'root' per say is rather loosely defined. I wound up having to chroot into /compat/linux to even come close to getting oracle to install (and locating all the linux utilities with FreeBSD equivalents that weren't installed in /compat/linux, causing the freebsd utilities to be run and of course fail due to missing or different options). The only thing I can think of us is to overlay the linux directory structure on top of the FreeBSD directory structure via union mounts. In otherwords, be able to chroot to /compat/linux and 'see' the entire FreeBSD directory structure (minus changes made via the mount to get all the linux binaries, libraries, etc, and such). We would then get rid of the /compat/linux prefix pathing entirely and simply have linux emulation automatically chroot to /compat/linux when a non-linux program exec's a linux program in order to access the modified view of the filesystem. Messy, I know. I don't know if there is a clean solution to the problem. At least if we use union mounts the whole mess is isolated away from the native FreeBSD install (note: we'd have to clean up union mounts to make them work properly). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:48: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id E9B0F37BACC; Sun, 23 Apr 2000 12:47:58 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA28428; Sun, 23 Apr 2000 13:47:35 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id NAA08296; Sun, 23 Apr 2000 13:47:35 -0600 (MDT) (envelope-from nate) Date: Sun, 23 Apr 2000 13:47:35 -0600 (MDT) Message-Id: <200004231947.NAA08296@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Matthew Dillon , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: <45851.956517875@critter.freebsd.dk> References: <200004231922.MAA63538@apollo.backplane.com> <45851.956517875@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Core should consider reverting the special rules that were originally > > created with the expectation of major breakage in 5.x back to > > the set of rules we had for 3.x and 4.x. > > I have no idea what special rules you are talking about for 4.x/5.x. > > 4.x-stable is a -stable tree and shall be treated as such. I was under the impression that 4.x hasn't been designated as the stable branch (yet). That will happen when 4.1 is released, but until that happens 3.x is still considered the -stable release. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:56:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id EC31237B517 for ; Sun, 23 Apr 2000 12:56:18 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id NAA70389; Sun, 23 Apr 2000 13:57:05 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sun, 23 Apr 2000 13:57:05 -0600 (CST) From: Ryan Thompson To: Nate Williams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: <200004231947.NAA08296@nomad.yogotech.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Numerous cross-posts and CC's removed Nate Williams wrote to Poul-Henning Kamp: > > > Core should consider reverting the special rules that were originally > > > created with the expectation of major breakage in 5.x back to > > > the set of rules we had for 3.x and 4.x. > > > > I have no idea what special rules you are talking about for 4.x/5.x. > > > > 4.x-stable is a -stable tree and shall be treated as such. > > I was under the impression that 4.x hasn't been designated as the stable > branch (yet). That will happen when 4.1 is released, but until that > happens 3.x is still considered the -stable release. > > Nate Nate, 4.0 is indeed -STABLE. Some (myself included) are simply staying with 3.4 on production machines until a few of the bugs have been shaken out of 4.0 (though there haven't been many!) Therefore, many individuals are recommending a wait until 4.1 before switching to RELENG_4. Virtually yours, - Ryan -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 12:58:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2511337B66F for ; Sun, 23 Apr 2000 12:58:48 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA07004; Sun, 23 Apr 2000 12:58:46 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA24527; Sun, 23 Apr 2000 12:58:46 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 23 Apr 2000 12:58:46 -0700 (PDT) Message-Id: <200004231958.MAA24527@vashon.polstra.com> To: jeff@mountin.net Subject: Re: CVSup core dumping In-Reply-To: <4.3.2.20000422140024.0235c610@mixcom.com> References: <4.3.2.20000422140024.0235c610@mixcom.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.3.2.20000422140024.0235c610@mixcom.com>, Jeffrey J. Mountin wrote: > > Running 4.0S as of 3/29 and CVSup has worked without a hitch up through > about 2 days back. Now it is core dumping with illegal instruction and > does this with cvsup7 or cvsup4. One recent change was the addition of > Samba, which was not running at the time. I removed it and rebooted with > the same results. The only other change was to remove the comment from > some categories that I do not bother to update very often. Long shot, but > it was another variable and CVSup then completed. > > Alright, comment out my usual ports and once again remove the comments from > the additional categories I wanted to update. Once again completed. > > Then when trying once more after adding the usual ports ended up with > another core dump for a total of 6 now, which I saved. > > Had no problems with doc, web, and system sources. I haven't seen any other reports of this problem. I'm not sure I follow all the intricacies of your supfile modifications. If you can narrow it down to one collection that is definitely tied to the problem, I might be able to help track it down. Illegal instruction is a pretty strange error to have. Aside from HW or kernel problems, the only semi-likely explanation for that would be an overflowed thread stack. If you have time, please grab the appropriate unstripped binary from http://people.freebsd.org/~jdp/ These correspond exactly with the cvsup-bin and cvsupd-bin ports, so if you're using those ports you will be able to use the unstripped binaries with your existing core dumps to get a stack trace. > Also cvsup6 was refusing connections today, which I haven't seen and > would not expect for early Saturday afternoon. Ping indicated that was caused by network problems. It seems to be OK now. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13: 2:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id 742B837B66B; Sun, 23 Apr 2000 13:02:17 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Sun, 23 Apr 2000 15:02:07 -0500 From: Richard Wackerbarth To: Matthew Dillon Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday Date: Sun, 23 Apr 2000 15:02:06 -0500 X-Mailer: KMail [version 1.1.40] Content-Type: text/plain Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG References: <45766.956517098@critter.freebsd.dk> <200004231928.MAA63577@apollo.backplane.com> In-Reply-To: <200004231928.MAA63577@apollo.backplane.com> MIME-Version: 1.0 Message-Id: <00042315020600.20614@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Apr 2000, Matthew Dillon wrote: > If core wants to change the current rules, that's fine by me. As I > said before I think the breakage that we thought would happen with 5.x > due to the BSDI merger that prompted the loose rules for 4.x is > overrated, and the rules should probably be reverted back to standard. Well, unless I missed some REQUIREMENT in "the rules", there is nothing to prevent you from applying to your own actions the policy that you think should be the rule and apply to everyone. Just because you COULD do something and stay within the letter of the law, that is no excuse to do it. Although I suspect that your change is a general improvement, it is certainly a change that might have adverse impact on some users. Therefore, I think that if should receive closer and more widespread review before being committed to any of the "stable" branches. Personally, I will use the attitude that you have been expressing to justify my claim that FreeBSD is still just a "developers' sandbox". Until ALL the developers start to think about changes from the perspective of the end user, it will remain so. IMHO, there is entirely too much rush to force untested changes on everyone. Every change should flow through the slowly widening set of exposures afforded by gradual commits to the various forums. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:14:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 07B2637BA1F; Sun, 23 Apr 2000 13:14:25 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA64138; Sun, 23 Apr 2000 13:14:21 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 13:14:21 -0700 (PDT) From: Matthew Dillon Message-Id: <200004232014.NAA64138@apollo.backplane.com> To: "Rodney W. Grimes" Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: SMP changes and breaking kld object module compatibility References: <200004231909.MAA09128@gndrsh.dnsmgr.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> There's another good reason to MFC the linux patch on wednesday... :> that is, to do it at the same time the SMP cleanup is MFC'd, and that :> is because both patch sets require the linux kernel module to be :> recompiled and I'd rather not force people to do that twice. :> :> The SMP patchset, in fact, requires that all kernel modules be :> recompiled due to the locks that were removed from the spl*() macros. : :In that case I have a strong objection to the SMP patchset being :merged to 4.0. I have kernel modules in object format only that :are working now, which this would break :-(. : :Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net This is a legitimate topic for discussion. In general I agree with the concept but I think .0 releases have to have a bit more flexibility, and that 4.0 in particular (due to the rules change made for the BSDI merger) has to be even more flexible. We should be allowed to break kernel module loader compatibility in between a .0 and a .1 release if it is deemed necessary, but that it should be avoided (as much as possible) after the .1 release. I would put forth that the SMP patches are a special case in that they provide a base for which further BGL unwinding can occur in both 4.x and 5.x without further API breakages (beyond this one). If we do not MFC the SMP cleanup, then there is no chance of being able to MFC *ANY* further SMP-related lock removal or performance work from 5.x to 4.x. I believe that it is fairly important to try to extend the SMP work into 4.x as much as possible, otherwise certain significant performance improvements that might be made in a very unstable 5.x will not be available to the general public in the stable 4.x for another year. I expect most production machines will be running 4.x for at least the year and a half. To be blunt, if we don't do this now then we are going to be behind the competition (linux, solaris) for much too long. As an example of how important this can be I would point back to the 3.x and 4.x trees during the VM work I did. By not MFCing from the outset we reached a point where bug fixes going into 4.x could *not* be backported to 3.x without a lot of work. We reached a point where bug fixes (garbage after file EOF in mmaps for example) simply could not be backported, or required a lot of work (some of the NFS fixes had to be rewritten for 3.x). I think it may be even more important for 4.x and 5.x in regards to the SMP work. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:21:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 24D8537BA0F; Sun, 23 Apr 2000 13:21:18 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA06740; Sun, 23 Apr 2000 13:18:26 -0700 (PDT) Message-Id: <200004232018.NAA06740@implode.root.com> To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 12:01:46 PDT." <200004231901.MAA63381@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 23 Apr 2000 13:18:26 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I do not consider the linux scripting patch to be a major infrastructure > change, I consider it to be a simple bug fix. If you have a functional > issue with the patch I'm all ears. If you disagree with my assessment of > the triviality of the linux scripting patch, then I will ask for a > second opinion from someone who is not quite so jaded in regards to my > commits... say Jordan or DG. I'm sure you're right that the impact is minor. I'm a little uncomfortable with immediate MFC's, even though I've been guilty of doing that myself at times in the past. Can we perhaps compromise and allow for a one day delay? At least that would catch glaring mistakes like mis-applied patches that happen sometimes even with highly skilled developers who have only the best intentions. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:22:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id ABF1537B5D1 for ; Sun, 23 Apr 2000 13:21:58 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Sun, 23 Apr 2000 15:21:49 -0500 From: Richard Wackerbarth To: Nate Williams Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday Date: Sun, 23 Apr 2000 15:04:33 -0500 X-Mailer: KMail [version 1.1.40] Content-Type: text/plain Cc: freebsd-stable@FreeBSD.ORG References: <200004231922.MAA63538@apollo.backplane.com> <45851.956517875@critter.freebsd.dk> <200004231947.NAA08296@nomad.yogotech.com> In-Reply-To: <200004231947.NAA08296@nomad.yogotech.com> MIME-Version: 1.0 Message-Id: <00042315043301.20614@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Apr 2000, Nate Williams wrote: > > 4.x-stable is a -stable tree and shall be treated as such. > > I was under the impression that 4.x hasn't been designated as the stable > branch (yet). That will happen when 4.1 is released, but until that > happens 3.x is still considered the -stable release. Then why does the banner say "-STABLE" and why is it on the freebsd-stable mailing list? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:23:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-202-179-64.dsl.snfc21.pacbell.net [63.202.179.64]) by hub.freebsd.org (Postfix) with ESMTP id 215CB37B9B9; Sun, 23 Apr 2000 13:23:27 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA51633; Sun, 23 Apr 2000 13:30:39 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004232030.NAA51633@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 11:55:08 PDT." <200004231855.LAA63309@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Apr 2000 13:30:39 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wonder if it makes sense to add a release id to the module header > and have the module loader refuse (unless forced) to load modules that > are out-of-date with the kernel? We actually have a whole module dependancy and versioning system more or less ready to go into -current. It could have gone in for 4.0, but we wouldn't have had time to test it. I would avoid rolling anything half-assed at this point in time. BTW; whilst I think Poul was entirely the wrong person to raise the issue, I agree that you probably want to hang back on MFCing the linux scripting changes for a week or so. This is really just common sense. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:25:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 69D9F37BA50; Sun, 23 Apr 2000 13:25:33 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA64213; Sun, 23 Apr 2000 13:25:30 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 13:25:30 -0700 (PDT) From: Matthew Dillon Message-Id: <200004232025.NAA64213@apollo.backplane.com> To: David Greenman Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <200004232018.NAA06740@implode.root.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> I do not consider the linux scripting patch to be a major infrastructure :> change, I consider it to be a simple bug fix. If you have a functional :> issue with the patch I'm all ears. If you disagree with my assessment of :> the triviality of the linux scripting patch, then I will ask for a :> second opinion from someone who is not quite so jaded in regards to my :> commits... say Jordan or DG. : : I'm sure you're right that the impact is minor. I'm a little uncomfortable :with immediate MFC's, even though I've been guilty of doing that myself at :times in the past. Can we perhaps compromise and allow for a one day delay? :At least that would catch glaring mistakes like mis-applied patches that :happen sometimes even with highly skilled developers who have only the best :intentions. : :-DG : :David Greenman Sure, no problem. I'll tell you what, I'll commit the linux scripting patch to 5.x on wednesday as originally planned, but since the SMP MFC is being moved to friday (at the very least) I will not MFC the scripting patch to 4.x until friday. ( That is, what I really want to do is to do the SMP MFC and the scripting MFC at the same time so people only have to recompile their kernel modules once. It happens to work out well ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:29:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 92FFD37BA4B; Sun, 23 Apr 2000 13:29:37 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA06779; Sun, 23 Apr 2000 13:25:43 -0700 (PDT) Message-Id: <200004232025.NAA06779@implode.root.com> To: Matthew Dillon Cc: "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility In-reply-to: Your message of "Sun, 23 Apr 2000 13:14:21 PDT." <200004232014.NAA64138@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 23 Apr 2000 13:25:43 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >:> There's another good reason to MFC the linux patch on wednesday... >:> that is, to do it at the same time the SMP cleanup is MFC'd, and that >:> is because both patch sets require the linux kernel module to be >:> recompiled and I'd rather not force people to do that twice. >:> >:> The SMP patchset, in fact, requires that all kernel modules be >:> recompiled due to the locks that were removed from the spl*() macros. I wonder if they really must be recompiled. It sounds like that would improve performance, but is seems like gratuitous locking in this area wouldn't necessarily cause things to break. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:35: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EA44537BA6E; Sun, 23 Apr 2000 13:34:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA64288; Sun, 23 Apr 2000 13:34:53 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 13:34:53 -0700 (PDT) From: Matthew Dillon Message-Id: <200004232034.NAA64288@apollo.backplane.com> To: David Greenman Cc: "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility References: <200004232025.NAA06779@implode.root.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>:> There's another good reason to MFC the linux patch on wednesday... :>:> that is, to do it at the same time the SMP cleanup is MFC'd, and that :>:> is because both patch sets require the linux kernel module to be :>:> recompiled and I'd rather not force people to do that twice. :>:> :>:> The SMP patchset, in fact, requires that all kernel modules be :>:> recompiled due to the locks that were removed from the spl*() macros. : : I wonder if they really must be recompiled. It sounds like that would :improve performance, but is seems like gratuitous locking in this area :wouldn't necessarily cause things to break. : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org The cpl, cml, and interrupt lock variables and initialization of such is gone, Kapoof. And the semantics have changed for a few things as well. I haven't actually tested it to see if old modules still load and operate properly because doing the testing properly would take more time then I have to spend. If a KLD doesn't use spl*() calls at all it may be ok. I think we should resign ourselves to recompiling the KLD's, though. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:38:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3653237BA61; Sun, 23 Apr 2000 13:38:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA10804; Sun, 23 Apr 2000 13:39:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Poul-Henning Kamp , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: To MFC or not to MFC, that is the question. In-reply-to: Your message of "Sun, 23 Apr 2000 12:30:19 PDT." <200004231930.MAA63599@apollo.backplane.com> Date: Sun, 23 Apr 2000 13:39:20 -0700 Message-ID: <10801.956522360@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Really, then you have a short memory. Why don't we ask Jordan for a > clarification. How about if you let me review the patches in question and I'll render a decision. If you, Matt, could put the SMP and linux stuff into -current first and then give me a day or so to check it out, I'll submit my own opinion on whether or not this is "immediate MFC" material. That covers the operational side of the discussion, and on the procedural side I unfortunately see a lot of arguing about "our policy" for things like this in spite of the fact that there has never really been an absolutely clear-cut mandate about when/where things should be MFC'd. It's a more complex mesh of judgement calls revolving around: o Whether the change is absolutely mandated by security criteria or just-plain-brokenness in -stble. o Whether the change is cosmetic or otherwise minor enough that there's no reason not to Just Do It right away. o How close we are to an impending release in the -stable branch in question. As has been stated frequently in the past, the release engineer would prefer for big changes in -stable to come along early in the game for maximum testing time rather than the day before code freeze starts. Determining where one sits with respect to all three of these merge-justification criteria comes down to a judgement call in each case, not some precise committer's checklist. I also personally don't mind that too much since no checklist can be written to cover all cases or codify the full range of "good judgement", so it ultimately comes down to personal opinion. I see two very big differences of personal opinion on this one and am willing to arbitrate between the two. In the longer-term, this kind of thing should be handled by the architecture group or the conflict-resolution committee depending on whether it's an architectural dispute or a simple clash between personalities or styles. In this case, I'd say it was a job for the CRC if we currently had one. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:43:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 536E737BA5D for ; Sun, 23 Apr 2000 13:43:39 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA10837; Sun, 23 Apr 2000 13:44:15 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: nate@yogotech.com (Nate Williams) Cc: Poul-Henning Kamp , Matthew Dillon , "Rodney W. Grimes" , freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-reply-to: Your message of "Sun, 23 Apr 2000 13:47:35 MDT." <200004231947.NAA08296@nomad.yogotech.com> Date: Sun, 23 Apr 2000 13:44:15 -0700 Message-ID: <10834.956522655@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was under the impression that 4.x hasn't been designated as the stable > branch (yet). FreeBSD usw3.freebsd.org 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:09:21 CDT 2000 root@usw3.freebsd.org:/usr/src/sys/compile/USW3 i386 If it hasn't been designated stable yet, then a lot of people are being confused every time they run uname(1). :-) It's -stable now. Probably more -stable than 3.x if you look at some people's experiences in the field. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 13:51: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 76F7B37BA6B; Sun, 23 Apr 2000 13:51:01 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA10875; Sun, 23 Apr 2000 13:52:03 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility In-reply-to: Your message of "Sun, 23 Apr 2000 13:14:21 PDT." <200004232014.NAA64138@apollo.backplane.com> Date: Sun, 23 Apr 2000 13:52:02 -0700 Message-ID: <10872.956523122@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In general I agree with the concept but I think .0 releases have to > have a bit more flexibility, and that 4.0 in particular (due to the > rules change made for the BSDI merger) has to be even more flexible. And this is something I can render an opinion on right away: I disagree. I want it treated as a full -stable branch, not some weaker derivative, and I don't think we'll win [m]any friends in the new-4.0 convert camp if we try to shake things up there, even with it in .0 status and the BSDi situation. The reasoning is quite simple: 4.0 turned out to have, in certain production environments, far less stability problems than 3.4 and that is partially Matt's fault for fixing things like NFS. :-) That in turn led to a lot more early-adoption of 4.0 than expected, and now 4.0 is being treated (and is behaving) like a full-blown -stable release with lots of good reasons to switch to it. The whole dot-zero conservativeness thing was our traditional attempt to put a happy face on situations that sucked (a .0 release being frail and buggy) rather than having that be an actual goal. Now that we've finally managed to shake off the .0 curse in many respects, I'm firmly behind the concept of treating it like any other release. I'm sure that something can be done for the kld compatibility issues so that you can have your SMP cake and eat it too. Just give it a bit more thought. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 14: 6:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 8F0A337B9AB for ; Sun, 23 Apr 2000 14:06:06 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [204.138.57.194]) by sabre.velocet.net (Postfix) with ESMTP id D5D3013807E for ; Sun, 23 Apr 2000 17:06:02 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id RAA04060; Sun, 23 Apr 2000 17:06:02 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14595.26042.23891.386879@trooper.velocet.net> Date: Sun, 23 Apr 2000 17:06:02 -0400 (EDT) To: stable@freebsd.org Subject: ATA datapoint. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just as a datapoint, because I see people recomending sysctl -w hw.atamodes=pio,pio,pio,pio, I have a configuration which resists anything being read or written from/to the primary master disk. For the time being, I have put wdc back in my kernel, and this is what it says: wdc0 at port 0x1f0-0x1f7 irq 14 drq 0 flags 0x80ff80ff on isa0 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-16 wd1: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S wdc0: driver is using old-style compatability shims isa_compat: didn't get drq for wdc wdc1 at port 0x170-0x177 irq 15 drq 0 flags 0x80ff80ff on isa0 isa_compat: didn't get drq for wdc wdc1: unit 0 (wd2): , 32-bit, multi-block-16 wd2: 6208MB (12715920 sectors), 13456 cyls, 15 heads, 63 S/T, 512 B/S wdc1: driver is using old-style compatability shims Now... the Fujitsu 3064 is a fairly common drive (I know there's 5 or six of them kicking around our small shop) and the controller is on the motherboard of a fairly plain K6-2 motherboard. When booting with the ata driver, it spits out 'ad0: READ command timeout - resetting' multiple times, but never spits out the done message. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 14:15:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from epsilon.lucida.qc.ca (epsilon.lucida.qc.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id 4784B37BA6A for ; Sun, 23 Apr 2000 14:15:25 -0700 (PDT) (envelope-from matt@ARPA.MAIL.NET) Received: (qmail 86959 invoked by uid 1000); 23 Apr 2000 21:15:24 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Apr 2000 21:15:24 -0000 Date: Sun, 23 Apr 2000 17:15:22 -0400 (EDT) From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Ryan Thompson Cc: Nate Williams , freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 23 Apr 2000, Ryan Thompson wrote: [...] : 4.0 is indeed -STABLE. Some (myself included) are simply staying with 3.4 : on production machines until a few of the bugs have been shaken out of 4.0 : (though there haven't been many!) Therefore, many individuals are : recommending a wait until 4.1 before switching to RELENG_4. Personally, I'm holding off on 4.0 with production machines simply due to the upgrade process involved. I would feel a lot better by doing a clean format and installing 4.0 fresh off the cds than trying to do make world to 4.0 and all the associated "nightmares" involved. I have been very impressed with 4.0 and have been running it on my workstation since release came out without any problems beyond the "problems" with the ad driver which are "fixed" by using wd. However, since all the production machines are SCSI, I do not foresee this to be a problem. : Virtually yours, : - Ryan Regards, Matt Heckaman matt@arpa.mail.net http://www.lucida.qc.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE5A2frdMMtMcA1U5ARAmQgAJoD5DrgA4pqKy1fJtPRDCoizk4/uwCgnFpF C+U/RjefprWNJpCKb/52fMk= =b2FV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 14:20:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pyros.yi.org (dialin26.mediawizards.net [209.63.39.26]) by hub.freebsd.org (Postfix) with ESMTP id 58A0A37BA6A; Sun, 23 Apr 2000 14:20:45 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (pyros.lan [192.168.100.1]) by pyros.lan (Postfix) with ESMTP id 758C78E1; Sun, 23 Apr 2000 14:01:55 -0700 (PDT) Message-ID: <390364C3.242B5F7C@es.co.nz> Date: Sun, 23 Apr 2000 21:01:55 +0000 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Matthew Dillon , Poul-Henning Kamp , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: To MFC or not to MFC, that is the question. References: <10801.956522360@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good greif that last one failed to go to stable@ or current@.. time to fix mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 14:20:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pyros.yi.org (dialin26.mediawizards.net [209.63.39.26]) by hub.freebsd.org (Postfix) with ESMTP id 569CE37BA68; Sun, 23 Apr 2000 14:20:44 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (pyros.lan [192.168.100.1]) by pyros.lan (Postfix) with ESMTP id 4B22D8DC; Sun, 23 Apr 2000 13:58:46 -0700 (PDT) Message-ID: <39036406.A256278@es.co.nz> Date: Sun, 23 Apr 2000 20:58:46 +0000 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Matthew Dillon , Poul-Henning Kamp , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: To MFC or not to MFC, that is the question. References: <10801.956522360@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > Really, then you have a short memory. Why don't we ask Jordan for a > > clarification. > > How about if you let me review the patches in question and I'll render > a decision. > > If you, Matt, could put the SMP and linux stuff into -current first > and then give me a day or so to check it out, I'll submit my own > opinion on whether or not this is "immediate MFC" material. > > That covers the operational side of the discussion, and on the > procedural side I unfortunately see a lot of arguing about "our > policy" for things like this in spite of the fact that there has never > really been an absolutely clear-cut mandate about when/where things > should be MFC'd. It's a more complex mesh of judgement calls > revolving around: > > o Whether the change is absolutely mandated by security criteria > or just-plain-brokenness in -stble. > > o Whether the change is cosmetic or otherwise minor enough that > there's no reason not to Just Do It right away. > > o How close we are to an impending release in the -stable branch > in question. As has been stated frequently in the past, the > release engineer would prefer for big changes in -stable to come > along early in the game for maximum testing time rather than > the day before code freeze starts. > > Determining where one sits with respect to all three of these > merge-justification criteria comes down to a judgement call in each > case, not some precise committer's checklist. I also personally don't > mind that too much since no checklist can be written to cover all > cases or codify the full range of "good judgement", so it ultimately > comes down to personal opinion. I see two very big differences of > personal opinion on this one and am willing to arbitrate between the > two. > > In the longer-term, this kind of thing should be handled by the > architecture group or the conflict-resolution committee depending on > whether it's an architectural dispute or a simple clash between > personalities or styles. In this case, I'd say it was a job for the > CRC if we currently had one. :) I'll be your CRC and say stop yer bickering and discuss this like adults (assuming you both are infact classed as such) which means no cheap shot insults (im sure you both have great memories and excusing that would be your workloads which im sure are right up there) and getting over whatever personal differences either party might have. ok good! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 15:10:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pyros.yi.org (dialin26.mediawizards.net [209.63.39.26]) by hub.freebsd.org (Postfix) with ESMTP id F40CB37B8D1; Sun, 23 Apr 2000 15:10:41 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (rock.bsdonline.org [192.168.100.1]) by rock.bsdonline.org (Postfix) with ESMTP id BBB938DB; Sat, 22 Apr 2000 23:37:14 -0700 (PDT) Message-ID: <39029A1A.D1CE182F@es.co.nz> Date: Sun, 23 Apr 2000 06:37:14 +0000 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: amr still seems to have issues. References: <20000421003205.A25458@fw.wintelcom.net> <200004211644.JAA02335@mass.cdrom.com> <20000421105539.C10782@fw.wintelcom.net> <20000421133517.I10782@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > I'm looking into the enclosure issues. I appreciate the continued > help from you. > > I was wondering if anyone else on the lists have had the same problems > as I have been having with the Enterprise 1200 (3 scsi port) version. Just as a kind of follow up to this and Martin's reply, I have a 1200 series 2 channel controller with 4 megs of cache (was going to be 8 until the 2 simms i was sent by CSO didnt want to work whatsoever.. they were IBM too.. weird) I have two 9.1 gig drives, one on each channel (soon to be 3 drives) and i've had only one problem to date, which was the wedged bug a couple days ago, but bear in mind this was with the older driver which didnt have the command limit. I'm building world right now (actually ive already built it once, ran out of /var for the bw.out and couldnt be sure if i had finished the build, so im building it again) and theres no problems. I've been using bonnie, rawio and iozone extensively with the older v1.7 amr.c and ive had no problems at all. If you are interested, here are the bonnie results with -s 100 command args. I'm using 64KB stripe sizes, Cached IO and Write Back caching: | -------Sequential Output-------- ---Sequential Input-- --Random-- | | -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- | | MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU | | 100 13324 74.0 13577 30.7 14245 42.2 14598 100.0 96666 100.0 10509.9 99.9 | And with Write Through: | -------Sequential Output-------- ---Sequential Input-- --Random-- | | -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- | | MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU | | 100 12730 74.2 13045 35.7 5611 20.3 12886 93.0 15655 24.2 225.6 4.7 | I'm interested to know if these are reasonable figures for the configuration (P2/450.) Havn't been able to try 128KB stripe widths due to lack of cache (well the bios wont let me due to 'not enough memory' so im assuming its this) but ive heard 64KB is the way to go. I know this probably isnt of much help to your problem, but I thought a little good news (in terms of stability) would be appreciated from msmith heh. Regards, mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 15:10:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pyros.yi.org (dialin26.mediawizards.net [209.63.39.26]) by hub.freebsd.org (Postfix) with ESMTP id D73FD37BA6A; Sun, 23 Apr 2000 15:10:44 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (rock.bsdonline.org [192.168.100.1]) by rock.bsdonline.org (Postfix) with ESMTP id 63D3D8D4; Sun, 23 Apr 2000 12:59:37 -0700 (PDT) Message-ID: <39035629.BC369DD4@es.co.nz> Date: Sun, 23 Apr 2000 19:59:37 +0000 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams Cc: Poul-Henning Kamp , Matthew Dillon , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <200004231922.MAA63538@apollo.backplane.com> <45851.956517875@critter.freebsd.dk> <200004231947.NAA08296@nomad.yogotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > I was under the impression that 4.x hasn't been designated as the stable > branch (yet). That will happen when 4.1 is released, but until that > happens 3.x is still considered the -stable release. That would kinda make sense since cvsuping with tag=RELENG_3 seems to give me FreeBSD 4.0-STABLE (#0: Sat Apr 22 20:59:03 PDT 2000).. But besides that, this whole back and forth dont-do-this-do-that charade is going to get pretty juvenile soon.. I mean we're (matt) already at bad memory insults heh so how bout you both kiss/reevaluate and make up before it gets so bad you try to keep away from each other next time you're both at one of these conventions or whatever.. hmm now theres an uncomfortable situation to be in for both sides. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 15:37: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pyros.yi.org (dialin29.mediawizards.net [209.63.39.29]) by hub.freebsd.org (Postfix) with ESMTP id E720B37B8EF; Sun, 23 Apr 2000 15:36:55 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (pyros.lan [192.168.100.1]) by pyros.yi.org (Postfix) with ESMTP id C6A183B; Sun, 23 Apr 2000 15:37:26 -0700 (PDT) Message-ID: <39037B26.33C1B62F@es.co.nz> Date: Sun, 23 Apr 2000 22:37:26 +0000 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nate Williams , Poul-Henning Kamp , Matthew Dillon , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <200004231922.MAA63538@apollo.backplane.com> <45851.956517875@critter.freebsd.dk> <200004231947.NAA08296@nomad.yogotech.com> <39035629.BC369DD4@es.co.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Muir wrote: > > Nate Williams wrote: > > > I was under the impression that 4.x hasn't been designated as the stable > > branch (yet). That will happen when 4.1 is released, but until that > > happens 3.x is still considered the -stable release. > > That would kinda make sense since cvsuping with tag=RELENG_3 seems to > give me FreeBSD 4.0-STABLE (#0: Sat Apr 22 20:59:03 PDT 2000).. Ok wait im a moron.. been using the stable-supfile instead of the 4.x-stable-supfile.. hmmmmm. mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 15:56:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 5BDB837BAAC for ; Sun, 23 Apr 2000 15:56:04 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA15131; Sun, 23 Apr 2000 23:55:40 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA00681; Sun, 23 Apr 2000 22:10:22 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004232110.WAA00681@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Frolkin Cc: Brian Somers , stable@freebsd.org, brian@hak.lan.Awfulhak.org Subject: Re: portmap strangeness In-Reply-To: Message from Alexander Frolkin of "Sat, 22 Apr 2000 17:03:05 BST." <20000422170304.A2166@gamma> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Apr 2000 22:10:22 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Apr 22, 2000 at 10:06:21AM +0100, Brian Somers wrote: > > In /usr/src/usr.sbin/portmap, can you > > > > cc -o from_local -DTEST from_local.c > > ./from_local > > > > and see how this compares to the output of ifconfig -a ? If this > > finds all the interface addresses after lp0, then there *should* be > > no problems. > > I've done that, and I get the addresses of all the interfaces which are 'up' > listed correctly, however portmap only works when lp0 is also up. (This is > the first interface in ifconfig -a, if that makes a difference). from_local > shows the address of lp0, when it is up, as 0.0.0.0, which is correct since > the address isn't set because I'm not using the interface at the moment. Well, I think the next step(s) are to ensure that portmap is LISTENing to *.111 and then to use tcpdump to see what address the nfs stuff is coming from - without lp0 being IFF_UP. It sounds like portmap is failing to identify the address as being local.... > Thanks, > > Alexander. Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 17:37:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id D80AC37B7A5; Sun, 23 Apr 2000 17:37:50 -0700 (PDT) From: "Jonathan M. Bresler" To: msmith@freebsd.org Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-reply-to: <200004232030.NAA51633@mass.cdrom.com> (message from Mike Smith on Sun, 23 Apr 2000 13:30:39 -0700) Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday Message-Id: <20000424003750.D80AC37B7A5@hub.freebsd.org> Date: Sun, 23 Apr 2000 17:37:50 -0700 (PDT) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > BTW; whilst I think Poul was entirely the wrong person to raise the > issue, I agree that you probably want to hang back on MFCing the linux > scripting changes for a week or so. This is really just common sense. > recently i added autoload to a usb related kernel module. very handy to have....just like with ifconfing autoloading ethernet drivers. i did an immediate MFC. i was WRONG. i should not have done that. even though it does strike me as an obivious win to have the autoload. lets let every change sit in -current for a little while before the MFC occurs. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 20: 7:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from marbles.lost.net.au (marbles.lost.net.au [203.30.236.113]) by hub.freebsd.org (Postfix) with ESMTP id D62CE37B735 for ; Sun, 23 Apr 2000 20:07:47 -0700 (PDT) (envelope-from jarrod@lost.net.au) Received: from localhost (jarrod@localhost) by marbles.lost.net.au (8.9.3/8.8.7) with ESMTP id MAA05369 for ; Mon, 24 Apr 2000 12:37:43 +0930 Date: Mon, 24 Apr 2000 12:37:43 +0930 (CST) From: Jarrod To: freebsd-stable@FreeBSD.ORG Subject: CRYPO dist installed outside US Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We have by accident installed the crypto distribution out of 4.0 onto a machine outside the US/CDN. User accounts have been added to this machine but the password updating program we use no longer works as the encrypted password in /etc/master.passwd is in DES format (im assuming) where we are use to the standard $1$salt$encpw$ Modula format. Short of reinstalling the system and adding the accounts again, how can I remove the crypo dist which shouldn't on there and bring the system back to the same passwd format our other FreeBSD (3.4-STABLE though) servers are using. Or is a full reinstallation required? Are there any penalties or legal issues using crypto in Australia? I'm not quite sure of why its a big deal during installation. TIA. -Jarrod To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 20:15: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9B85137B718; Sun, 23 Apr 2000 20:14:58 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA74464; Sun, 23 Apr 2000 20:14:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 23 Apr 2000 20:14:58 -0700 (PDT) From: Kris Kennaway To: Jarrod Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CRYPO dist installed outside US In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Apr 2000, Jarrod wrote: > Short of reinstalling the system and adding the accounts again, how can I > remove the crypo dist which shouldn't on there and bring the system back > to the same passwd format our other FreeBSD (3.4-STABLE though) servers > are using. Or is a full reinstallation required? All you need to do is point the /usr/lib/libcrypt.* symlinks at /usr/lib/libscrypt.* instead of /usr/lib/libdescrypt.* where they are now. i.e. boot single-user, remove the symlinks, and recreate them with ln -s Then reset any passwords which were created in DES format using 'passwd'. Now your system will be MD5 ("$1$....") only again. > Are there any penalties or legal issues using crypto in Australia? I'm > not quite sure of why its a big deal during installation. You're quite allowed to use it :) In fact it's a good thing to install the crypto dist: you now have SSH support almost out of the box [*]. The only downsides are: 1) DES passwords get automatically selected, and DES passwords suck (relatively speaking) 2) You're using the semi-crippled US version of OpenSSL, instead of the better international version. See [*] [*] See http://www.freebsd.org/handbook/openssl.html Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 23: 3:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 10ADE37B747; Sun, 23 Apr 2000 23:03:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA66185; Sun, 23 Apr 2000 23:03:14 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 23:03:14 -0700 (PDT) From: Matthew Dillon Message-Id: <200004240603.XAA66185@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: To MFC or not to MFC, that is the question. References: <10801.956522360@zippy.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Really, then you have a short memory. Why don't we ask Jordan for a :> clarification. : :How about if you let me review the patches in question and I'll render :a decision. : :If you, Matt, could put the SMP and linux stuff into -current first :and then give me a day or so to check it out, I'll submit my own :opinion on whether or not this is "immediate MFC" material. The linux patch is the only patch under discussion here in regards to the simultanious commit/MFC issue. The SMP work was committed to current almost a month ago so MFC'ing it now is not really an issue. (besides, if you remember our conversation back then both of us actually did all of our testing of the SMP patch under 4.x rather then 5.x). The linux scripting patch is available, as I already posted, at: http://www.backplane.com/FreeBSD4/ While it has not been committed to -current or -stable yet, it has been up for review for a while (3 weeks) and I have tested extensively while installing oracle and java under linux emulation. And it only effects linux emulation so it isn't as though MFC'ing it will suddenly break FreeBSD even under the worst possible assumptions. As DG said, the linux scripting patch is simply not this big a deal... I don't know what Poul is barking at. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Apr 23 23:17:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E79D437B9D7; Sun, 23 Apr 2000 23:17:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA66270; Sun, 23 Apr 2000 23:17:51 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 23:17:51 -0700 (PDT) From: Matthew Dillon Message-Id: <200004240617.XAA66270@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility References: <10872.956523122@zippy.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm sure that something can be done for the kld compatibility issues :so that you can have your SMP cake and eat it too. Just give it a bit :more thought. :) : :- Jordan Thought I have. Time I don't. While I don't particularly see a problem staying compatible with KLD modules that do spl*() calls, It's several day's worth of additional work when we go through the whole review / test / test-again process. I've already gone through this process for what was committed to -current and I have already tested the patches under 4.x. I do not have time to go through it yet again due to having to make additional difficult-to-test changes. If this is an issue I suppose core can vote on whether the SMP cleanup should be MFC'd to 4.x. I've already laid out all the reasons why I think it's a good idea to do. I don't have the 40 man-hours it will take to guarentee compatibility with existing kld's (even if most are probably already compatible) so if you make that a requirement, the result will be no MFC at all. So you guys (core) choose -- do you want 4.x to reap the benefits of further SMP development or not? If you choose no, beware that without this base cleanup there is *NO* chance whatsoever of any further SMP work being MFC'd to 4.x. None. Zilch. It will have diverged too much. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 0:33:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay.uvd.chel.su (uvd.chel.su [195.54.2.174]) by hub.freebsd.org (Postfix) with ESMTP id 0F7F137B976 for ; Mon, 24 Apr 2000 00:33:48 -0700 (PDT) (envelope-from lw@pd.chel.ru) Received: from isergeya.uvd.chel.su (isergeya.uvd.chel.su [192.168.200.123]) by relay.uvd.chel.su (Postfix) with ESMTP id 18AC93C for ; Mon, 24 Apr 2000 13:33:35 +0600 (YEKST) Date: Mon, 24 Apr 2000 13:33:31 +0500 From: "Sergey A. Ivanov" X-Mailer: The Bat! (v1.41) UNREG / CD5BF9353B3B7091 Reply-To: "Sergey A. Ivanov" X-Priority: 3 (Normal) Message-ID: <5564.000424@pd.chel.ru> To: freebsd-stable@freebsd.org Subject: sio interrupt handler problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello freebsd-stable! I have 4.0S installed on old 468dx66. Part of dmesg: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16450 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16450 I have slip to my provider by 33.6 modem connected to sio0 (slattach -ha -s 38400 -r "" /dev/cuaa0) It seems to be working, but i have lots of messages in /var/log/message like: Apr 24 13:29:47 relay /HUB: sio0: 5 more silo overflows (total 4632) Apr 24 13:30:45 relay /HUB: sio0: 2 more silo overflows (total 4634) man sio says "Interrupt handler problem". What can i to eliminate this problem? Best regards, Sergey mailto:lw@pd.chel.ru ICQ UIN: 49432691 http://lw.narod.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 3:25:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id CFC5637B58A; Mon, 24 Apr 2000 03:25:33 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12jg3Y-0002Zv-0X; Mon, 24 Apr 2000 11:25:32 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA04164; Mon, 24 Apr 2000 11:34:47 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 24 Apr 2000 11:30:58 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday In-Reply-To: <200004231855.LAA63309@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Apr 2000, Matthew Dillon wrote: > There's another good reason to MFC the linux patch on wednesday... > that is, to do it at the same time the SMP cleanup is MFC'd, and that > is because both patch sets require the linux kernel module to be > recompiled and I'd rather not force people to do that twice. > > The SMP patchset, in fact, requires that all kernel modules be > recompiled due to the locks that were removed from the spl*() macros. > This is something I would contemplate doing for 4.0->4.1, but not > something I would consider for 4.1 onward. Even though 4.0 is the > most stable .0 release we've ever had, it's still a .0. > > I wonder if it makes sense to add a release id to the module header > and have the module loader refuse (unless forced) to load modules that > are out-of-date with the kernel? This sounds quite reasonable. Perhaps you should commit the linux patch to -current right now and then merge it on Wednesday. That would give plenty of time for any teething problems to show up. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 3:36:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 790B737B79F; Mon, 24 Apr 2000 03:36:34 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12jgEC-000Jnf-0K; Mon, 24 Apr 2000 10:36:32 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA04192; Mon, 24 Apr 2000 11:45:43 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 24 Apr 2000 11:41:53 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: "Jordan K. Hubbard" , "Rodney W. Grimes" , Poul-Henning Kamp , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SMP changes and breaking kld object module compatibility In-Reply-To: <200004240617.XAA66270@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Apr 2000, Matthew Dillon wrote: > :I'm sure that something can be done for the kld compatibility issues > :so that you can have your SMP cake and eat it too. Just give it a bit > :more thought. :) > : > :- Jordan > > Thought I have. Time I don't. While I don't particularly see a > problem staying compatible with KLD modules that do spl*() calls, > It's several day's worth of additional work when we go through > the whole review / test / test-again process. I've already gone > through this process for what was committed to -current and I have > already tested the patches under 4.x. I do not have time to go > through it yet again due to having to make additional difficult-to-test > changes. > > If this is an issue I suppose core can vote on whether the SMP > cleanup should be MFC'd to 4.x. I've already laid out all the > reasons why I think it's a good idea to do. I don't have the 40 > man-hours it will take to guarentee compatibility with existing kld's > (even if most are probably already compatible) so if you make that > a requirement, the result will be no MFC at all. > > So you guys (core) choose -- do you want 4.x to reap the benefits of > further SMP development or not? If you choose no, beware that without > this base cleanup there is *NO* chance whatsoever of any further SMP > work being MFC'd to 4.x. None. Zilch. It will have diverged too > much. Personally (i.e. not speaking for core), I really want to preserve both the API and ABI for as many kernel interfaces as possible in the 4.x branch. This does restrict the kinds of work which can be done on 4.x but I'm convinced that this will improve both the percieved ("I recompiled my kernel and now it panics on boot - this sucks") and actual stability of the system. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 8:41:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 99AB937BB5A for ; Mon, 24 Apr 2000 08:41:09 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12jkyn-0000G3-00 for freebsd-stable@freebsd.org; Mon, 24 Apr 2000 11:40:57 -0400 Date: Mon, 24 Apr 2000 11:40:57 -0400 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: sio interrupt handler problem Message-ID: <20000424114057.A692@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <5564.000424@pd.chel.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <5564.000424@pd.chel.ru>; from lw@pd.chel.ru on Mon, Apr 24, 2000 at 01:33:31PM +0500 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Sergey A. Ivanov" probably said: > sio0: type 16450 > sio1: type 16450 > Apr 24 13:29:47 relay /HUB: sio0: 5 more silo overflows (total 4632) > Apr 24 13:30:45 relay /HUB: sio0: 2 more silo overflows (total 4634) > What can i to eliminate this problem? Get some real serial ports. 16450 ports, in my experience, really suck. From the era when they were common you can find dual fast serial cards with two 16550A ports on them, which are considerably better. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 10: 6:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [63.147.8.7]) by hub.freebsd.org (Postfix) with ESMTP id B073937BA1C for ; Mon, 24 Apr 2000 10:06:33 -0700 (PDT) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [63.147.8.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id PAA04260; Sun, 23 Apr 2000 15:55:50 -0400 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id PAA89571; Sun, 23 Apr 2000 15:19:53 -0500 (CDT) (envelope-from kris@hiwaay.net) Date: Sun, 23 Apr 2000 15:19:52 -0500 (CDT) From: Kris Kirby To: mi@privatelabs.com Cc: binderj@earthlink.net, freebsd-stable@FreeBSD.ORG Subject: Re: SB16 in 4.0 In-Reply-To: <200004201226.IAA06154@misha.privatelabs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know where the (unusable) pcm0 comes from... > > -mi IIRC, that is the "auto-detect" entry. Most PnP sound cards are setup to use pcm1. ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 10: 8: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 970A637B5F1; Mon, 24 Apr 2000 10:07:58 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id KAA27091; Mon, 24 Apr 2000 10:07:36 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <39047F57.61D37EC4@gorean.org> Date: Mon, 24 Apr 2000 10:07:35 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0422 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: "Jordan K. Hubbard" , "Rodney W. Grimes" , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility References: <10872.956523122@zippy.cdrom.com> <200004240617.XAA66270@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > So you guys (core) choose -- do you want 4.x to reap the benefits of > further SMP development or not? If you choose no, beware that without > this base cleanup there is *NO* chance whatsoever of any further SMP > work being MFC'd to 4.x. None. Zilch. It will have diverged too > much. I think that we can find a middle ground on this issue. Jordan made an excellent point in that this ".0" release has had more early adopters than any previous first release on a new branch. Therefore we want to take extra care to maintain the "-stable" perception of the 4.0-Stable branch. At the same time, Matt is correct in saying that the base of the SMP improvements needs to go into 4.0 now. The PR ramifications alone would be disastrous if the only place the SMP improvements were available was 5.0-Current. That would simply reinforce the perception that FreeBSD is nothing more than a toy for the developers. On the third hand (so to speak) is the fact that we really would like to be able to present a stable external interface to encourage third party developers to develop to the 4.x branch. So, my suggested compromise is this. Do the MFC now, with the caveat that this will be the only external interface change in 4.x-Stable. Architect out whatever changes have to happen, and make sure that the best guess as to what the interface should be gets committed, then stick to it, no matter how painful it is. It's still early enough to get away with this, but we can only "sell it" once, so let's get it right this time. I've got a fleet of SMP boxes at work, and given the coming instability of -Current I'd really like to stick with 4.0-Stable if I can, and in fact I've already made plans that relied on the work Matt's already done being MFC'ed as previously announced. I could probably justify the development time to track -Current if the performance gains were large enough, and in fact I'll probably put a machine or two on it to try and make a contribution to testing, etc. But speaking as a sysadmin the advantages of being able to rely on well tested changes that get MFC'ed on a regular basis for the majority of my machines would be a huge win. Doug -- Excess on occasion is exhilarating. It prevents moderation from acquiring the deadening effect of a habit. -- W. Somerset Maugham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 10:28:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hbo.isi.edu (hbo.isi.edu [128.9.160.75]) by hub.freebsd.org (Postfix) with ESMTP id 9B1A937B668 for ; Mon, 24 Apr 2000 10:28:34 -0700 (PDT) (envelope-from larse@hbo.isi.edu) Received: (from larse@localhost) by hbo.isi.edu (8.9.3/8.9.3) id KAA33819; Mon, 24 Apr 2000 10:28:33 -0700 (PDT) (envelope-from larse) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14596.33857.265346.378085@hbo.isi.edu> Date: Mon, 24 Apr 2000 10:28:33 -0700 (PDT) From: Lars Eggert To: freebsd-stable@freebsd.org Subject: inetd _secure_path messages Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I see a number of these messages in syslog: inetd[6716]: _secure_path: cannot stat /etc/login.conf: Permission denied I couldn't find any indication why inetd would complain, since /etc/login.conf is there and readable: [larse@sub: ~] ls -lg /etc/login.conf* -rw-r--r-- 1 root wheel 6325 Apr 19 17:30 /etc/login.conf -rw-r--r-- 1 root wheel 32768 Apr 21 01:26 /etc/login.conf.db Any ideas? Thanks, Lars ________________________________________________________________________ Lars Eggert Information Sciences Institute http://www.isi.edu/~larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 11:55: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2B21537BB8D; Mon, 24 Apr 2000 11:55:00 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA14088; Mon, 24 Apr 2000 11:55:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility In-reply-to: Your message of "Sun, 23 Apr 2000 23:17:51 PDT." <200004240617.XAA66270@apollo.backplane.com> Date: Mon, 24 Apr 2000 11:55:57 -0700 Message-ID: <14085.956602557@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So you guys (core) choose -- do you want 4.x to reap the benefits of > further SMP development or not? I've read all the feedback on this thread and now feel that it would be worthwhile to simply bring the SMP changes in on Wednesday. As others have pointed out, we don't have enough 3rd party 4.0 klds yet (I'd have a hard time even saying "any") to make this a real problem so let's just go for it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 12:17: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from logatome.francenet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id E5C8037BBE4 for ; Mon, 24 Apr 2000 12:16:53 -0700 (PDT) (envelope-from e-masson@kisoft-services.com) Received: from localhost.nantes.kisoft-services.com (pppA229.francenet.fr [193.149.100.139]) by logatome.francenet.fr (8.10.1/8.10.1) with SMTP id e3OJGnh89252 for ; Mon, 24 Apr 2000 21:16:49 +0200 (CEST) X-Mailer: 21.1 (patch 9) "Canyonlands" XEmacs Lucid (via feedmail 8 Q); VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14596.37283.563515.214828@localhost.nantes.kisoft-services.com> Date: Mon, 24 Apr 2000 20:25:39 +0200 (CEST) From: Eric Masson To: freebsd-stable@FreeBSD.ORG Subject: Re: sio interrupt handler problem In-Reply-To: <20000424114057.A692@pir.net> References: <5564.000424@pd.chel.ru> <20000424114057.A692@pir.net> Reply-To: e-masson@kisoft-services.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Radcliffe writes: >Get some real serial ports. > >16450 ports, in my experience, really suck. From the era when they >were common you can find dual fast serial cards with two 16550A ports >on them, which are considerably better. Hello Thinkpad 390 2626-700 (PII-266 64Mo) FreeBSD notbsdems.nantes.kisoft-services.com 4.0-STABLE FreeBSD 4.0-STABLE #0: Mon Apr 24 13:02:58 CEST 2000 emss@notbsdems.nantes.kisoft-services.com: /usr/src/sys/compile/THINKPAD i386 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A So i assume my box has real serial ports :). I encounter lots of silo overflows while using userland ppp under Xfree. - Under XFree86 4.0, approximately 250 Silo Overflows (SO) while fetching mail & news (10 minutes). - Under XFree86 3.3.6, approximately 220 SO for the same task. - Shell mode, xemacs -nw & fetchnews generate 1 SO from time to time. From the previous, i could think that XFree86 is responsible for the SO, but one month ago this box was running 3.4-STABLE & XFree86 3.3.6 and I was wondering what were these SO messages in freebsd-stable mailing list ;). I don't really understand the point. Maybe i misconfigured my kernel. Well all comments welcome. Regards Eric Masson # # THINKPAD -- Generic kernel configuration file for FreeBSD/i386 # machine i386 cpu I686_CPU ident THINKPAD maxusers 32 makeoptions DEBUG=-g options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options NFS_NOSERVER #Disable NFS server code options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SOFTUPDATES options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options TCP_DROP_SYNFIN options TCP_RESTRICT_RST options PSM_HOOKRESUME options PSM_RESETAFTERSUSPEND options PCIC_RESUME_RESET options DDB device isa device pci device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 #device pcm device apm0 at nexus? flags 0x20 # Advanced Power Management device card device pcic0 at isa? device pcic1 at isa? device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device ed pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device bpf #Berkeley packet filter device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ums # Mouse -- Opinions stated below are mine and can't be considered as official Kisoft Services policy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 12:42:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jking1.lgc.com (jking1.lgc.com [134.132.228.2]) by hub.freebsd.org (Postfix) with ESMTP id 2085B37B531 for ; Mon, 24 Apr 2000 12:42:35 -0700 (PDT) (envelope-from king@sstar.com) Received: from jking (jking.lgc.com [134.132.75.164]) by jking1.lgc.com (8.9.3/8.9.3) with SMTP id OAA06266; Mon, 24 Apr 2000 14:42:10 -0500 (CDT) (envelope-from king@sstar.com) Message-ID: <003801bfae25$39a6d100$a44b8486@jking> From: "Jim King" To: , References: <5564.000424@pd.chel.ru><20000424114057.A692@pir.net> <14596.37283.563515.214828@localhost.nantes.kisoft-services.com> Subject: Re: sio interrupt handler problem Date: Mon, 24 Apr 2000 14:42:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, April 24, 2000 1:25 PM, Eric Masson wrote: > Peter Radcliffe writes: > >Get some real serial ports. > > > >16450 ports, in my experience, really suck. From the era when they > >were common you can find dual fast serial cards with two 16550A ports > >on them, which are considerably better. > Hello > > Thinkpad 390 2626-700 (PII-266 64Mo) > > FreeBSD notbsdems.nantes.kisoft-services.com 4.0-STABLE > FreeBSD 4.0-STABLE #0: Mon Apr 24 13:02:58 CEST 2000 > emss@notbsdems.nantes.kisoft-services.com: > /usr/src/sys/compile/THINKPAD i386 > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > > So i assume my box has real serial ports :). > > I encounter lots of silo overflows while using userland ppp under Xfree. > - Under XFree86 4.0, approximately 250 Silo Overflows (SO) while fetching > mail & news (10 minutes). > - Under XFree86 3.3.6, approximately 220 SO for the same task. > - Shell mode, xemacs -nw & fetchnews generate 1 SO from time to time. > > >From the previous, i could think that XFree86 is responsible for the SO, > but one month ago this box was running 3.4-STABLE & XFree86 3.3.6 and I was > wondering what were these SO messages in freebsd-stable mailing list ;). > > I don't really understand the point. Maybe i misconfigured my kernel. Well > all comments welcome. One thing I've done in the past to overcome serial port problems is to patch sys/isa/sio.c to set the FIFO receive trigger level to 8 bytes instead of 14 (FIFO_RX_MEDH instead of FIFO_RX_HIGH). If you have a piece of hardware or a misbehaved driver that's causing high interrupt latency this change be really beneficial, and greatly outweighs the higher interrupt overhead when using an 8 byte trigger. An 8 byte trigger is a safer option that causes better operation on weird hardware without signifcantly changing anything on good hardware. I really wish sio.c would be changed to set the trigger to 8 bytes by default, or at least have a flags option to change the trigger level. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 12:45:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web111.yahoomail.com (web111.yahoomail.com [205.180.60.81]) by hub.freebsd.org (Postfix) with SMTP id 26C3937BC82 for ; Mon, 24 Apr 2000 12:45:07 -0700 (PDT) (envelope-from jimbots@yahoo.com) Received: (qmail 24433 invoked by uid 60001); 24 Apr 2000 19:45:03 -0000 Message-ID: <20000424194503.24432.qmail@web111.yahoomail.com> Received: from [216.126.161.93] by web111.yahoomail.com; Mon, 24 Apr 2000 12:45:03 PDT Date: Mon, 24 Apr 2000 12:45:03 -0700 (PDT) From: Jim Stevens Subject: unsubscribe To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 13:13: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D2DF737BBA2; Mon, 24 Apr 2000 13:12:54 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA13091; Mon, 24 Apr 2000 16:12:25 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA24935; Mon, 24 Apr 2000 16:12:25 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 24 Apr 2000 16:12:24 -0400 (EDT) To: "Jordan K. Hubbard" Cc: Matthew Dillon , "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility In-Reply-To: <14085.956602557@zippy.cdrom.com> References: <200004240617.XAA66270@apollo.backplane.com> <14085.956602557@zippy.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14596.39482.793985.323658@grasshopper.cs.duke.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard writes: > > So you guys (core) choose -- do you want 4.x to reap the benefits of > > further SMP development or not? > > I've read all the feedback on this thread and now feel that it would > be worthwhile to simply bring the SMP changes in on Wednesday. As others > have pointed out, we don't have enough 3rd party 4.0 klds yet (I'd have > a hard time even saying "any") to make this a real problem so let's > just go for it. Are there any 3rd party NIC klds yet? If we're going to be having a module flag day, I'm thinking that it might be a good time to MFC Jonathan Lemon's checksum offloading code. Doing this would require changing MSIZE to 256, which in turn would require recompiling any module using mbufs (all NICs, network filesystems, etc). Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 13:19:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 817F337BBCE; Mon, 24 Apr 2000 13:19:29 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA14569; Mon, 24 Apr 2000 13:20:16 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Andrew Gallatin Cc: Matthew Dillon , "Rodney W. Grimes" , phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility In-reply-to: Your message of "Mon, 24 Apr 2000 16:12:24 EDT." <14596.39482.793985.323658@grasshopper.cs.duke.edu> Date: Mon, 24 Apr 2000 13:20:16 -0700 Message-ID: <14566.956607616@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are there any 3rd party NIC klds yet? NTMK. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 13:31:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id 6A4F437BBD7 for ; Mon, 24 Apr 2000 13:31:46 -0700 (PDT) (envelope-from kdulzo@caffeine.gerp.org) Received: (qmail 10444 invoked by uid 100); 24 Apr 2000 20:14:08 -0000 Date: Mon, 24 Apr 2000 15:13:35 -0500 From: "Kevin M. Dulzo" To: Jim King Subject: Re: sio interrupt handler problem Message-ID: <20000424151335.A10431@caffeine.gerp.org> References: <5564.000424@pd.chel.ru><20000424114057.A692@pir.net> <14596.37283.563515.214828@localhost.nantes.kisoft-services.com> <003801bfae25$39a6d100$a44b8486@jking> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1us In-Reply-To: <003801bfae25$39a6d100$a44b8486@jking>; from king@sstar.com on Mon, Apr 24, 2000 at 02:42:09PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 24, 2000 at 02:42:09PM -0500, Jim King wrote: > > One thing I've done in the past to overcome serial port problems is to patch > sys/isa/sio.c to set the FIFO receive trigger level to 8 bytes instead of 14 > (FIFO_RX_MEDH instead of FIFO_RX_HIGH). If you have a piece of hardware or > a misbehaved driver that's causing high interrupt latency this change be > really beneficial, and greatly outweighs the higher interrupt overhead when > using an 8 byte trigger. > > > An 8 byte trigger is a safer option that causes better operation on weird > hardware without signifcantly changing anything on good hardware. I really > wish sio.c would be changed to set the trigger to 8 bytes by default, or at > least have a flags option to change the trigger level. > > > Jim Couldn't something like this be turned into a tuneable nob via sysctl? Software settable UART buffering is available on MS OSes, could we not mimic this in someway? -Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 13:54:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (mail.dohboys.com [208.26.253.10]) by hub.freebsd.org (Postfix) with ESMTP id 0B17F37B62C for ; Mon, 24 Apr 2000 13:54:17 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (unverified [208.26.242.50]) by corinth.bossig.com (Rockliffe SMTPRA 4.2.1) with ESMTP id ; Mon, 24 Apr 2000 13:58:33 -0700 Message-ID: <3904B46A.3EDB63B4@3-cities.com> Date: Mon, 24 Apr 2000 13:54:02 -0700 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kirby Cc: mi@privatelabs.com, binderj@earthlink.net, freebsd-stable@FreeBSD.ORG Subject: Re: SB16 in 4.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kirby wrote: > > > I don't know where the (unusable) pcm0 comes from... > > > > -mi > > IIRC, that is the "auto-detect" entry. Most PnP sound cards are setup to > use pcm1. If they are PCI, on 4.0 they come up on pcm0. You also use snd0 for the mixer and etc. setup on 4.0. Kent > > ----- > Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. > | > ------------------------------------------------------- > "God gave them the ability to reproduce... > ... Science gave us the hope they won't." -KBK > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 14: 4:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jking1.lgc.com (jking1.lgc.com [134.132.228.2]) by hub.freebsd.org (Postfix) with ESMTP id 97ADA37BBE1 for ; Mon, 24 Apr 2000 14:04:37 -0700 (PDT) (envelope-from king@sstar.com) Received: from jking (jking.lgc.com [134.132.75.164]) by jking1.lgc.com (8.9.3/8.9.3) with SMTP id QAA27978; Mon, 24 Apr 2000 16:03:54 -0500 (CDT) (envelope-from king@sstar.com) Message-ID: <006901bfae30$9f74d300$a44b8486@jking> From: "Jim King" To: "Kevin M. Dulzo" , References: <5564.000424@pd.chel.ru><20000424114057.A692@pir.net> <14596.37283.563515.214828@localhost.nantes.kisoft-services.com> <003801bfae25$39a6d100$a44b8486@jking> <20000424151335.A10431@caffeine.gerp.org> Subject: Re: sio interrupt handler problem Date: Mon, 24 Apr 2000 16:03:53 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, April 24, 2000 3:13 PM, Kevin M. Dulzo wrote: > On Mon, Apr 24, 2000 at 02:42:09PM -0500, Jim King wrote: > > > > One thing I've done in the past to overcome serial port problems is to patch > > sys/isa/sio.c to set the FIFO receive trigger level to 8 bytes instead of 14 > > (FIFO_RX_MEDH instead of FIFO_RX_HIGH). If you have a piece of hardware or > > a misbehaved driver that's causing high interrupt latency this change be > > really beneficial, and greatly outweighs the higher interrupt overhead when > > using an 8 byte trigger. > > > > > > An 8 byte trigger is a safer option that causes better operation on weird > > hardware without signifcantly changing anything on good hardware. I really > > wish sio.c would be changed to set the trigger to 8 bytes by default, or at > > least have a flags option to change the trigger level. > > > > > > Jim > > Couldn't something like this be turned into a tuneable nob > via sysctl? Software settable UART buffering is available on MS > OSes, could we not mimic this in someway? > > -Kevin Sounds like a good idea to me. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 14: 8: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 1438037BC32 for ; Mon, 24 Apr 2000 14:08:02 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id OAA43700; Mon, 24 Apr 2000 14:07:56 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 24 Apr 2000 14:07:56 -0700 (PDT) From: Doug White To: Cy Schubert - ITSD Open Systems Group Cc: Matthew Dillon , freebsd-stable@FreeBSD.ORG Subject: Re: Linux Emulation Root (was: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday) In-Reply-To: <200004231924.MAA00521@cwsys.cwsent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Apr 2000, Cy Schubert - ITSD Open Systems Group wrote: > In message <200004231835.LAA62963@apollo.backplane.com>, Matthew Dillon > writes: > > I intend to commit this to -current and immediately MFC it to -stable. > > I don't expect there to be any controversy though I'm sure there is a > > cleaner way to do it. > > On a semi-related topic, it would be handy to have a feature, > environment variable, table in the kernel, a sysctl variable, etc., to > set the Linux emulation root to the real root. For example, the backup > component of Legato for Linux (nsrexecd and friends) runs nicely on > under Linux emulation, however, recovering files in the root directory > sees them placed in the Linux emulation root directory. I ran into a similar problem with ADSM -- it would happily back up /compat/linux thinking it was backing up /. I patched the linux mode KLD to disable the /compat/linux path munging. I tried to submit it back but was shot down; the emulation people wanted a more general method, which I assume included a way to define your own 'linux root'. The discussion got lost some time after that in -emulation. > To work around this I've used a union filesystem that mounted / on > another mount point and redirected my restores to it. Unforunately union mounts are known unstable. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 15: 2:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A3CF837BBB4; Mon, 24 Apr 2000 15:02:34 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA11779; Mon, 24 Apr 2000 15:01:34 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004242201.PAA11779@gndrsh.dnsmgr.net> Subject: Re: SMP changes and breaking kld object module compatibility In-Reply-To: <14566.956607616@zippy.cdrom.com> from "Jordan K. Hubbard" at "Apr 24, 2000 01:20:16 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 24 Apr 2000 15:01:34 -0700 (PDT) Cc: gallatin@cs.duke.edu (Andrew Gallatin), dillon@apollo.backplane.com (Matthew Dillon), phk@critter.freebsd.dk (Poul-Henning Kamp), freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG {First one bounced by hub with ``out of memory'' error... second attempt} > > Are there any 3rd party NIC klds yet? > > NTMK. It's not quite a kld, but ET Inc's modules are distributed as a .o. Also I know of work underway to support some of the fancier SDL WanNic cards that would have to be kld's or .o's as well, due to NDA on parts of the code used to develope them. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 15:22:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hbo.isi.edu (hbo.isi.edu [128.9.160.75]) by hub.freebsd.org (Postfix) with ESMTP id 21E9937B5AA for ; Mon, 24 Apr 2000 15:22:50 -0700 (PDT) (envelope-from larse@hbo.isi.edu) Received: (from larse@localhost) by hbo.isi.edu (8.9.3/8.9.3) id PAA01431; Mon, 24 Apr 2000 15:20:53 -0700 (PDT) (envelope-from larse) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14596.51397.26843.479453@hbo.isi.edu> Date: Mon, 24 Apr 2000 15:20:53 -0700 (PDT) From: Lars Eggert To: freebsd-stable@freebsd.org Subject: CS461x & newpcm & rat/vat Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having problems using a Crystal Semiconductor CS4614 onboard audio device with newpcm and the mbone tools vat/rat. [larse@hbo: ~] cat /dev/sndstat FreeBSD Audio Driver (newpcm) Apr 18 2000 10:07:38 Installed devices: pcm0: at irq 5 (1p/1r channels duplex) The device works fine playing MP3, CD and other audio - however, running vat results in: [larse@hbo: ~] vat dum/7777 sorry don't know how to deal with this card failed to select input sorry don't know how to deal with this card failed to set mic volume failed set input line volume failed to output level 70 failed to output level 70 sorry don't know how to deal with this card failed to set mic volume failed set input line volume Running rat gives no such message, but no audio is being received or sent. Any clues? Lars ________________________________________________________________________ Lars Eggert Information Sciences Institute http://www.isi.edu/~larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 17: 9:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay1.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with SMTP id C115337B5AA for ; Mon, 24 Apr 2000 17:09:12 -0700 (PDT) (envelope-from keefeg@keefeg.com) Received: (qmail 25786 invoked from network); 25 Apr 2000 00:01:14 -0000 Received: from adsl-151-201-240-68.bellatlantic.net (HELO gregpc) (151.201.240.68) by relay1.pair.com with SMTP; 25 Apr 2000 00:01:14 -0000 X-pair-Authenticated: 151.201.240.68 Message-ID: <000a01bfae49$b910e100$0100a8c0@gregpc> From: "Gregory Keefe" To: Subject: join Date: Mon, 24 Apr 2000 20:03:44 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01BFAE28.3192EAA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01BFAE28.3192EAA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable join ------=_NextPart_000_0007_01BFAE28.3192EAA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
join
------=_NextPart_000_0007_01BFAE28.3192EAA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 20:43:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id BA7D037BC45 for ; Mon, 24 Apr 2000 20:43:43 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id XAA93541 for ; Mon, 24 Apr 2000 23:43:42 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id XAA03865 for ; Mon, 24 Apr 2000 23:43:41 -0400 (EDT) Message-Id: <4.2.2.20000424233913.039ecf08@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 24 Apr 2000 23:42:22 -0400 To: stable@freebsd.org From: Mike Tancsa Subject: /usr/src/sys/modules/mlx Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone else seeing problems in make world on RELENG_4 ? cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_attach': /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:273: `disks_registered' undeclared (first use in this function) /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:273: (Each undeclared identifier is reported only once /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:273: for each function it appears in.) /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_detach': /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:291: `disks_registered' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/sys/modules/mlx. newmail# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 21: 7:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.kurgan.ru (phoenix.kurgan.ru [195.54.28.21]) by hub.freebsd.org (Postfix) with ESMTP id C15EF37BC18 for ; Mon, 24 Apr 2000 21:07:48 -0700 (PDT) (envelope-from Martin@McFlySr.Kurgan.Ru) Received: from McFlySr (hilldale.kurgan.ru [195.54.28.11]) by phoenix.kurgan.ru (8.9.3/8.9.3) with ESMTP id KAA31289 for ; Tue, 25 Apr 2000 10:04:42 +0600 (YEKST) Date: Tue, 25 Apr 2000 10:07:42 +0600 From: Martin McFlySr Reply-To: Martin McFlySr Organization: Back To The Future X-Priority: 3 (Normal) Message-ID: <4422.000425@McFlySr.Kurgan.Ru> To: stable@FreeBSD.ORG Subject: 3.4 make trouble Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello stable@FreeBSD.ORG, cvsup, then "make world". OK reboot, #cd /usr/src/sys/i386/conf #config Machine OK #cd ../../compile/Machine #make depend OK #make cc -c -x assembler-with-cpp -DLOCORE -O -Wreturn-type -Wcomment -Wredundant-decl s -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint er-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_g lobal.h -elf ../../i386/i386/locore.s /var/tmp/ccx23297.s: Assembler messages: /var/tmp/ccx23297.s:2395: Error: operands given don't match any known 386 instru ction /var/tmp/ccx23297.s:2396: Error: operands given don't match any known 386 instru ction /var/tmp/ccx23297.s:2412: Error: operands given don't match any known 386 instru ction /var/tmp/ccx23297.s:2413: Error: operands given don't match any known 386 instru ction /var/tmp/ccx23297.s:2418: Error: operands given don't match any known 386 instru ction /var/tmp/ccx23297.s:2423: Error: operands given don't match any known 386 instru ction /var/tmp/ccx23297.s:2428: Error: operands given don't match any known 386 instru ction *** Error code 1 Stop. What must i do for make kernel ? Thank you, -- Tuesday, April 25, 2000, 10:05 Best regards from future, Martin McFlySr, HillDale. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 21:54:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from greed.zenspider.com (greed.zenspider.com [216.39.164.65]) by hub.freebsd.org (Postfix) with SMTP id 540C937BC73 for ; Mon, 24 Apr 2000 21:53:49 -0700 (PDT) (envelope-from ryand@zenspider.com) Received: (qmail 81382 invoked from network); 25 Apr 2000 04:52:06 -0000 Received: from lust.zenspider.com (HELO ?216.39.164.68?) (216.39.164.68) by greed.zenspider.com with SMTP; 25 Apr 2000 04:52:06 -0000 Mime-Version: 1.0 Message-Id: Date: Mon, 24 Apr 2000 21:53:46 -0700 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org From: Ryan Davis Subject: 3.4S -> 4.0S botched, can't build anything now Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG buildworld worked fine. installworld failed. I followed the instructions in /usr/src/UPDATING as best I could, but I still think it is conflicting on whether to build the kernel first or not. Doesn't matter, trying to build the kernel first failed, presumably because config has changed. I have gone through several phases: 1) The first and most innocent ended with: ===> lib/libcom_err/doc install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming & development tools.' Try `install-info --help' for a complete list of options. I fixed this with something from the mail archives. 2) Next was the immediate coredump on any make: "/usr/src/Makefile", line 101: warning: "LC_TIME=C date" returned non-zero status *** Signal 12 I figured out that /bin/sh would core. I copied /bin/bash over it and it worked fine. 3) Finally, after trying to clean up and rebuild: /usr/obj/usr/src/i386/usr/bin/byacc -> /usr/obj/usr/src/i386/usr/bin/yacc cd /usr/src/usr.bin/colldef; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for /usr/src/usr.bin/colldef yacc -d /usr/src/usr.bin/colldef/parse.y *** Signal 12 I am stuck. The only thing I've found that is relevant to #3 is to cd to yacc's directory and make install, but I'm apparently not far enough in the general build anymore for that to work. The wierd thing is, unlike #2 where any use of /bin/sh would core, yacc works fine on the commandline. I am trying to restore from tape now to see if I can roll out the partial install until I get this under control. I am really disappointed in how bad this transition has been. I usually brag to linux bigots about how painless keeping up to date BSD is w/ cvsup and /usr/src. -- Ryan Davis -=- Zen Spider Software -=- mailto:ryand@ZenSpider.com -=- http://www.ZenSpider.com/ -=- I know that you believe you understand what you think I said but, I'm not sure you realize that what you heard is not what I meant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 22:14:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id CC12337BC9D; Mon, 24 Apr 2000 22:14:29 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id WAA08655; Mon, 24 Apr 2000 22:14:26 -0700 (PDT) Date: Mon, 24 Apr 2000 22:14:26 -0700 From: Brooks Davis To: Ryan Davis Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 3.4S -> 4.0S botched, can't build anything now Message-ID: <20000424221426.A2314@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from ryand@zenspider.com on Mon, Apr 24, 2000 at 09:53:46PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 24, 2000 at 09:53:46PM -0700, Ryan Davis wrote: > I followed the instructions in /usr/src/UPDATING as best I could, but > I still think it is conflicting on whether to build the kernel first > or not. Doesn't matter, trying to build the kernel first failed, > presumably because config has changed. You must build a kernel first. The instructions are pretty clear. I supposed it could be changed to "YOU MUST INSTALL A NEW KERNEL BEFORE RUNNING `INSTALLWORLD' OR YOU WILL HOSE YOUR SYSTEM!!!", but that seems like overkill. Generally it's assumed that instructions listed in order should be executed that way unless someone says otherwise. > I am stuck. The only thing I've found that is relevant to #3 is to cd > to yacc's directory and make install, but I'm apparently not far > enough in the general build anymore for that to work. The wierd thing > is, unlike #2 where any use of /bin/sh would core, yacc works fine on > the commandline. You probably have a libc installed that won't work with your kernel. > I am trying to restore from tape now to see if I can roll out the > partial install until I get this under control. I am really > disappointed in how bad this transition has been. I usually brag to > linux bigots about how painless keeping up to date BSD is w/ cvsup > and /usr/src. That's the easiest answer. It's definatly recommended that you read the lists extensivly before making a major version jump. Doubly so when doing it via sources. Extensive examples of people shooting their foot in exactly the same way you did are available in both the -stable and -current archives. :-) -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 22:37: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yoda.dccnet.com (mail.deltacable.com [207.230.239.70]) by hub.freebsd.org (Postfix) with ESMTP id C2C5937BC93; Mon, 24 Apr 2000 22:36:54 -0700 (PDT) (envelope-from kg@versys.net) Received: from versys.net (unverified [209.5.131.193]) by yoda.dccnet.com (Rockliffe SMTPRA 3.4.6) with ESMTP id ; Mon, 24 Apr 2000 22:30:15 -0700 Message-ID: <39052DCF.DC16C2E7@versys.net> Date: Mon, 24 Apr 2000 22:31:59 -0700 From: "Kevin G. Eliuk" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ryan Davis Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 3.4S -> 4.0S botched, can't build anything now References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ryan Davis wrote: > > buildworld worked fine. > > installworld failed. > > I followed the instructions in /usr/src/UPDATING as best I could, but > I still think it is conflicting on whether to build the kernel first > or not. Doesn't matter, trying to build the kernel first failed, > presumably because config has changed. > > I have gone through several phases: > > 1) The first and most innocent ended with: > > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." > --defentry="* libcom_err: (com_err). A Common Error > Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & > development tools.' > Try `install-info --help' for a complete list of options. > > I fixed this with something from the mail archives. > > 2) Next was the immediate coredump on any make: > > "/usr/src/Makefile", line 101: warning: "LC_TIME=C date" returned > non-zero status > *** Signal 12 > > I figured out that /bin/sh would core. I copied /bin/bash over it and > it worked fine. > > 3) Finally, after trying to clean up and rebuild: > > /usr/obj/usr/src/i386/usr/bin/byacc -> /usr/obj/usr/src/i386/usr/bin/yacc > cd /usr/src/usr.bin/colldef; make obj; make depend; make all; make install > /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for > /usr/src/usr.bin/colldef > yacc -d /usr/src/usr.bin/colldef/parse.y > *** Signal 12 > > I am stuck. The only thing I've found that is relevant to #3 is to cd > to yacc's directory and make install, but I'm apparently not far > enough in the general build anymore for that to work. The wierd thing > is, unlike #2 where any use of /bin/sh would core, yacc works fine on > the commandline. > > I am trying to restore from tape now to see if I can roll out the > partial install until I get this under control. I am really > disappointed in how bad this transition has been. I usually brag to > linux bigots about how painless keeping up to date BSD is w/ cvsup > and /usr/src. Just dId the same today (cautiously) quite cleanly. (Starting from 3.4R) # cd /usr/src # make buildworld # cd /usr/src/sbin/mknod # make install # cd /usr/src/sys/modules # make install # cd /usr/src (Having edited my kernel config file "QUARTZ" while waiting for buildworld to finish) # make buildkernel KERNEL=QUARTZ # make installkernel KERNEL=QUARTZ # cp /usr/src/etc/MAKEDEV /dev # cd /dev # ./MAKEDEV ad0 (in my case) # ./MAKEDEV ad0s2a (again in my case) # vi /etc/fstab (change wd* to ad* entries) # shutdown -r now Rebooting and interupting the reboot ok set boot_single ok unload ok load /QUARTZ ok boot (I must admit I held my breath) After booting and manually mounting the slices ... # cd /usr/src # make -DNOINFO installworld # make installworld # mergemaster -cv -t /usr/tmp/root-20000424 # shutdown -r now After fixing a couple of other things like snd devices and ethernet devices it was a lot less tramatic than I was made to believe. -- Regards, Kevin G. Eliuk Technician | VerSys Communications Ltd. | http://www.versys.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Apr 24 23:37:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 2B8D737BCAC; Mon, 24 Apr 2000 23:37:05 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA09320; Tue, 25 Apr 2000 02:36:59 -0400 Date: Tue, 25 Apr 2000 02:36:59 -0400 (EDT) From: Mike Nowlin To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, adoyle@viewsnet.com Subject: Re: To MFC or not to MFC, that is the question. In-Reply-To: <10801.956522360@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > personalities or styles. In this case, I'd say it was a job for the > CRC if we currently had one. :) Does that make it a "CRC Check"? :) (Good old redundant-terminology Cyclical-Reduncancy-Check Checks.....) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 0:44:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ds9.sci.fi (ds9.sci.fi [195.74.0.54]) by hub.freebsd.org (Postfix) with ESMTP id 9523B37BCA2; Tue, 25 Apr 2000 00:44:29 -0700 (PDT) (envelope-from juksi@iname.com) Received: from sjukebox (MMCDLVII.hdyn.saunalahti.fi [195.197.44.57]) by ds9.sci.fi (8.9.1/8.9.1) with ESMTP id KAA24918; Tue, 25 Apr 2000 10:43:56 +0300 (EET DST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000424221426.A2314@orion.ac.hmc.edu> Date: Tue, 25 Apr 2000 10:43:38 +0300 (EEST) From: Jukka Simila To: Brooks Davis Subject: Re: 3.4S -> 4.0S botched, can't build anything now Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Ryan Davis Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Apr-00 Brooks Davis wrote: > On Mon, Apr 24, 2000 at 09:53:46PM -0700, Ryan Davis wrote: >> I followed the instructions in /usr/src/UPDATING as best I could, but >> I still think it is conflicting on whether to build the kernel first >> or not. Doesn't matter, trying to build the kernel first failed, >> presumably because config has changed. I wasn't able to build a custom kernel; instead I built a GENERIC and that worked. (After I had similar problems like you) > >> I am trying to restore from tape now to see if I can roll out the >> partial install until I get this under control. I am really >> disappointed in how bad this transition has been. I usually brag to >> linux bigots about how painless keeping up to date BSD is w/ cvsup >> and /usr/src. > > That's the easiest answer. I don't think so; I messed up my 3.4 installation (as I thought) when I tried to upgrade to 4.0. Installworld gave me signal 12 thousands of times before I went back to the UPDATING. Thou I had tried to make installworld with 3.4's kernel and also tried to copy old sh to /bin/sh, when the new one gave the signal 12, I was still able to compile the GENERIC. And after a reboot with GENERIC, I could finish the installworld. So if you (Ryan) just have the GENERIC (4.0) around, or are able to compile it, then give it a try before starting it all over again. After you have a working 4.0 system, your custom kernel should also work. @-`--,--`--- Jukka Simila To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 3:15:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 399AA37BCDD; Tue, 25 Apr 2000 03:15:02 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-20.iptelecom.net.ua [212.9.226.148]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA23880; Tue, 25 Apr 2000 13:22:24 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA00515; Tue, 25 Apr 2000 13:14:24 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <39056FFF.5734CAA8@altavista.net> Date: Tue, 25 Apr 2000 13:14:23 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Cc: stable@freebsd.org Subject: KLD related panic (RELENG_4 & RELENG_5) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just found what it seems to me an error somewhere in the KLD modules implementation affecting both 4-STABLE and 5-CURRENT. Following course of actions makes kernel panic on both releases: 1. Load vn module into kernel 2. Configure vn device using vnconfig 3. Mount vn device 4. Unmount vn device 5. Unconfigure vn device 6. Unload vn kernel module 7. Try to mount vn device. Instead of expected "device not configured" you'll have kernel panic. It seems that vn device failed to deregister itself properly on kldunload. -Maxim Following is script of my session: # kldstat Id Refs Address Size Name 1 2 0xc0100000 1c2f48 kernel 2 1 0xc02c3000 30c8 splash_bmp.ko root@notebook# vnconfig -c /dev/vn0 /tmp/tst root@notebook# kldstat Id Refs Address Size Name 1 3 0xc0100000 1c2f48 kernel 2 1 0xc02c3000 30c8 splash_bmp.ko 3 1 0xc08b9000 3000 vn.ko root@notebook# mount /dev/vn0c /mnt root@notebook# mount /dev/ad0s1a on / (ufs, asynchronous, NFS exported, local, noatime, writes: sync 4 async 41, reads: sync 507 async 22) procfs on /proc (procfs, local) /dev/vn0c on /mnt (ufs, local, writes: sync 2 async 0, reads: sync 1 async 0) root@notebook# umount /mnt root@notebook# vnconfig -u /dev/vn0 root@notebook# kldunload -i 3 root@notebook# kldstat Id Refs Address Size Name 1 2 0xc0100000 1c2f48 kernel 2 1 0xc02c3000 30c8 splash_bmp.ko root@notebook# mount /dev/vn0c /mnt Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc08bb9f0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc016d9b9 stack pointer = 0x10:0xc3313d64 frame pointer = 0x10:0xc3313d70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 209 (mount) interrupt mask = none trap number = 12 panic: page fault To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4: 4:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id ED31537BD64 for ; Tue, 25 Apr 2000 04:04:13 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-205.ix.netcom.com [209.109.232.205]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA21769; Tue, 25 Apr 2000 07:04:09 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id EAA02860; Tue, 25 Apr 2000 04:04:06 -0700 (PDT) To: Martin Blapp Cc: freebsd-stable@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 25 Apr 2000 04:04:05 -0700 In-Reply-To: Martin Blapp's message of "Mon, 24 Apr 2000 11:45:38 +0200" Message-ID: Lines: 42 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Martin Blapp (Moved back to -stable, don't know why it was in -current.) * I really like to see your fix committed to STABLE. It fixes also the * bad designed Staroffice 5.2 installation for some part (/usr/sbin/test). Well, speaking of -stable, I'm still running 3.4-stable and need to use StarOffice 5.2 beta. So I took Matt's patch and butchered it to apply to the 3-stable sources. It helped me get a little closer (error3 is with the fix, error4 is without the fix) although I still can't install it. === --- error4 Tue Apr 25 03:51:48 2000 +++ error3 Tue Apr 25 03:56:28 2000 @@ -1,5 +1,4 @@ -/usr/tmp/sv001.tmp/setup: /usr/bin/test: not found checking installed system patches ... no patches required -/a/tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory +/usr/tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory glibc version: 2.1.2 === As you can see, at least it doesn't complain about /usr/bin/test anymore. (My /usr/tmp is a symlink to /a/tmp outside the Linux tree and a symlink to ../var/tmp inside the Linux tree, not sure why it doesn't say "/var/tmp" in the latter case.) If anyone (esp. Matt) is interested and wants to MFC, the patch is at: http://people.FreeBSD.org/~asami/linux-script-01.diff Warning: use at your own risk! I have no idea what it does, I just looked at the patch and took out hunks that are already applied (huh?), changed the context around a bit to make it blend into the surrounding, etc. Someone with a shovelful of clue should look at it first. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4: 7:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from guardian-ext.merrion.nua.net (guardian-ext.merrion.nua.net [195.7.46.2]) by hub.freebsd.org (Postfix) with ESMTP id ACA4F37BC9F for ; Tue, 25 Apr 2000 04:07:19 -0700 (PDT) (envelope-from tony@nua.ie) Received: (from uucp@localhost) by guardian-ext.merrion.nua.net (8.8.8/8.8.6) id MAA29619; Tue, 25 Apr 2000 12:06:41 +0100 (IST) Received: from globetrotter.merrion.nua.net(195.7.46.55) via SMTP by guardian-int.merrion.nua.net, id smtpdj29614; Tue Apr 25 12:06:33 2000 From: Tony Byrne To: Mike Tancsa Cc: stable@FreeBSD.ORG Subject: Re: /usr/src/sys/modules/mlx Date: Tue, 25 Apr 2000 12:05:02 +0100 Organization: Nua Ltd. Message-ID: References: <4.2.2.20000424233913.039ecf08@mail.sentex.net> In-Reply-To: <4.2.2.20000424233913.039ecf08@mail.sentex.net> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Apr 2000 23:42:22 -0400, you wrote: >Is anyone else seeing problems in make world on RELENG_4 ? >/usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function = `mlxd_detach': >/usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:291: = `disks_registered'=20 >undeclared (first use in this function) >*** Error code 1 Mike, Yup. I'm seeing similar problems, but during a GENERIC kernel compile. Actually I'm in the early stages of doing a source upgrade of my RELENG_3 workstation to RELENG_4. Maybe the problem is related to this? I did a cvsup of the latest RELENG_4 sources this morning. Regards, Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4:21:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from grove.iup.edu (maple.grove.iup.edu [144.80.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 191FF37B737 for ; Tue, 25 Apr 2000 04:21:22 -0700 (PDT) (envelope-from bvjg@grove.iup.edu) Received: from grove.iup.edu (slack@[144.80.62.205]) by grove.iup.edu (PMDF V5.2-32 #30978) with ESMTP id <01JON7SVPS2490NGD1@grove.iup.edu> for stable@FreeBSD.ORG; Tue, 25 Apr 2000 07:21:17 EDT Date: Tue, 25 Apr 2000 07:18:30 -0400 From: Nader Turki Subject: Re: /usr/src/sys/modules/mlx To: stable@FreeBSD.ORG Message-id: <39057F06.13D94EFD@grove.iup.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <4.2.2.20000424233913.039ecf08@mail.sentex.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I Installed 4.0-RELEASE last night then I cvsup using RELENG_4 this morning .... and on make world i got the same errors /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_detach': /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:291: `disks_registered' Later, Tony Byrne wrote: > On Mon, 24 Apr 2000 23:42:22 -0400, you wrote: > > > > >Is anyone else seeing problems in make world on RELENG_4 ? > >/usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_detach': > >/usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:291: `disks_registered' > >undeclared (first use in this function) > >*** Error code 1 > > Mike, > > Yup. I'm seeing similar problems, but during a GENERIC kernel compile. > Actually I'm in the early stages of doing a source upgrade of my > RELENG_3 workstation to RELENG_4. Maybe the problem is related to > this? I did a cvsup of the latest RELENG_4 sources this morning. > > Regards, > > Tony. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4:24:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 1456237BD00 for ; Tue, 25 Apr 2000 04:24:29 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-205.ix.netcom.com [209.109.232.205]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA26896; Tue, 25 Apr 2000 07:24:25 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id EAA03105; Tue, 25 Apr 2000 04:24:22 -0700 (PDT) To: Martin Blapp Cc: freebsd-stable@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 25 Apr 2000 04:24:21 -0700 In-Reply-To: asami@FreeBSD.ORG's message of "25 Apr 2000 04:04:05 -0700" Message-ID: Lines: 25 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) * === * --- error4 Tue Apr 25 03:51:48 2000 * +++ error3 Tue Apr 25 03:56:28 2000 * @@ -1,5 +1,4 @@ * -/usr/tmp/sv001.tmp/setup: /usr/bin/test: not found * checking installed system patches ... * no patches required * -/a/tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory * +/usr/tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory * glibc version: 2.1.2 * === * * As you can see, at least it doesn't complain about /usr/bin/test * anymore. (My /usr/tmp is a symlink to /a/tmp outside the Linux tree * and a symlink to ../var/tmp inside the Linux tree, not sure why it * doesn't say "/var/tmp" in the latter case.) Oops, I'm an idiot, there wasn't a var/tmp inside /compat/linux and it was trying the real (outside /compat/linux) /usr/tmp. Once I created var/tmp, the message started saying "/compat/linux/usr/tmp/..." (although it still dies with the same error). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4:25: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from grove.iup.edu (maple.grove.iup.edu [144.80.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 67A9F37B823 for ; Tue, 25 Apr 2000 04:24:59 -0700 (PDT) (envelope-from bvjg@grove.iup.edu) Received: from grove.iup.edu (slack@[144.80.62.205]) by grove.iup.edu (PMDF V5.2-32 #30978) with ESMTP id <01JON7XEGVX690NGRO@grove.iup.edu> for freebsd-stable@FreeBSD.ORG; Tue, 25 Apr 2000 07:24:56 EDT Date: Tue, 25 Apr 2000 07:22:09 -0400 From: Nader Turki Subject: Re: mlx To: freebsd-stable@FreeBSD.ORG Message-id: <39057FE0.D847B495@grove.iup.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed 4.0-RELEASE last night and cvsup this morning using RELENG_4 But, when i did make world i got errors that says: /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_detach': /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:291: `disks_registered' undeclared (first use in this function) *** Error code 1 Later, Nader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4:37: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from guardian-ext.merrion.nua.net (guardian-ext.merrion.nua.net [195.7.46.2]) by hub.freebsd.org (Postfix) with ESMTP id 73A2337BD1C for ; Tue, 25 Apr 2000 04:36:58 -0700 (PDT) (envelope-from tony@nua.ie) Received: (from uucp@localhost) by guardian-ext.merrion.nua.net (8.8.8/8.8.6) id MAA00728; Tue, 25 Apr 2000 12:36:24 +0100 (IST) Received: from globetrotter.merrion.nua.net(195.7.46.55) via SMTP by guardian-int.merrion.nua.net, id smtpdhjn722; Tue Apr 25 12:36:17 2000 From: Tony Byrne To: Tony Byrne Cc: Mike Tancsa , stable@FreeBSD.ORG Subject: Re: /usr/src/sys/modules/mlx Date: Tue, 25 Apr 2000 12:34:45 +0100 Organization: Nua Ltd. Message-ID: References: <4.2.2.20000424233913.039ecf08@mail.sentex.net> In-Reply-To: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Apr 2000 12:05:02 +0100, you wrote: >Mike, > >Yup. I'm seeing similar problems, but during a GENERIC kernel compile. >Actually I'm in the early stages of doing a source upgrade of my >RELENG_3 workstation to RELENG_4. Maybe the problem is related to >this? I did a cvsup of the latest RELENG_4 sources this morning. I've checked the CVS repository and there's been a very recent commit of mlx_disk.c (about 16 hours ago) which *might* be the cause. Since I don't have a Mylex RAID controller and I only needed a 4.0 kernel in order to complete a source upgrade of 3.4 to 4.0, I commented out the mlx device line in my GENERIC kernel config file and the system happily compiled the kernel. Regards, Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 4:42:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web108.yahoomail.com (web108.yahoomail.com [205.180.60.75]) by hub.freebsd.org (Postfix) with SMTP id 9177D37BD27 for ; Tue, 25 Apr 2000 04:42:36 -0700 (PDT) (envelope-from jimbots@yahoo.com) Received: (qmail 9156 invoked by uid 60001); 25 Apr 2000 11:42:36 -0000 Message-ID: <20000425114236.9155.qmail@web108.yahoomail.com> Received: from [209.244.123.49] by web108.yahoomail.com; Tue, 25 Apr 2000 04:42:36 PDT Date: Tue, 25 Apr 2000 04:42:36 -0700 (PDT) From: Jim Stevens Subject: unsubscribe To: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 5:49:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from logatome.francenet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B3D737BCA0 for ; Tue, 25 Apr 2000 05:49:27 -0700 (PDT) (envelope-from e-masson@kisoft-services.com) Received: from localhost.nantes.kisoft-services.com (pppA258.francenet.fr [193.149.100.168]) by logatome.francenet.fr (8.10.1/8.10.1) with SMTP id e3PCnIS49026; Tue, 25 Apr 2000 14:49:18 +0200 (CEST) X-Mailer: 21.1 (patch 9) "Canyonlands" XEmacs Lucid (via feedmail 8 Q); VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14597.37879.611136.906144@localhost.nantes.kisoft-services.com> Date: Tue, 25 Apr 2000 14:47:51 +0200 (CEST) From: Eric Masson To: "Jim King" Cc: Subject: Re: sio interrupt handler problem In-Reply-To: <003801bfae25$39a6d100$a44b8486@jking> References: <5564.000424@pd.chel.ru> <20000424114057.A692@pir.net> <14596.37283.563515.214828@localhost.nantes.kisoft-services.com> <003801bfae25$39a6d100$a44b8486@jking> Reply-To: e-masson@kisoft-services.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim King writes: >One thing I've done in the past to overcome serial port problems is to patch >sys/isa/sio.c to set the FIFO receive trigger level to 8 bytes instead of 14 >(FIFO_RX_MEDH instead of FIFO_RX_HIGH). If you have a piece of hardware or >a misbehaved driver that's causing high interrupt latency this change be >really beneficial, and greatly outweighs the higher interrupt overhead when >using an 8 byte trigger. > > >An 8 byte trigger is a safer option that causes better operation on weird >hardware without signifcantly changing anything on good hardware. I really >wish sio.c would be changed to set the trigger to 8 bytes by default, or at >least have a flags option to change the trigger level. > I applied the following crappy patch to sio.c, and i still encounter the SOs *** /sys/isa/sio.c.ORIGINAL Tue Apr 25 14:15:06 2000 --- /sys/isa/sio.c Tue Apr 25 14:15:34 2000 *************** *** 1113,1119 **** com->tx_fifo_size = 32; printf(" ST16650A"); } else { ! com->tx_fifo_size = COM_FIFOSIZE(flags); printf(" 16550A"); } } --- 1113,1119 ---- com->tx_fifo_size = 32; printf(" ST16650A"); } else { ! com->tx_fifo_size = 8; printf(" 16550A"); } } sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A lookalike with 8 bytes FIFO sio0: 1 more silo overflow (total 1) sio0: 1 more silo overflow (total 2) sio0: 1 more silo overflow (total 3) sio0: 2 more silo overflows (total 5) sio0: 1 more silo overflow (total 6) sio0: 1 more silo overflow (total 7) sio0: 2 more silo overflows (total 9) sio0: 2 more silo overflows (total 11) sio0: 1 more silo overflow (total 12) sio0: 1 more silo overflow (total 13) sio0: 1 more silo overflow (total 14) sio0: 2 more silo overflows (total 16) Did I understand your point ? (Kernel patching isn't part of my daily work :). Regards Eric Masson -- Opinions stated below are mine and can't be considered as official Kisoft Services policy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 6: 5:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 296B237B5EE for ; Tue, 25 Apr 2000 06:05:36 -0700 (PDT) (envelope-from steve@sse0691.bri.hp.com) Received: from l3107mxr.atl.hp.com (l3107mxr.atl.hp.com [15.19.254.19]) by atlrel2.hp.com (Postfix) with ESMTP id B12F0178A for ; Tue, 25 Apr 2000 09:05:25 -0400 (EDT) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by l3107mxr.atl.hp.com (Postfix) with ESMTP id 31CA14FD88 for ; Tue, 25 Apr 2000 09:05:24 -0400 (EDT) Received: (from steve@localhost) by sse0691.bri.hp.com (8.9.3/8.9.3) id OAA14999 for freebsd-stable@freebsd.org; Tue, 25 Apr 2000 14:03:07 +0100 (BST) (envelope-from steve) Date: Tue, 25 Apr 2000 14:03:07 +0100 From: Steve Roome To: freebsd-stable@freebsd.org Subject: Kernel Modules seem broken. Message-ID: <20000425140307.A14845@moose.bri.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whine, whine whine moan, sulk whinge. (Just though I ought to get it out of the way first.) I submitted a problem report a while back now, on how certain kernel modules cause panics; (kern/17375). This problem manifests itself on more than one 3.4-stable machines of mine. I'm trying to develop a kernel module, yet I keep getting bitten by this. The "how to repeat" I've given is an example of how to definitely panic your machine, but it does happen at other times too, directly after a kldload, or perhaps while loading a module. Using kldload/kldunload cycles with [guess] any modules with considerable data declated static seems to be responsible, but I'm not sure. Seeing as it's more than a month since I submitted this pr, and if it's as broke as it seems it could be the cause of some random panics for people out there then I wondered if there's much chance of it being looked at or if anyone on the list has a clue what might be causing it, or how to fix! I don't know enough about it to figure this out, or even if it's something I'm doing wrong. I'll try if I ever get myself a spare machine at home, but until then, it's kind of hard to develop kernel modules when they cause panics - I'm prepared to try some stuff of course! I tried emailing the guy who's been made responsible but to no avail, if random panics from kldload are acceptable then lets close the patch and move on, and I apologise for wasting anyones time. Thanks in advance, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 6:36:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id F36F737BD2B for ; Tue, 25 Apr 2000 06:36:43 -0700 (PDT) (envelope-from mike@sentex.ca) Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id JAA31105; Tue, 25 Apr 2000 09:36:07 -0400 (EDT) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id JAA17060; Tue, 25 Apr 2000 09:36:07 -0400 (EDT) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000425093237.020411c0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 25 Apr 2000 09:32:37 -0400 To: Tony Byrne From: Mike Tancsa Subject: Re: /usr/src/sys/modules/mlx Cc: stable@FreeBSD.ORG In-Reply-To: References: <4.2.2.20000424233913.039ecf08@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:34 PM 4/25/00 +0100, Tony Byrne wrote: >I've checked the CVS repository and there's been a very recent commit >of mlx_disk.c (about 16 hours ago) which *might* be the cause. > >Since I don't have a Mylex RAID controller and I only needed a 4.0 >kernel in order to complete a source upgrade of 3.4 to 4.0, I >commented out the mlx device line in my GENERIC kernel config file and >the system happily compiled the kernel. Unfortunately for me, I need the mlx driver working :-) The problem seems to be a reference to a variable that is not declared (disks_registered) in two spots. I am not sure if they are meant to be removed, or that the declarations are meant to be included. Either way, msmith@freebsd.org will no doubt know what to do. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 6:55:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from spassmobil.saargate.de (spassmobil.saargate.de [212.88.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 1A7AE37BD6E for ; Tue, 25 Apr 2000 06:55:16 -0700 (PDT) (envelope-from domi@saargate.de) Received: from localhost (localhost [127.0.0.1]) by spassmobil.saargate.de (8.9.3/8.9.3) with ESMTP id PAA02582 for ; Tue, 25 Apr 2000 15:51:54 +0200 (CEST) (envelope-from domi@saargate.de) Date: Tue, 25 Apr 2000 15:51:54 +0200 (CEST) From: Dominik Brettnacher X-Sender: domi@localhost To: stable@freebsd.org Subject: removed files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is there a list available that contains all files/programs which were removed from FreeBSD? I installed 2.2.5-RELEASE some years ago and it would be great to be able to keep this system clean. -- Dominik - http://www.brettnacher.org/users/dominik/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 6:58:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jking1.lgc.com (jking1.lgc.com [134.132.228.2]) by hub.freebsd.org (Postfix) with ESMTP id D4DC437B6AD for ; Tue, 25 Apr 2000 06:58:35 -0700 (PDT) (envelope-from king@sstar.com) Received: from jking (jking.lgc.com [134.132.75.164]) by jking1.lgc.com (8.9.3/8.9.3) with SMTP id IAA00608; Tue, 25 Apr 2000 08:58:23 -0500 (CDT) (envelope-from king@sstar.com) Message-ID: <001301bfaebe$5717cca0$a44b8486@jking> From: "Jim King" To: Cc: References: <5564.000424@pd.chel.ru><20000424114057.A692@pir.net><14596.37283.563515.214828@localhost.nantes.kisoft-services.com><003801bfae25$39a6d100$a44b8486@jking> <14597.37879.611136.906144@localhost.nantes.kisoft-services.com> Subject: Re: sio interrupt handler problem Date: Tue, 25 Apr 2000 08:58:23 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Eric Masson" To: "Jim King" Cc: Sent: Tuesday, April 25, 2000 7:47 AM Subject: Re: sio interrupt handler problem On Tuesday, April 25, 2000 7:47 AM, Eric Masson wrote: > Jim King writes: > >One thing I've done in the past to overcome serial port problems is to patch > >sys/isa/sio.c to set the FIFO receive trigger level to 8 bytes instead of 14 > >(FIFO_RX_MEDH instead of FIFO_RX_HIGH). If you have a piece of hardware or > >a misbehaved driver that's causing high interrupt latency this change be > >really beneficial, and greatly outweighs the higher interrupt overhead when > >using an 8 byte trigger. > > > > > >An 8 byte trigger is a safer option that causes better operation on weird > >hardware without signifcantly changing anything on good hardware. I really > >wish sio.c would be changed to set the trigger to 8 bytes by default, or at > >least have a flags option to change the trigger level. > > > > I applied the following crappy patch to sio.c, and i still encounter the > SOs > > *** /sys/isa/sio.c.ORIGINAL Tue Apr 25 14:15:06 2000 > --- /sys/isa/sio.c Tue Apr 25 14:15:34 2000 > *************** > *** 1113,1119 **** > com->tx_fifo_size = 32; > printf(" ST16650A"); > } else { > ! com->tx_fifo_size = COM_FIFOSIZE(flags); > printf(" 16550A"); > } > } > --- 1113,1119 ---- > com->tx_fifo_size = 32; > printf(" ST16650A"); > } else { > ! com->tx_fifo_size = 8; > printf(" 16550A"); > } > } > > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A lookalike with 8 bytes FIFO > > sio0: 1 more silo overflow (total 1) > sio0: 1 more silo overflow (total 2) > sio0: 1 more silo overflow (total 3) > sio0: 2 more silo overflows (total 5) > sio0: 1 more silo overflow (total 6) > sio0: 1 more silo overflow (total 7) > sio0: 2 more silo overflows (total 9) > sio0: 2 more silo overflows (total 11) > sio0: 1 more silo overflow (total 12) > sio0: 1 more silo overflow (total 13) > sio0: 1 more silo overflow (total 14) > sio0: 2 more silo overflows (total 16) > > Did I understand your point ? (Kernel patching isn't part of my daily work > :). You need to patch the code that sets the FIFO receive trigger level. I think all you did was change the number that gets printed when the port is probed. :-( Look for a line like: com->fifo_image = t->c_ospeed <= 4800 ? FIFO_ENABLE : FIFO_ENABLE | FIFO_RX_HIGH; Change the "FIFO_RX_HIGH" to "FIFO_RX_MEDH". Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 7:53:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from logatome.francenet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 50F2237BD48 for ; Tue, 25 Apr 2000 07:53:09 -0700 (PDT) (envelope-from e-masson@kisoft-services.com) Received: from localhost.nantes.kisoft-services.com (pppA100.francenet.fr [193.149.100.10]) by logatome.francenet.fr (8.10.1/8.10.1) with SMTP id e3PEqk504395; Tue, 25 Apr 2000 16:52:46 +0200 (CEST) X-Mailer: 21.1 (patch 9) "Canyonlands" XEmacs Lucid (via feedmail 8 I); VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14597.45415.131516.431525@localhost.nantes.kisoft-services.com> Date: Tue, 25 Apr 2000 16:53:27 +0200 (CEST) From: Eric Masson To: "Jim King" Cc: Subject: Re: sio interrupt handler problem In-Reply-To: <001301bfaebe$5717cca0$a44b8486@jking> References: <5564.000424@pd.chel.ru> <20000424114057.A692@pir.net> <14596.37283.563515.214828@localhost.nantes.kisoft-services.com> <003801bfae25$39a6d100$a44b8486@jking> <14597.37879.611136.906144@localhost.nantes.kisoft-services.com> <001301bfaebe$5717cca0$a44b8486@jking> Reply-To: e-masson@kisoft-services.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim King writes: >You need to patch the code that sets the FIFO receive trigger level. I >think all you did was change the number that gets printed when the port is >probed. :-( > >Look for a line like: > com->fifo_image = t->c_ospeed <= 4800 ? FIFO_ENABLE : FIFO_ENABLE | >FIFO_RX_HIGH; > >Change the "FIFO_RX_HIGH" to "FIFO_RX_MEDH". I applied your change, i still encounter SOs but my TP seems to recover much faster from them. That makes modem much more useable. Thanks for the tip Regards Eric -- Opinions stated below are mine and can't be considered as official Kisoft Services policy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 7:57: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id C3A0C37BD27 for ; Tue, 25 Apr 2000 07:56:57 -0700 (PDT) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.3/8.9.3) with ESMTP id QAA24458 for ; Tue, 25 Apr 2000 16:56:55 +0200 (MET DST) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id QAA29563; Tue, 25 Apr 2000 16:56:00 +0200 (MET DST) X-Authentication-Warning: knecht.cs.uni-magdeburg.de: jesse set sender to jesse@cs.uni-magdeburg.de using -f To: freebsd-stable@freebsd.org Subject: OpenSSH: DISPLAY not set From: Roland Jesse Date: 25 Apr 2000 16:55:59 +0200 Message-ID: <0vem7ui60w.fsf@cs.uni-magdeburg.de> Lines: 45 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am using OpenSSH on a 4.0-stable box. The manpage states: The session terminates when the command or shell in on the remote machine exists and all X11 and TCP/IP connections have been closed. The exit status of the remote program is returned as the exit status of ssh. If the user is using X11 (the DISPLAY environment variable is set), the connection to the X11 display is automatically forwarded to the remote side in such a way that any X11 programs started from the shell (or com- mand) will go through the encrypted channel, and the connection to the real X server will be made from the local machine. The user should not manually set DISPLAY. Forwarding of X11 connections can be configured on the command line or in configuration files. The DISPLAY value set by ssh will point to the server machine, but with a display number greater than zero. This is normal, and happens because ssh creates a ``proxy'' X server on the server machine for forwarding the connections over the encrypted channel. However, the DISPLAY variable does not get set when I connect to a remote machine (running ssh but not OpenSSH). Here is an example session: r.arthur ~ % echo $DISPLAY :0.0 r.arthur ~ % ssh -V SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. r.arthur ~ % ssh -l jesse knecht jesse@knecht.cs.uni-magdeburg.de's password: Last login: Tue Apr 25 10:33:55 2000 from arthur.cs.uni-ma Sun Microsystems Inc. SunOS 5.6 Generic August 1997 You have mail. SunOS 5.6 jesse.knecht ~ % echo $DISPLAY jesse.knecht ~ % Am I just missing some config setting or does it simply not work? Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 8:18:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id A886E37BD62 for ; Tue, 25 Apr 2000 08:18:37 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12k76i-0000tH-00 for freebsd-stable@freebsd.org; Tue, 25 Apr 2000 11:18:36 -0400 Date: Tue, 25 Apr 2000 11:18:35 -0400 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: OpenSSH: DISPLAY not set Message-ID: <20000425111835.A2200@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <0vem7ui60w.fsf@cs.uni-magdeburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <0vem7ui60w.fsf@cs.uni-magdeburg.de>; from jesse@mail.CS.Uni-Magdeburg.De on Tue, Apr 25, 2000 at 04:55:59PM +0200 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roland Jesse probably said: > jesse.knecht ~ % echo $DISPLAY > > jesse.knecht ~ % > > Am I just missing some config setting or does it simply not work? X forwarding is off by default with openssh. See `man sshd` for the config entry to turn it on in (IIRC) /etc/ssh/sshd_config. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 8:20:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nwcst285.netaddress.usa.net (nwcst285.netaddress.usa.net [204.68.23.30]) by hub.freebsd.org (Postfix) with SMTP id 900F137BD87 for ; Tue, 25 Apr 2000 08:20:47 -0700 (PDT) (envelope-from elljay@usa.net) Received: (qmail 1234 invoked by uid 60001); 25 Apr 2000 15:20:46 -0000 Message-ID: <20000425152046.1233.qmail@nwcst285.netaddress.usa.net> Received: from 204.68.23.30 by nwcst285 for [165.21.83.140] via web-mailer(M3.4.0.33) on Tue Apr 25 15:20:44 GMT 2000 Date: 25 Apr 00 23:20:44 SGT From: Leslie Jay To: stable@freebsd.org Subject: Problem installing Domino for Linux (0x19E) X-Mailer: USANET web-mailer (M3.4.0.33) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Like a few people before me, I have run into problem installing Domino for Linux 5.0.2c on a FreeBSD 4.0-stable. I have Linux emulation, and had installed linux-base 6.1 from the ports collection. After modifying the install script to accept FreeBSD as a Linux architecture, the installation went thru fine ( its Perl scripts ). Again modifying the startup script to accept FreeBSD as a Linux OS, running "http httpsetup" as per the installation instructions gave the error "error: Notes error : 0x19E" Searching thru FreeBSD's archives, Notes fourm, DejaNews archives reviews no solution or explanation. Not willing to give up so easily, I copied wholesale, = first Redhat 6.2's files into /compat/linux, = then Redhat 6.0's files into /compat/linux, = all fruitless attempt. Finally, I did a ktrace, "ktrace http httpsetup", and found the = following which I thought could be a clue, but I don't have any clue to proceed, so I am here asking for help, anything. The following is the last portion of the kdump output: I also attached a gzip-ed ktrace. Hoped I provided all the info needed ( and written to the right forum ). = Thanks in advance for any help. ------------- 25934 http CALL #91(0x28ec9000,0x2000) 25934 http RET #91 0 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x7b0,0) 25934 http RET getrusage -1 errno -22 Unknown error: -22 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x3b0,0) 25934 http RET getrusage -1 errno -22 Unknown error: -22 25934 http CALL old.sigvec(0x1,0xbfbff1ec) 25934 http RET old.sigvec 0 25934 http CALL dup2(0xbfbff250) 25934 http RET dup2 686592000/0x28ec9000 25934 http CALL ioctl(0x1,0x5401 ,0xbfbff1e8) 25934 http RET ioctl 0 25934 http CALL write(0x1,0x28ec9000,0x2) 25934 http GIO fd 1 wrote 2 bytes "\r " 25934 http RET write 2 25934 http CALL write(0x1,0x28ec9000,0x1c) 25934 http GIO fd 1 wrote 28 bytes "Lotus Notes: error 0x19E\r \r " 25934 http RET write 28/0x1c 25934 http CALL #91(0x28ec9000,0x2000) 25934 http RET #91 0 25934 http CALL exit(0xffffffff) ------------- Regards, /LJ ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 8:22:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nwcst276.netaddress.usa.net (nwcst276.netaddress.usa.net [204.68.23.21]) by hub.freebsd.org (Postfix) with SMTP id C5BB637B737 for ; Tue, 25 Apr 2000 08:21:52 -0700 (PDT) (envelope-from elljay@usa.net) Received: (qmail 5308 invoked by uid 60001); 25 Apr 2000 15:21:49 -0000 Message-ID: <20000425152149.5307.qmail@nwcst276.netaddress.usa.net> Received: from 204.68.23.21 by nwcst276 for [165.21.83.140] via web-mailer(M3.4.0.33) on Tue Apr 25 15:21:47 GMT 2000 Date: 25 Apr 00 23:21:47 SGT From: Leslie Jay To: stable@freebsd.org Subject: Problem installing Domino for Linux (0x19E) X-Mailer: USANET web-mailer (M3.4.0.33) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----NetAddressPart-00--=_yPVv0848S763f7f60d6" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------NetAddressPart-00--=_yPVv0848S763f7f60d6 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Greetings, Like a few people before me, I have run into problem installing Domino for Linux 5.0.2c on a FreeBSD 4.0-stable. I have Linux emulation, and had installed linux-base 6.1 from the ports collection. After modifying the install script to accept FreeBSD as a Linux architecture, the installation went thru fine ( its Perl scripts ). Again modifying the startup script to accept FreeBSD as a Linux OS, running "http httpsetup" as per the installation instructions gave the error "error: Notes error : 0x19E" Searching thru FreeBSD's archives, Notes fourm, DejaNews archives reviews no solution or explanation. Not willing to give up so easily, I copied wholesale, = first Redhat 6.2's files into /compat/linux, = then Redhat 6.0's files into /compat/linux, = all fruitless attempt. Finally, I did a ktrace, "ktrace http httpsetup", and found the = following which I thought could be a clue, but I don't have any clue to proceed, so I am here asking for help, anything. The following is the last portion of the kdump output: I also attached a gzip-ed ktrace. Hoped I provided all the info needed ( and written to the right forum ). = Thanks in advance for any help. ------------- 25934 http CALL #91(0x28ec9000,0x2000) 25934 http RET #91 0 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x7b0,0) 25934 http RET getrusage -1 errno -22 Unknown error: -22 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x3b0,0) 25934 http RET getrusage -1 errno -22 Unknown error: -22 25934 http CALL old.sigvec(0x1,0xbfbff1ec) 25934 http RET old.sigvec 0 25934 http CALL dup2(0xbfbff250) 25934 http RET dup2 686592000/0x28ec9000 25934 http CALL ioctl(0x1,0x5401 ,0xbfbff1e8) 25934 http RET ioctl 0 25934 http CALL write(0x1,0x28ec9000,0x2) 25934 http GIO fd 1 wrote 2 bytes "\r " 25934 http RET write 2 25934 http CALL write(0x1,0x28ec9000,0x1c) 25934 http GIO fd 1 wrote 28 bytes "Lotus Notes: error 0x19E\r \r " 25934 http RET write 28/0x1c 25934 http CALL #91(0x28ec9000,0x2000) 25934 http RET #91 0 25934 http CALL exit(0xffffffff) ------------- Regards, /LJ ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 ------NetAddressPart-00--=_yPVv0848S763f7f60d6 Content-Type: application/octet-stream; name="notes.http.redhat61.ktrace.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="notes.http.redhat61.ktrace.gz" H4sICFktBTkAA25vdGVzLmh0dHAucmVkaGF0NjEua3RyYWNlANQ9a3QURbqdkGAyoMSV3cXV 3S3aQRFMhrdccMSQBAIGEvISV0gymemQWWamx56eBBZGWODoKqjgHl0XXAUVrtdVeRxXxAdB VNbjrruul1Xx3gPq5eULUEFAg9yvuqtnuubRU12z98fNOZWqrvq++h5V9dVXj+7pLwhCPoSZ kiDMVxWPF+L4n+R1zS4t/LdxYwYIQ2tf3VcqbH3FKCqBkJcFbzXgnVjw+1ca8/posDeU9B1a B6E/A81HCM3GvEQRC82nTDT7QDamh4tZaD4fp/nqPjs09+Qg5z845dyfg5yfcspZNJZfzh+P 5ZNzyFh+OUeM5ZPz+hzknMYpZ3MOcrZzyrk0Bzk3ccr5fA5yvsYp5zs5yLmfU87PcpDzNKec PxzHL6dzHJ+co8bxyzlpHJ+c0wnNiUCx5ExPz6BzPT1OCJcASJ8suLMBV6h88l2XHFZdAVmN Rlzt/pCrU1XD2Vi+GdDHVwkayxNhKixiZBnjzQQ8g+WHV184dPxpneULsrCMcecArtC5e5/G aKRTZ3PYbowS6RRoFPjDKJ4pCTaN/AKNTWu8z6fobA6Mt6A1fNlUnc5AoadHIGKw0Llhqk7n UkY6NYTOpYTO4D46XjY6XkLnJaDw+Op+RQ9+19MzQFO5NV54KlF5l0dxBT3+gCskq1KEhdV7 CKsvCa/uyyf5JQysriesTgDm1GccRT5gdRLBzcbuUwa7kuoFdgMB2VvmlUMdLPz2EH4nmPh1 MvD7FqbZNGz360JRXEjck/MhPg9/ZngWPg4QPl4XiDHY5RhaxMDHgGpdbxfjMfh2vyIWWldU 67QuNuWz0Kox0/qQjdacNLRYhshthNYgRv3dTegMMg0RFjoPVtsbiturU4ciC53XCB0XI52/ EToum3Q+IHSGM9I5SOgMN9FhGa9fETqF0Ot7zum4Y3qNScgaV5gm6OM10yRkjV41TWe5kAwV POxYWG6aprM8R9DnavznYFRTO6E5h9DEeCxDJkRo9gXIPoy0FhBafYX/eNfIZ5FvhUk+h6BP 5nmMNO9Nko+V5sOEZjP4P4b5XAWmm4XmHwnN5hT/xxrv+SSamJ7KSHNPnGYin4XmkRzk/IZT zvzpqXLiMhaaF03nk/NSE01jjCxmlHPIdD45RybRxPR8jDTdnHJW5yBnI6ecrWnkxGUsNOdz ytllojmA5LP222Wcct6dRNPO+FzLKeeTJpqYTu/Znp6DZ9lobk9Dk8W7/k9Cc0pevoD7Kza2 LPT+h9CbYlPGY0kyYvkMXrPR/JZTrxNv1Gn2IXMKWtWv6Dx03gsKsDtijRsEXKGoebeD5Dkc VziuQJGFEVUKIm/QF4HnppAnKLnFKI5Ex2RPRNIz2klKdFSFutyiFOoSHQ2yorrFCPwXHZX+ jg636IP/oqM+6BaVoOio6/a5xXC3DyAlSEUkSFUtCCuADv9FxwyoKAj1VHQGZSj34kh0TFWk sFucB/+hJAoEvFGovwLyvJADPCPMtOpR1GgYRbyKP6win9QenTfPH5oHEvg70C2oNIRE56KG xvL6xqa6yslTW6tmNsdENHciUjulkKPY1z6vwx+QRrpdajDs8rVHRpY5nfHsUfHsUVq2E2RG i5ETC4yuR04D29Hhd+hKlEKRqCKhsEfthOe68sZqt+iKRhTsR03Q/jkX4dyY6ADZcTX4iSAP HjwY4pm1jVUN9VXN7rEjRowwoIxMB9JBfZIqKUF/SEI15fUV1Ya4bU6t3dqQG5VPmx0XE8Gf Buf2twfDcrdDCiSDV9eVNqVD6AyHPWnAG6Kh2gYK3AyBSsMYKBL2KF4KKFFvJBqCYi1TCkQk R3GxLn8K1ILx47RMUHEqGzX+UHRBGq4DOD8N/BRFkiY3VGbEACJ6t/kVdButwNRXEgxK3k4Z iU2h+SG5O4TCAY/aISvBOCFRB1rgV5HWNUgb6i1FBpukorAi+6JeVessCBb0Ea1EDgUWIjHh gYvIH0GRaBhXIfkcNTiv0q+4nYtqahubGiqn1U8oNYPHHEa+22kAxzkgJY46IF0vdZUr3s5K P4uZuv9G3Uz1EfQVNDY1LG62UmNamZ5gW5neXpO6MmUx+2/WJDZVBsEqeMW3PT0suxT7AS/N 1tstLLyeq0ndVWHhtf+MVF77MvA6aAbhlZnDkTMMDhN/LC1XMcPUckJ/pparn8G3pxAjtPIF Y9K8whL+6pk6nXyyEKuVDDrWeD0zdTqzGOnsJXRmCf20zSQMO1BI7Kqm4C0tKMJ4M4DAh9dt f+UC4ArvOW2B1jX3jvxM+IRuZJZO9wKy6MPyFVnRJXjt9aY2KzHazBpnQX2m0WaNd0lDogdX H+xXdPJ0T89FQmLXOBPeUMDTejCZFV2ai8HC6ayG1J5cwMCpl3A6LK79yyxbvZvQGUby+sTp WOMtb0juxStfSQvf+/4+bRnZSPfiungrW+OpjYmtiwJGWnc2Ztq6sMZ7rzHhZmI9YNd2KcEt EErT66OEuKhzBWGXhqv/kcnXofNrjds8l55viuL8WuPtidOk+S2y4pe0X20Lza8lnwTH10Lz afCakU+CpxBa9PaTNc4dLaltWMBA63eEVsLqWcNvaMlk9azxnmmhrV7dWXtW788ttNXD44HF Ep1oSViixQf1uRQvbbJZou8Bj7JEt7BweXlrphnfGu+a1lQu+zJweW2rkDLjW2PUtvLZyWhr sv2ybu/PW2n7NUti64/z25JnYWv4WBtff/xLW26zcLGX7o8J+azxOr3J842197PEm2m+scZb 6WVsL2Ibv/fS7VUvZbFVBE/1pZtvrHF+48s031jj7fXR882zNuab4UH++WZKkG++aQvS882z NuabQ0H7883ZIN98UxSyP9/8LMQ335SG7M0314b4xncFpnNsd3x8I5vzzdoQPb7rGcf3WyF7 dnK6TI+7BkY7+VfZnp08IPPpsSRM63GpTTtZrdB6bGDU4xNKsp3ckd4XJfA9SiY7aY33pmLP To6P0O3VyGgnt0Ts28nXInx2skSl7eQKG3bypcX8dvL9xXx28uvFtJ1cYcNOdsfs28mnY3x2 8uWYfTu5N8ZnJw/G7NnJYzG+8f1djPaDTpyxN74vuY0e342M47vqNnt2cvtt9LhrYrST45fY s5PTl/DpMbYkaX1j004+/Gtaj02Mevz+18l20prPgcsy2UlrPHFZcnuNst6nXUa3V3PcTlrj 9S5LZyetcUqWZ7KT1nix5bSdbLRhJx9ZyW8nd6zks5N7V9J2stGGnWxaZd9O/nIVn51cuMq+ nVy9is9OPrLKnp18chXf+H5uFe0H7bJpJ99eRY/vZsbxLdxtz07Kd9Pj7iZGO3n8bnt2Mv8e Pj2OuSfJL7dpJ2etpvV4E6Me315tz04eXs1nJ79abc+fbF9Dt9dsRn9y3xr7/uQXa/j8Sfd9 tJ102rCT0bX8dnL1Wj47+eRa2k46bdjJYevs28kb1vHZydp19u2kbx2fnVTX2bOTS9bxje+V 62g/aLVNO7lpHT2+ZzOO7/fW2Tsl7HiIHnc3x+lY4330kL1TwlMPZdKjNd7EPyT55Tb3L+57 hNbjzYx6HLc+WY/Wp5lPr6f1+ItsdAge2pCsR2v4sRv4Tls7NtDzjd193tbHaD1i+Uqs6BK8 3sesrmBZ4179uEBdwVLconORcV0jpr/V4Qp44L/qggJ8cyQmOmrq6msr66ua8aN2wYO6x5G4 5kGDORrl+mhoij+gX+Fqcxq3uZBzBBp1/ZUj23QIzAJdYQxoU8gxkdxfCXrCqKZ85lSkyqgG J+IXrvSbMzOnmi7OaABusUJ06Fd99GcNylHsBWYQiIifYsgP4MV1tQ3TZiOEFs+Bh7Ac8S8w HqRQa1PDMPJQZX6AkqmTTSXaw9WQThAvLp440VEsRTxe86UcjQtdqIDsBY1jppHWAGX+kB9d ibw+LGUkLHn9HX7Jh3x+RfKqsrIQX9bCcNNCfqwgtygSHXSY8ONaoEDj5UQlHbKCfCA9anPW dfvaUJt2xciJL4dpF86AbKmExIhrggu55oltE5FPBoEMck6fKw3FYpqmGQgXtiuSZz4kQBnF PjkkxW8/DdavzZmRTa2pX34SjUSFHA34sLyowx/yoaviJK7C4lREFUUKqajS0BkCQbFUormi +E2pSo/qqZa1TroI3/+LIbEljuoWoZ+YmYph1SyqiKoxVOodObK0zXTnz6jJxDi0YzybqD1J lmnBsCKHJWgKAMPsm6QpQ5WyFNEE9coh1YNLE6xdhUBKZWF6qRJXvsgdS3zjKxK/HwijjsVM 3fR46hUsloPHI48nDh5XrOlX5ITpGl/2yHbw2ItNlPl41Lj6ycKsuJHvDHLyRkYfnviBL2+0 6cMTvL9utLfXcd0meg68RWLb69i2yf5ex+ub+PY6Bv477cMP/Fb3iS8Usvvwl282cPU//MoP kwM/fjPdKwsFNge+anN6Zlkc+D1JzLI4ux9s5nPgj25O956QNY6whc+Bv2iLvQX6oC18DvyQ LbTjudSm4zlpC+0wJQaDNd53W0zX0xDb9bQBWzNdKcxyhW6rvQF+fis9wOfEndwsG4zbktvM Gv7ebZnazBpv17bcLjMM/BPdZgn5slyCeM7eYmHpc7Qe5zIuFr56zt5ioXA732Jh3Pbc9Ojd Qesxq3wEr+8L9vR4+wu0HlsY9XjmBXt67Pcinx7dL+a26Kp/mdZjVvkI3p6X7W3y9dtpOAi6 fKybfD/ZaW9T9r6ddHu1SowXM3psbPIRnMt6bG7yEbzOnvRz7o81nWSwP2S+vni/IKzfkLfb mHO1y/Kad4x9ZYel6SNVjN5PT8EDhCx+DcGbvJ/fVbj1gH1X4Y4DfK7CAwfsuwpPH+BzFV48 YM9V2HOAz1V4B/B2nenldhU+PUAP81bGYf7Ah8nDz/qOx4SP6OHXHqdjjff2R8l6tIY/+FEm PVrjXfoxrUe75rL5IK1HLB/L4u9PBxOLP5/QX7t1ynJL/w3Ai78TEx/mLJx+djB15cfCaS/h dCdepgKnJ6GnFTBwesGhBKdM93cP6fzttMnfsEOp/LFocqyJP3uanJ6GUxY3ezbhtD9A4jZn 4dLHzeVCwmX/DB/hy9gzD/Hvnn6MuTXvnlKblhNStzEVKeIy9hgzvIGJHMZOpLbZqu1E+tuD w66Ob7Npr5LWTJusY5u32Uhmmg3UNLzoL4HG68F7l/oLkLarEcnmXbGxl6njJzFc2Qr59eX1 N7emYZwutCVAcr1mQTirTRGIrofs4EaioZRWyVnI3MRhY7wznMx3QzWApWE5kZ+eWzOeiVFL tGQeE8D/D3Wp7eJr26oNEpPZv/hw6u4pi5n66RF+M1VxhDZT0bB2tqBtYaM6/NavFOryK3Io iLfIuzyK39MekOhX17UXv5MbAr9enChwOxcZ29ppxlV2a2gioW+L/wurN520JGp0pKtWJ5/y Tny7xzsf9JY43cAnJRFJ6ZIUQ1FO6ogKuZGol4uo1GN5koGr8uNt/jFoNBqFRpJDlQ5FDuJ+ SR01lDkX+bWuqcqpZWKbE3/PADn9aDga2WY+mMGVmQeQnqvKaC668krk1D55gKLDu7W8610+ qcsVigYC2rkchnfO6CKVZADQVTAJBJXQCDMl8r46TiWf1CQrVdSh9AOLYjL84sdCyJFeJYCV ThkjIT+zlMnAqSI5K8KoNGwldCaRDYFZxDWEBSnjJzTegOQJ/Z90NTyiylnM1LwjfIc8244k /PzO+/S3y34uZPf7Xscmin73nTp71j6LwPba2bdH+F6McxxNZX0IA+s/Arykj5WlYR0bowo2 ASqO8glQn0YAlvcP5x4VON4/XMTJ5V1puGR5//ABg0tmDv94NHUFyLLm33nU3pp/9Cf0mt/L uObv+cTemn/vJ3xr/r6f5rZF+rvP6TU/hmFZ/5UcMx2zjGA7ZrnyGN9XALzHTIfLg/qbvrlh jdcNeKnrTbb+df8xvhGwKQ2vLDZyq5nX3GzkB5ysf5qGdRYb+Q1m/V9pI39+nE8A1/FUAVhs 5MTjAoeNXMPJ5WNpuGSxkc8YXDJz+NpxPhv53nF7x5q1J2gb6ZPYjjX3nLB3rPn+Cb5jzX5f 5mYjq7+mbSSWj2VZt+lr/mXd3wCXWtap8gw5GlL1rzLpy5zypsbaGbVNMxtbyQea1GC4NRhS xRi409gbTFzpWuwsN9WweLGIKCcSf2fM/FzmdIIbHHeJE9/ewg6xdKvZIdbogDedgp9MIMUF rw9qDnwSHu0tK9EQkhZI3qiKV62l5H6cV8vHN6QUOYDw19Ewd2EwMbDGjS9tFcRw17BM8ZoW a2WsKKYbVzl+HC7D595GQQn+zF3i+29UEegubYG24hiR4M4nI7+qpapwCTAL5hnJHajDEw2o 0Dv0fYKwInulSET7nBhkti9EU3A5qpe8Mqw8FqIG7U5ZmaNe0uTFlTVodbnHkkVLkpLMy5bE x83w983S1owLZkqSfgkyIElhbV3kQR1SN6yOoKW1kqBnvoS0b9/hLQ5obhWLAmkN3SwJpDo9 XRIRqAyTxh1Vl9/tTBFDK+3uxD0JZCFqwj09FRSLA0t44xty2jpQ76LQ6qisrMzQRQwa/gYx Dpg+1+BoUjxHV2cSCyxm6tTXqcs6FnP/q5P2XOKvTtLmXmJ0iaVT9lziO07xucQvnMrN3L95 mjb3Cfms8QJn7L06cOQMrccOie3VgV+ctffqQPAs36sDfzibmx7/+R2txw5GPd7ay3iLBRxM zW/tpfU4LxsdgtdyjvEWC4EPn7N5i4XgrT+Xmx53nKf1OI/R/YgARDr3A1aaWd2PB3DtU06/ YrgfqSaQ+tymZsk0sz06ngdzEI703b2EoYRZqNuvdhpTETF0iY9ZGhnxTWINb56MjStMAdi+ YmubxpymyTZ26/TNOg1AUhRZSf54psPB0hB7QSlmA/uRwNahK/LybBnYl/PyqA7dyWhgx+Tn 2TKwU/LzuAzsAsATNh/m7tB3FeRRHbqTsUP3FujyFQj6T/zg6534V0KmCtk79LDCPGHp38fu ziN0UjuU9fIV31VG+F9EAm+PqbvcW6iLWUC6i/GDJtnE/EehLib+uZwHB/Yv+m8IRyGIQvZF 4mHAzb4Wx3KwbErs6ktq88rBsMfADvjbXQFfqfZQFpHLRpnvBuGqBXNVA/WqhlTqyjD/KI/5 vlMmvLmVujJK9RYXWGj9ktAqFQq1n2MSdhUUlTDQutWbF/9Vi+uf1XGdbxcO1VVljfsk4Gqr c0pV+CdpAj6sJFicBGSP7wcmradURW49bt9AqkrBthSetNm7G3ThC+H5e/JTNJbCE7wvNySE X39K/7Y47kXXWglPcIVH0wlv2QWhE/n1Q5CIfCEDicPPpyFxLYM2B+1I14eZeTMP9Ewk5u5I qFwgLJl3gjLhKTt0lQeAAsZ546TxyXprvBWEXsBUVMJA79EdCYcA07v8EDQzIOLBUZAF9zOs xpK/x+84LqmqmZKXl/iefB9ik1ff1FcYA/ETRwZr+WMEBCVDhSsgNn19Xvu7E12uhUIiAC5f D8/rR+hBnVoovHG+UOhLyrFerpk3WLimWw/40AAHXI75LwaANRDweMW62QbhGFR6OeT9hdBs IxPV54SZCDwPhPRO8nwDntogXAbpcgjvQxpPGrMBbi08d0H8ZZIgH2P2IP9nEL8HZTWQxlfb /myC+akJ5wv8A0oQfgTp30J4PE+X3QV4AUgMhvA5PLfk6z5GA8G9i/DuJfFUzDuEayC8ADDv Y14g7gdhBcH5DZT9HuJRBOc5kn8nhDpIOyD/MKQ/MPE3naRvhRj/MtJvyXMjhHsB/n54PoHr JvljIZj3GJvyE+kvICyHUAGwV0H+JxA7Cd5EeD4J6VcJbD7J/wHB3wPPBZDeCGkPpItw20K4 DcIzBHYupO+EMBPCVnhWIN4D8dUQL4KAzxouA1iR0Fiep//C1xAII0gd30K8DGCXQzhN8l40 6eOHEFaS59dIHv7tujqAbyH5eZB+AtJ3QIzfaesl+YcgPmiq6zykx0G4E8JbEEZC3o2AMxrC O9jEQfwWgS0jeJ9BvA3Cf5H8RyF8A88ziJ7WQPp2kh4NYR88XwTPn0H6sIl2BeTdDs8yxDdB vIGULSSxmK/PyXg8+SC9AuJOiGshHID0BID7J4RmU/s+QOKhkPcUSf8EYO7C/RvCKZI3HNKz CJ0JJnzjT4U8bGJaIZ5Oyh0m3heQ9EaIn4F4PsCUQoji/k9gGiE9lMDdQ+q4Dp6xEy1CvDJf 9xWvxXn/296bgEdRdG3DPZOZYUswICoIaBCUKKABkU1QdlEQI6CooElIBhLIZhYlLBpEARU0 KioiQtxRUSPuihp3xIUoKLiguIOi8igqIsp3312n0jWdIXTmff73+q/r+zpXperUXtU11afu OnWK9YG7q8T/WuzOsEdI2iBsrC2tmTD/wv9vmKvgngX/o+HeLWl60h+mBcwTnG/E/1TEmwNT CXoQzLEwX0hYb/iPFPet7DPQeTDtpC01CFsE+lK4J8HsgrnM6K9DEfahQR/C9sBvLN8X3D/o vgPdC+Zx0EdLu77n2JHwQ4x30VPcYdhkZy6Fucx4BzMkvLvYC/m7Q/gYiXM66FmcM2Ce5DwI vyckbR9Jk8M5jZ8SmBDc22A3krBFcC9huaD7wkyCewDsjZI/1tHW85JfNvzKETZZ6OuYH0xr zp9MK3nm8rcFv0q4j4P7eqM9qwx3MdzxMKcgziug2xj98hj8p8G8DvMZ6K3sI5j5oCciXgLM v7qPXN+GMsnnAiO/LTDnizsF/ufz3cO9WPySQP+DfAbCngY6DvYUmPXwW2Pk/5a4L/crfuNh mFfhdyPfCfwOZnvh10zK/hT+WbA/l/RT4b8Q9pWwz0HYQzB9QL8E+1aY/pJuGEwqzIQov9vx 8JsOMxTuDNiNjPodD/oO0P1YV/F7B3Qh3xvMC3ruNNJ0Ezc5yiM4T8HdCfYFrn7lkw6Tb9Tp GLhnw/xtxNkEcxjScqFZgbCrorSBT4v9+Ht9DnbRZPS5lm79P8v2f/z0rCfslBjzbL4f/85i 960nbdN6whryJInNW4bOihJ+TD1p+zewrCKY4fWEd/CQx+H78S+BOb6edCvFfnA/4d1gbnT5 9TLcj9aT992GOwMmH+ZJw68cZlGUdFNgjq0nXz5xhvt/+NOq8zxdT9jJYj++n/A/xB67n/A9 MM8YdGOZd96LErdQ7ADidBF3Bcy5rngbYa4x6MthLoGZYPgNFvsEV9r7YaaKuwnMfCOsmv9Q 9mih74D5U9wnSb2Xw4yAeR/mW0uBUDkwCQj/VeLuFpuAxzYjf4rtHSf5XCB+14o9B2agEfeE KPMzn2PgvwJ2JuvB73mUeGfApBv+7cWuMeKE95O/+Qw24mw/cHTrIZiDkeY/sD8Rv1PIg8Je K/RpkuezRrojxW9qlDrNNPxKmBe/Y+S5xa8j3D8b8bn2nbef+j0g9oOav4I9ywi/QezbYcbA XAjzgRE+WdK1hN3XqNdB4i6GmWHET4G5DWFLYfIlznoYXht3N8x9cCfBpmiCF5zi+eci8XIb a7AOjFN8/JzCKS5AzDXfeMNE/pSy9Di1tgaTvWAiH7+pyprNGSvxqORshTZ4al+jtarM2dZR yTrIS/sOXdvw9t2y1tU+1NVLWZtiKOtnd1npnT2V9beUFe1sap00cu628Vu+eo8Z7y/d0Lcc uLLCgCvJv+4XS5S055FxbjAkaIP/RZccCK+UMu6KVoaqXP2d+C4TNhhLdSrn5QUftC42wLLD ukjA8hmPgOUJ62IDLPuviwQs4xsAWM5e5/MEWBY+pJjk3PcDtr8GLNuCdXfP79+uDNjGBCyt B5DuWWUSD7OsHZutCMAy+aWAlbxeGTdgycUSJ3cu8PmhIfPABfcPlmJQWgmwwAUpP54X+tRH nB9vgmL8uNwlkzXBoZmysOfCmYALP/oEqPTiiSBIZ3Hz49LNaCAXoARZ8o32clHLDyHvgyMY QACIAFI5TBHMMp8CAgmO8SNGPJ4fvT2SnuAFAcD7fWqBzYfMwDXiJoDIRdL3+p34FMNKwOUK +eiQoSMzQ3BtlqQjkHSbuIdYCnDayjb4nAV4oSzoCSoQIJsj/gRhyMDyg9xDyuUHzgQG1lnq o8qnVBiE6yzFLBAcJTPCj+1snwI7CPZy0dlSFtD241OgA5kEglJchN4Os9woh4DGFJ8CnS8x /H8Uu8CnwOz7fApo0UBdN+MdcbGvASaCkwQXNZBAgIKM8EJJ106YGz4EiQmUasbraPEnQDrO pwAAPgSTCIJV+BR4phlhgrYXG/W4SeyrhUEgyECGrAnMOZYCsZdKngSVCT4WG+kJ4BCkJRN7 jsQ7T+wJPgfsIhDD3zQBZxMg1IseMigEkchczxG/FT4FFpAJau5TgDuBiXslPUF3grwEiwmK ExgexfFtqUUQ7+q9ReK+A3OyzwEOCeyToSJYXmopYEovAAjCE3wiYE4gYpTR3omWwzQTaOWi gMwxmTYCauSYhhrt45Ppov83nvZR/DTYsb+FXXA//v/Np109YXrxrxft5gJ7hCtud7EHGn4d DDcZnwRxN9tPeQS4Ai6/41x0RxfdMko+ekFpAhpDXXFS9lMHLuq4scGF+XTxO89Smy/6IbM/ SNxaMQqf68U+3ZWnGyBKNtwEEglecGG3wPC/VWxukJQZ/vzGEhi6Zz/1Hyc2AWMupgk4mgt9 AmlcfOrFsAmo3OzK62XDPVJsAijvGv6rxb5EbC769UXnBHwINGt+ZYvYBK+42bDUyOc2satg yIVywc2Fa4alwFsCmLwDjgv7jRKXYACBHfJOXFQNsNRGyf0Szk0V6svhJiABGb045eKeC0AC Dtxs4QYjN730op38xGajbgQG9MYneQ5u4lDRA0Hfr414BLWrxX2n2AQ+ZsO+AmaDEZebll8a 9BEyJ3FzgkAxN2e4GKUgCsEKbooScONilWBAW0nX2pjLWoj7SNf8RoCih09tFjxnqUX4LiM8 yVIbPARPCOycKP7cpCGrxxUFN6G+M9IQbOBG4yGal7DUBi4fbmT+BcOTFiaA8JTlANgEULjh Q7CTG5mvWwpION+oOzd2uNA3mzPRIAgAaPCNC+wHfGpDyXwI6oUMvyViE5AjSMENXG5scmOV mwmXwz7VpzZKu/sUWDDMpzYRCfAQyCGAZAIEBHK5EbjYpzYV9ZMj5XIjmpu/L8CdRd7GpzYZ uDDkJlq2pTZCJlt1n/knOW7OM60PiqQDnJQX+O1+bIlfwmNHRIZ3csUfGoqkXxRGi/wh+Ybh cZHhBUIvt9RcO/HEyPCgi851lbdIULWTJH2JLzJ8dctI+puukfRdUr8Fkn5L/8jwrc0j6dQU pz2Mf+YpkeGb5UN1orR3anxk+OIzlftYSb/3VEV/I3RbV/1bSPmXS/g1Ut95kn+rJoomf8rw TnhfKXhfyZZ6XycfHZnfjfL+TpL4gxE/HfE7SfzFIyLjr20SSX8oH1d+R8mH9Xa9n/ZtlHuO 1O/mQyPD2TyusSzb/Z99o1z12940kv5HyntD2t89ITL8YFf/zzgtkv6pZyR9hCt844BIes7x kXQ/1/sf5hp/mYFI+vDWkfSqxpH0v4mRdN8+kfRjrvzOlF0aVpvtny2/L87Z7N9bpL+PlvB0 1+/rWmH+Wkv4vTL+OE/x/Y04LDL+xmMj6T8aKXc/Sf+11G+A0JODkfGHuer/niv/QYL8Xy7r iD2u/vaCU9Ssiw2w3LXOAdnKPYJsobddIFtSsieQrd/bTlmrPJb1sruslGRP4OiGtw1wdGvX 5B3y4fdS5o63NTjatUHg6J4Y2tfyHTf429VTX45+p+FlTXaXldjNU1kl7zQcHJ3zTmzg6Ivv OOBoeQPB0Q3coY8Jf4TlERw96t0oZXgBR89kwpiQW1U5Ly/4hndjA0effTcSHF3pERx9+93Y wNFN70aCo3u/8Q6OtnnP5wkcJbfJ79zeJ9VsXx84uvQSv20ipDlBV85TZhumgQW/RYKjlcsR 9ogy0cBRSlwRRCQDS+kUzA02IEXwhAw6Jea4cCIoSSCUAOYOAVwI8lC68BkBaIirU+qS4GS2 ACwEGAkOVVoKJCUYRjCQTDkBJA3WPexTkjXXSVubCpNd7VMgFyVECU5ukPiUHqQEFsEqSlZy YUf+j8AhQVd+W7lo5UKJoJiWhOFCc7O4KaFmS+kK3VtAJIKQlA77XRY+BCj/glkr8ciwU8KL YCoXYwQTCUw+DfOmxOHCjkDTZz61MOBwIGBK4JhgJ7+temFLME1LrXGi2+JTQCsfSgppwJXA KKVtKVWlF/lcuLWRRQgBbM1TUcKWwPIdsmDR0mi/iE0pJ4LGlLwi0PyyMdh+EJteXDhSCo/g 4esS53Mnqi0N+6tPgb8Eqil9qkFUSpWRR/5UaIJuBCQJLBOI4+KTwCsXnSbwQfCZUp3VlgKN CeJRoo3rhX8kDkHna63Ip4OlpIM1AM+pjJLAGZYCFykJ97KlgPvfJI6W+Ptc6J0+BcwSoFgm fgR/g+Km1B0Xk/wdcQH4paWAVy0VQUCVEqEEUe4UP0ozE2jh5gEBR0qWUopRS8JSYphMHkFP AukEOgng86tC4N2WfJS8KHlKUJygN4FfLiS5cKRkJwFiSrFys4PAxfs+tSlAAJsLaS2ZwUUl 58ICKZ8bHXdIWJVPLVYJCmgJ5//mk3DgKPt93BI+XPhwjcJ1zoEkYLwApkli1yfZtL+nXwxp NPDLdVg0iS63RBQ3RHobNDcaUj2UM85wc43WyqD1mkavlbhmiyYtNVBsNwhL0M0ENTVQYQKW xjra3gTg08iVz5kumqCiW+qKDzfPTOkrbmQRQCBYraXjuHmj18JZYhMM0hJEXJARlCS4aqwh bYCRj8ZBXhCbG1nXW3UfDRgR7DOwCXuTkUDwA4YfwU+9PiPQxc1ADeSWWw6QS6aXIB83zkyJ /7etug9BTwJrBKG/ET8t0UMQkKDZlUITJCXIyY0iUzpGY0JPif2TqwwCpHujlE1Ak5tgBEcJ ePqNuUJLqDYX+yjxJyjLxW66pTZytAQZcReCSLdbzkOAlkArgUWCqgTcCSRyUy1T4hCkJXjK DTMttcPNSm4GEogmYM+NFG4McDONHP63Eo/gMPEAbkARdDtD/AneEQAlOK1PA/DhZjEBUoI3 3JTjxucgS4Gz3FwkIErg7lCjHzTYys2G2s01S4GIfAhyExTUbCE3brdaalP6eyeb2s06PsPE zQ1qblZxw4ubiQSQCXAS3CeoyI24Xvo7bKnN0TShuXnGTYvR+ptmqY0RbpAT9B4v/hp/4eYc N7m58ael9bTUOjd7DRzEBtsJ7hLAJbjKzTtu9Gkwlc87EpdAFoFcAsJzxI9AqwaOCWZzQ5wb gQR7uUHKzZopEs5NRBNk54YDQUQCLNxw5MYgN4k0MExg9w0jPjdSJ0gYT6jo0xrcXKU0Pzfz uSGwTuITUOemOU8C8XTMhRKfADU31XmahmD5a+LPTXuCx5ST4IY+N0i4+UkAhZvAXDZwLUip c576WCnpuNHNjWWemOLGMoUPuJFqS6P5FHjDjW6eeqEAwaWSjsII3KQmeM2Nf25sU7CBwDlP XxD/pDAEN7F54oWb9NwUJ0CpN2bMJx6TUEp/v80bEGAkn5u0z2f/Rkh/iYk99Ts1V5PeDOZ1 4OsO/V1XLof8tfQCTEoVHf3275r0xahg+XC/zbeQjpfJKMNSbRwuA1AD0K/iY18BZrWdzg8f rer/qPUG6S7ycdKA9Isd8H0DI1Ul4UfjQ5s41G9/50k/jkyr2vjtbwTpZvJh0YD0QNlRvEbK L8Nkkogf52KJX4YPThKYcQ2wb0F5O/HSnxZ6ECa7ajC4Rwq9mJm09NvzO+mPDFFUfoevw4er KuS3eU+Gp6Ki5Q856WeDSaxa6dCJsgGgAelq9PdWv9O/g/F+kr4UwQnQrYQJ0oDzaEy86Sf5 7e8EwxuBkSp8Q82zpA8Hs1a5TX3fST+KRImYgHsI/WCHyPrfiI97NX68h0t4PuLvxIRxq0/R eWBi0zEAj5LwDGEMNCCdyAAsNMZKeCnedzUm1EShQ+iflKDfnjdJF6G+W9dqgDNerYcfUZwg AeoTUb9CLFzfl/BP0HE1Dzv9Nwfll39l1dbnN6mPBqz/g/6pONkZv+8hvPobNR+R5om/8het WsD+EcSv7u23PvUr+ggZzyzPC05x+PrYwNHu6x2QbZlHkG3BehfIVtPNE2C5ZL0BWKamJCeL JJKXMh9drwHLlAYBli/E0L6P3O1DXb2U1aKm4WUdW+Mqq9xbWb1qGg5YDqmJDbA8v8YBLAsb CFhmEwyJTZoznOkRsNwSrQxVuY71HltvxlVubNKcduVM/T77KyP1/f0BlvWnm/R+JGC5pBaw rD/dxe/vD7CsP91l70cCljsiAMv6065hP3oALFOXKsZw5ScHlua864yAbUzAshp09QXK9MTK ZeWLkYBl/F0BK361Mm7AkkwrGXYusLgg44LOlEzhh4mLMoIvXGhqabBSSTvbiMu6lFtqEciH TAcXclxQsnvSjbh5Yp/qah+BFr1wLTT8sww3GVoCk5zx+GEj6GcuwMlM6CO+ZNDIKJvSL2T6 tLQSFynkGY40wvWkQyZquuHPhQrBNoIIZJjIxGhpQi7OCTrYu65GGjLLBIP5wSejTYChsxHO BSdBCDLYZFL4oeeCjgtZLmw0eMuFO4FTvfjk4pYfeDKcBPEIsJDh5wJMSwfx4YKNgBwZGr0Y 1IsLLrDIwF8htHlMI9ZHT+4NeUwAhEyCsUlsHeqK28Zw8zcQZ9V9tLQOmRBDQMMe890N2g2Y aGm3+oAnDeqQT9NAhwYqTSCJDCkBSIJDBIAud+VDQIgLaS54CSSYYEeS4SbQZEozuo9pjRGb AAwX6gQijU1mm/Hm3KJBbPLjBPnOEzrTqvtoaWoNhJmSu2RkCUgRwBloKVCIYCE3HgiEEHQj iEwGb6KRToOU5vy7vyfFmPT4e/oOiZOwYmcbyAROJY0VeqrQz2U4beX4OQuDJKWZ3z6OzPAd iJ+O9LdI/Br8yAqP8dtzGelxaED1Wp+VHlD0unSVn14E9EN4FVaNmkndifzKz/XZvxvS10uH a6mUh+QHoBcFx7ikEIoOiaTnI/9KLHJCkv9gDMzK99TvmfSdiL9xcsD+bbfA/xRMdtX3+GqZ 6DIMtNRfffZxddI/IP7O5302SEB6mUyOnOf4m2D38ltgWYqpD6A/Eg/32+/dZvrRfxX/+mww iTQ3tNIv89kLbNJb8aOswsr8Fwn/VPpLS1G8gPByMIu/SfhT8iPWUhMXor/K3/PZGw8MfwD1 /QbtC0j7fnTlV4EfUfVwnw2IMf4StLdil88ed6Sno79SHvXZ3x3S3ISpaeG352rS2Ug/8EKf DWyQvgD01gk+exyT3iPlXSbv61v0R7UxPm6Q8dVc6v+eSAFNFno+4m89ym9v2DF+Etpb85zP Bl1IX0f6FZ+9sUd6vLx/LTXyE8dXkq9W6miulNdV2n+70OwfzjsXuH4fbwsTxQ0Gvt9y+bHN lPzjJb0ezwuEbiF0e4mvpbgqUd/0D332piTrU4jxU4hF+cdC3+0aT73RMakTffbGDcMnSvjt Ev6H/D6ukfynSfvPEXoLPhpbD/LbmztMPwz5pVzks4EYG2TAeKzEIv4a+X3q+fYuyZ8bV9Qt cYSM/xvxe9t5ubPo/RXpk1r77Y060pOkvf3kfb+D9g7EeM6W+E/KB6if5P8C4leNc8bLYciv Zp/P6iz1ITi0s6PaDCadLh+WQdK+c9meST77+8DwFCn/DCk/JB+VdVLeKIynmrZ+exOL8d/B eB+IH+Fh0r7D8SFLnRBn8xKkE/h7A7O/QdcHdirqVyrhaLqVhEX7Y0JT7UrlXQ6IcRreT+F7 zu/pctkVWiz1n8DxneSv/b3bG8Z7fPZ4I52L8VfZwWeDaqTbg96JwT9N4qfx9/+Sz964tecT zjed/fa3gnQFBmJNs7ha0IeAYCJeVs84AbHYP+f7bDCPNDdaU0E0kvaeIAzEU37Vf8/K/Ntd 6l/mGu9Vxu+Jfu9jPA7EfKFBsL58v839NjBOunGQ7ffZgD7pJxC/8kmfDY6S7ij5dZT8e0t9 ThH6Ws6nic74prqfmj98tXSW/B6+lfj/gi581mePb4bPl/EyUsJ3gU4c77MBR3u+c80Pt+J9 bv3EZz0j/feizA8a9LuOoJLxPenD8f+Cz948tkFGtv9grKhkvC0DnY7+yZHwSpl/Dpb+Xs/2 gThRwh+V+V5L4TUHo1P4jK/2e0aeaOgjzvfnkrjI8Z/D8d/Bbwss2N9n1/fzT/l9DZf8n+f4 7OS3N9Tt8YT+KRznzKe3oL01xvflIunvMkm/CL/3ynY+60XpryHS3+sl/BjkX47vY43kV4j4 iZk+e21hg1JSv04SfyYFz+Y588+xMh/q+WodBl3lNb7a318v13gcInSh5KeP/ZdI+hfR39Ut /faGjP37kvj6exnP9j7ilJ/kdJ/tflDqe6Lkv1p+L0cJzfeceLtVC+peMslJ3wLv6yoXbaUN PX/0oDNPH2KlnTbqrMGDRqWdNXz42GHj0sYNGjxqWJqVljYlryA/zVZJnQYyJz+nxEqbDAtB WeGi8JSc4pJwUdrkooy8MEInF8A/mu/YcGZpUU5JWdrpyCEnIzdnRkZJTkG+RXLs2FEjw2XF VlZpXl7Z5NL8TGtcWl44rzhcYk1B2KicSYwFd0lRQf6UIUVlhSUF1jRFndtjSE5hdrgIlDVt aNhWM37uiVH8zHiS1Iw2zL6kK8JrXDivUHkPyfGCU5z8wf4Ay/rTjf3AAdkWfuMNE3n7Azeg 1z3ZCyay5QMDsKw8KTlbjhl4KfO3DzRgeZILsKw/HT86DW1fuw2u9qGuXsrKjKGsGe6yEnt5 Kmv+hoYDlos3xAZYvr/BASwnGoAlv8MHAhO/2hALJpiF319mRlaeR8Syy8Yohaja1d+L4zfG AqcatfPyim/bGBtk+eDGSMhygUfI8rmNsUGWb2yMhCw/awBkGfrQG2SZNFnBCq+domJqyLKd 1aYOZHnVj37bRMhYgq78W5nsXpaVfGokZNm6Q5zVursylIGj0ZAlv3YadiRkRgiE0BghCXKK F8i74efPhBDJDhKKIWTXTvpypoQNtBQUkmSpZQkfsqNcMulDkeYhc0IyhA4JSxKCIyvO7iSL pd8XYR3CcvxsEx7R8JqWmckw8iNHw1US4RmyTYQyCD0S1ukkcQjzEUqcJjQhUMI4ZGMIw2SL P9kSLn25PCMUSLjPlFfiQ1aSMCthKC5z0i0FVbllpghl8r1peJSwKZcVhC2nWv+zp/GBo9Q+ 5NhMKNA4dxIBN7rl2fR2qnFuxx5D3Sxvj2aR9EM43NSQNsAVX8s5EYLUkB4hyBZW3Ye/H8KZ hIbNQ6tDxHYfouXykZAElxkamjNlPDmncMlJtpi/Mc64mlMj1EjY/Gyh3fA7IWgtU0TYjvCl ljsj5JgTpf76Oa+NUz/2VRfXIZ+bByq3hudulJenl0dDpYM1PPGYvEQNp22RQ1AaTlsq7PvX Ev6q65AU5YGrpqh5oSV64VSBH0z4i/OKZanlx85Gkekp95s0RW2JMP05Uj/NXm9yxX9F2q/h rYVSPw0PPSSHtvTyTSs20MuFQzE4dy5Rv2eWVyj9d4WEn05462pLZBASrOXSf7dIeNhVvybI r2KJhlcSrBIJ1/BWX9f72eDqv9yByq3hrselvvdJ/4Vl8Gv46iKJr+GqS4TWy9FvUZ+By5Xm X9bnWclPw1UnJylaw1XzXOMhU/LTy/d1MhlpuKq3yBj8KO17Bu2rutmS5XuCNdz1/qulfA1P DZb8NTz1kQhwzo5TdIm0V8NVtxk/ZkZ9CO1LvEOP54Q68FSupNdwU6or/TfNIumHpX76/f4k cIKGk84kXLxUj6cE63ZMOhXl6v2T3iL9o+GlJTJe9PK6TBgYBZ+gfHn/Y4S+3FW/51zj/Xwu f6/X8EqC9arrEN9pUp6GjypQXkWZ+gYyfpjjfamSHyQ931WePxhJa63EGt75y3Wo7kGZLzTc M26govV4uVZovbymzHrF9Up2nOWvlvKXSP+caTAwzP8OGY8a3vldwvX8tcrVP4/J70vDOcWy H6V//1cY9eHv41JX+3vIeNVwzXbKHM33ybcowTrc9fstcKWf4qKr0G/V+ZbAOwlWZ/R/ym2W wJUJ1iaJv0jKixdNGRre+VX6W8M5l8n89qXQHD6Nj3fmU32eRI+3EtQ35SZ1HoLltZbxruGb b9F/6YvU94nhN0l/3iThPVHfpKWWwPsJ1pGSXsM3O2W8a7jmdtf7WCHwS4qEXyi/Rz3/3ufq r6cEjtW/3wu4PXS7Ghcsv0rGQ+14Qvuqb3Hm7xckXMM37kPYbjjnOeSfeoc6G8T01I6eeIPq f9Ifu+b3JCc72/2vMECaV3levkcazhkzyIlPuCbDRf+vwTdThuanFhUQdkkdOWRsb15yflZm iVBjc6bkh7Mi/PrartFjh4SLSsaGL7apMWMHKezGps4c2mNQ7hRxnqSdjH9uuKg4pyDfpoeO HlRSUnTW6UOtKWPDmYOy8mrho3AWKjVszNiSomH5mQVZ4XFlhWGFJtnxrDHh4oLSosywk0CH jsqZZGH1aHdGWnE4L6Mwu6AoXGydNfa0cMkw5/L6UQX5U5CG688xGflZBXmDy+C0xg4bokhr fFFOSZitZa2tyYVFOfklk5Xv4IzicK+eqERGlhOhOByeZk0uCefmWnkZubkFmdbkIkSwUOyg sUNOP13FKgqHraFhNsnxVNkpXysvnJdZWGYhqZ2Har47rvK1hmSHM9VLUs7Bw8aMQJHhIgt9 l6YyHFKQX1xSVIruRkVOLwnnDS7IKrPGTsspdGKPDk8vYe6n56ODwrkF6GtERjjv1SvKGhXO t1IziorDrvGgPGuHgSLtWvJd2JFZYLF1ZkZJZjZfM3J1J1flYhDWltA9xc4jLW3SjHBRAdMM m14SzueoKSaVWjopNydzZLjMwljKmVzGHDNKSovC1nD0Lvwl88xpGVNUle3uUH02ujTPoIbl FZaUGTTGWw6GhePh9J47EltmF2i0k7GNupLE0Ldj2c1kEnoO5tVXdkmkatujuoE9ICU5La2t h+4uLzjFaR/GBlmmfejAbLM8wmwbP9Qwm5RV2MsTZLn9QwOyTO+bvFYOJ3gpc++HGrLs2yDI sulHDW9fx4/cWiz7eoIRcz5qOIx400exwYgPf+TAiKkGjEjs4kAI3wsfxQLUebpzR0povClK Capq9Xdhz02xIJyRV+7UX0LZptgAxGs3RQKI0z0CiEs3xQYg3rcpEkB8pwEA4tebvAGIKT0T bQBkxw517La+K3d2P3+LbUwA0VoDjusdZZ44Fxzhwe0iAMTXWtxlvdZBGTeAGIc47Q3NJD4w fN/BHIRO5b1gY/GLW3eY0v5zGdxngMMdJ0wkr7c5DwzyrYj/Ffx6CLP8ECqXJPuG5xt69Y9p 4shT8kARmbmzhMHPQoUSE9XhoIfhPwPlvI98hgnD9++hlvWWMNudEDYe5R2CptagDsWoWwHC w8IMHwd3Gtydkfde1GOdpHsJ9J+ywHsryknRuYJYXWsIjfHgW3vkT82gTWUxx2tprke9uoH+ TpC45kj7piy+26CffhRGtAXq+Rz64BV09uMo+2nOuciL95qPh/8VCUoTzA1Sx0r5QRyBOKMQ 9hXinSMD6Db0c7Ew6L0R/0sp7wekSRZGfxnK/UHezx+o4xcGUngm4u9C2KnId7Tk2RdtuBf5 TkC+70rcIxFnLdrzEOqwHnksRNzTZSHwlqQj8DQHZpO839/g3oY+z+N+OsrZjPzCshgeAz8C LyehXF4NNEzakIE6t0KcB2QRV4S6zEXa0+C/W+qSifCzkP4Y0KNhLkb5/6BuByOvNqhnd8S9 XuIOBD0Fdf4d9JUo7zv03eMyJh5JUAfqh0uftUSc66TunZHHgOYKCF+CMfoF+nOijLtZiJOD OgxAPttRv2Ml/QPShq3ItwPqV470F8IcgnzfhmktYyjuUCVDxIcHmO6G+xKOA5TZAnG6IG0i fn83Yny8LO9wAfzOQNh0xD8L8TfA3CXlZaJ+hx6sDlS/Ladty/nblPB16N9lxm/uL4SnIJ+e yPN5lPFkS+fqJT4jUc7gluqqnB6o/x9oazukeQx93PFguUoE4eehT+49WF1Z1NJ1J8Zr6JNX UIffpNxGyKdUfivviv0C2nav9EPQ+H39g/7bIO//MoR/DfMwwpeizG/wroeyfxA+F3W620C6 36Zcn9CU7XscacYkquukzGeGjMEv0FcL4H4T5T0J+1G053fUlwDMAuRzKdLPA30c2t0ZZX+A smeDrkI5cWjviQgfhD7+E304C+nfRZ1msO/gdw/sxhgfY+QdNEXeIfTJT/I7/AxxH4R7kYyd GqP9e+HfXOaiz1F2JuLmSn+slv7ajfi/oP9+S3RkVVcizRXS3+fKGD9Myjsb8SinNtEYB+RM diGfN40F/tEo7xi07xOjPqPRT3fAj4ezeJVTCvrm0cPUIb+pBjjXDP32Ow84IY98lNcR9dOy bmOME9nXIO0Q5FGOOGPg3ifvjHJnS9G+U5HPxRK/QPohJPlskbhpSHcu4vYA/TTq8D36Z5rM 1Z/A7wqYrfB/EIbyoCvQhi1IswhmBdrSHHW7COmP4xyLOCMNkO4Z+PeV8srhvscQnp+KeOPQ X73wPttI3UoPVtft3I4yPoT7c4RPRpoTkPefGPdJGB+dDc1gbWQeuQJ5D0bZAyXssJaOhrs+ MvdXGWP3BeT5KOhHD1Kg5OOoQyrS3o7ykoz32gp+P8o3Yw/yfJjpUNejpb6Ufz0C7h8Qb470 56doF4Hg25DPTYj/ONJ9i3hbkPdxiPc8wnfFR2rUa486PIE0t5q7R3i+A90Dab+SPv0Mcfag Xe/xm8nvfUDxSkfgff2BPJeiLu3QFxmG3O/zMv70JsuPiD9F3u978hvINYD5fojfTsbxLORz Hcool/c2Am06F+HT0NdXGuN6LuJ3Q5zVHGuGDNXpiJfO8Q4zCeH5xveSsskr0Y5mSHsX/P/W sptIsxd9fpvEXQz/SsoZId/NqPcoY3zp5w35TY8x5t5rkMf6OHUA+kzk8TfSvSR9/hHa21/K W4K8j0RYZ5gPeSgVbTwF4c9KH+wDvRLu+6Xcxw1Q+FKpY0/4HYmyVhi//yONtsa3VNeBHYR8 r0C5lyHPtw0e6RS4f4d5uJm6Rux7yv0hzUvGbz0NaedxnKMft6O8c82dSTxNOI/Ke2+KfvpW 3unZLFviUt6MV//9I3W7sbFSpjIMeSah7dmo26No5yfGb2CktPdP5HO2tO9wxJ2EPP1Cf4jy WiK8OfrgMqT/WOayNfAfgbz/Y+xsViP8UNBt0bYhiHc/6tkVZcxG3RfLe0xAPW46TF1Z9Rrs TTDDyIMi3jyUfS7a0Rv5vCztONSYOzOQxx0otzn64zrEbS15no04FYcpsPIq8hVGmm+Rz060 uZ+0dQTCt8DvKMn/c9T3D4ynq9GWuYg3FGW/BvdP0q8TEG+O5PcJ3N8g/W7Mi3/C73mYQn47 0b7GxjunrC7l1U+V39ZTsNOM9/06+nYP/LagvGsQ7wz07a/Sj3fzm4X8+sp7SkH4R0baAa7D Kino45OR18ssk/yGvLeb0b9h5BVGXvfC/R3s75HXe4j/sdRrDWWy0Z9TkaYreTe05QnEaSdz 1U4p6x+Evy19PQt5dke6jojXBfGOkXb/IvU9Efmvht/PiLMH6U7j3IB6nYM+KzbGypEo7xCk WYJ83uF7pTw96Fyp/ziUk4z+Xcjfa6LaYHwAcXccrDY3tBKI5Wj3QLRtKPyeRn0+5PtDm6aQ 94S9spmSHf2MbZfyU/n7gd/LiUpp00DE2YTwEQififLfl/7+QL45WWJ/QRlnjgfEWy59WCZ5 zob/5Wh3EPZNxlxBpRLXo+3HtlCbYNfJuOuKuuYjv3XIu718h66A33bUaxvyebSxUqo0wtTS gmcZ6lzAdabMcQ/DPfRgtYFwBtIH5T38gnTpiDsB4/gqxC2BuQb9NAH1fhPxilCf31DOQ+TN UKdW8t2Iwzu/SN71GplzGksdxhvvjxvIXQ5S18Juk7Q1yK8z0swg742401D+n0j7I+hGsDug 7EYo72bU5SuuWRB3FuryCPxXIn6ujDcekH8PYR/Ar9mh3gC2nM2xAYhzNjsAW65HgO22zS6A raqvJwDxvs0GgFhYk2wdqXS5eynzic0aQKxpEIBYHUP7Nrjbh7p6Kav/xw0v67yP3RosP/VU VvjjhoOVRR/HBlbe/rEDVvY3wEoKaxwISnzk41gQwcKSbG7I8Ab0lG7WgXHH3bqUhmRcb5dJ xkmfxHapesonTpd1eNm5Ub59fV0maU/5JBq+69wJn5mRmR32cnX6NdEyau+hO5/+JNpLc9XA y+j+prb7VBd4RWt/+yQSrY3/3duviTr93Gitl19T/KfOL3eEx7L6fur65Vbs8PTLPf3TBvxy Jc05nzbwlyvp/v7LGYYf3rqjdhh2sA48elrsiTYI8Bty/468DMWZ0TJTtai/tx7YE+3HEKUW Xl7Z5j2xDcfteyKHY7bHzYM9e2LbPGj0d+TmwZoGbB60a+/3tHmwtbeSnqye7kgfB61k/G9v g/w9DVMphrNgQPqt4y2OIc91sIT5LKvO5kOvW5QxNx8Ggh54nzLPYAUfyI6UXh6xl8yfzzZV ltKCpzcfXreUtlKtcY+a43iwjtrRKG2rpX21lC+lqJ6UNlDqlpKbFHiidDE14FFKRWsX1Fq1 qJnvTnFT6pgHl/R9m/qhtDAlzKgRj9rDqKVVS5yyjyhtqLWBUoGAvoaEmkyptY2atyh4w0Nd lDamNCAlMqkhVSthooKIgZaSFKIGpyRLadDTWhippZTCKJRypnT1TvHnRgn5Vw2OULJbX91E CVZqp9Pa5SjVQwUWWlECha2oyIIS4eWWUtrA91sl4dT6R0k0SpBTCx6lbiiZZUoXD7OU5DS3 pvS1VlQyQSlZarvVWgypBekqS2nHulf8tNQvtQhSUppSVpQMooYwjkdT+QS1vq43yuW6JN1S GvOoDZDnajTurJUT8BAiJTH1XFptKY25ZGg4nVPrGMcapY+oPY+bT1oTqX44BqmFUGtLpGa8 ElccHhalRO9WSymf+Fb8eShcS81TExq12+krYiix5ZY050MtiVqbotYWZ15vMtH6//8TdNEt o8Y68EMepsl+wvR6kRL7R7vC3HcXu7WG8tF4ITVOUpKfa19KrGsp7w5R0piPeVUUlzfdXeE8 uaAVsWiJ8Ci4ny3xzi+rvi9e36rSOUpcPjwloaXP3dc58dFKZ4jrkE3R18Hp+4m1RJ2p+MJ8 +KmhNLhWdnGFK5xS8pS21FL1C8U2lW1QqM5UGKJPb1BLNr+RnPd5IkLfPU3pdS3Vz5McK8RN qUWt4EafLCHmYJ5I4CpFn0KhYpgp4uaBY26GmFpQ+ZjKbV621CkRPlR8w9MEWvELNVnyxAwl Cald8U3xf1FsDcxUGPnpu7x5woRKbqh1U38jyYgYN57UKqcxn5O4YX2RmqMozfgQBuV5TX0i PdnC+loG3VSRVm6KATWiXM2RjM8DRk/00xoME6xe8hKGWSp+OgbEEwv0lSAJ1psCaGjp9DPQ udPnW3LYPMHqgPAlw9RcSXqogEH6dMJy/Dg3T1Dv2pY2xcejXYX6rpDejUGYhI+qT6Qz75D6 nCDpu+JHWDlRvdOjKI2NdlX2cfJ7AgEjrnakt9ejvZ9d6dSfyisq+6m8mP4h5Ld3giWHxROs rwS0u0DK29U0svxk1H/c+Vr6O8Gag/7eMV1rcEywfkP5KdcooQM73FXfk5BJp+scaW0C4vfk 69MMCZYP/dG4QktXoz/xIguHK+2kpM+WSUyfBulIoK7c6f9mhoZCzkcvywRSe6UK/m273hKN ggnWKoSnzHf65y9X/I3UWDjBeT9u6do5iZHjIRn9kTVdX3GUYD2O9o3I1RoKE6xRGB/nDXfe FzWI5xrvY6eMVy2dzU301FJLDqsnWOe7ylsMets8p/5r0fCupyjeiPRbfL8Xqm8o6ZbcOJyp D1+jv5H+m8vVHGWPV6Sv6q9+a6SvdI1XClDszVE8j35/48JKEzrpAVL/M6R+1+D3UzhBn6ZI sG5H/CunqW876Z/RvnSjPnoTSvd/Iehd83V7E6xh/sj3vwj1H3WllvZOsBZJei19PQr1KU9z 5ofDeXi+rwojfToc5ddZoowF/Y/8Ol2l5mbSVyG/nguc8slPDTTe1wr0V88Bip+zTys0curH 98f5ZsFNise1f+9IuGahumnAHm9I3/9U5/fzPdq3xKjfndwQztPS8wn25sOay7W0fIK9WaTD Sc9D/2ZPs0SjZ4J1CcpPN8YH55eqCiVwQ3qa1He+9Fcl4pcY7dWnSfTv/3uM3z5nqJsLGL5M wvXphUTQexc48w+Ve2Yb7cnUwjYSfyLqUynvn+0LuH6/R7eKpFNaRI5/avkf1099m5n+OdR/ sTHfHS/jcYycBnqTG9rpzmmFQvRXzVTFq5I+IdFpL+OnUmnmyc74+Vf6S/8+ixpFxj+Zwh7z 1HfRHg8Y3xON79Fpxvxl/7552uYCfbqg7umem13z6yT0f7oxfzzhmr8CqO+qvpZofE2oPf2R 5lf9RSGLgeMd6f+Dmjrz21EyH3S9yTktMQMFdbpMaX3W38vWJ6t1COmTUJ9dw5z5Y7nre9LE NR4oTDOrryXKUBKsucL49pD3eQGVj0xVPAPDn5f+bRpQ/ZEU7/Q/4x/imm/vd43fL7jZkeeM LyrfWSXt9aRQoL0/ps2DZkf4a2Gzrh4B765H+F2bBzs8bR70l7KUhtefkofKUWIvZY6UMmdb PzVo86Ashvbd5G4f6uqlrDHH+RsM6E85zh8ToF8hZREW7NpAJQZ3HeePQfq4KFxckMtb6o/v 0dU6MOr3ky6kAfl6wVFbdfHHBOd37uJ02DwDR02qr8Mk7UlIu18c1ai/Fxi1IlpeSR46dE2X aG+tbiW8jPCfajuxYSjqv9KJGkU9zyOKGt/VHxOK2qarPwJFXdUAFLXHGd5Q1OqjFCKVWqhY No2iHmm184SiXvGwYw6Eot78sDImiloJuvIFMQiY2DUSRa3AcrfiFWXcKCq55/lG/uRuyJES ceOX/XiJo1WhctWr3wGRRa0rQd9VxAk53ciPSCxX4Pwqap0I/IITAUyy1KrX7HqikBrVJEpL dISrfqIZGn0hesmvXi/LQW+4qiIqoVE+E5nQCDDHWbnhz74zkRkibm70jo9Wk0skcKClOGZT UpQcqlYtyh8DUVyuCkxVpUQ0zAuxZxpuIiJEGtKsug8RC35FyNxo5EqjwuREiL4SbSZCQvRv vIRpRESjQXyIYGsJxTmGPxEJogBEpbzqczjQw4ksGqLl5SHHFA2BMqS2bA65eZQ40R63elo+ XDXxN6CRPv4ONXKt71hy69UYLLZWi6tV4hJ510gkUWyNXBN9jIbUER07O4o/OWWiNfpuE73T oCXhslzxuUInGqd1imh0UCOqGmnVqB/RMq52C4Tmyom7IET2iVJwAUF0iMiY5s759IhSV/1M oApE/LivbcRy462XQ05dWI8VBryaZMnvebDWSRFvtQ5GhifKhKd1VAx2pR8g+eszw9NR/qhq 9btsgRF3POikIfoMe7z1AOiuY9U9daSfd+XnRjk2ucJ511tiX3Wfj61CUuqrVVoGpT56ldNN 6n+2tL+/q33vk3HFj3aAqAS8SiYSvYr/R2h9hp73AbbrY9Wq7D3EVb8q5Fc9U82zDOcdb5sx QeyW/Hn33cQ+CqW07/lA/OwZelUdb52pRWWl/BxXfW9h/860alXCJoAuP0Xdf2OrMIV/xQzn XpWXJK3WObJP6LbSnnukf4olvLOrvKPZnhfUnMT3+bqE61X7FJS/sNp53znU2bBU3SfE8rlz VogfYLaoIHxDPt76DHd7xE+6Wf127fEg/f2hhN9ljC/OMVOlvkdIHn9IXSn+zvhEjD+boVel 8VaB6/086xovR6O81MHOvRzuVbDf1R+zUP+FZer7wfiHgl48y6q9F+Z7xE+/yapVmfqwpNXj qcbV/+Nd9Xsgzmkvf08U1asux7dUxs/PXAVfZdWqtHxd0j4uv0+uwnfP0ihYvPUX6jNisVWr MrgY/ZSCJf14ye9rxO+EVetjTRXd3KUToVrar3V0HOeqr76TU+tE4JGepDKrVkWqXFVq8zgM vwv0SnzYL2yhwqkKtTGW3Il+NX54/2GrflqHRryt+rKmhxpntopXV/nvSf6PSv1OQPum36JX 6fHWZOS/drpG1eKt+eyfMqtWJfSZrvd7NvJbPETraIm3UbG17LygxEf6jZikdwnN+5QqLlf3 TpJeKfmVSXsHs32TFVrE8Kdd8+WvyL/mdnXUxVa5Ke3ROjgekv79XejzZHxonRuPuH4fK/g+ ZzrzSX/kN26IQ9feDedX5TdjeuP3N4Ei70ud/uP9VIt7W7UqyZ+Q5GnSvi1S31Spz/Mov/8s xfcw/hZDJaetMwNm92CrViXuIkmvdcJ8iP7bfKP6BjI8w6VC9QnX77ejL7I/K13hnPeqh1i1 Knl3uMbPPMRPRGGtpP97S35aRwfvyNx9kuJlbRXdPuf92rswoPucpHarGf4v5/t+6j5Te/6R +Pr3z7vVOs21alVm3+aqL3e2eg62au9Fep1LninO73U4UawhijeyVdJK+gGS/l/pr65SXpLT XNt9k7j1/PtHyAm3dWY0iqSbuuj/NZ0a9C1Oy84vmCbOLDqz8tPC0wsz8rOstCnhkuLsgqIS q7ikiBof0tIK00qo5oKOzNyM4mKruKw4t2CKHSGjOJyZV2hNyixA1IxJTMdcETk7LVxUlF+Q lluQqZSusjBknl1QXDKpLB8V6mF7qZa4IzPv7CJmg+gZuTkZzDKT9UibZOXkh0vSCktUtHyl lqI4rTicgTR2A7IjSqgtNCMrqwhVRX2LRW0Ggy8uDReV1Saz4yginF9iTS4oDOdbk9kpiHxp DnpocmZuQXG4bnMs1EBSpYXzs8Rl1EY6vOBSp/PzMnJybSK/OI1R0vJLCgoNsjS/MCNzmla+ wcxyqR8ErxxjYVpOoWRbWKr94VJvz45CAASuyYVp+dJKFgpTmltCRQ7FyqOgUBGiTMQLTjH9 jNhQ1GvPcFDGJI8o44ozXChjtTeU8S2jrHYeyzp3pKusmp88IbZZIw3Etvzn5L0CAngps3ik Rmx/bhBiO3dkw9t3i7t9qKuXstqkNrysE1NdZVV6K2twasPR4bNSY0OHJ6c6YGeSgQ5zXXcg dLg0NRZ0OCvXBh+TrQMDmS/rAjzm6QUV3pYaGyqccrbTUScsd1DhdvV1lKQddnY9qLDU3Qsi /HC0fNp56MjPzq4HEY7ovPrzOWhMbGhw0phINHiERzT4hDGxocEDxkSiwcsagAYPn+4NDS5s oxCcUc1UWEPR4MZtHXMgNLhtW2VMNLgd6HZdlOGttLw13kSDdyF8VxdlKPdKo9Fgcu1EOon6 EtHQiCMRJnL7PaQ+RF7J/XJwEp0i96dRM+ZBlJEDgbPaydJWomHdpJwkiasRK3LrGtUkckPu laio1vAb7QZy/QQtR1us+9FyeHFRwppG8TMfoosaESRTyhULxybHGbnldhLmvuFdvyON/JHT JlKu5QbICWsEMUVsosdEPDV6rdFb8/lRGqGRtUSenzpEyaZqZEY/STDzXHSVL5I+1hXuRsI0 0vG7rPSHueJfLfXRK4E1Qj8r8gcPuuLPdZWvZV35/jiWWkt6ra30fglvLOGbXPl1Rfxlh2p5 mnj7sKcZTnldHkzVl8W8YyAdHMuUc64+1EGutrjq50ZmCl35a1ng1aLd9HVX+qvE3Vv670Qp /xShl7jid5BwvXK7Q2itTXSXKz4v99rdQsv3xdcO8naS//Ou+uqbs08T5OoZy+kP9u+XLiTo VVf49br+Ur/Nrv7UN6uHgyq82KeUibxt91+8Le/O518J1zeA89Iw0m9Kfmsl/11S/xP9qv// FlqvzC931fcpF32Bq/1HSHn/xkVfqXI8UCmIRvJucSGH7YyVPFemx7joFBf9v7hyzaIKQKxq qFPQAoU1Y0FRWlFpPok0e6WmosBSizT6O64puQWTMnLTijOpSZAeuQUZWWGsefNz0/KKp6Rh 7ZmWmV+C9R/YAqpqLMlNyyrAGi1f1llZmViBlYSnl9ipi6ngLzfNroVkVzCttDCtuCxvUkGu vT6r642qwWH6X6I0T4az9pfQHQFZXGLnkVbrkMNBaXmlqJ1eUkd6YoFXUlRQVscfS+5pdTxL isqi+pfmR/POKCkpilqoHbCfgu0wrJg1tiBh08JlaZlwlZieiFZcGM7MmZyTafhOiepbkJ9p Js1xNHE6nhklkwuK0AxNZ+aGM/LR04Wlxdmo7+RwUZSwgkIulksKisJWZq0iTRliVCQpA0GG JaEJGRlpGRpuyMpV8AKSKIce0vkFMqhR30sKpoXTsogY5GRiIOZPw88gzeKIJJ/ay8rN6mbz rzbXaqAil1IFqIYKasEbOEowplB8uAij1VI/RIRn5eTztxkuyQrn5uRZ4en260ubVDRN1y2z tGgSeyktrNSTWngpdqyw+gmEs6jQEkmKiyVX4h6Ww1Jbp406ffCQtB7Hp9S6ulunDRly/Omj xw0bM3qQvWEXNLiKoM3hBGVHLyi03zaIV66+osHaOI3s/347Vghf0KD8hfCR4P9g7Z/ineLs 0uKEz1R/N67/tSn5OPI5LWRu89m5+qzEnJwEHdbOCItDaAsJ43eMc2RjV5wA/q9JHNBI70Sn 1Ib5bTSf/BX5IubD1MyDfok2HTLy8ltT4pxdZhW/kSt+sDY++WHWZSPsEPyqaYOx20ob36Ca LuoCuddoI4MdtMFfraENxmwzbTCla2mD2d1JG0zeO7TB7H5DGwzyNtpgaD+jDcb3GdpgmId2 Ud/IEV2UxvBRtFF+Km1UbBxt1OM82mBOJ9Kmghna+C5l0UY9smmjHrm0eQEnbbyIEtpgJKfT BsM+izY+bOW08RG7kjaY0AW0waQvpA1mq4I2zGLaYNCX0MYCYBltMOWVtPFC7qEN5nwlbbRr FW0wo1W00b4naIPJP+fqb8dyN8qaMOfVw8A0z32+nFRJcNsHaP3Vf2zj1sq25WBYrr1w71uv WvtsjTP77ta77fvuJpdty5Vs34qF+L67+TazGby9xqY5crLpub3apsk1Z/Pf9iqb5qjMTiJd adN0ZnM5sr3CpjkysznEtpfbNIOyuTzZXmjTXM1kDySdbtOMms0Nye2pNs3VTDY3ILYPtGkm zeam+fYUm+YKKjuddJJNM6tsNmh7ok1TXiObwiTbLZu27xyhkMv2nUQe7ubPP7vcbr9Ns6js BXb7bZpyKtkVdvttmkVnL7Hbb9OUA8mutNtv06xK9kq7/TbNvcPsKrv9Ns2qZT9jt9+muarO rrbbb9OsavZau/02zRVCdo3dfptm1bM32+23acqZZG+12//vPr0BHDEu9rXluNhGmKX0lB9b ViwqOcZalBq4+qZv4HWtta/m2rl0ze1jlW6b+7x9GqYkftHcHfBL3TYBmb45l4k5ndiDyMz7 7rbiueiSiDKvtctcYOd18KK5VCaeqrNc+Q+KjZJmvM6roqIC/nN3JNYG9feCU7w8PTY0eMt0 B1WM94gq/j3djQb/7AmhbVJmILRbf06Ol3MxXso8rCw2hPaYsoa3r3+Zq31bvaGm5WUNR01v KosNNf24zAEDAwZqSkm6A6GmO8tiQU3Br2R26dKNXFCv47t3627zF1609E6Y4RFDjVqCF0R1 3ozYENXbZzid+NYtDqJ6fH2dKGkfnBENUS0tLtKgZtTWeMFYJ86PkvPxHjp64fxo7/VAVfLy i3hpfmyo6wfzI1HXPh5R1y/nx4a6/jI/EnVd2ADUdfpj3lDXqiU+G2UcOF7xg1oNcgfriDqo 6bY+cbYxUVOrL0o4XZnN+DZWbYxETZO2x1lJfynjRk3JzfEumHf9kfIqE+BXE1CImJa5u10a ciPiToQ5DHFGyp76cLF3iLo9Pk3gp2U0Hgoo9Xxvwnwp5UwOWnWehRJfX6eaA7oL4iUITZmo dpKOV8ZuRV66SycKYvwz/F6E7Zc0pyH+h5Rdgt3NKFOr7RoVUDIKVGnWP6A0CfDhqcb+yIdX J/sQdjHMW1J3jeCsA328kedcv5KDoqxcGO7fDSTnHannloBCIO8Tf6p307JxRJYKJL8l8F/n UyjgB3A/aeRlt0vq8G9AqWflU4r4pfC/kCdxEH8VzMlxjmqubnFKewAfX5xS2cqr3eUmeKuJ MeDi4fcq0p8q5X4pYc2F7iH1fIl9i7gHu6Bqqg70Sb4DJE0l6N3it178liLf4+F3CNLzuvgN 8P8P6F6wT0cZT8FdJGU9J3UgYv8+3D38SjXgGtiDYH8fUPKARyKsm+SfF3BkOS4LKBStJ/Lr IfX4WuqdL2VMhH04zGfwfyFOnTDvIuW2jjJmeafVHOR1GuKcjfB/kOZYyrZI/jztyR9sKeJl wn0jwnjCUaPiQxC2Ev5nw1wRUKqGOwaVHFsyzEkw32sEPU6dUr2U+cF8pMcUxxrSvgN7rLT7 SmO87OKqLU5pxRiGdP9B2G2gj5H2vM0yjfgXIKyIbQo4cvKjKe8lbUpCugfh7kMZJvhnBZVW CKpAbQt3Z9gr4J8Cs9OYV05AWK+AIKSI85qE3QT3jdJG3r1GBJnyYu8hfDzcyUGlQvxRiX+O X90lNAF+h8H86lMqVztIew4NWrXyskMRPhfujTDrjDHKua8ZzAKYrwNKLW2lMf7/9CntJHnw f9rvoORfxSn1peaTLGVN0/Od0ZcZcA9AfSiP+BHc18CepuuJdD/CTIX5DmEVHPsIfw9l3QP3 ML7TgLonrTv7AunWGmW/Lu5NYi+TehwjNFEG7gKcCn/K61Jl9E+SlvKxH0t8qn0mip7hU+j3 aJ/aXagIKJSjEOazgNJCswzxTpT68wR8jpZbQziR55MQdoNrrtor5VAl5Wfip+VNH4Z9h1/J TVJGcrkxXkqi/N74fAPTHWFHI+7PSLsdZgrowUZ87sLdJHlV+5xdkMvlPY5FXXZxvPL9+tRu 5qsBpSr1u4Czi8PnH0nzIGyqOv5AaH5L+wQUKtM7Tp31uAfmWdD74pTGl+Gwf0L8nij/XPj/ AVMOc5jRR4sQJw11543oW+F/qdEHO0GXCH0I4lBOkGobX5U6cLekr4R/4XPOTTwgfp9KOb/E OecOxklYOuK/APd1CPs0oDS+8DmBvz+/0k6TKOl5d+BdiDPSr076jxL/JxF3qOR3bFDJP98p dWvD3xbiVSNOqcTpCDs+qBAlreFikl/J9+8LqF2XMeL/lk/tcPxt9McgecfcpXwO6RICSmac Txexqb79Crh7I+4c2FWIkwf3o6jHaH7vA+rcj1xdax0s+X9olHME3NdKO3b7nPMA1FAUpJtj BOYI5Bsv5b4N+m4jj28l/edSjr7SgLLsx3Ju5bgJqB1FylX+jPhzjN/3sXCnw390UJ1z0DtZ 5xvz1BiEP4E8WiIsG/Fuht0L5k74vwv7/DglWzsAadrAPgqmo1HGF3BT6RbveLs2Tu1WUW3y ds4VoE9FnhNh/8HxE1Ty62Ng/w76XNjFLBumC3kA0C/41LUPQ+HOR5w4eV9afptwzPlBZ1fr L6MuPEH8Csovh5+fvwPWB2ZVnNqtv9dSV9e3CqjzE5SmyeL3P6DkmmfAvhim0q928/h8JeVS 29Bx8HsJ6RcF1C4yZci/4fwL/4P4e4VJ8qmzBANhGsNMQ/gT8NuAsCzjN3uL5Ls7Tsmi8jnI p1TxNiIPgXDeg7cnoK4n2CFxKId7NtI0ht8sfkM5f4H+y692RvkQpxon9f9H0s1AnGc4j0h/ HRRUZzROgl+61IVo9xnw62SMwUBQ7XguQP594F5ihO3xKzl0/fxjhBF9rt2JhH0R6PUBdS3G XTAnI6+rYH8ldX5X7O9g32nkk2u4d8Q5d9v+CxMMKtXRfCbB/YsRl89w0Ima50AdPkV6Knw7 Wfy4kz4C6S7kuJb+olr0sRJ+u9jcYb0b9eorcS4PqKtKMmC3Qtgk2BNgMhG+APRjcLeGSZO+ 4fLqSqNubaWtt2ne2K+kS16WOG2Qz4txSrrkU8T9QfKhVYC4pyBeNb+nMP2kTk8b+TeD3xlC E8a5ylJaDq424tzP7xTMWWwv4s+VMo6LU5oAqL4/R+IXwz1EwnnlxnK4K2CWwnwB+kWJ14z9 CPcPMAlBdQbjHP4myZvD7o6675O2Xw/6TdBnSf1/lfz12bJW8L+M3yrEu1DinAR3rl9pcpgJ N/WepiCMZwUyjHFIbWOzEO8OhN/n4rX0M0b87XMSBOZheObhkqA606HvTOXdiKYEgn6ozS0X cT+WfDKkjgNBX0PEBOYEyeMG+I0iTx6ntLo1gT0bYfNgn+LiUdJBfxBQUkHtYT/Hfovzhkr6 VseGurZd3fCT/hmrXajkTm+oa9FqA3VN+TW5aosK81LmnNUadf21QajrdTG07153+1BXL2WN /bzhZeV/7u5Lb2XN/LzhCO+Cz2NDeNeE4qIivMSeDoTwfhCKiwHhzbN3tztbB0Yaj2gU5w3S VVl6wXCHIstYMNzxjZxu6r3MwXDb1tdNkjbMZuxPKlZV3QtguzpaNm09dOOWRtFeU0T5XkZz 58ZxMaGzfRvHRaCzyR7R2RFSXkPR2XOlPI3OzmoAOtu9S5wndLZmgJIBfSZPHe/RMrHdrOM8 ycT2f8RXaw4kE3sW4tAEpQMYngo69UVlcuGxwBeJ7sY/6rPiX1LGrSGBK6yzfIor5cONVy27 NsAo/FBxU/ffsVG+lLy1XGtReNnwp95PIm1axpXoIevOk148na11JxJx/F3cU4z03NGkrOOf Qv9iOTIRXB3wZCsRh+4+pZ+UD7UGaK0GfAb6lN5c/TwqdmujHZQ77etTXFsLn9J1y4dcErUX UC8tZWpP9Cm9igf7lL7SdpJHY7H18GgvdrLYp0l+8T51upVzDXVFUVcj9Ui+YqlTjXzIUfH9 kGsnqsjL2bji6Cd5MBoRks1Ct/SpVbjWlUqZTJ7Qpt7ZjuJH1HSwT+mlJSKRbvQH9fQSUeOq a4hPVhgwf8Fq41Ooy1E+ddruBKPPhvqUjtvjGMenTtGSY+JngycQ74Tx+9RKnSfH97Bdkn6Y pU7j6of6hbn6aQW/TuLPVRBXAPxiEpHSqwLqrqVu5K9hdluOfk8+h/iUfDa1AVCHMOUpX5cw InVaDyW5ZcpEHu1TpxE1qkE5ZSL91IPXWeqh9Q2f7nNQ4rthDjfqz98RhRS4M/CFVffpIHGJ /Eyy1IpNa3ygzjfqyeJp62ESj6t96vUdJajTMUZenEeot62HUb7WckKEmbqI9WefstcZ4qZs bjMjDWWgecFSgk9pAKBsch+fOs0711L6hY+J8lv3+jQ7cBTrkANHiXjaGu6j9htLPdH05yYZ 7k6Woz1Dy+frud6t0zbaw+/0kQZNyZwBrjiHi00BHuPOGFsGPsUVt4/YvT2Uvb/nTHlfg61I XdV8TN3eRPkGWnV1Kk8Q27XItuWweb5Bo3EjxS4UW38+jxb7QrGvsNRpeT6Uwdf6gN3PKBdd ZLi1hpuuhh+RW708uMGVljp051iOthierh4hbr1TSamix8Wt9e+aaO5ywz1UbL0bt9IIu1ds oro8q2BqRLlI7FfFNjXmUIhB6yZ/w6r7EOFMNWjqLZwqbkokuXV186HwTheD/kZsrqS5Wj65 Toq6z2TDrTWzdLAUb8ddAmpOelD8qcmI0lA8Xb5Y/HiGhrLwxzvZWM19DvqlH61Ribrjv7XU ie8vLcWv7LUUj7IL5m8rUlPNBrGvjFJ3alAif6j1GG+11C4FH+qtp5x7uaUQd62nnnr1uXul EQnqOubqnZpaKIlGfa08pU80mzu9MyQetTRpbUrcTaR++K4a9RB/UwuSfm7FpD8Qk7zSgBJv 8w8DJ6i5hHL5JWQ5K9TvkuGb8DFLHOOzv/Wkl/JFgFFYJDQRv9wK9Z0nTQ0TVfeo8UE6BEai +gFVX9JXY1KomeSzdwxJv4QfetVS1S7S3JVLvVK9C9L3I37iZJ/NO5CehQlz57MKoSF9hBzq 0ed2/uHlhuiIVZJ+JOq7FQzMdULvABNV+Lf6fZJ+AfF3goHYIe3f3Ei9oATJf5wcfpp6lsr/ Y9SnPNtn82UM58WrW9GfT0l+p+CDknK+U95KlF+B/npeaPIT1Rc4Ghh4kWrKjepbwXC+s/QX tZ7PRGsZyq9cpfhChg9H+X0u8tlzkd2/8dz98Nk8Kul8TKybwcQ0Fvoy9geYjEslfSLCa8Cw DZPwTLS38mnFN5JOQv1Tx/tsfpb0qfiIVu9V45f0V9Qo8YhVm/9DGB+jUn02z0ialz8noXO2 Cb1ePsJt5P1kYKCl4oO/UPIfBM8KMPq9JH4pGKBqVJb1Yf/8zcsML/TZ31qG88Lc8rWKfyXd iRd37lW8P2lemJeyT/FzpKfi/SSCqfxB6Kf5fib47O8Eae44p85T85b9/lC/JDDJlfp9IH76 BT77u32UnFuh3lsd332ui79T6inuKe+XO/YVlc74vkUYjgtlPHVCe9MLfNYN0h83N1Ka5voL PR7xt2I8pUt+11PPLCaHSyU/XkxcVa00W5CmxMpnKxTvSfpzhCe+oeY70pcb/Uual/fOwkf7 FQn/APnvxALkOKHLEL4VTODtQnMnqWqZ4q1J78V4mPWI1o0fb53Ni3nxY9V0LzK0F/usx6S8 H1CfijfUnE36OuSXeLdVO790wHitweKlvcTfJ9uBnWT8vIV/VWDcT5D4xyC8EouhR4Xel8DL L533ezHoQiwuPxd6NeKngEn/UfJ/Bu+z8AbFj9vzEeqbWOaz+WjS+u4JrcHpEI7Hc53y5gij kizh1ECSepf6njC8EuWnoz9HyPv7C5ESsViZJuVnofyaeUpqwZ6PqOd8j9ZzHm89if6sHK7W zV5wipld4mJCZ2/tEleLKO742hsm8qyUVYsoJv7mCZ19S8qy0dnqXcmb5UPv6X4hKXO2tatB 6Oy2GNq3190+1NVLWb1mxjUYMT1zZlxMiGnZTAcK3LWrYYjpwpmxIKaZnhHTj3X+3rL0gpi2 nRUbYtp9ltNNjVc0DDE9dVY9iGmmZ8T0hmjZeEFMX5pVD2Ka6Rkx/XlWbIjpvlmRiGlrj4hp 89mxIabtZkciprkNQEwXP+YNMV15hZJn3fGCWpNoxHQg1s9eENPlq5rXmgMhpo8hDo2JmFaD rl6jzC4sWdrlRiKmez9vbu39WZlo8rBfhNS+P2XK7g8qvXf8sa31KZnStxH+REjJ1QwNKVlL ylO0EG52Rkh98YbL14v7wEQpKXOzGflNlXjUe3UR0T3k8yT8nnWpAljFfENqfzpf9pmpM3A2 DHVZfeZXcgYLYE6XtFouje2gnNgdAQf9aBxQ14tTdo/yCK/Bfgkmhyix5E807aM4JcvBh/KU Xf1KJoN75jwZvwl51CDdKzBnh9QVxNzjphwdZao+NuAFInBgMO1rjymjpfftT4fdDulKYP4T VH6dQkquhGjq5SEl+0IOgEmqLbUvS/kayjKMlz1qImtfB5Xc0Pygkq0KwJwl/fG35L1D+mW5 0KUhhd5QBi5T4tq3JEn4QchjAfwLJIwyhJRtHhtSSPaskEJlyZlvQ/veDyh9a+TMKW9K+T/K xGpUhvK3lDW7Q/KPR/qHYD5E2rf8CuWl3Aqv66beMsplUL8kr8um3lCNMJ4DvyuIMvuUbPEY Y8xw3h4v+f8iflzhPAXzfFDJOlJ2SssXk4vn9fSUvT0spGQjVsg4oOztBfC7AeYl432u9Stk sRxx3wyqlTVvS7lP6rcopGTJa6Re5Njug/tmmEtgrhP/1rCvl7LiQmrv/S+hqbXhUb/aAViF sKnot2NhPxNQOgspIzc3pORPb4LN2wlS5P3ODyjZ3U7MC4Y3d1whYZRvugBhr4ccjQ7d4F4Z UjITn0i8FaBnBJWM2ki4NyBdz5DSP0h52ZUiq0C5dModfEKZo5CS2eRDmaiHpY8px94EYZNh voDf+7DTOH8g3WzK8AWVjNPakJKl0DpZKdtxZEDJVlJm5y7JT8us3xdUsmM3wn6c+Qadd0SZ 62uQz43sM/jPCirNCTNh3wt7SUjJrL0XcmSJ3jEmVspz3RtQsqdr5J10tCKfvJCSDTefLyjb KvlQ/pbyxyeHlCz8HNjzfUp+bD7ct0o7KRNIORHKd1H2mTLky0BT1yTlTogI7ZG2UTaJsl6U xfvAaG+8UY9vgkruq73RnqUMN+Ifz98TzBs+Jd+aSK0SME8GlczkiDglR60fyp4/Kv1Ujnjv wOyR/FNDSuYYrKXVA3GokzY/oM47VASd8wY8T3E38nwe4b1gDoK7KE7Jlmk5so+CapVDua/m ISU7WcxypextcUo+j3pTrxZZHMrw8IzAYMTfBHsp/A8JKfkhXqOeFVKyz5RtGxbn7BB0FBmp AMch/E9EvO0BJWvNXYkHOb5CSkbumZCSB+TzKX8/cL8B8520jbLrlFnXKOAlUl/KOFNGKDlO nTHoF1Lf2RqfI5PHletQyYeycjwnQDkyrtgo35sHegnsU2S8UGYuKPkPCqnzC4thukj4BOO9 h+McuabF3PEJKVld6gHluZFWEvcq2FXwW2PMpbcGlGzVyShvNX+/ASUnTPl16ommfFAS85M0 PFPQD6a30FoXLM8DVHCuM/J+K6R23Cj/uVXijZR6PgL6XOS9LqhkjR6GORXmFUlPnbTDYK51 8Qrf6jEUUPKI3Y3wTsiLunfJmI6Q8tqIfZoxt2eKmygHz/Y85VPID2WVv5U4+mY17rRRHvA9 1hd5j/Mp+TzKuZfDTd2o3DVcHFJyWv1h1iAsnb+7kJKlp0zueUElC7sI9oMhddYmFFRyeNfC fZe8oxeDSl8r5fx4CHu5X8lshjnH+ZXc8WxpE2XSvxU3kRyiDdwB1LLh7xv9Rp3Ye2U8af2r +rlX6FFi3xt0dCJfBnsAUQXyYjBD/Eo2lzKp01Hnx+C3ReJS3pTy4JTLfDekzmK0RbzL+P1H 2Kuwr5Z+NXV8n8HfC9NK+ZSNpCzwcyHnPIj5xBtpH5D8lofUri01C7wUUucb3pa0v7FPYe4J KXlNnidpEadkZPlQbvcc1s2vZB9vh7tM3gdlI+9B+OVBdf6JZ4Ao5/54nJIn5FmyzvBbjzR/ InwH0g2B3/WwHyZfEXDOTOSG1PkRyuTOg/s8mOSQOp/TVuryUcg5K8LVMc+DbIbfxpCS0+ZT GKdkIJuynq7fB2UIKc/HHbTHjL67EvF+CSr5zUtD6kzOtSwT8eLg/sGv0PIiyU/L5VOGlmfe eLPSFLiPDKnzMXz6ixzvN8b7oK7jz4KOzP4fQSWXThlCyupSUqAypCQPSiUfnrejhiaeS3sx pOQ2z4W9nvw77GkhdXbtGEudl3rWr84J8IwXZb955uDKOCWP/ZXx/Xsc6a4CfRzsqqA6p0YZ cuo3nh5SkgYPBZW+cf3cw7lI6tWX30rkeZuEcxeaspyUBe4cUOdV/Ah7gd9TKZcao3rAb6Gk 4ZmDn/xK0xflVHcG1Xmu41l3xDk6qM4PDvYrKYyXg0pWk+cI/oHNnRTuSrQNqJ0+nlUaH1Jn /y4KKbnTFdwtD6qdoq7wey6oZDV5VsYfUGcKeAaD8rfvwhT5ldQBH8riFgadc3GUGtmIdFz8 zkRe/WHuDioJmM8D6rzWDIm7FO5PQupMCJ8h8s6520GZVMptP4d8JsK9Sn/7jL4+P6TklXnW gwDvCyF1TmiyX8n58+zakJA6G2m/T586P8SHO0JaD/79cG8Q9+FwfwDzOeiDmL/2l7rdLeVT dvVHF193luT9M8L2wWg9zF5wijarY0NMe652EMXPPCKKeatdiGLNLk+I6czVBmJaHnfsZ9O9 t+/a1Roxjau9nNdL+5bE0L6H3e1DXb2U9XGjQIPL+gNpItFZb2UFGgcajM62aByICZ09R8oi 7Fizq2F6XnMIhjT8FrASAoLdveh5fVIX4DFPL/jsp9JR/P01BJ/9MZaOkrR72I46+Ox/saP6 NZEC/osdld4kto4qaBJ7R81u8v/xiHqhyX9/RP0TY0e1bOp0VNtbG6Y5OKlptBGlr3JTdfcC +V8RLR8vmoOrmkZ7U5EV8DJHftU0EBPm/5t0nsb8d//mbU72NwvEhPknNgtEYP6jGoD5v8bD vx4w/53NFZ6/UkRANeafBO4wZB0Y899zjGMOhPkndFYmKB3A8CTQSb2VIa5OnCAk4WRn+uMN 9e+jTDTNwZRgpmQeJZsoEUWelniw1hRHHruX1J/lEjvuJnXTmm/Nm9C1tB9nDkozUFqPG7Fk Erj7r/E08nesn5Z+01g9x0MbK/ZHS2dGuz9MP1o601wqKUkl55ywKWXJvqJEJMcc3w/fW5Ir T+LBnSy1w67v7aEkpJbyouTl0eKmxHW0O8YqfE7dmf4nocuF1ufBtFTSXa74+ryyvr34agnX t/+Sx6/Cy7jSp26bdUuZNJX0WjtwmT8y/68lv6WSf46RH2+zfVHC1W3bCq8041e48iP2P7CF c7u1ljrX/TcI8dMPd27z5dWOFYfr254T7HWfmd986R++L47lQ4TWtysXu/qLEtA9W6gxc1SU 2403Es8/XGHqDH/PWHfY/WtF5pdnxGf99hr5k46T9OUS/11XfQ433h/pya5wvZ76zq/oZUZ7 Oe76CK3fdzvQVUlYx8Sp8m9y9U+SlHeYxN/B9Xt7p39HSnlam++peo9N4veX9Fq7L8+yVx/u tDdkvF/2310S/y+/6j++l+rWSgLU7l9Xf55j5Mfwr5jeqB/Pvqe3d9r3m9RXj98ky3nobmrg EtT228pF/69p/83IKUjLzMjPDOdSoSqIovDFpWBlipU2WSuqUlvGQ1lZjJw2OUt8wAnlTC7T wUXhsM7Liqrs1im5V0+bsNW6mm7bNbm4LD9TfG133UttVIlh3sVS6hSKEm1tsqJUllFEl26t 09GDmzvZMtXfZmaHswoz0EsWqMKcLMvRcKtV8kb4FFPda0lGZjZeSEm4NkwU7prqdp2c09IK 6Yum2bZl/4OnrW+WvkrxrPo/mTph7darPtBZinpZ84Uo9bnqVSJH7ZAuLAqXlBblRxC2s7i0 uJBaZo26qpfjalEBCrk0w2i/7VOSkxfOquutVRSrC4yMYqR81bZaF3xz4c7FIM0piBhUaQX5 uWVWnnqTThwkULGKc6bYL5+vq9R4XXYtlD5pbzqAcyZJUtIpDVTcq3+OSs11cekkvgl1a1Nx SUFhtID96/oVJnh/Gn4dFcD2LBqo1cjrFztg6+8NiI+/1l/TQfF1UgYN/2BteKPa9H7RCsyp V2v5nbO+qInmz/bJnOyzlJbfFoaWXz3fMSzOpcG3VW2Y396H1Rp8E0UjL3WA0a+FaPBtasTP i3NOq2mNvZHxA7XxyZeSB5oudkofZXeFHYKjZx+lsTe5j9LU24c2GKlOfZQG3mW91SmkStqY 7++hjfJX9layHqt6K1mQKtpg6J7orTTzPtNbaeZd01tp5q3urTTzvkYbNVxLG8zeO72Vpt4a 2vhWbaSNTtpMG8zrZ7TxgdzaW2nw/YY2GJRtvZUG3x29lebenb2V5t5dtPFx3d1bafDd21tp 8CVjTA2+AdpgmBvTBkMc30dp8k2kDUanVR+lwbd1H6W5l/eIUmNvUh+lsTdCI+tx1I5qn1Eo CW6jRrCr/9hGhU3b3mvz/zT1/t+hqXff3WxK9ja7/TZ9Jemddvttmk3L3m23/x/SC+3372P7 bbrCfv+ka/6Jrvn31mR7nNXV/FtRq/m3wtH8u8Qej7Waf2+3Nf8u3p/m35OTo2v+7WiXaWsk pOZfiv3Uav5dsh/Nv790dmn+bTz+3NrADxDY/Y83h+0lE7nvcb7AbUeibnNfC8ydHW8ddCVf ybWzG197ZnzfvgddxROCbw5jt1lX7942r4kXnOKf7oGYMP92PRyceo1HnHpgDxdObQWO9YKJ jJWylA6LwLHJstD1UuYUKXM2ytL+Xtp3SQztu87dPtTVS1k7ezQch29yYl0cXpVVf7qfTnTa lfurblf9aeJ7uto1UL+3+tON3m68t5pdyVZVc8/tK9oeqCPd7qXMU0YF65QZ9FhmMdLGUuaQ FUaZVX2TrepbPLfz1RW6zL4NKvPPt+uW6bWd971Tt8x4D2Wu/1mVOYEoWMWO5CaHeCsv6RdV 3gRrh+ukQv3pjmwbsstbIKiil7L6IA3LWmC9pK8IF2yy/nSPSVmtPJazVsppJeUwrpc+/GiI KmeU8Mft/vL2G/xliCpvlHXXyw15Z39OUuWNbGB5h2Wq8kYa5Xnpx16ZDevH4Zm6HwONdT96 GRuZUs4MxOzksU0zpKwZRlArD2XFFYes8mUvvvwIeiAJ3qN2q3fe2GMbOxWrch+xfkpuSLm9 jHKJfQ1sYLmnxVjueUa5R8XQ3pwYy10l5T4qZ95X7WlYuS9LuY828JvY8jU1lro1YJ7p+poq q5v2rw409lJWP6OsFKTxdLdqbVmvUuGGnc5LWReZ7arxVtY0V1k63YHK+vktVdZUlEBNQtng LTh2DrS335LCUVF3Yu39UqIeJxSHiy4JFx1iHXi3MEfnFi0DTyIi61Tzp2Ja13usXrYJ71xX t/ndPVT48f02f7+bxqoxCR4y978dJXMvtUphwobJEXjv4rK3dRc7j5cu3rLB6eI+v7/00vTf 9AirP93uDftrTCwjLHljyJGAiGWEDd0Y2wg7f2Pd5nt5l1M3xvguvYywVdEy91KrTRtjHPde urj9h3VHWCsPXXz4d853j3vAC//A9wfG+f7Un/7k7/R3r2HljjbK5Ri8EmXu/t17uZOilOtl XX3dd2pI9ZJDC75xlrV1w6fJXsqskjJ7Gd/agIcyf/vOzR/WH7/x93X5bC9t23REo1qhl3u+ VmkpI69OA9efdhfSNnBw2l7H5+TnqNPA+/nmfbnhY+Y/7MhGHoSDarP0IhtUhCyVeIszq3iR DXrmSKeblhjd1MRDM95nM/Dj91ZRSfSzUVHLkpuo66uopMtLauQdI5HGzUtq1DBZRUn3RZLT KWt+alin7EmKoVMO7lC3U+pluiRd+qBGEcJJFTsOsBCSdJcPalRHOMnLS7hHyiN4tNVjWa9K WbXgUcWOZC9t+9DVtk4/eSvvuyhta+2hvD+RjpPwQitYq3qMzwgZAF7KbjxYlb3QCKp3wEm6 noMbRQh9sY/KLaVyMXCAtFcirTXps1qhrwmjOfIubDo0pyicWVJQVDYgklVpOjKnZFxZYXhA j6ZjwyWlhUMHDyimfWl40vH5xZObnoPv7OiMvPCApkM4++WXKcLONbWoYEpRRt6AOhPXSSk9 TlTTVlMv/bRE+kmDzuUe39HGwXXfUXkD39H2KO/Iy9gfNqThE9C0IXUnoHrHvqSbJWVpoI2o g5fylkp5JtBWb79KuqJi1a+l6FcK1libq3avOm+oVdXIqfOByr61WJVNtWQ/yBfIS9kr91d2 nPeyn45Stpd+HnqHM8dw6b/jPweYYyTdpDsaOH/qfr7DmT9TDwS+S5ouy+vOn14+YoOXN6pl 7mzBTDB32zy2b4KU2auBH87PpMyAlMm6cuuKwoP7ncckbdMVKq0WIk2ofyaRVAUrVE0DMpP4 Pdb0phV1a8pN4k4earoaacuP6PiKrukoToRJ9gTZL8mWR0pKmd6977CEproNim2tkx/i2NCu qw2sR7zkXV+6ryv3N0vUn67RnXVnicYeyutyp35DPnuX+v8AL1Y5yNiiAQA= ------NetAddressPart-00--=_yPVv0848S763f7f60d6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 8:30:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id DF46C37BE97 for ; Tue, 25 Apr 2000 08:30:32 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA29494; Tue, 25 Apr 2000 08:30:28 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda29490; Tue Apr 25 08:30:22 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA07614; Tue, 25 Apr 2000 08:30:21 -0700 (PDT) Message-Id: <200004251530.IAA07614@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdNE7604; Tue Apr 25 08:30:18 2000 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Mailer: nmh 1.0.4, Exmh 2.1.1 X-Sender: cschuber To: Doug White Cc: Cy Schubert - ITSD Open Systems Group , Matthew Dillon , freebsd-stable@FreeBSD.ORG Subject: Re: Linux Emulation Root (was: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday) In-reply-to: Your message of "Mon, 24 Apr 2000 14:07:56 PDT." Date: Tue, 25 Apr 2000 08:30:18 -0700 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Doug White writes: > On Sun, 23 Apr 2000, Cy Schubert - ITSD Open Systems Group wrote: > > > In message <200004231835.LAA62963@apollo.backplane.com>, Matthew Dillon > > writes: > > > I intend to commit this to -current and immediately MFC it to -stable > . > > > I don't expect there to be any controversy though I'm sure there is a > > > cleaner way to do it. > > > > On a semi-related topic, it would be handy to have a feature, > > environment variable, table in the kernel, a sysctl variable, etc., to > > set the Linux emulation root to the real root. For example, the backup > > component of Legato for Linux (nsrexecd and friends) runs nicely on > > under Linux emulation, however, recovering files in the root directory > > sees them placed in the Linux emulation root directory. > > I ran into a similar problem with ADSM -- it would happily back up > /compat/linux thinking it was backing up /. I patched the linux mode KLD > to disable the /compat/linux path munging. I tried to submit it back but > was shot down; the emulation people wanted a more general method, which I > assume included a way to define your own 'linux root'. The discussion got > lost some time after that in -emulation. Legato for Linux backs up /, it just cannot restore to it. Instead if you restore for example restore /etc/rc.local, it's restored to /compat/linux/etc/rc.local. Any redirection using the Legato recover subcommand relocate to /etc does not work. Mounting a unionfs (or nullfs) of / on some other directory and redirecting the restore to it does work. > > > To work around this I've used a union filesystem that mounted / on > > another mount point and redirected my restores to it. > > Unforunately union mounts are known unstable. Nullfs mounts have always caused me problems, however unionfs mounts under 3.4 and 4.0 haven't caused my FreeBSD systems to crash yet. As a matter of fact I set up yet another one on my network at home, NFS mounting /compat on my 486DX33 from my P120 and union mounting /compat/linux on top of it so it could write the ldconfig cache. No problems so far. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 8:50:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from greed.zenspider.com (greed.zenspider.com [216.39.164.65]) by hub.freebsd.org (Postfix) with SMTP id 374FF37BD48 for ; Tue, 25 Apr 2000 08:50:47 -0700 (PDT) (envelope-from ryand@zenspider.com) Received: (qmail 36039 invoked from network); 25 Apr 2000 15:49:02 -0000 Received: from lust.zenspider.com (HELO ?216.39.164.68?) (216.39.164.68) by greed.zenspider.com with SMTP; 25 Apr 2000 15:49:02 -0000 Mime-Version: 1.0 Message-Id: Date: Tue, 25 Apr 2000 08:50:36 -0700 To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org From: Ryan Davis Subject: disks_registered in what .h file? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am close to saving my ass on a botched 4.0s upgrade, but my kernel won't build (GENERIC) because of a missing declaration. I restored /usr/include from backups, so it isn't in there... Where is it? Anyone? I've grepped every .h file on my entire system. I assume it is on tape. -- Ryan Davis -=- Zen Spider Software -=- mailto:ryand@ZenSpider.com -=- http://www.ZenSpider.com/ -=- I know that you believe you understand what you think I said but, I'm not sure you realize that what you heard is not what I meant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 9: 9:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id A9DBD37BF85; Tue, 25 Apr 2000 09:09:41 -0700 (PDT) (envelope-from mike@sentex.ca) Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id MAA56529; Tue, 25 Apr 2000 12:09:40 -0400 (EDT) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id MAA29267; Tue, 25 Apr 2000 12:09:39 -0400 (EDT) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000425120609.02403890@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 25 Apr 2000 12:06:09 -0400 To: Ryan Davis , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: disks_registered in what .h file? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:50 AM 4/25/00 -0700, Ryan Davis wrote: >I am close to saving my ass on a botched 4.0s upgrade, but my kernel >won't build (GENERIC) because of a missing declaration. I restored >/usr/include from backups, so it isn't in there... Where is it? >Anyone? I've grepped every .h file on my entire system. I assume it >is on tape. If you dont need the mlx drivers, you can change /usr/src/sys/modules/Makefile and delete the mlx entry. You wont be able to compile a kernel with the mlx drives without deleting the references to the non declared variable where the error happens. But if you dont need the drivers, then its not a problem. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 9:20:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id CD7E437BE1A; Tue, 25 Apr 2000 09:20:35 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id JAA22904; Tue, 25 Apr 2000 09:20:34 -0700 (PDT) Date: Tue, 25 Apr 2000 09:20:34 -0700 From: Brooks Davis To: Jukka Simila Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Ryan Davis Subject: Re: 3.4S -> 4.0S botched, can't build anything now Message-ID: <20000425092034.A19838@orion.ac.hmc.edu> References: <20000424221426.A2314@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from juksi@iname.com on Tue, Apr 25, 2000 at 10:43:38AM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 25, 2000 at 10:43:38AM +0300, Jukka Simila wrote: > > On 25-Apr-00 Brooks Davis wrote: > > On Mon, Apr 24, 2000 at 09:53:46PM -0700, Ryan Davis wrote: > >> I followed the instructions in /usr/src/UPDATING as best I could, but > >> I still think it is conflicting on whether to build the kernel first > >> or not. Doesn't matter, trying to build the kernel first failed, > >> presumably because config has changed. > > I wasn't able to build a custom kernel; instead I built a GENERIC and that > worked. (After I had similar problems like you) I strongly recommend that anyone who doesn't require a custom kernel just to boot use GENERIC during the bootstrap and then recreate their custom kernel from GENERIC. That way you should pick up all the new things that have become defaults and get rid of obsolete, but working syntax like the removal of numbers from declerations of PCI devices (fxp0->fxp). -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 9:52:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id F03F337B5CF for ; Tue, 25 Apr 2000 09:52:20 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id JAA04328 for freebsd-stable@FreeBSD.ORG; Tue, 25 Apr 2000 09:52:19 -0700 (PDT) Date: Tue, 25 Apr 2000 09:52:18 -0700 From: Brooks Davis To: freebsd-stable@FreeBSD.ORG Subject: Re: OpenSSH: DISPLAY not set Message-ID: <20000425095218.B19838@orion.ac.hmc.edu> References: <0vem7ui60w.fsf@cs.uni-magdeburg.de> <20000425111835.A2200@pir.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000425111835.A2200@pir.net>; from pir@pir.net on Tue, Apr 25, 2000 at 11:18:35AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 25, 2000 at 11:18:35AM -0400, Peter Radcliffe wrote: > X forwarding is off by default with openssh. > > See `man sshd` for the config entry to turn it on in (IIRC) > /etc/ssh/sshd_config. I believe that is incorrect. It may be disabled in the client by default, but it should not be disabled on the server. There is no risk to the server by enabling X forwarding. The risk is to the client. Just make sure your ~/.ssh/config file contains a "ForwardX11 yes" line in an appropriate place. See ssh(1) for more info on config file format. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 9:52:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cosrel2.hp.com (cosrel2.hp.com [156.153.255.162]) by hub.freebsd.org (Postfix) with ESMTP id 58DC737B575; Tue, 25 Apr 2000 09:52:32 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from l3107mxr.atl.hp.com (l3107mxr.atl.hp.com [15.19.254.19]) by cosrel2.hp.com (Postfix) with ESMTP id 0AB3D4F6; Tue, 25 Apr 2000 10:52:19 -0600 (MDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by l3107mxr.atl.hp.com (Postfix) with ESMTP id 9A8964FD9E; Tue, 25 Apr 2000 12:52:27 -0400 (EDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0.1) id JAA10315; Tue, 25 Apr 2000 09:52:26 -0700 (PDT) Message-ID: <3905CD4A.1C0AB01C@cup.hp.com> Date: Tue, 25 Apr 2000 09:52:26 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Satoshi - Ports Wraith - Asami Cc: Martin Blapp , freebsd-stable@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi - Ports Wraith - Asami wrote: [snip] > * -/a/tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory > * +/usr/tmp/sv001.tmp/setup.bin: error in loading shared libraries: libvos1GCC.so: cannot open shared object file: No such file or directory > > Oops, I'm an idiot, there wasn't a var/tmp inside /compat/linux and it > was trying the real (outside /compat/linux) /usr/tmp. Once I created > var/tmp, the message started saying "/compat/linux/usr/tmp/..." > (although it still dies with the same error). Set LD_LIBRARY_PATH=. before installing. HTH, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 10:13: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 37C2537BE04 for ; Tue, 25 Apr 2000 10:13:00 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e3PHg7a12378; Tue, 25 Apr 2000 10:42:07 -0700 (PDT) Date: Tue, 25 Apr 2000 10:42:07 -0700 From: Alfred Perlstein To: Leslie Jay Cc: stable@FreeBSD.ORG Subject: Re: Problem installing Domino for Linux (0x19E) Message-ID: <20000425104207.C9754@fw.wintelcom.net> References: <20000425152046.1233.qmail@nwcst285.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000425152046.1233.qmail@nwcst285.netaddress.usa.net>; from elljay@usa.net on Tue, Apr 25, 2000 at 11:20:44PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Leslie Jay [000425 08:53] wrote: > Greetings, > > Like a few people before me, I have run into problem installing > Domino for Linux 5.0.2c on a FreeBSD 4.0-stable. > > I have Linux emulation, and had installed linux-base 6.1 from > the ports collection. ... > The following is the last portion of the kdump output: > I also attached a gzip-ed ktrace. Hoped I provided all the > info needed ( and written to the right forum ). > Thanks in advance for any help. I think It's getting mad at us not supporting some Linux feature of getrusage, perhaps you can decode the arguments and tell us what's being passed to getrusage() so that we can figure out how to implement it. thanks, -Alfred > ------------- > 25934 http CALL #91(0x28ec9000,0x2000) > 25934 http RET #91 0 > 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x7b0,0) > 25934 http RET getrusage -1 errno -22 Unknown error: -22 > 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x3b0,0) > 25934 http RET getrusage -1 errno -22 Unknown error: -22 > 25934 http CALL old.sigvec(0x1,0xbfbff1ec) > 25934 http RET old.sigvec 0 > 25934 http CALL dup2(0xbfbff250) > 25934 http RET dup2 686592000/0x28ec9000 > 25934 http CALL ioctl(0x1,0x5401 ,0xbfbff1e8) > 25934 http RET ioctl 0 > 25934 http CALL write(0x1,0x28ec9000,0x2) > 25934 http GIO fd 1 wrote 2 bytes > "\r > " > 25934 http RET write 2 > 25934 http CALL write(0x1,0x28ec9000,0x1c) > 25934 http GIO fd 1 wrote 28 bytes > "Lotus Notes: error 0x19E\r > \r > " > 25934 http RET write 28/0x1c > 25934 http CALL #91(0x28ec9000,0x2000) > 25934 http RET #91 0 > 25934 http CALL exit(0xffffffff) > ------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 10:31:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server1.huntsvilleal.com (server1.huntsvilleal.com [63.147.8.7]) by hub.freebsd.org (Postfix) with ESMTP id 97D4337BDC5 for ; Tue, 25 Apr 2000 10:31:32 -0700 (PDT) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [63.147.8.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id MAA29640 for ; Tue, 25 Apr 2000 12:09:48 -0400 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id LAA25380 for ; Tue, 25 Apr 2000 11:34:13 -0500 (CDT) (envelope-from kris@hiwaay.net) Date: Tue, 25 Apr 2000 11:34:08 -0500 (CDT) From: Kris Kirby To: stable@freebsd.org Subject: Process accounting and logging: What turns the files over? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pardon me if I am doing that "stupid user" thing again, but I must ask: What program is responsible for turning over /var/account/acct? I have these files building up and no clear indication as to how they roll over. I'd like to automagically compress them, but it appears that newsyslog is not the tool for this. Yes, I know I could do it with a simple script, and I'm just as likely to do that. ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 10:40:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 23DC037BDA9 for ; Tue, 25 Apr 2000 10:39:52 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.10.0/8.10.0) id e3PHdpn03781 for freebsd-stable@freebsd.org; Tue, 25 Apr 2000 10:39:51 -0700 (PDT) Date: Tue, 25 Apr 2000 10:39:51 -0700 (PDT) From: David Wolfskill Message-Id: <200004251739.e3PHdpn03781@pau-amma.whistle.com> To: freebsd-stable@freebsd.org Subject: Don't know how to make ... obj/ ... /src/usr/include/sys/param.h Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK; I'm fairly confident that I've managed to do something fairly silly or stupid... but I'm not finding it, and would appreciate a pointer. I managed to resurrect an NEC 6030X laptop, and had installed 4.0-R on it. Over the previous week, I figured that since I finally had a system that I actually expected to need to re-boot anyway, this would be a reasonable vehicle for trying to track 4.x-STABLE. Accordingly, I started with a likely-looking supfile, and started trying out CVSup (which appeared to work just fine). Following that, over in /usr/src, I did a "make world" which (eventually) finished OK (the beastie only has 32 MB memory & runs at 133 MHz). And I re-built the kernel, and started learning how to use mergemaster, all of which seemed to go OK. The system subsequently identified itself (via "uname") as running FreeBSD 4.0-STABLE, which seemed like a fair amount of progress. A couple of days later (as time permitted), I ran CVSup again, which updated a handful of files, and I repeated the performance: one of my goals is to gain familiarity with the process.... Then, over the last weekend, I tried it again... and tripped. The CVSup ran as before, but the "make world" (well, I switched to splitting that into "make buildworld" and "make installworld", since that laptop is at home and I sometimes do things to it while I'm at home and sometimes while I'm at work) fails rather early in the process: dhw-laptop[19] sudo make buildworld Password: -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/home/david/build/src/i386 mkdir -p /usr/obj/home/david/build/src/i386/usr/bin mkdir -p /usr/obj/home/david/build/src/i386/usr/lib/compat/aout mkdir -p /usr/obj/home/david/build/src/i386/usr/games mkdir -p /usr/obj/home/david/build/src/i386/usr/libdata/ldscripts mkdir -p /usr/obj/home/david/build/src/i386/usr/libexec/elf mkdir -p /usr/obj/home/david/build/src/i386/usr/sbin mkdir -p /usr/obj/home/david/build/src/i386/usr/share/misc mkdir -p /usr/obj/home/david/build/src/i386/usr/include/arpa mkdir -p /usr/obj/home/david/build/src/i386/usr/include/g++/std mkdir -p /usr/obj/home/david/build/src/i386/usr/include/objc mkdir -p /usr/obj/home/david/build/src/i386/usr/include/protocols mkdir -p /usr/obj/home/david/build/src/i386/usr/include/readline mkdir -p /usr/obj/home/david/build/src/i386/usr/include/rpc mkdir -p /usr/obj/home/david/build/src/i386/usr/include/rpcsvc mkdir -p /usr/obj/home/david/build/src/i386/usr/include/openssl mkdir -p /usr/obj/home/david/build/src/i386/usr/include/security mkdir -p /usr/obj/home/david/build/src/i386/usr/include/ss ln -sf /home/david/build/src/sys /usr/obj/home/david/build/src/i386/sys -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- cd /home/david/build/src; MAKEOBJDIRPREFIX=/usr/obj/home/david/build/src/i386 DESTDIR=/usr/obj/home/david/build/src/i386 INSTALL="sh /home/david/build/src/tools/install.sh" MACHINE_ARCH=i386 TOOLS_PREFIX=/usr/obj/home/david/build/src/i386 PATH=/usr/obj/home/david/build/src/i386/usr/sbin:/usr/obj/home/david/build/src/i386/usr/bin:/usr/obj/home/david/build/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools cd /home/david/build/src/games/fortune/strfile; make obj; make depend; make all; make install /usr/obj/home/david/build/src/i386/home/david/build/src/games/fortune/strfile created for /home/david/build/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a -I/usr/obj/home/david/build/src/i386/usr/include /home/david/build/src/games/fortune/strfile/strfile.c cd /home/david/build/src/games/fortune/strfile; make _EXTRADEPEND echo strfile: /usr/obj/home/david/build/src/i386/usr/lib/libc.a >> .depend make: don't know how to make /usr/obj/home/david/build/src/i386/usr/include/sys/param.h. Stop *** Error code 2 Stop in /home/david/build/src. *** Error code 1 Stop in /home/david/build/src. *** Error code 1 Stop in /home/david/build/src. dhw-laptop[20] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 10:47:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41]) by hub.freebsd.org (Postfix) with ESMTP id 6F41737B737 for ; Tue, 25 Apr 2000 10:47:27 -0700 (PDT) (envelope-from sasha@frolkin.demon.co.uk) Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1) id 12k9Qt-0000IY-00; Tue, 25 Apr 2000 18:47:35 +0100 Date: Tue, 25 Apr 2000 18:47:35 +0100 From: Alexander Frolkin To: Brian Somers Cc: stable@freebsd.org Subject: Re: portmap strangeness Message-ID: <20000425184734.A940@gamma> Reply-To: Alexander Frolkin References: <200004232110.WAA00681@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200004232110.WAA00681@hak.lan.Awfulhak.org>; from Brian Somers on Sun, Apr 23, 2000 at 10:10:22PM +0100 X-Operating-System: Linux 2.2.14 X-GPG-Key-Fingerprint: 6C84 3EB2 550E E581 62FA BB0C D510 B042 FD5C E7A7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 23, 2000 at 10:10:22PM +0100, Brian Somers wrote: > > On Sat, Apr 22, 2000 at 10:06:21AM +0100, Brian Somers wrote: > > > In /usr/src/usr.sbin/portmap, can you > > > > > > cc -o from_local -DTEST from_local.c > > > ./from_local > > > > > > and see how this compares to the output of ifconfig -a ? If this > > > finds all the interface addresses after lp0, then there *should* be > > > no problems. > > > > I've done that, and I get the addresses of all the interfaces which are 'up' > > listed correctly, however portmap only works when lp0 is also up. (This is > > the first interface in ifconfig -a, if that makes a difference). from_local > > shows the address of lp0, when it is up, as 0.0.0.0, which is correct since > > the address isn't set because I'm not using the interface at the moment. > > Well, I think the next step(s) are to ensure that portmap is > LISTENing to *.111 and then to use tcpdump to see what address the > nfs stuff is coming from - without lp0 being IFF_UP. With lp0 down, netstat shows that portmap is listening on *.111, but there is no RPC traffic in tcpdump -ilo0 when I run mountd and nfsd. With lp0 up, netstat shows the same, but there is some sunrpc traffic on lo0, when the services register. Also, I've noticed that if the system boots with lp0 down I can bring lp0 up and then down again, and the services will register (this is without restarting portmap). Thanks, Alexander > It sounds like portmap is failing to identify the address as being > local.... > > > Thanks, > > > > Alexander. > > Cheers. > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 11:21:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id AD47137B810 for ; Tue, 25 Apr 2000 11:21:42 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA26855 for stable@FreeBSD.org; Tue, 25 Apr 2000 11:21:31 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200004251821.LAA26855@freeway.dcfinc.com> Subject: Re: Process accounting and logging: What turns the files over? In-Reply-To: from Kris Kirby at "Apr 25, 0 11:34:08 am" To: kris@hiwaay.net (Kris Kirby) Date: Tue, 25 Apr 2000 11:19:37 -0700 (MST) Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Kris Kirby wrote: > Pardon me if I am doing that "stupid user" thing again, but I must > ask: What program is responsible for turning over /var/account/acct? > I have these files building up and no clear indication as to how they > roll over. I'd like to automagically compress them, but it appears > that newsyslog is not the tool for this. Yes, I know I could do it > with a simple script, and I'm just as likely to do that. /usr/sbin/sa Check "man 8 sa". -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 11:36:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id C923D37B607 for ; Tue, 25 Apr 2000 11:36:21 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA26960; Tue, 25 Apr 2000 11:35:47 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200004251835.LAA26960@freeway.dcfinc.com> Subject: Re: Process accounting and logging: What turns the files over? In-Reply-To: <200004251821.LAA26855@freeway.dcfinc.com> from "Chad R. Larson" at "Apr 25, 0 11:19:37 am" To: kris@hiway.net Date: Tue, 25 Apr 2000 11:35:46 -0700 (MST) Cc: stable@FreeBSD.org Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Chad R. Larson wrote: > > Check "man 8 sa". > Sorry, I should have added that my /etc/daily contains: if [ -f /var/account/acct ] ; then echo "" echo "Gathering accounting statistics:" cd /var/account if [ -f acct.2 ] ; then mv -f acct.2 acct.3 ; fi if [ -f acct.1 ] ; then mv -f acct.1 acct.2 ; fi if [ -f acct.0 ] ; then mv -f acct.0 acct.1 ; fi cp -pf acct acct.0 sa -s > /dev/null fi -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 12:33: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id B1AAC37B732 for ; Tue, 25 Apr 2000 12:32:58 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id UAA21206; Tue, 25 Apr 2000 20:32:53 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA31667; Tue, 25 Apr 2000 20:32:48 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004251932.UAA31667@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Frolkin Cc: Brian Somers , stable@freebsd.org, brian@hak.lan.Awfulhak.org Subject: Re: portmap strangeness In-Reply-To: Message from Alexander Frolkin of "Tue, 25 Apr 2000 18:47:35 BST." <20000425184734.A940@gamma> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Apr 2000 20:32:48 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Apr 23, 2000 at 10:10:22PM +0100, Brian Somers wrote: > > > On Sat, Apr 22, 2000 at 10:06:21AM +0100, Brian Somers wrote: > > > > In /usr/src/usr.sbin/portmap, can you > > > > > > > > cc -o from_local -DTEST from_local.c > > > > ./from_local > > > > > > > > and see how this compares to the output of ifconfig -a ? If this > > > > finds all the interface addresses after lp0, then there *should* be > > > > no problems. > > > > > > I've done that, and I get the addresses of all the interfaces which are 'up' > > > listed correctly, however portmap only works when lp0 is also up. (This is > > > the first interface in ifconfig -a, if that makes a difference). from_local > > > shows the address of lp0, when it is up, as 0.0.0.0, which is correct since > > > the address isn't set because I'm not using the interface at the moment. > > > > Well, I think the next step(s) are to ensure that portmap is > > LISTENing to *.111 and then to use tcpdump to see what address the > > nfs stuff is coming from - without lp0 being IFF_UP. > > With lp0 down, netstat shows that portmap is listening on *.111, but there > is no RPC traffic in tcpdump -ilo0 when I run mountd and nfsd. > > With lp0 up, netstat shows the same, but there is some sunrpc traffic on > lo0, when the services register. > > > Also, I've noticed that if the system boots with lp0 down I can bring lp0 up > and then down again, and the services will register (this is without > restarting portmap). So it looks like a problem with the rpc library ? Have you got ``::1 localhost'' in /etc/hosts ? If so, try removing it to see if the problem is that portmap isn't ip6 aware. > Thanks, > > Alexander > > > It sounds like portmap is failing to identify the address as being > > local.... > > > > > Thanks, > > > > > > Alexander. > > > > Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 15:32:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41]) by hub.freebsd.org (Postfix) with ESMTP id 55B2537BE35 for ; Tue, 25 Apr 2000 15:32:25 -0700 (PDT) (envelope-from sasha@frolkin.demon.co.uk) Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1) id 12kDtW-0001Wc-00; Tue, 25 Apr 2000 23:33:26 +0100 Date: Tue, 25 Apr 2000 23:33:26 +0100 From: Alexander Frolkin To: Brian Somers Cc: stable@freebsd.org Subject: Re: portmap strangeness Message-ID: <20000425233326.A5755@gamma> Reply-To: Alexander Frolkin References: <200004251932.UAA31667@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200004251932.UAA31667@hak.lan.Awfulhak.org>; from Brian Somers on Tue, Apr 25, 2000 at 08:32:48PM +0100 X-Operating-System: Linux 2.2.14 X-GPG-Key-Fingerprint: 6C84 3EB2 550E E581 62FA BB0C D510 B042 FD5C E7A7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 25, 2000 at 08:32:48PM +0100, Brian Somers wrote: > > On Sun, Apr 23, 2000 at 10:10:22PM +0100, Brian Somers wrote: > > > > On Sat, Apr 22, 2000 at 10:06:21AM +0100, Brian Somers wrote: > > > > > In /usr/src/usr.sbin/portmap, can you > > > > > > > > > > cc -o from_local -DTEST from_local.c > > > > > ./from_local > > > > > > > > > > and see how this compares to the output of ifconfig -a ? If this > > > > > finds all the interface addresses after lp0, then there *should* be > > > > > no problems. > > > > > > > > I've done that, and I get the addresses of all the interfaces which are 'up' > > > > listed correctly, however portmap only works when lp0 is also up. (This is > > > > the first interface in ifconfig -a, if that makes a difference). from_local > > > > shows the address of lp0, when it is up, as 0.0.0.0, which is correct since > > > > the address isn't set because I'm not using the interface at the moment. > > > > > > Well, I think the next step(s) are to ensure that portmap is > > > LISTENing to *.111 and then to use tcpdump to see what address the > > > nfs stuff is coming from - without lp0 being IFF_UP. > > > > With lp0 down, netstat shows that portmap is listening on *.111, but there > > is no RPC traffic in tcpdump -ilo0 when I run mountd and nfsd. > > > > With lp0 up, netstat shows the same, but there is some sunrpc traffic on > > lo0, when the services register. > > > > > > Also, I've noticed that if the system boots with lp0 down I can bring lp0 up > > and then down again, and the services will register (this is without > > restarting portmap). > > So it looks like a problem with the rpc library ? Have you got ``::1 > localhost'' in /etc/hosts ? If so, try removing it to see if the > problem is that portmap isn't ip6 aware. No, I only have the ip4 address. I'll see if the problem goes away when I next make world. For now, I can add ifconfig_lp0="up" to my rc.conf, and it will work. Thanks, Alexander. > > Thanks, > > > > Alexander > > > > > It sounds like portmap is failing to identify the address as being > > > local.... > > > > > > > Thanks, > > > > > > > > Alexander. > > > > > > Cheers. > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 15:43:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id EF15837BE77 for ; Tue, 25 Apr 2000 15:43:47 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA24908; Tue, 25 Apr 2000 17:43:25 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-107.max1.wa.cyberlynk.net(207.227.118.107) by peak.mountin.net via smap (V1.3) id sma024904; Tue Apr 25 17:43:22 2000 Message-Id: <4.3.2.20000425164428.02347810@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Tue, 25 Apr 2000 17:40:53 -0500 To: John Polstra From: "Jeffrey J. Mountin" Subject: Re: CVSup core dumping Cc: stable@FreeBSD.ORG In-Reply-To: <200004231958.MAA24527@vashon.polstra.com> References: <4.3.2.20000422140024.0235c610@mixcom.com> <4.3.2.20000422140024.0235c610@mixcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:58 PM 4/23/00 -0700, John Polstra wrote: >I haven't seen any other reports of this problem. I'm not sure I >follow all the intricacies of your supfile modifications. If you >can narrow it down to one collection that is definitely tied to the >problem, I might be able to help track it down. Illegal instruction >is a pretty strange error to have. Aside from HW or kernel problems, >the only semi-likely explanation for that would be an overflowed >thread stack. Rebuilt 4.0S as of Monday morning and will try duplicating the problem. Since it choked on the collections I added, the first being audio, which took several tries to get through. I'll blow away the additions and try again starting from the 4.0R tarball. >These correspond exactly with the cvsup-bin and cvsupd-bin ports, so >if you're using those ports you will be able to use the unstripped >binaries with your existing core dumps to get a stack trace. Grabbing it now. Thanks! Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 18:25: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from nw171.netaddress.usa.net (nw171.netaddress.usa.net [204.68.24.71]) by hub.freebsd.org (Postfix) with SMTP id CD82637B797 for ; Tue, 25 Apr 2000 18:24:58 -0700 (PDT) (envelope-from elljay@usa.net) Received: (qmail 23641 invoked by uid 60001); 26 Apr 2000 01:24:54 -0000 Message-ID: <20000426012454.23640.qmail@nw171.netaddress.usa.net> Received: from 204.68.24.71 by nw171 for [165.21.83.140] via web-mailer(M3.4.0.33) on Wed Apr 26 01:24:54 GMT 2000 Date: 26 Apr 00 09:24:54 SGT From: Leslie Jay To: Alfred Perlstein , Leslie Jay Subject: Re: [Re: Problem installing Domino for Linux (0x19E)] Cc: stable@FreeBSD.ORG X-Mailer: USANET web-mailer (M3.4.0.33) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Okay, good to know I'm on the right track now. Disappointed to confirm my colleagues' suggestion that there is something wrong with FreeBSD, ( actually, its the linux emulation, but I'll still suffer some heat for insisting on using FBSD over RedHat ) So, how do I proceed?? I'm not familiar with what you mentioned, "decoding the arguments to find out what is passed. Where can I read up on this. Regards, /LJ Alfred Perlstein wrote: > * Leslie Jay [000425 08:53] wrote: > > Greetings, > > > > Like a few people before me, I have run into problem installing > > Domino for Linux 5.0.2c on a FreeBSD 4.0-stable. > > > > I have Linux emulation, and had installed linux-base 6.1 from > > the ports collection. > ... > > The following is the last portion of the kdump output: > > I also attached a gzip-ed ktrace. Hoped I provided all the > > info needed ( and written to the right forum ). > > Thanks in advance for any help. > > I think It's getting mad at us not supporting some Linux > feature of getrusage, perhaps you can decode the arguments > and tell us what's being passed to getrusage() so that > we can figure out how to implement it. > > thanks, > -Alfred > > > ------------- > > 25934 http CALL #91(0x28ec9000,0x2000) > > 25934 http RET #91 0 > > 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x7b0,0) > > 25934 http RET getrusage -1 errno -22 Unknown error: -22 > > 25934 http CALL getrusage(0x17,0xf8b0d800,0x4458ac,0x3b0,0) > > 25934 http RET getrusage -1 errno -22 Unknown error: -22 > > 25934 http CALL old.sigvec(0x1,0xbfbff1ec) > > 25934 http RET old.sigvec 0 > > 25934 http CALL dup2(0xbfbff250) > > 25934 http RET dup2 686592000/0x28ec9000 > > 25934 http CALL ioctl(0x1,0x5401 ,0xbfbff1e8) > > 25934 http RET ioctl 0 > > 25934 http CALL write(0x1,0x28ec9000,0x2) > > 25934 http GIO fd 1 wrote 2 bytes > > "\r > > " > > 25934 http RET write 2 > > 25934 http CALL write(0x1,0x28ec9000,0x1c) > > 25934 http GIO fd 1 wrote 28 bytes > > "Lotus Notes: error 0x19E\r > > \r > > " > > ------------- ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 23: 2: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id B59E337B543 for ; Tue, 25 Apr 2000 23:02:02 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA44453; Tue, 25 Apr 2000 23:01:47 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <3906864B.E6BBC0D5@gorean.org> Date: Tue, 25 Apr 2000 23:01:47 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0422 i386) X-Accept-Language: en MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: Doug White , Matthew Dillon , freebsd-stable@FreeBSD.ORG Subject: Legato for linux (was: Re: Linux Emulation Root (was: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday)) References: <200004251530.IAA07614@passer.osg.gov.bc.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert wrote: > Legato for Linux backs up /, it just cannot restore to it. FYI, there is a native FreeBSD legato client, but it does not have a GUI. Matt Jacob wrote it, and it's good stuff. He was kind enough to add a port for it just a little bit ago as well. Doug -- Excess on occasion is exhilarating. It prevents moderation from acquiring the deadening effect of a habit. -- W. Somerset Maugham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 23:18: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 4262137B834 for ; Tue, 25 Apr 2000 23:18:06 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA44670; Tue, 25 Apr 2000 23:18:02 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <39068A19.33C429EC@gorean.org> Date: Tue, 25 Apr 2000 23:18:01 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0422 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brooks Davis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: OpenSSH: DISPLAY not set References: <0vem7ui60w.fsf@cs.uni-magdeburg.de> <20000425111835.A2200@pir.net> <20000425095218.B19838@orion.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brooks Davis wrote: > > On Tue, Apr 25, 2000 at 11:18:35AM -0400, Peter Radcliffe wrote: > > X forwarding is off by default with openssh. > > > > See `man sshd` for the config entry to turn it on in (IIRC) > > /etc/ssh/sshd_config. > > I believe that is incorrect. Please check your facts before responding. There was a mixup at one point early in the openssh import process wherein the default for the server was to have X11 forwarding off. Unfortunately, this mistake has not been corrected yet, so the proper advice is to check the configuration files for both the client and the server to make sure the forwarding is allowed. Doug (whose word for today is, "be sure before you post") -- Excess on occasion is exhilarating. It prevents moderation from acquiring the deadening effect of a habit. -- W. Somerset Maugham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Apr 25 23:43:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 05ED337BB00 for ; Tue, 25 Apr 2000 23:43:20 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-15.ix.netcom.com [209.111.212.143]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id CAA22380; Wed, 26 Apr 2000 02:42:44 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id XAA03472; Tue, 25 Apr 2000 23:42:04 -0700 (PDT) To: Marcel Moolenaar Cc: Martin Blapp , freebsd-stable@FreeBSD.ORG, dillon@apollo.backplane.com Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday References: <3905CD4A.1C0AB01C@cup.hp.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 25 Apr 2000 23:41:59 -0700 In-Reply-To: Marcel Moolenaar's message of "Tue, 25 Apr 2000 09:52:26 -0700" Message-ID: Lines: 32 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Marcel Moolenaar * Set LD_LIBRARY_PATH=. before installing. Wonderful. I got the installation to work with that. Thanks! I had to change the "soffice" script a bit (since this is run straight from our shell, it's treated as a FreeBSD script) and it's running fine now on my 3.4-stable machine. I haven't tested it much but if someone wants to try, the (absolutely no warranty) patch is in: http://people.FreeBSD.org/~asami/linux-script-01.diff Satoshi ------- --- ./soffice.org Mon Feb 21 21:20:00 2000 +++ ./soffice Tue Apr 25 12:04:51 2000 @@ -17,12 +17,12 @@ # resolve installation directory sd_platform=`uname -s` case $sd_platform in - SCO_SV) test=/bin/test ;; + SCO_SV|FreeBSD) test=/bin/test ;; *) test=/usr/bin/test ;; esac sd_cwd="`pwd`" -if $test -L "$0" ; then +if $test -h "$0" ; then sd_basename=`basename $0` sd_script=`ls -l $0 | sed "s/.*${sd_basename} -> //g"` else To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 1:14:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-132.dsl.snfc21.pacbell.net [63.202.176.132]) by hub.freebsd.org (Postfix) with ESMTP id C7E4E37B5A2 for ; Wed, 26 Apr 2000 01:14:37 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA01521; Wed, 26 Apr 2000 01:22:06 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004260822.BAA01521@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: Tony Byrne , stable@FreeBSD.ORG Subject: Re: /usr/src/sys/modules/mlx In-reply-to: Your message of "Tue, 25 Apr 2000 09:32:37 EDT." <3.0.5.32.20000425093237.020411c0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Apr 2000 01:22:06 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Since I don't have a Mylex RAID controller and I only needed a 4.0 > >kernel in order to complete a source upgrade of 3.4 to 4.0, I > >commented out the mlx device line in my GENERIC kernel config file and > >the system happily compiled the kernel. > > Unfortunately for me, I need the mlx driver working :-) The problem seems > to be a reference to a variable that is not declared (disks_registered) in > two spots. I am not sure if they are meant to be removed, or that the > declarations are meant to be included. Either way, msmith@freebsd.org will > no doubt know what to do. Yeah. Read this list and test patches when I post them. I put the diff that got committed up for general review several days before it was committed, and received no feedback (not even a "can you wait"). I'm currently without a functional 4.x system to test on, but desperately wanted to get the log message fix back before the bug bites too many people. *sigh* Unfortunately, one line escaped me; I think that Bill Fumerola has already fixed this. Please folks - if you need this code working, keep an eye on the list so that I can catch your attention when I need some help. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 6:37:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 3646537B952 for ; Wed, 26 Apr 2000 06:37:17 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.10.0/8.10.0) id e3QDbFw06373 for freebsd-stable@FreeBSD.ORG; Wed, 26 Apr 2000 06:37:15 -0700 (PDT) Date: Wed, 26 Apr 2000 06:37:15 -0700 (PDT) From: David Wolfskill Message-Id: <200004261337.e3QDbFw06373@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: Don't know how to make ... obj/ ... /src/usr/include/sys/param.h In-Reply-To: <200004251739.e3PHdpn03781@pau-amma.whistle.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 25 Apr 2000 10:39:51 -0700 (PDT) >From: David Wolfskill >OK; I'm fairly confident that I've managed to do something fairly silly >or stupid... but I'm not finding it, and would appreciate a pointer. >... >Then, over the last weekend, I tried it again... and tripped. The CVSup >ran as before, but the "make world" (well, I switched to splitting that >into "make buildworld" and "make installworld", since that laptop is at >home and I sometimes do things to it while I'm at home and sometimes while >I'm at work) fails rather early in the process: >-------------------------------------------------------------- >>>> stage 1: bootstrap tools >-------------------------------------------------------------- >... >echo strfile: /usr/obj/home/david/build/src/i386/usr/lib/libc.a >> .depend >make: don't know how to make /usr/obj/home/david/build/src/i386/usr/include/sys/param.h. Stop >*** Error code 2 OK; I got it to work: seems that there were some (extraneous?) .depend files in my source tree; in particular, one of them was claiming that the above-mentioned strfile depended on stdlib.h. Issuing find /usr/src -name .depend -print identified the 5 or 6 that were there; I removed each of them, re-started the buildworld, and it finished successfully by the time I got up this morning. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 8: 9:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.surf24.de (mail.surf24.de [212.62.192.50]) by hub.freebsd.org (Postfix) with ESMTP id 418C937B5AC; Wed, 26 Apr 2000 08:09:39 -0700 (PDT) (envelope-from Rainer.Duffner@surf24.de) Received: from duffner.surf24.de (surf233.surf24.de [212.62.193.233]) by mail.surf24.de (8.9.3/8.9.3) with SMTP id RAA29721; Wed, 26 Apr 2000 17:09:42 +0200 Date: Wed, 26 Apr 2000 17:08:31 +0100 (MESZ) From: Rainer M Duffner Subject: mlx fails to build on make world.... To: msmith@freebsd.org Cc: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Organization: enigma, http://www-stud.fh-konstanz.de/~enigma X-Mailer: ANT RISCOS Marcel [ver 1.46] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_attach': /usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:273: `disks_registered' undeclared (first use in this function) When is it possible to get the world build again ? Why does it build this, anyway ? I don't have a Mylex-Adapter in my PC (though I wish I had that many disks that I needed/could use one...) cheers, Rainer -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |Rainer Duffner, E-Mail: duffner@fh-konstanz.de | | & Rainer.Duffner@surf24.de | |Fachhochschule Konstanz, Germany | |"What's a Network ?" - Bill Gates, early 1980s | | WWW:http://www-stud.fh-konstanz.de/~duffner | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 8:19:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id 8A31737BDC8 for ; Wed, 26 Apr 2000 08:19:24 -0700 (PDT) (envelope-from mike@sentex.ca) Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id LAA90992; Wed, 26 Apr 2000 11:19:21 -0400 (EDT) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id LAA87382; Wed, 26 Apr 2000 11:19:21 -0400 (EDT) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000426111544.00cbaa00@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 26 Apr 2000 11:15:44 -0400 To: Rainer M Duffner From: Mike Tancsa Subject: Re: mlx fails to build on make world.... Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:08 PM 4/26/00 +0100, Rainer M Duffner wrote: >Hi, > >/usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c: In function `mlxd_attach': >/usr/src/sys/modules/mlx/../../dev/mlx/mlx_disk.c:273: `disks_registered' undeclared (first use in this function) > >When is it possible to get the world build again ? >Why does it build this, anyway ? I don't have a Mylex-Adapter in my >PC (though I wish I had that many disks that I needed/could use one...) cvsup again, and the fix is there. The commit went in last night. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 8:45:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mindful.ttmedia.com (mindful.ttmedia.com [209.186.7.23]) by hub.freebsd.org (Postfix) with SMTP id 84CD337B970 for ; Wed, 26 Apr 2000 08:45:19 -0700 (PDT) (envelope-from ben@freezone.com) Received: (qmail 7122 invoked from network); 26 Apr 2000 15:44:54 -0000 Received: from mindless.ttmedia.com (HELO freezone.com) (209.186.7.24) by 192.168.2.7 with SMTP; 26 Apr 2000 15:44:54 -0000 Message-ID: <39070F19.38005ADF@freezone.com> Date: Wed, 26 Apr 2000 10:45:29 -0500 From: Ben Schmitz Organization: Freezone Network X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en,zh,zh-CN,zh-TW MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: subscribe Content-Type: multipart/mixed; boundary="------------B16CB2FF869D146EA6B7B91E" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------B16CB2FF869D146EA6B7B91E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit subscribe neb@mindless.com -- ben schmitz webmaster The FreeZone Network ben@freezone.com v.312.705.3817 f.312.573.3810 http://freezone.com "To understand is to perceive patterns." - Isaiah Berlin --------------B16CB2FF869D146EA6B7B91E Content-Type: text/x-vcard; charset=us-ascii; name="ben.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ben Schmitz Content-Disposition: attachment; filename="ben.vcf" begin:vcard n:Schmitz;Ben tel;fax:312-597-3810 tel;home:Yeah Right!! 8^) tel;work:312-705-3817 x-mozilla-html:TRUE url:http://www.freezone.com org:FreeZone Network version:2.1 email;internet:ben@ttmedia.com title:WebMaster adr;quoted-printable:;;730 North Franklin St.=0D=0ASuite 706;Chicago;Illinois;60610;USA fn:Ben Schmitz end:vcard --------------B16CB2FF869D146EA6B7B91E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 9:43:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id B329537BE56 for ; Wed, 26 Apr 2000 09:43:16 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id JAA22630; Wed, 26 Apr 2000 09:43:15 -0700 (PDT) Date: Wed, 26 Apr 2000 09:43:15 -0700 From: Brooks Davis To: Doug Barton Cc: freebsd-stable@FreeBSD.ORG Subject: Re: OpenSSH: DISPLAY not set Message-ID: <20000426094315.A11043@orion.ac.hmc.edu> References: <0vem7ui60w.fsf@cs.uni-magdeburg.de> <20000425111835.A2200@pir.net> <20000425095218.B19838@orion.ac.hmc.edu> <39068A19.33C429EC@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <39068A19.33C429EC@gorean.org>; from Doug@gorean.org on Tue, Apr 25, 2000 at 11:18:01PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 25, 2000 at 11:18:01PM -0700, Doug Barton wrote: > Please check your facts before responding. There was a mixup at one > point early in the openssh import process wherein the default for the > server was to have X11 forwarding off. Unfortunately, this mistake has > not been corrected yet, so the proper advice is to check the > configuration files for both the client and the server to make sure the > forwarding is allowed. Oops, my bad. I assumed that since there were no objections and it was a one line change that it has been done. I shouldn't have done that. I've submitted a PR. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 11:24:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from physics.angelo.edu (physics.angelo.edu [204.66.18.230]) by hub.freebsd.org (Postfix) with ESMTP id 9F4D437B5A2 for ; Wed, 26 Apr 2000 11:24:36 -0700 (PDT) (envelope-from awallace@physics.angelo.edu) Received: (from root@localhost) by physics.angelo.edu (8.9.3/8.9.3) id NAA16776 for freebsd-stable@FreeBSD.org; Wed, 26 Apr 2000 13:24:33 -0500 (CDT) (envelope-from awallace) Date: Wed, 26 Apr 2000 13:24:33 -0500 (CDT) From: Andy Wallace Message-Id: <200004261824.NAA16776@physics.angelo.edu> To: freebsd-stable@FreeBSD.org Subject: subscribe Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 11:25:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.campbell-mithun.com (Mercury.campbell-mithun.com [192.159.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 82A0B37B9B7 for ; Wed, 26 Apr 2000 11:25:16 -0700 (PDT) (envelope-from swb@accord.grasslake.net) Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by mercury.campbell-mithun.com (8.9.1a/8.9.1) with ESMTP id NAA31717 for ; Wed, 26 Apr 2000 13:25:14 -0500 Received: from localhost (swb@localhost) by accord.grasslake.net (8.9.3/8.9.3) with ESMTP id NAA13453 for ; Wed, 26 Apr 2000 13:25:18 -0500 (CDT) (envelope-from swb@accord.grasslake.net) Date: Wed, 26 Apr 2000 13:25:18 -0500 (CDT) From: Shawn Barnhart To: freebsd-stable@freebsd.org Subject: Samba updates into STABLE? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How long does it generally take for updates to Samba to make it into the stable tree? I'm curious if RELENG_3 will have 2.0.7 anytime soon -- it fixes some Win2k annoyances that are present in 2.0.6. The fixes are really to annoyances, its not totally broken. I'm more curious how long a new port like samba does take to make it into the RELEASE branch. (If this is question for ports instead of Stable, my apologies.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 11:33:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id C934F37B9B7 for ; Wed, 26 Apr 2000 11:33:22 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id LAA05671; Wed, 26 Apr 2000 11:32:44 -0700 (PDT) Date: Wed, 26 Apr 2000 11:32:43 -0700 From: Brooks Davis To: Shawn Barnhart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Samba updates into STABLE? Message-ID: <20000426113243.A4673@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from swb@grasslake.net on Wed, Apr 26, 2000 at 01:25:18PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 26, 2000 at 01:25:18PM -0500, Shawn Barnhart wrote: > How long does it generally take for updates to Samba to make it into the > stable tree? > > I'm curious if RELENG_3 will have 2.0.7 anytime soon -- it fixes some Win2k > annoyances that are present in 2.0.6. > > The fixes are really to annoyances, its not totally broken. I'm more > curious how long a new port like samba does take to make it into the RELEASE > branch. > > (If this is question for ports instead of Stable, my apologies.) This was a ports question. Ports are in no way tyed to stable. We now tag ports for releases, but ports are not branched. You'll want to update your ports tree (or part of it) and get the new samba that way (assuming the port has been updated). -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 11:49:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 47D4B37B5AC; Wed, 26 Apr 2000 11:49:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA67719; Wed, 26 Apr 2000 11:49:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 26 Apr 2000 11:49:22 -0700 (PDT) From: Kris Kennaway To: Shawn Barnhart Cc: freebsd-stable@freebsd.org Subject: Re: Samba updates into STABLE? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000, Shawn Barnhart wrote: > How long does it generally take for updates to Samba to make it into the > stable tree? That's up to the maintainer. > I'm curious if RELENG_3 will have 2.0.7 anytime soon -- it fixes some Win2k > annoyances that are present in 2.0.6. As another respondant mentioned, all versions of FreeBSD share the same ports tree. But the samba port hasn't yet been updated to 2.0.7, you'll have to talk to the maintainer (hosokawa@jp.FreeBSD.org) to see what plans there are for the update. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 16:57:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id E988C37BA73; Wed, 26 Apr 2000 16:57:07 -0700 (PDT) (envelope-from saper@tricord.system.pl) Received: (from saper@localhost) by tricord.system.pl (SYSTEM Internet) id BAA25575; Thu, 27 Apr 2000 01:57:30 +0200 (MET DST) Date: Thu, 27 Apr 2000 01:57:30 +0200 From: Marcin Cieslak To: stable@FreeBSD.ORG Cc: asami@FreeBSD.ORG Subject: Re: distfiles no longer on 4.0 CDs Message-ID: <20000427015730.B25261@tricord.system.pl> Mail-Followup-To: stable@FreeBSD.ORG, asami@FreeBSD.org References: <200004182028.QAA36438@blackhelicopters.org> <7630.956090286@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <7630.956090286@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Tue, Apr 18, 2000 at 01:38:06PM -0700 Organization: SYSTEM Internet Provider - http://www.system.pl/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard (jkh@zippy.cdrom.com) napisa³(a): > I could certainly make a super-set INDEX file with some sort of CD# > field (I'd have to extend or munge the current INDEX format) available > on each of the CDs, sure. That's a good idea. There is a nice way to handle this in IBM's AIX ... it has already 3 CD of a base system (all system is split into "packages"). The install utility, installp (much better than all rpm's) takes care of informing the user which CD to insert. The funny thing is, that installp accepts "/dev/cd0" - path to CD-ROM device - as a "source" path... i.e. the user does not have to mount the CD to get the packages - installp (un)mounts it in his favourite mount point on an as-needed basis. (I guess one would even add an interface to support changers, why not). In my opinion, we should work on pkg_add to support such a feature (a "-C device" option)... and of course bsd.port.mk could be updated to handle this. But there is always a tradeoff between end-user convenience (Please insert CD #blahblah) and the UNIX traditional mechanisms, like setting just ${DISTDIR}. Perhaps we end up in adding ${CDROMDIR} and some simple CD changing handler. One thing I would like personally to avoid is a Solaris-like vold (volume manager) thing. This is the first process which gets killed on my machines. -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 17:42:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 4143837B9FB for ; Wed, 26 Apr 2000 17:42:13 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA00421 for stable@FreeBSD.org; Wed, 26 Apr 2000 17:42:11 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200004270042.RAA00421@freeway.dcfinc.com> Subject: sendmail missing? To: stable@FreeBSD.org Date: Wed, 26 Apr 2000 17:42:11 -0700 (MST) Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may have already been discussed on some other list, but I'm surprised to find sendmail has gone missing from the ports collection. Why is this? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 17:59:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from luna.cdrom.com (luna.cdrom.com [204.216.28.135]) by hub.freebsd.org (Postfix) with ESMTP id D4ED637B677 for ; Wed, 26 Apr 2000 17:59:28 -0700 (PDT) (envelope-from jim@luna.cdrom.com) Received: by luna.cdrom.com (Postfix, from userid 1000) id 8184331E6; Wed, 26 Apr 2000 17:59:28 -0700 (PDT) Date: Wed, 26 Apr 2000 17:59:28 -0700 From: Jim Mock To: "Chad R. Larson" Cc: stable@FreeBSD.ORG Subject: Re: sendmail missing? Message-ID: <20000426175928.C78347@luna.cdrom.com> Reply-To: jim@luna.cdrom.com References: <200004270042.RAA00421@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <200004270042.RAA00421@freeway.dcfinc.com>; from chad@DCFinc.com on Wed, Apr 26, 2000 at 05:42:11PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000 at 17:42:11 -0700, Chad R. Larson wrote: > This may have already been discussed on some other list, but I'm > surprised to find sendmail has gone missing from the ports > collection. Sendmail isn't in the ports collection, it's in the base system. - jim -- - jim mock - walnut creek cdrom/freebsd test labs - jim@luna.cdrom.com - - phone: 1.925.691.2800 x.3814 - fax: 1.925.674.0821 - jim@FreeBSD.org - - editor - The FreeBSDzine - www.freebsdzine.org - jim@freebsdzine.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 18:19:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id DADC337B69F for ; Wed, 26 Apr 2000 18:19:20 -0700 (PDT) (envelope-from chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au (8.9.3/8.9.3) with ESMTP id LAA29156 for ; Thu, 27 Apr 2000 11:19:14 +1000 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.0.2.R) for ; Thu, 27 Apr 2000 11:18:44 +1000 Reply-To: From: "Chris Knight" To: Cc: Subject: RE: sendmail missing? Date: Thu, 27 Apr 2000 11:18:41 +1000 Message-ID: <002c01bfafe6$87c47000$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal In-Reply-To: <20000426175928.C78347@luna.cdrom.com> X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-Return-Path: chris@aims.com.au X-MDRcpt-To: jim@luna.cdrom.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, So? BIND is in the ports collection and in the base system. Admittedly, BIND was added so people could use v8 when v4 was only in the base system, and has been maintained due to security issues with BIND. It should be the same with sendmail. However, sendmail does build cleanly for FreeBSD from the source without mods required. This does require that NO_SENDMAIL should be set to true in /etc/make.conf to avoid clobbering the newer version of sendmail if performing a make world. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Jim Mock > Sent: Thursday, 27 April 2000 10:59 > To: Chad R. Larson > Cc: stable@FreeBSD.ORG > Subject: Re: sendmail missing? > > [snip] > > Sendmail isn't in the ports collection, it's in the base system. > > - jim > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 18:38:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 8EEDF37BA5C for ; Wed, 26 Apr 2000 18:38:07 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA00612; Wed, 26 Apr 2000 18:38:03 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200004270138.SAA00612@freeway.dcfinc.com> Subject: Re: sendmail missing? In-Reply-To: <20000426175928.C78347@luna.cdrom.com> from Jim Mock at "Apr 26, 0 05:59:28 pm" To: jim@luna.cdrom.com Date: Wed, 26 Apr 2000 18:38:02 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Jim Mock wrote: > On Wed, 26 Apr 2000 at 17:42:11 -0700, Chad R. Larson wrote: > > This may have already been discussed on some other list, but I'm > > surprised to find sendmail has gone missing from the ports > > collection. > > Sendmail isn't in the ports collection, it's in the base system. Yes, but in the past, you could set NO_SENDMAIL in /etc/make.conf so it wouldn't be built as part of the base system, and then build and install one from the ports. That generally got you the latest-n-greatest version. Or, allowed you to install a down-rev'd version if needed for compatibility on your network. And the one in the ports collection has gone missing since I last Or, And perhaps I've been hallucinating again and it never was a port. But if so, why isn't it? We've got ports for things like Adobe Acrobat, which only fetch and install a binary. We surely could fetch and build sendmail from Sendmail.org. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 19:35:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from luna.cdrom.com (dialup-63.208.128.91.SanFrancisco1.Level3.net [63.208.128.91]) by hub.freebsd.org (Postfix) with ESMTP id 34CB437BD43 for ; Wed, 26 Apr 2000 19:35:17 -0700 (PDT) (envelope-from jim@luna.cdrom.com) Received: by luna.cdrom.com (Postfix, from userid 1000) id 99CC431DC; Wed, 26 Apr 2000 19:35:14 -0700 (PDT) Date: Wed, 26 Apr 2000 19:35:14 -0700 From: Jim Mock To: "Chad R. Larson" Cc: stable@FreeBSD.ORG Subject: Re: sendmail missing? Message-ID: <20000426193514.A474@luna.cdrom.com> Reply-To: jim@luna.cdrom.com References: <20000426175928.C78347@luna.cdrom.com> <200004270138.SAA00612@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <200004270138.SAA00612@freeway.dcfinc.com>; from chad@DCFinc.com on Wed, Apr 26, 2000 at 06:38:02PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000 at 18:38:02 -0700, Chad R. Larson wrote: > As I recall, Jim Mock wrote: > > On Wed, 26 Apr 2000 at 17:42:11 -0700, Chad R. Larson wrote: > > > This may have already been discussed on some other list, but I'm > > > surprised to find sendmail has gone missing from the ports > > > collection. > > > > Sendmail isn't in the ports collection, it's in the base system. > > Yes, but in the past, you could set NO_SENDMAIL in /etc/make.conf so > it wouldn't be built as part of the base system, and then build and > install one from the ports. That generally got you the > latest-n-greatest version. Or, allowed you to install a down-rev'd > version if needed for compatibility on your network. Er, the reason NO_SENDMAIL exists is so if you're using postfix or qmail (which both use a binary called 'sendmail') they don't get overwritten with the real sendmail app. It also allows you to install a new version from source and not overwrite it when you make world. > And the one in the ports collection has gone missing since I last Or, > And perhaps I've been hallucinating again and it never was a port. You're hallucinating again :-) There hasn't ever been a sendmail port to my knowledge.. and the CVS repository seems to agree with me.. [root@dionysus:/usr/ports/mail]# cvs log sendmail cvs log: nothing known about sendmail [root@dionysus:/usr/ports/mail]# That was run on a ports tree updated (via CVS, not CVSup) about 5 minutes before sending this message. > But if so, why isn't it? We've got ports for things like Adobe > Acrobat, which only fetch and install a binary. We surely could fetch > and build sendmail from Sendmail.org. There's no real reason to have the same version of sendmail available in the base system as in the ports tree. I do think, however, that if there are beta versions of sendmail available, a port of it is reasonable for the simple fact that the source tree has the latest 'stable' version of it even though some people would want newer betas. Then again, there's no reason why you can't compile sendmail from source since it works just fine ;-) - jim -- - jim mock - walnut creek cdrom/freebsd test labs - jim@luna.cdrom.com - - phone: 1.925.691.2800 x.3814 - fax: 1.925.674.0821 - jim@FreeBSD.org - - editor - The FreeBSDzine - www.freebsdzine.org - jim@freebsdzine.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 19:37:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id DDADD37B57B for ; Wed, 26 Apr 2000 19:37:49 -0700 (PDT) (envelope-from will@blackdawn.com) Received: from argon.blackdawn.com (04-128.dial.008.popsite.net [209.69.197.128]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id TAA47200; Wed, 26 Apr 2000 19:37:33 -0700 (PDT) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 9EF1C1919; Wed, 26 Apr 2000 22:37:13 -0400 (EDT) Date: Wed, 26 Apr 2000 22:37:13 -0400 From: Will Andrews To: "Chad R. Larson" Cc: jim@luna.cdrom.com, stable@FreeBSD.ORG Subject: Re: sendmail missing? Message-ID: <20000426223713.C1070@argon.blackdawn.com> References: <20000426175928.C78347@luna.cdrom.com> <200004270138.SAA00612@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004270138.SAA00612@freeway.dcfinc.com>; from chad@DCFinc.com on Wed, Apr 26, 2000 at 06:38:02PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 26, 2000 at 06:38:02PM -0700, Chad R. Larson wrote: > Yes, but in the past, you could set NO_SENDMAIL in /etc/make.conf so > it wouldn't be built as part of the base system, and then build and > install one from the ports. That generally got you the > latest-n-greatest version. Or, allowed you to install a down-rev'd > version if needed for compatibility on your network. We've never had sendmail in ports. (00-04-26 22:34:37) [will@shadow ~]% cd /home/ncvs/ports/mail/sendmail cd: no such file or directory: /home/ncvs/ports/mail/sendmail That should be proof enough for you. > But if so, why isn't it? We've got ports for things like Adobe Acrobat, > which only fetch and install a binary. We surely could fetch and build > sendmail from Sendmail.org. I don't know why; nor do I (honestly) care. I just use Postfix. :-) I'm sure that if you pony up the port, someone with the inclination will add it to the ports tree. You could go look up the archives to see whether this sort of thing has been discussed before, and take appropriate action. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 20: 4: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 5214D37B671; Wed, 26 Apr 2000 20:03:58 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id WAA75520; Wed, 26 Apr 2000 22:03:34 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <001601bfaff5$2d04c980$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: Cc: References: <20000426175928.C78347@luna.cdrom.com> <200004270138.SAA00612@freeway.dcfinc.com> <20000426193514.A474@luna.cdrom.com> Subject: Re: sendmail missing? Date: Wed, 26 Apr 2000 22:03:33 -0500 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jim Mock" > On Wed, 26 Apr 2000 at 18:38:02 -0700, Chad R. Larson wrote: > > As I recall, Jim Mock wrote: > > > On Wed, 26 Apr 2000 at 17:42:11 -0700, Chad R. Larson wrote: > > > > This may have already been discussed on some other list, but I'm > > > > surprised to find sendmail has gone missing from the ports > > > > collection. > > > > > But if so, why isn't it? We've got ports for things like Adobe > > Acrobat, which only fetch and install a binary. We surely could fetch > > and build sendmail from Sendmail.org. > There was talk on creating a sendmail port on the current list last year, when it was proposed that sendmail be replaced with postfix(?). There is no reason not to have a port for sendmail as it allows us to use the latest version, while we wait for it to get imported into base system. Check the PR database to see if someone has cobbled together a sendmail port, if not see if you can create one and submit it to the ports collection. > There's no real reason to have the same version of sendmail available in > the base system as in the ports tree. I do think, however, that if > there are beta versions of sendmail available, a port of it is > reasonable for the simple fact that the source tree has the latest > 'stable' version of it even though some people would want newer betas. > Then again, there's no reason why you can't compile sendmail from source > since it works just fine ;-) > The latest release of Sendmail is 8.10.1, while in stable & current we have 8.9.3. Some one should put together a port of Sendmail 8.10, with optional support on the security/cyrus-sasl port (Adds AUTH capability to Sendmail). Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 20:38: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 8256A37BEE4 for ; Wed, 26 Apr 2000 20:37:55 -0700 (PDT) (envelope-from sdk@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 81D763978 for ; Wed, 26 Apr 2000 22:37:54 -0500 (CDT) Received: (from sdk@localhost) by isis.visi.com (8.8.8/8.8.8) id WAA05268 for stable@FreeBSD.ORG; Wed, 26 Apr 2000 22:37:54 -0500 (CDT) Date: Wed, 26 Apr 2000 22:37:54 -0500 From: Stephen To: stable@FreeBSD.ORG Subject: Minimal supfile for 4.0 Message-ID: <20000426223754.A5153@visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just installed 4.0-RELEASE and am about to cvsup to stable. I didn't install nor use games or kerberos, and am wondering if I can remove the following from my supfile and not run into any issues later during the make world, etc? src-games src-kerberos5 src-kerberosIV Thanks for the assistance, sk -- sdk@yuck.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 20:49: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id 998C737B781; Wed, 26 Apr 2000 20:48:56 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id XAA75466; Wed, 26 Apr 2000 23:48:55 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id XAA11636; Wed, 26 Apr 2000 23:48:54 -0400 (EDT) Message-Id: <4.2.2.20000426234307.0342e878@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 26 Apr 2000 23:47:44 -0400 To: Matt Dillon From: Mike Tancsa Subject: Re: cvs commit: src/sys/gnu/ext2fs ..... Cc: stable@FreeBSD.ORG In-Reply-To: <200004262036.NAA81630@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:36 PM 4/26/2000 -0700, Matt Dillon wrote: >dillon 2000/04/26 13:36:37 PDT > MFC sequential write detection heuristic. This extends the sequential > read heuristic to also cover sequential writes, causing write-behind > to be used only for the sequential write case. This solves a number of > performance issues with random writes to medium sized files using > large block sizes, as occurs with DBM files. Well, it does seem to make a difference for me. I was building another box, and decided to try out a 'before' and after. The first is from a stable box from the AM, the second with the above commit. -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 500 17721 84.5 18474 34.8 6166 12.4 14853 97.6 25036 30.6 110.7 2.0 500 17566 82.9 18419 35.0 8301 16.9 14885 97.1 25014 20.5 108.2 1.6 Sure enough, an increase in the rewrite performance on the drive.... The other differences are most likely statistically insignificant, but the rewrite does seem to be valid. Way to go! drive is a ad1: 39082MB [79406/16/63] at ata0-slave using UDMA33 on a Intel PIIX4 ATA33 controller ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 21:22: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id BFD5F37B719 for ; Wed, 26 Apr 2000 21:21:57 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id VAA00981; Wed, 26 Apr 2000 21:21:50 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200004270421.VAA00981@freeway.dcfinc.com> Subject: Re: sendmail missing? In-Reply-To: <20000426223713.C1070@argon.blackdawn.com> from Will Andrews at "Apr 26, 0 10:37:13 pm" To: andrews@technologist.com (Will Andrews) Date: Wed, 26 Apr 2000 21:21:49 -0700 (MST) Cc: jim@luna.cdrom.com, stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Will Andrews wrote: > I'm sure that if you pony up the port, someone with the inclination > will add it to the ports tree. You could go look up the archives to > see whether this sort of thing has been discussed before, and take > appropriate action. I did check the archives, there was no thread that seemed to apply. But it makes sense to me to have a port, for the same reason it made sense to have a port for bind. What started this for me was a desire to pick up some of features in 8.10, and the base system is currently using 8.9. It's true that grabbing the sources from Sendmail.org into /usr/local/src and building them is not tricky (especially given that Eric Allman is a CRSG luminary), but a port could automate that. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 21:51:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 3A0A837B5FB for ; Wed, 26 Apr 2000 21:51:17 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id XAA76588; Wed, 26 Apr 2000 23:51:15 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <006a01bfb004$38226840$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Stephen" Cc: References: <20000426223754.A5153@visi.com> Subject: Re: Minimal supfile for 4.0 Date: Wed, 26 Apr 2000 23:51:14 -0500 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Stephen" > I've just installed 4.0-RELEASE and am about to cvsup to stable. I didn't > install nor use games or kerberos, and am wondering if I can remove the > following from my supfile and not run into any issues later during the > make world, etc? > > src-games > src-kerberos5 > src-kerberosIV > Removing those from your supfile should be no problem, but you want to make sure you have "cvs-crypto" in the supfile. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Apr 26 22: 5:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from grove.iup.edu (maple.grove.iup.edu [144.80.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 352BB37BE94 for ; Wed, 26 Apr 2000 22:05:26 -0700 (PDT) (envelope-from bvjg@grove.iup.edu) Received: from grove.iup.edu ("port 1635"@[144.80.62.205]) by grove.iup.edu (PMDF V5.2-32 #30978) with ESMTP id <01JOPN9I17S890NN46@grove.iup.edu> for stable@FreeBSD.ORG; Thu, 27 Apr 2000 01:05:23 EDT Date: Thu, 27 Apr 2000 01:02:36 -0400 From: Nader Turki Subject: 4.x-stable-supfile To: stable@FreeBSD.ORG Message-id: <3907C9EB.364ABBFA@grove.iup.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.72 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I have FreeBSD 4.0-RELEASE installed and I wanna upgrade to 4.0-STABLE. I didb'r cvsup few times while i was using 3.x. Anyway, I usually have the following in my supfile: *default host=cvsup.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix src-all What about these lines! do I need any of them? Please let me know which i need and maybe i need to add stuff other than these to my supfile :) #cvs-crypto #src-crypto #src-secure #src-sys-crypto Thanks, Nader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 0:40:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pyyhe.saunalahti.fi (mail.sci.fi [195.74.0.41]) by hub.freebsd.org (Postfix) with ESMTP id DB88537B871 for ; Thu, 27 Apr 2000 00:40:34 -0700 (PDT) (envelope-from juksi@iname.com) Received: from sjukebox (MMDCCXXX.hdyn.saunalahti.fi [195.197.45.30]) by pyyhe.saunalahti.fi (8.9.1/8.9.1) with ESMTP id KAA05520 for ; Thu, 27 Apr 2000 10:52:41 +0300 (EET DST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 27 Apr 2000 10:40:17 +0300 (EEST) From: Jukka Simila To: stable@freebsd.org Subject: no run-time symbol table Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last night my box produced the following, 1) Why might that "shared object has..." message appear? 2) How do I fix it? 3) Why is my WinTV message in kernel log? 4) Does it need attention? by the way, sometimes wintv is recognized without remote, thou it has one, and sometimes it works fine. I'm running 4.0-stable, uname -a: FreeBSD sjukebox 4.0-STABLE FreeBSD 4.0-STABLE #2: Thu Mar 30 20:38:49 EEST 2000 sjuke@sjukebox:/usr/src/sys/compile/CELERON i386 -----FW: <200004262300.CAA04110@sjukebox.home>----- Date: Thu, 27 Apr 2000 02:00:16 +0300 (EEST) From: Charlie Root To: undisclosed-recipients:; Subject: sjukebox security check output checking setuid files and devices: /usr/libexec/ld-elf.so.1: awk: Shared object has no run-time symbol table USER=root host=sjukebox HOME=/root PS1=# OPTIND=1 PS2=> LOGNAME=root PATH=/sbin:/bin:/usr/bin MP= TMP=/var/run/_secure.4109 SHELL=/bin/sh IFS= LC_ALL=C LOG=/var/log /usr/libexec/ld-elf.so.1: xargs: Shared object has no run-time symbol table cmp: EOF on /var/run/_secure.4109 ** [ snip ] ** sjukebox kernel log messages: > Hauppauge WinCast/TV, Philips PAL I tuner. ** [ snip ] ** --------------End of forwarded message------------------------- @-`--,--`--- Jukka Simila To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 2:12:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 8548037B6B4 for ; Thu, 27 Apr 2000 02:12:12 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12kkKk-000LF5-00; Thu, 27 Apr 2000 11:11:42 +0200 From: Sheldon Hearn To: chad@DCFinc.com Cc: jim@luna.cdrom.com, stable@FreeBSD.ORG Subject: Re: sendmail missing? In-reply-to: Your message of "Wed, 26 Apr 2000 18:38:02 MST." <200004270138.SAA00612@freeway.dcfinc.com> Date: Thu, 27 Apr 2000 11:11:42 +0200 Message-ID: <81658.956826702@axl.ops.uunet.co.za> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000 18:38:02 MST, "Chad R. Larson" wrote: > And the one in the ports collection has gone missing since I last Or, > And perhaps I've been hallucinating again and it never was a port. > > But if so, why isn't it? We've got ports for things like Adobe Acrobat, > which only fetch and install a binary. We surely could fetch and build > sendmail from Sendmail.org. No sendmail-devel nor sendmail-current nor sendmail-beta ports exist because the people like you who think that such a port might be useful haven't submitted one, or because no committer has felt that any such submission is worthy of his time. :-) This is the answer to many "why isn't there" questions relating to a volunteer project. If you can either find me a submission in the PR database or submit one yourself, mail me the PR number privately (so as not to perpetuate this thread on the list) and I'll commit it or tell you what's wrong with it. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 2:16: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mailhub.unibe.ch (mailhub.unibe.ch [130.92.254.109]) by hub.freebsd.org (Postfix) with ESMTP id 6FAA937B6FF for ; Thu, 27 Apr 2000 02:15:55 -0700 (PDT) (envelope-from roth@iamexwi.unibe.ch) Received: from iamexwi.unibe.ch (haegar.unibe.ch [130.92.71.10]) by mailhub.unibe.ch (PMDF V5.2-32 #42480) with ESMTP id <0FTO008LZ49TSZ@mailhub.unibe.ch> for freebsd-stable@freebsd.org; Thu, 27 Apr 2000 11:13:06 +0200 (MET DST) Received: from vangogh.unibe.ch (vangogh [130.92.62.27]) by iamexwi.unibe.ch (8.8.8+Sun/8.8.8) with ESMTP id LAA26210 for ; Thu, 27 Apr 2000 11:16:39 +0200 (MET DST) Received: from localhost (roth@localhost) by vangogh.unibe.ch (8.9.1b+Sun/8.9.1) with ESMTP id LAA10301 for ; Thu, 27 Apr 2000 11:16:38 +0200 (MET DST) Date: Thu, 27 Apr 2000 11:16:37 +0200 (MET DST) From: Tobias Roth Subject: libresolv In-reply-to: To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I might be confused but isn't there something wrong? I can't find libresolv on my system. I tried to compile something and I got stuck with a missing -lresolv. I looked for libresolv but all I found was the include: /usr/include/resolv.h The include in the source tree, (/usr/obj is linked to /var/obj): /usr/obj/var/src/i386/usr/include/resolv.h and an empty dir here: /usr/obj/var/src/lib/libresolv/ No libresolv* in /usr/lib/ Is there anything wrong with my system? I cvsupped and rebuilt it on Monday. thx, Tobe ------------------------------------------------------ Tobias Roth Phone: +41 31 305 96 29 Buchenweg 22 +41 76 345 66 47 3012 Bern email: hard.wired@switzerland.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 2:19:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from survis.surfnet.nl (survis.surfnet.nl [192.87.108.3]) by hub.freebsd.org (Postfix) with ESMTP id DE33F37B5DB for ; Thu, 27 Apr 2000 02:19:29 -0700 (PDT) (envelope-from Ronald.vanderPol@surfnet.nl) Received: from zuurtje.surfnet.nl ([192.87.109.5]) by survis.surfnet.nl with ESMTP (exPP) for freebsd-stable@freebsd.org id 12kkSG-000393-00; Thu, 27 Apr 2000 11:19:28 +0200 Received: from surah.surfnet.nl (surah.surfnet.nl [192.87.109.3]) by zuurtje.surfnet.nl (8.9.3/8.9.3/ZUURTJE-0.7) with ESMTP id LAA25109 for ; Thu, 27 Apr 2000 11:19:28 +0200 (MET DST) Received: from sure.surfnet.nl (sure.surfnet.nl [192.87.109.131]) by surah.surfnet.nl (8.9.3/8.9.3/SURAH-0.1) with ESMTP id LAA15488 for ; Thu, 27 Apr 2000 11:19:27 +0200 (MET DST) Date: Thu, 27 Apr 2000 11:22:52 +0200 (CEST) From: Ronald van der Pol To: freebsd-stable@freebsd.org Subject: Re: does FreeBSD 4.0-RELEASE support DEC/INTEL 21041? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 20 Apr 2000, Ronald van der Pol wrote: > I am trying to get a Farallon Ethernet card working on FreeBSD 4.0-RELEASE. > It has a chip labelled "digital 21041-pb". > > The kernel meesages say: > de0: irq 9 at device 16.0 on pci0 > de0: driver is using old-style compatibility shims Hmm, the problem was in my BIOS setup. I need to set "plug-and-play=disable" in my BIOS. This means the BIOS handles plug-and-play. I never understood PC's :-) rvdp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 2:58:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 510D437B734 for ; Thu, 27 Apr 2000 02:58:12 -0700 (PDT) (envelope-from brameld@twave.net) Received: from [208.47.188.96] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id fa101483 for ; Thu, 27 Apr 2000 05:58:01 -0400 From: Walter Brameld To: freebsd-stable@freebsd.org Subject: knapster can't connect after make world Date: Thu, 27 Apr 2000 05:54:19 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00042705580600.00233@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using knapster for about a month now with no problems, but after doing a cvsup and make world yesterday it can no longer connect to the server. My only clue is it uses port 6699 for downloads. Any help as to where to look for what may be blocking it? All my other online services are still working. I'm running 4.0 STABLE. Thanks in advance. -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: And what does THIS button do?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 5:44:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pobox.rwwa.com (pobox.rwwa.com [216.254.75.81]) by hub.freebsd.org (Postfix) with ESMTP id 9406137B94D for ; Thu, 27 Apr 2000 05:44:08 -0700 (PDT) (envelope-from witr@rwwa.com) Received: from rwwa.com (spooky.rwwa.com [192.124.97.13]) by pobox.rwwa.com (8.9.3/8.9.3) with ESMTP id IAA75352 for ; Thu, 27 Apr 2000 08:51:31 -0400 (EDT) (envelope-from witr@rwwa.com) Message-Id: <200004271251.IAA75352@pobox.rwwa.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-stable@FreeBSD.ORG Subject: Re: sendmail missing? In-Reply-To: Your message of "Thu, 27 Apr 2000 11:18:41 +1000." <002c01bfafe6$87c47000$020aa8c0@aims.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Apr 2000 08:44:10 -0400 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG chris@aims.com.au said: :-This does require that NO_SENDMAIL should be set to true in /etc/ :-make.conf to avoid clobbering the newer version of sendmail if :-performing a make world. Actually, I've kinda wondered if it would be better for *all* of these kind of things (separately-maintained things) to be ports and *not* be part of the base systems. Wait, Wait! Before you freak out! ;-) What I had in mind is that the install program, would install these things much like it installs Linux compatibility now. This would give you the best of both worlds: a complete and functional system at installation time, and easy and modular update-ability/upgrade-ability in the future. Just an idea. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 5:56:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 70D6737B7D1 for ; Thu, 27 Apr 2000 05:56:23 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 12536A839; Thu, 27 Apr 2000 22:56:51 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 100E95410; Thu, 27 Apr 2000 22:56:51 +1000 (EST) Date: Thu, 27 Apr 2000 22:56:51 +1000 (EST) From: andrew@ugh.net.au To: Robert Withrow Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sendmail missing? In-Reply-To: <200004271251.IAA75352@pobox.rwwa.com> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Apr 2000, Robert Withrow wrote: > Actually, I've kinda wondered if it would be better for *all* of these > kind of things (separately-maintained things) to be ports and *not* be > part of the base systems. I think I agree, although its important that these ports still get the care and attention they did when they were part of the base system (not saying they wouldn't). The installer should probably then have an option to install a "traditional FreeBSD installation" that automatically picks sendmail, bind etc. That way its no harder for people who want things to stay the same. It would be nice if so much stuff became optional we could fit on smaller drives...200MB seems to be the minimum for bin + man atm...of course I'm not even going to dare suggest what should be made optional :-) I don't suppose many people are trying to use smaller drives now days anyway, except for the embedded people and thats what PicoBSD is for. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 7: 1:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B850837B569 for ; Thu, 27 Apr 2000 07:01:48 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e3REVEA27872; Thu, 27 Apr 2000 07:31:14 -0700 (PDT) Date: Thu, 27 Apr 2000 07:31:14 -0700 From: Alfred Perlstein To: Tobias Roth Cc: freebsd-stable@FreeBSD.ORG Subject: Re: libresolv Message-ID: <20000427073114.I489@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from roth@iamexwi.unibe.ch on Thu, Apr 27, 2000 at 11:16:37AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Tobias Roth [000427 03:06] wrote: > Hello > > I might be confused but isn't there something wrong? I can't find > libresolv on my system. Under FreeBSD 'libresolv' is bundled in with libc. You don't need -lresolv to get the resolver functions. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 8: 6:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id D9D4C37B6F8 for ; Thu, 27 Apr 2000 08:06:37 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12kmZo-0004JC-00; Thu, 27 Apr 2000 12:35:24 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12kmZo-000NCI-00; Thu, 27 Apr 2000 12:35:24 +0100 Date: Thu, 27 Apr 2000 12:35:23 +0100 From: Ben Smithurst To: Tobias Roth Cc: freebsd-stable@freebsd.org Subject: Re: libresolv Message-ID: <20000427123523.T86507@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tobias Roth wrote: > I might be confused but isn't there something wrong? I can't find > libresolv on my system. > > I tried to compile something and I got stuck with a missing -lresolv. > I looked for libresolv but all I found was the include: Just remove -lresolv from the command line, it isn't needed in FreeBSD and it's quite normal that libresolv doesn't exist. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 8:11:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id C196C37B63D for ; Thu, 27 Apr 2000 08:11:13 -0700 (PDT) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id BAA26202; Fri, 28 Apr 2000 01:10:51 +1000 (EST) (envelope-from jon) Date: Fri, 28 Apr 2000 01:10:47 +1000 From: Jonathan Michaels To: Robert Withrow Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sendmail missing? Message-ID: <20000428011040.A26139@phoenix.welearn.com.au> Reply-To: jon@seaholm.caamora.com.au Mail-Followup-To: Robert Withrow , freebsd-stable@FreeBSD.ORG References: <002c01bfafe6$87c47000$020aa8c0@aims.private> <200004271251.IAA75352@pobox.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200004271251.IAA75352@pobox.rwwa.com>; from Robert Withrow on Thu, Apr 27, 2000 at 08:44:10AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 27, 2000 at 08:44:10AM -0400, Robert Withrow wrote: > > chris@aims.com.au said: > :-This does require that NO_SENDMAIL should be set to true in /etc/ > :-make.conf to avoid clobbering the newer version of sendmail if > :-performing a make world. > What I had in mind is that the install program, would install these things > much like it installs Linux compatibility now. This would give you the > best of both worlds: a complete and functional system at installation time, > and easy and modular update-ability/upgrade-ability in the future. yup and from the outside looking it i appears to have teh potential of taking some of teh 'ifs,ands,ors,buts' out of an installation from the point of view of someone new to freebsd. well sorta, makes it easier when everyting is out in teh open and one dosen't need to drege the rc.* and or make* and or blah* someting like that. sorry, i'm not a 'real programmer', i don't understand dilbert. > Just an idea. sounds like a reasonable one to me regards jonathan -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 11: 9: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 7E5B737BF15; Thu, 27 Apr 2000 11:08:56 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id UAA09732; Mon, 1 May 2000 20:34:25 -0500 (CDT) From: Joe Greco Message-Id: <200005020134.UAA09732@aurora.sol.net> Subject: 29160/39160 under 3.*-stable To: scsi@freebsd.org, stable@freebsd.org Date: Mon, 1 May 2000 20:34:24 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will the 29160 and 39160 be supported under 3.*-stable? With the old cards no longer being available, and the relative newness of 4.*-stable, I do not really want to run 4.0R on production servers. Thanks for any info, -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 12:14:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41]) by hub.freebsd.org (Postfix) with ESMTP id 67D3B37B94F for ; Thu, 27 Apr 2000 12:14:44 -0700 (PDT) (envelope-from sasha@frolkin.demon.co.uk) Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1) id 12ktkV-0000Lo-00; Thu, 27 Apr 2000 20:14:55 +0100 Date: Thu, 27 Apr 2000 20:14:55 +0100 From: Alexander Frolkin To: Nader Turki Cc: stable@FreeBSD.ORG Subject: Re: 4.x-stable-supfile Message-ID: <20000427201455.A749@gamma> Reply-To: Alexander Frolkin References: <3907C9EB.364ABBFA@grove.iup.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <3907C9EB.364ABBFA@grove.iup.edu>; from Nader Turki on Thu, Apr 27, 2000 at 01:02:36AM -0400 X-Operating-System: Linux 2.2.14 X-GPG-Key-Fingerprint: 6C84 3EB2 550E E581 62FA BB0C D510 B042 FD5C E7A7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 27, 2000 at 01:02:36AM -0400, Nader Turki wrote: > Hi there, > > I have FreeBSD 4.0-RELEASE installed and I wanna upgrade to 4.0-STABLE. > I didb'r cvsup few times while i was using 3.x. > Anyway, I usually have the following in my supfile: > > *default host=cvsup.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=RELENG_4 > *default delete use-rel-suffix > src-all > > What about these lines! do I need any of them? Please let me know which > i need and maybe i need to add stuff other than these to my supfile :) > > #cvs-crypto > #src-crypto > #src-secure > #src-sys-crypto You need either the first one or the last three. The three src-* collections make up cvs-crypto. Alexander. > Thanks, > Nader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 18:21:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id C53BC37B8CC for ; Thu, 27 Apr 2000 18:21:18 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id SAA09405 for ; Thu, 27 Apr 2000 18:21:18 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda09403; Thu Apr 27 18:21:06 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id SAA07749 for ; Thu, 27 Apr 2000 18:21:05 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdve7743; Thu Apr 27 18:20:45 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.10.1/8.9.1) id e3S1KiF38119 for ; Thu, 27 Apr 2000 18:20:44 -0700 (PDT) Message-Id: <200004280120.e3S1KiF38119@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdW38116; Thu Apr 27 18:20:30 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.0-STABLE X-Sender: cy To: freebsd-stable@freebsd.org Subject: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Apr 2000 18:20:30 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Under 4.0S building a kernel with IPFILTER enabled, I get the following message yet I cannot find xxxio.h. The system runs quite nicely w/o xxxio.h. I'm confused. In file included from ../../netinet/ip_frag.c:31: ./../sys/ioctl.h:46: warning: #warning "Don't #include ioctl.h in the kernel. Include xxxio.h instead." Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 23: 5:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id D90CE37BB69 for ; Thu, 27 Apr 2000 23:05:21 -0700 (PDT) (envelope-from faber@lunabase.org) Received: from praxis.lunabase.org ([63.200.244.110]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FTP00JEGQ6AK2@mta6.snfc21.pbi.net> for stable@FreeBSD.org; Thu, 27 Apr 2000 23:03:47 -0700 (PDT) Received: from praxis.lunabase.org (localhost [127.0.0.1]) by praxis.lunabase.org (8.9.3/8.9.3) with ESMTP id XAA43247 for ; Thu, 27 Apr 2000 23:04:14 -0700 X-URL: http://www.lunabase.org/~faber Date: Thu, 27 Apr 2000 23:04:14 -0700 From: Ted Faber Subject: can't make buildworld To: stable@FreeBSD.org Message-id: <200004280604.XAA43247@praxis.lunabase.org> Organization: My Secret Broadcast Base on the Moon X-Mailer: exmh version 2.1.1 10/15/1999 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii I cvssupped RELENG_4 (to an empty directory) at about Thu Apr 27 20:30:00 PDT 2000 and can't get a clean build. It fails while building newfs with: arvon:/usr/src$ sudo make [ ... ] ===> sbin/mount_nwfs Warning: Object directory not changed from original /usr/src/sbin/mount_nwfs cc -O -pipe -DNWFS -I/usr/src/sbin/mount_nwfs/../mount -c mount_nwfs.c cc -O -pipe -DNWFS -I/usr/src/sbin/mount_nwfs/../mount -c /usr/src/sbin/mount_nwfs/../mount/getmntopts.c gzip -cn mount_nwfs.8 > mount_nwfs.8.gz mount_nwfs.c: In function `main': mount_nwfs.c:330: structure has no member named `tz' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Am I missing an entry in make.conf or something or is this just broken?? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: Exmh version 2.1.1 10/15/1999 iD8DBQE5CSndaUz3f+Zf+XsRAhpRAJkB2m84aLdzDB1Ut+z04e+ecNfFBQCfQVfV zizcYUgwGvxMHan4tAYriM0= =dXJY -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Apr 27 23:33: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zensai.zerorez.net (zensai.zerorez.net [216.36.30.13]) by hub.freebsd.org (Postfix) with ESMTP id BAFFD37B5E0 for ; Thu, 27 Apr 2000 23:33:00 -0700 (PDT) (envelope-from dustin@zerorez.com) Received: from zensai.zerorez.net (IDENT:dustin@localhost [127.0.0.1]) by zensai.zerorez.net (8.9.3/8.9.3) with ESMTP id XAA23291; Thu, 27 Apr 2000 23:32:52 -0700 Message-Id: <200004280632.XAA23291@zensai.zerorez.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ted Faber Cc: stable@FreeBSD.ORG, dustin@zensai.zerorez.net Subject: Re: can't make buildworld In-Reply-To: Message from Ted Faber of "Thu, 27 Apr 2000 23:04:14 PDT." <200004280604.XAA43247@praxis.lunabase.org> Date: Thu, 27 Apr 2000 23:32:51 -0700 From: dustin@zerorez.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii I did a buildworld from RELENG_4 about 24 hours before yours and it worked fine. The change that seems relevant to your problem was committed on 4/17 by bp, so I'm not sure why you're having this problem and not me. - --dustin -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBOQkwk1slaNw2GeVzEQKrBQCg0NPvtynKdqsAqLDKv5Xz0YkevLgAniui dqAlNSJDUTHaQruyrkCq9+qC =d6PS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 4:22:47 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rhea.salford.ac.uk (rhea.salford.ac.uk [146.87.255.99]) by hub.freebsd.org (Postfix) with SMTP id D139B37B6C7 for ; Fri, 28 Apr 2000 04:22:36 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 25818 invoked by alias); 28 Apr 2000 11:22:35 -0000 Received: (qmail 25809 invoked from network); 28 Apr 2000 11:22:35 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by rhea.salford.ac.uk with SMTP; 28 Apr 2000 11:22:35 -0000 Received: (qmail 36157 invoked by uid 141); 28 Apr 2000 11:22:35 -0000 Date: Fri, 28 Apr 2000 12:22:35 +0100 (BST) From: Mark Powell To: freebsd-stable@freebsd.org Subject: How good is AMI MegaRAID support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As the DPT SmartRAID IV controllers are now obsolete, what's the best bet for hardware RAID under FreeBSD? From a bit of reading the AMI controllers seem to be well featured and regarded. Just how good is the support for these controllers in 4.0R? I'm trying to hold off using 4.x on any servers until I've used 4.0R for a while to become familiar with it and more specifically until 4.1R is released. Am I being paranoid or will the AMI controllers and 4.0S be just fine as a server? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 4:57:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id 5520937BF2D for ; Fri, 28 Apr 2000 04:57:15 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id HAA41426; Fri, 28 Apr 2000 07:57:12 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id HAA05734; Fri, 28 Apr 2000 07:57:11 -0400 (EDT) Message-Id: <4.2.2.20000428074518.03404fa0@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 28 Apr 2000 07:56:07 -0400 To: Mark Powell , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: How good is AMI MegaRAID support? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:22 PM 4/28/2000 +0100, Mark Powell wrote: >As the DPT SmartRAID IV controllers are now obsolete, what's the best bet >for hardware RAID under FreeBSD? From a bit of reading the AMI >controllers seem to be well featured and regarded. Just how good is the >support for these controllers in 4.0R? I'm trying to hold off using 4.x on >any servers until I've used 4.0R for a while to become familiar with it >and more specifically until 4.1R is released. If you are using 3.x you might as well start using 4.x in production, as it is as stable if not more as the 3.x branch was/is. As for RAID support, I would say take a look at the Mylex cards. In comparing two older models (the AMI 428 vs the DAC960P/PD) the found the performance differences minor, if not insignificant. Similarly, the feature set is not *that* different and might be irrelevant for you-- Especially if all you want is RAID 0,1,5 ) You might want to pick up a Mylex and a AMI off of E-Bay cheap and test them out for your self. I have been using 4.x for our internal Squid proxy with great results. I didnt have problems with the AMI card, except that I could artificially wedge it under high load. There have been new patches to the driver, so its possible the problem has been fixed, but I havent had time to test that. For us the plan is to replace our main production servers with 4.x as soon as we have the time to do it with Mylex cards where appropriate. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 5:11:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iapetus.salford.ac.uk (iapetus.salford.ac.uk [146.87.255.98]) by hub.freebsd.org (Postfix) with SMTP id 6DCEF37B6AB for ; Fri, 28 Apr 2000 05:11:16 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 93638 invoked by alias); 28 Apr 2000 12:11:14 -0000 Received: (qmail 93632 invoked from network); 28 Apr 2000 12:11:14 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by iapetus.salford.ac.uk with SMTP; 28 Apr 2000 12:11:14 -0000 Received: (qmail 36280 invoked by uid 141); 28 Apr 2000 12:11:14 -0000 Date: Fri, 28 Apr 2000 13:11:14 +0100 (BST) From: Mark Powell To: Mike Tancsa Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-Reply-To: <4.2.2.20000428074518.03404fa0@mail.sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Mike Tancsa wrote: > At 12:22 PM 4/28/2000 +0100, Mark Powell wrote: > >As the DPT SmartRAID IV controllers are now obsolete, what's the best bet > >for hardware RAID under FreeBSD? From a bit of reading the AMI > >controllers seem to be well featured and regarded. Just how good is the > >support for these controllers in 4.0R? I'm trying to hold off using 4.x on > >any servers until I've used 4.0R for a while to become familiar with it > >and more specifically until 4.1R is released. > > If you are using 3.x you might as well start using 4.x in production, as it > is as stable if not more as the 3.x branch was/is. As for RAID support, I > would say take a look at the Mylex cards. In comparing two older models > (the AMI 428 vs the DAC960P/PD) the found the performance differences > minor, if not insignificant. Similarly, the feature set is not *that* > different and might be irrelevant for you-- Especially if all you want is > RAID 0,1,5 ) Yep, 0,1,5,10 and 50 are the only levels we may require. Some sort of FBSD management utility would be useful, although unlikely? Feedback from the driver regarding array status would be very useful. The DPT driver lacked this, requiring you to be able to hear the controllers alarm. This is of course impractical with remotely based servers. > You might want to pick up a Mylex and a AMI off of E-Bay cheap and test > them out for your self. I already have an old DAC960 which I may test. However, I'd like others opinions. I'm sure more testing than I could ever hope to do has already been done. > I have been using 4.x for our internal Squid proxy > with great results. I didnt have problems with the AMI card, except that I > could artificially wedge it under high load. There have been new patches > to the driver, so its possible the problem has been fixed, but I havent had > time to test that. Does anyone on the list know if this has been fixed? > For us the plan is to replace our main production > servers with 4.x as soon as we have the time to do it with Mylex cards > where appropriate. Are you moving to the Mylex cards just because of the above problem, or something else? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 5:16:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 30A8D37B992 for ; Fri, 28 Apr 2000 05:16:53 -0700 (PDT) (envelope-from joe@pavilion.net) Received: from genius.systems.pavilion.net (postfix@genius.systems.pavilion.net [212.74.1.100]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id NAA76096; Fri, 28 Apr 2000 13:15:39 +0100 (BST) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 1B4DA362; Fri, 28 Apr 2000 13:16:19 +0100 (BST) Date: Fri, 28 Apr 2000 13:16:19 +0100 From: Joe Karthauser To: Mark Powell Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? Message-ID: <20000428131619.K40708@pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from M.S.Powell@salford.ac.uk on Fri, Apr 28, 2000 at 12:22:35PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 28, 2000 at 12:22:35PM +0100, Mark Powell wrote: > As the DPT SmartRAID IV controllers are now obsolete, what's the best bet > for hardware RAID under FreeBSD? From a bit of reading the AMI > controllers seem to be well featured and regarded. Just how good is the > support for these controllers in 4.0R? I'm trying to hold off using 4.x on > any servers until I've used 4.0R for a while to become familiar with it > and more specifically until 4.1R is released. > Am I being paranoid or will the AMI controllers and 4.0S be just fine as > a server? > Cheers. Simon Shapiro's writing an i2o subsystem for 3.x, which supports the DPT smart raid V card. He's working on support for 4.x, but it's to there yet. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 5:19:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from iapetus.salford.ac.uk (iapetus.salford.ac.uk [146.87.255.98]) by hub.freebsd.org (Postfix) with SMTP id 01F3537BEBC for ; Fri, 28 Apr 2000 05:19:25 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 99082 invoked by alias); 28 Apr 2000 12:19:23 -0000 Received: (qmail 99069 invoked from network); 28 Apr 2000 12:19:23 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by iapetus.salford.ac.uk with SMTP; 28 Apr 2000 12:19:23 -0000 Received: (qmail 36298 invoked by uid 141); 28 Apr 2000 12:19:23 -0000 Date: Fri, 28 Apr 2000 13:19:23 +0100 (BST) From: Mark Powell To: Joe Karthauser Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-Reply-To: <20000428131619.K40708@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Joe Karthauser wrote: > On Fri, Apr 28, 2000 at 12:22:35PM +0100, Mark Powell wrote: > > As the DPT SmartRAID IV controllers are now obsolete, what's the best bet > > for hardware RAID under FreeBSD? From a bit of reading the AMI > > controllers seem to be well featured and regarded. Just how good is the > > support for these controllers in 4.0R? I'm trying to hold off using 4.x on > > any servers until I've used 4.0R for a while to become familiar with it > > and more specifically until 4.1R is released. > > Am I being paranoid or will the AMI controllers and 4.0S be just fine as > > a server? > > Cheers. > > Simon Shapiro's writing an i2o subsystem for 3.x, which supports > the DPT smart raid V card. He's working on support for 4.x, but > it's to there yet. I appreciate the good work Simon and Mike are doing in this area. However, I wanted to know what is the current RAID solution of choice for FreeBSD. As I'm sure you understand I need a proven solution. Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 5:24:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id CBF1937BEB8 for ; Fri, 28 Apr 2000 05:24:30 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id IAA43976; Fri, 28 Apr 2000 08:24:30 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id IAA12125; Fri, 28 Apr 2000 08:24:27 -0400 (EDT) Message-Id: <4.2.2.20000428081704.03735e30@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 28 Apr 2000 08:23:23 -0400 To: Mark Powell From: Mike Tancsa Subject: Re: How good is AMI MegaRAID support? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <4.2.2.20000428074518.03404fa0@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:11 PM 4/28/2000 +0100, Mark Powell wrote: >Yep, 0,1,5,10 and 50 are the only levels we may require. Some sort of >FBSD management utility would be useful, although unlikely? Its there for the Mylex... e.g. newmail# mlxcontrol Unknown command '(null)'. Valid commands are: status displays device status rescan scan for new system drives detach detach system drives check consistency-check a system drive rebuild initiate a rebuild of a dead physical drive config examine and update controller configuration help give help on usage newmail# See the man page for mlxcontrol. The config from scratch isnt there yet, but the rebuild/status/check is etc is... newmail# mlxcontrol check mlxd0 newmail# mlxcontrol status mlxd0 mlxd0: online [consistency check: 8223936/8273920, 0% complete] newmail# mlxcontrol status mlxd0 mlxd0: online [consistency check: 3345472/8273920, 59% complete] newmail# > > You might want to pick up a Mylex and a AMI off of E-Bay cheap and test > > them out for your self. > >I already have an old DAC960 which I may test. However, I'd like others >opinions. I'm sure more testing than I could ever hope to do has already >been done. www.dejanews.com/usenet. Choose power search, use *freebsd* for the form, and try mylex or megaraid for the keywords... Search through and see what people have said. > > I have been using 4.x for our internal Squid proxy > > with great results. I didnt have problems with the AMI card, except > that I > > could artificially wedge it under high load. There have been new patches > > to the driver, so its possible the problem has been fixed, but I havent > had > > time to test that. > >Does anyone on the list know if this has been fixed? This was discussed recently. IIRC, one said yes, one said no. > > For us the plan is to replace our main production > > servers with 4.x as soon as we have the time to do it with Mylex cards > > where appropriate. > >Are you moving to the Mylex cards just because of the above problem, or >something else? Partly the above problems (we have a need to move ahead now), but mostly because we havent been able to crash the driver with whatever artificial load we threw at it. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 5:36: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from web108.yahoomail.com (web108.yahoomail.com [205.180.60.75]) by hub.freebsd.org (Postfix) with SMTP id 1795937BE73 for ; Fri, 28 Apr 2000 05:35:49 -0700 (PDT) (envelope-from jimbots@yahoo.com) Received: (qmail 16324 invoked by uid 60001); 28 Apr 2000 12:35:48 -0000 Message-ID: <20000428123548.16323.qmail@web108.yahoomail.com> Received: from [216.126.161.60] by web108.yahoomail.com; Fri, 28 Apr 2000 05:35:48 PDT Date: Fri, 28 Apr 2000 05:35:48 -0700 (PDT) From: Jim Stevens Subject: unsubscribe To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe __________________________________________________ Do You Yahoo!? Talk to your friends online and get email alerts with Yahoo! Messenger. http://im.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 6:22:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 6E37137B64F for ; Fri, 28 Apr 2000 06:22:16 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 89035DA6D; Fri, 28 Apr 2000 15:21:54 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000428131619.K40708@pavilion.net> References: <20000428131619.K40708@pavilion.net> Date: Fri, 28 Apr 2000 14:29:57 +0200 To: Joe Karthauser , Mark Powell From: Brad Knowles Subject: Re: How good is AMI MegaRAID support? Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:16 PM +0100 2000/4/28, Joe Karthauser wrote: > Simon Shapiro's writing an i2o subsystem for 3.x, which supports > the DPT smart raid V card. He's working on support for 4.x, but > it's to there yet. This system has been under development for a very long time. DPT has since released a SmartRAID VI card that will supposedly use the same i2o drivers, and they have since been bought by Adaptec. I was supposed to be getting a loaner card (with official drivers from DPT) for evaluation and testing sometime last year, but it never came off. According to , the driver is already a standard feature of FreeBSD 2.2.8, 3.1 and 4.0, but I don't see it myself (unless he's talking about the older SmartRAID IV). There's another page at that indicates an i2o patch is available for RELENG_3, but this would seem to directly contradict the claims made on the other page. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 6:22:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rhea.salford.ac.uk (rhea.salford.ac.uk [146.87.255.99]) by hub.freebsd.org (Postfix) with SMTP id 4BA2037BEEA for ; Fri, 28 Apr 2000 06:22:38 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 90230 invoked by alias); 28 Apr 2000 13:22:34 -0000 Received: (qmail 90216 invoked from network); 28 Apr 2000 13:22:34 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by rhea.salford.ac.uk with SMTP; 28 Apr 2000 13:22:34 -0000 Received: (qmail 36519 invoked by uid 141); 28 Apr 2000 13:22:34 -0000 Date: Fri, 28 Apr 2000 14:22:34 +0100 (BST) From: Mark Powell To: Mike Tancsa Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-Reply-To: <4.2.2.20000428081704.03735e30@mail.sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Mike Tancsa wrote: > At 01:11 PM 4/28/2000 +0100, Mark Powell wrote: > > >Yep, 0,1,5,10 and 50 are the only levels we may require. Some sort of > >FBSD management utility would be useful, although unlikely? > > Its there for the Mylex... e.g. > See the man page for mlxcontrol. The config from scratch isnt there yet, That's acceptable. Not really necessary anyhow. > but the rebuild/status/check is etc is... > > newmail# mlxcontrol check mlxd0 > newmail# mlxcontrol status mlxd0 > mlxd0: online [consistency check: 8223936/8273920, 0% complete] > newmail# mlxcontrol status mlxd0 > mlxd0: online [consistency check: 3345472/8273920, 59% complete] > newmail# That's just what's needed. > >I already have an old DAC960 which I may test. However, I'd like others > >opinions. I'm sure more testing than I could ever hope to do has already > >been done. > > www.dejanews.com/usenet. Choose power search, use *freebsd* for the form, > and try mylex or megaraid for the keywords... Search through and see what > people have said. Cheers, I didn't know the mailing lists made it onto Deja. I find the official search facility lacking. > > > could artificially wedge it under high load. There have been new patches > > > to the driver, so its possible the problem has been fixed, but I havent > > had > > > time to test that. > > > >Does anyone on the list know if this has been fixed? > > This was discussed recently. IIRC, one said yes, one said no. Hmmm. The Mylex controllers are looking more attractive. > > > For us the plan is to replace our main production > > > servers with 4.x as soon as we have the time to do it with Mylex cards > > > where appropriate. > > > >Are you moving to the Mylex cards just because of the above problem, or > >something else? > > Partly the above problems (we have a need to move ahead now), but mostly > because we havent been able to crash the driver with whatever artificial > load we threw at it. That's my problem too. We are currently ordering a machine, but have been told the SmartRAID IV controller is no longer available. Still pondering over the AMI or Mylex cards Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 6:36:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 15C4937BEC7 for ; Fri, 28 Apr 2000 06:36:52 -0700 (PDT) (envelope-from joe@pavilion.net) Received: from genius.systems.pavilion.net (postfix@genius.systems.pavilion.net [212.74.1.100]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id OAA99417; Fri, 28 Apr 2000 14:35:33 +0100 (BST) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id B5E1D362; Fri, 28 Apr 2000 14:36:12 +0100 (BST) Date: Fri, 28 Apr 2000 14:36:12 +0100 From: Joe Karthauser To: Brad Knowles Cc: Mark Powell , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? Message-ID: <20000428143612.N40708@pavilion.net> References: <20000428131619.K40708@pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Fri, Apr 28, 2000 at 02:29:57PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 28, 2000 at 02:29:57PM +0200, Brad Knowles wrote: > At 1:16 PM +0100 2000/4/28, Joe Karthauser wrote: > > > Simon Shapiro's writing an i2o subsystem for 3.x, which supports > > the DPT smart raid V card. He's working on support for 4.x, but > > it's to there yet. > > This system has been under development for a very long time. DPT > has since released a SmartRAID VI card that will supposedly use the > same i2o drivers, and they have since been bought by Adaptec. I was > supposed to be getting a loaner card (with official drivers from DPT) > for evaluation and testing sometime last year, but it never came off. > > According to , the > driver is already a standard feature of FreeBSD 2.2.8, 3.1 and 4.0, > but I don't see it myself (unless he's talking about the older > SmartRAID IV). There's another page at > that indicates an i2o patch > is available for RELENG_3, but this would seem to directly contradict > the claims made on the other page. I've been talking to him a lot of the last week and the case is as I specified above. He's got a patch set for 3.X (which I'm using with a DPT smart raid V card), and is working on 4.x, but with nothing published yet. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 7:25: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frigga.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id C46CB37B885 for ; Fri, 28 Apr 2000 07:25:02 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FRIGGA with Internet Mail Service (5.5.2650.21) id ; Fri, 28 Apr 2000 10:24:46 -0400 Message-ID: From: Troy Arie Cobb To: 'Mike Tancsa' , Mark Powell Cc: freebsd-stable@FreeBSD.ORG Subject: RE: How good is AMI MegaRAID support? Date: Fri, 28 Apr 2000 10:24:45 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't find this in 4.0-STABLE, cvsup'd just a few days ago. Can anyone point me to this tool? - Troy > -----Original Message----- > From: Mike Tancsa [mailto:mike@sentex.net] > Sent: Friday, April 28, 2000 8:23 AM > To: Mark Powell > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: How good is AMI MegaRAID support? > > > At 01:11 PM 4/28/2000 +0100, Mark Powell wrote: > > >Yep, 0,1,5,10 and 50 are the only levels we may require. > Some sort of > >FBSD management utility would be useful, although unlikely? > > Its there for the Mylex... e.g. > newmail# mlxcontrol > Unknown command '(null)'. > Valid commands are: > status displays device status > rescan scan for new system drives > detach detach system drives > check consistency-check a system drive > rebuild initiate a rebuild of a dead physical drive > config examine and update controller configuration > help give help on usage > newmail# > See the man page for mlxcontrol. The config from scratch > isnt there yet, > but the rebuild/status/check is etc is... > > newmail# mlxcontrol check mlxd0 > newmail# mlxcontrol status mlxd0 > mlxd0: online [consistency check: 8223936/8273920, 0% complete] > newmail# mlxcontrol status mlxd0 > mlxd0: online [consistency check: 3345472/8273920, 59% complete] > newmail# > > > > > You might want to pick up a Mylex and a AMI off of > E-Bay cheap and test > > > them out for your self. > > > >I already have an old DAC960 which I may test. However, > I'd like others > >opinions. I'm sure more testing than I could ever hope to > do has already > >been done. > > www.dejanews.com/usenet. Choose power search, use > *freebsd* for the form, > and try mylex or megaraid for the keywords... Search > through and see what > people have said. > > > > > I have been using 4.x for our internal Squid proxy > > > with great results. I didnt have problems with the AMI > card, except > > that I > > > could artificially wedge it under high load. There > have been new patches > > > to the driver, so its possible the problem has been > fixed, but I havent > > had > > > time to test that. > > > >Does anyone on the list know if this has been fixed? > > > This was discussed recently. IIRC, one said yes, one said no. > > > > > For us the plan is to replace our main production > > > servers with 4.x as soon as we have the time to do it > with Mylex cards > > > where appropriate. > > > >Are you moving to the Mylex cards just because of the > above problem, or > >something else? > > Partly the above problems (we have a need to move ahead > now), but mostly > because we havent been able to crash the driver with > whatever artificial > load we threw at it. > > ---Mike > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 7:30:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id AB1D137BEFF for ; Fri, 28 Apr 2000 07:30:08 -0700 (PDT) (envelope-from mike@sentex.ca) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id KAA61244; Fri, 28 Apr 2000 10:30:02 -0400 (EDT) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id KAA26525; Fri, 28 Apr 2000 10:30:02 -0400 (EDT) Message-Id: <3.0.5.32.20000428102649.00ad1b20@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 28 Apr 2000 10:26:49 -0400 To: Troy Arie Cobb From: Mike Tancsa Subject: RE: How good is AMI MegaRAID support? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:24 AM 4/28/00 -0400, Troy Arie Cobb wrote: >I can't find this in 4.0-STABLE, cvsup'd just a few days ago. Can anyone >point >me to this tool? mlxcontrol imported to RELENG_4 from current on the 24th of April. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 8: 4:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id C726D37BF3C for ; Fri, 28 Apr 2000 08:04:06 -0700 (PDT) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 8E372E895 for ; Fri, 28 Apr 2000 11:04:05 -0400 (EDT) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA05829; Fri, 28 Apr 2000 11:04:05 -0400 (EDT) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="F8jIq+Bmm/" Content-Transfer-Encoding: 7bit Message-ID: <14601.43109.419114.997113@onceler.kcilink.com> Date: Fri, 28 Apr 2000 11:04:05 -0400 (EDT) To: stable@freebsd.org Subject: Cron setting SIGCHLD to SIG_IGN X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --F8jIq+Bmm/ Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit There was a nice little bug found in Cron over on the BSDI users mailing list. Apparently SIGCHLD is ignored when the child command is run, and perl 5.6.0 complains about it. The fix is to cron. This seems to be applicable for FreeBSD 3.4-STABLE and 4.0-STABLE according to the sources as of today, as well. Attached is the patch from Paul Vixie. --F8jIq+Bmm/ Content-Type: message/rfc822 Content-Description: forwarded message Content-Transfer-Encoding: 7bit Return-Path: Delivered-To: khera@kcilink.com Received: from mailinglists.org (server1.mailinglists.org [63.160.175.18]) by kci.kciLink.com (Postfix) with SMTP id B6D39E895 for ; Thu, 27 Apr 2000 17:47:18 -0400 (EDT) Received: (qmail 6669 invoked by alias); 27 Apr 2000 21:47:11 -0000 Mailing-List: contact bsdi-users-help@mailinglists.org; run by ezmlm Precedence: bulk X-No-Archive: yes list-help: list-unsubscribe: list-post: Delivered-To: mailing list bsdi-users@mailinglists.org Received: (qmail 6658 invoked from network); 27 Apr 2000 21:47:11 -0000 Message-Id: <200004272147.OAA45395@redpaul.mibh.net> References: <200004271826.OAA23896@iridium.mv.net> In-Reply-To: mem@mv.mv.com's message of "27 Apr 2000 11:22:33 -0700" X-UIDL: 4a81c6fe911aa9ad0d37a67c4361ec54 From: Paul A Vixie Sender: bsdi-users-return-2689-khera=kci.kcilink.com@mailinglists.org To: bsdi-users@bsdi.com Subject: Re: Cron setting SIGCHLD to SIG_IGN Date: Thu, 27 Apr 2000 14:47:02 -0700 mem@mv.mv.com ("Mark E. Mallett") writes: > Looking at the cron source code, I do see that cron is forcing > SIGCHLD to SIG_IGN for the children that it spawns. I'm afraid that > the reasoning behind this move escapes me. It's because cron (then called crond) was the first program I ever wrote that used signals or called fork or exec. This was in 1986, just after 4.3BSD came out, and well before signals had been posixified. signal(2) says, quite clearly: When a process which has installed signal handlers forks, the child pro- cess inherits the signals. All caught signals may be reset to their de- fault action by a call to the execve(2) function; ignored signals remain ignored. This means that having set SIGCHLD to SIG_IGN for my own purposes, I really needed (and apparently still need) to set it back to SIG_DFL before fork()'ing to run each command found in a crontab. Ouch! Sorry, all. Here's a patch against cron 4.0 (see ftp://ftp.isc.org/isc/cron/, since this is more recent than what ships with BSD/OS). The patch ought to apply, with some fuzz, to the shipping version. Index: do_command.c =================================================================== RCS file: /proj/src/isc/cvs-1/cron/do_command.c,v retrieving revision 1.4 diff -u -r1.4 do_command.c --- do_command.c 2000/01/02 20:53:41 1.4 +++ do_command.c 2000/04/27 18:45:37 @@ -222,6 +222,13 @@ chdir(env_get("HOME", e->envp)); /* + * Since ignored signals remain ignored after fork()/exec(), + * we need to unignore our ignored signals before letting + * some unsuspecting user level command inherit them. + */ + (void) signal(SIGCHLD, SIG_DFL); + + /* * Exec the command. */ { --------------------------------------------------------------------- Searchable Archive: http://www.nexial.com/cgi-bin/bsdibody To unsubscribe, e-mail: bsdi-users-unsubscribe@mailinglists.org For additional commands, e-mail: bsdi-users-help@mailinglists.org --F8jIq+Bmm/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 8:19: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 88AA937BEFF for ; Fri, 28 Apr 2000 08:19:04 -0700 (PDT) (envelope-from joe@pavilion.net) Received: from genius.systems.pavilion.net (postfix@genius.systems.pavilion.net [212.74.1.100]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id QAA32639; Fri, 28 Apr 2000 16:16:13 +0100 (BST) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 2BEF8362; Fri, 28 Apr 2000 16:16:53 +0100 (BST) Date: Fri, 28 Apr 2000 16:16:53 +0100 From: Joe Karthauser To: Sheldon Hearn Cc: Clifton Royston , Jaime Bozza , freebsd-stable@FreeBSD.ORG Subject: Re: Perl Base Modules Message-ID: <20000428161652.O40708@pavilion.net> References: <20000306091538.B1871@lava.net> <12817.952371991@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <12817.952371991@axl.ops.uunet.co.za>; from sheldonh@uunet.co.za on Mon, Mar 06, 2000 at 09:46:31PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 09:46:31PM +0200, Sheldon Hearn wrote: > > > On Mon, 06 Mar 2000 09:15:39 -1000, Clifton Royston wrote: > > > Give it another chance? > > Actually, I'm more concerned with how we precisely denote on the vendor > branch the origin of the updates. How well the CPAN auto-updater thing > works is something of a side-issue at this point. > > Remember, the CPAN updates are going to get blown out of the water by > your next ``make world'' without some Makefile fiddling. basically, if > we're going to do this in the source tree without taking the files off > the vendor branch, we need a meaningful vendor release tag. Why does this happen? Isn't there a INC path for Perl, and shouldn't the locally installed modules come first? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 8:45:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id CDB1A37B822 for ; Fri, 28 Apr 2000 08:45:36 -0700 (PDT) (envelope-from mike@sentex.ca) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id LAA71279; Fri, 28 Apr 2000 11:45:34 -0400 (EDT) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id LAA24257; Fri, 28 Apr 2000 11:45:34 -0400 (EDT) Message-Id: <3.0.5.32.20000428114221.01c8ca50@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 28 Apr 2000 11:42:21 -0400 To: Troy Arie Cobb From: Mike Tancsa Subject: mlxcontrol (was RE: How good is AMI MegaRAID support?) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:24 AM 4/28/00 -0400, Troy Arie Cobb wrote: >I can't find this in 4.0-STABLE, cvsup'd just a few days ago. Can anyone >point >me to this tool? Also, you might get caught by this like me. Make sure you do a sh /dev/MAKEDEV mlx0 after you make world and kernel and reboot so that mlxcontrol works. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 9: 4:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from members.nyinet.com (members.nyinet.com [204.248.157.35]) by hub.freebsd.org (Postfix) with ESMTP id E4FB937BEFF for ; Fri, 28 Apr 2000 09:04:08 -0700 (PDT) (envelope-from javier@nyi.net) Received: from nyi.net (root@cpq.nyi.net [204.248.157.72]) by members.nyinet.com (8.9.3/8.9.3) with ESMTP id MAA80299 for ; Fri, 28 Apr 2000 12:03:22 GMT (envelope-from javier@nyi.net) Message-ID: <3909B6DF.8DAE389A@nyi.net> Date: Fri, 28 Apr 2000 12:05:51 -0400 From: Javier Frias Organization: NYI X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: DPT SmartRaid VI References: <20000428131619.K40708@pavilion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding the DPT SmartRaid series... they have been promising FreeBSD support for the SmartRaid VI series.... so far, i have not heard anything yet, anyone know the status of such port? URL: http://www.dpt.com/techsup/sr5drv.html -- MMM \|/ www __^__ (o o) @ @ (O-O) /(o o)\ -ooO-(_)-Ooo---oOO-(_)-OOo---oOO--(_)--OOo---oOO==(_)==OOo Javier A. Frias Sr. System Administrator The New York Internet Company 20 Exchange Place 21st Floor New York, N.Y. 10005 "Error #152 - Windows not found: (C)heer (P)arty (D)ance" --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 10:41:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-105.dsl.snfc21.pacbell.net [63.202.176.105]) by hub.freebsd.org (Postfix) with ESMTP id C38D537B558 for ; Fri, 28 Apr 2000 10:41:30 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00403; Fri, 28 Apr 2000 10:49:28 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004281749.KAA00403@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Powell Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Fri, 28 Apr 2000 13:11:14 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Apr 2000 10:49:27 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yep, 0,1,5,10 and 50 are the only levels we may require. Some sort of > FBSD management utility would be useful, although unlikely? Feedback from > the driver regarding array status would be very useful. The DPT driver > lacked this, requiring you to be able to hear the controllers alarm. This > is of course impractical with remotely based servers. The only driver with this capacity currently is that for Mylex adapters. I'm working with AMI to remedy the situation there. > > I have been using 4.x for our internal Squid proxy > > with great results. I didnt have problems with the AMI card, except that I > > could artificially wedge it under high load. There have been new patches > > to the driver, so its possible the problem has been fixed, but I havent had > > time to test that. > > Does anyone on the list know if this has been fixed? There's an issue with AMI controllers over-reporting the number of outstanding commands they can handle, which was worked around recently. I haven't been able to tie either of the outstanding problem reports directly to the driver or adapter; they both seem to be related to external symptoms. In summary, however, I would at this very moment recommend the Mylex adapter family over the AMI family. I'm hoping to bring things to a more equitable state in the coming months, but time alone will tell. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 11:43:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 23EFF37B86F for ; Fri, 28 Apr 2000 11:43:09 -0700 (PDT) (envelope-from king@sstar.com) Received: from jking ([134.132.75.164]) by sstar.com with SMTP (IPAD 2.52) id 4377500; Fri, 28 Apr 2000 13:43:04 -0500 Message-ID: <004d01bfb141$96fb5eb0$a44b8486@jking> From: "Jim King" To: "Mike Smith" Cc: References: <200004281749.KAA00403@mass.cdrom.com> Subject: Re: How good is AMI MegaRAID support? Date: Fri, 28 Apr 2000 13:43:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > In summary, however, I would at this very moment recommend the Mylex > adapter family over the AMI family. I'm hoping to bring things to a more > equitable state in the coming months, but time alone will tell. Are there any particular Mylex models to avoid, or that are highly recommended? Some of the older non-Ultra DAC960's are priced attractively on eBay. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 12: 9: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147]) by hub.freebsd.org (Postfix) with ESMTP id 8838B37BF78 for ; Fri, 28 Apr 2000 12:08:57 -0700 (PDT) (envelope-from mph@fabel.dk) Received: from fabel.dk ([195.249.202.137]) by fepC.post.tele.dk (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000428190855.YDMK7404.fepC.post.tele.dk@fabel.dk> for ; Fri, 28 Apr 2000 21:08:55 +0200 Message-ID: <3909E1BA.456F23CB@fabel.dk> Date: Fri, 28 Apr 2000 21:08:42 +0200 From: mph X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 12:17:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147]) by hub.freebsd.org (Postfix) with ESMTP id 2C64D37BEE3 for ; Fri, 28 Apr 2000 12:17:10 -0700 (PDT) (envelope-from mph@fabel.dk) Received: from fabel.dk ([195.249.202.137]) by fepC.post.tele.dk (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000428191709.YERL7404.fepC.post.tele.dk@fabel.dk> for ; Fri, 28 Apr 2000 21:17:09 +0200 Message-ID: <3909E3A7.533C2CBF@fabel.dk> Date: Fri, 28 Apr 2000 21:16:55 +0200 From: mph X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 12:17:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id 334F937BF89 for ; Fri, 28 Apr 2000 12:17:41 -0700 (PDT) (envelope-from mike@sentex.ca) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id PAA96821; Fri, 28 Apr 2000 15:17:35 -0400 (EDT) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id PAA05188; Fri, 28 Apr 2000 15:17:35 -0400 (EDT) Message-Id: <3.0.5.32.20000428151421.02505bf0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 28 Apr 2000 15:14:21 -0400 To: "Jim King" From: Mike Tancsa Subject: Re: How good is AMI MegaRAID support? Cc: In-Reply-To: <004d01bfb141$96fb5eb0$a44b8486@jking> References: <200004281749.KAA00403@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:43 PM 4/28/00 -0500, Jim King wrote: >Mike Smith wrote: >> In summary, however, I would at this very moment recommend the Mylex >> adapter family over the AMI family. I'm hoping to bring things to a more >> equitable state in the coming months, but time alone will tell. > >Are there any particular Mylex models to avoid, or that are highly >recommended? Some of the older non-Ultra DAC960's are priced attractively >on eBay. msmith is obviously the authority on this, but I have been using DAC960PL and the DAC960P/PD both bought on ebay actually with good results. More verbose output below.... mlx1: DAC960P/PD, 1 channel, firmware 3.51--48, 4MB RAM Hardware ID 0x03020101 Firmware ID 0x30043303 Configured/Actual channels 1/1 Max Targets 16 Max Tags 2 Max System Drives 32 Max Arms 8 Max Spans 4 DRAM/cache/flash/NVRAM size 4194304/3014656/262144/8192 DRAM type 0 Clock Speed 40ns Hardware Speed 280ns Max Commands 63 Max SG Entries 17 Max DP 256 Max IOD 765 Max Comb 304 Latency 45s SCSI Timeout 6s Min Free Lines 32 Rate Constant 50 MAXBLK 128 Blocking Factor 1 sectors Cache Line Size 16 blocks SCSI Capability 20MHz, 16 bit Firmware Build Number 0 Fault Management Type 1 and mlx0: DAC960PL, 1 channel, firmware 3.51--48, 32MB RAM Hardware ID 0x03020102 Firmware ID 0x30043303 Configured/Actual channels 1/1 Max Targets 16 Max Tags 2 Max System Drives 32 Max Arms 8 Max Spans 4 DRAM/cache/flash/NVRAM size 33554432/32178176/262144/8192 DRAM type 0 Clock Speed 40ns Hardware Speed 350ns Max Commands 63 Max SG Entries 17 Max DP 256 Max IOD 765 Max Comb 304 Latency 19s SCSI Timeout 6s Min Free Lines 32 Rate Constant 50 MAXBLK 128 Blocking Factor 1 sectors Cache Line Size 16 blocks SCSI Capability 10MHz, 16 bit Firmware Build Number 0 ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Sentex Communications mike@sentex.net Cambridge, Ontario Canada www.sentex.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 13:14: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.campbell-mithun.com (Mercury.campbell-mithun.com [192.159.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 6E7DF37BF63; Fri, 28 Apr 2000 13:14:02 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184]) by mercury.campbell-mithun.com (8.9.1a/8.9.1) with SMTP id PAA32214; Fri, 28 Apr 2000 15:14:01 -0500 Message-ID: <056e01bfb14e$54cefd00$b8209fc0@marlowe> From: "Shawn Barnhart" To: "Mike Smith" Cc: References: <200004281749.KAA00403@mass.cdrom.com> Subject: Re: How good is AMI MegaRAID support? Date: Fri, 28 Apr 2000 15:14:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | In summary, however, I would at this very moment recommend the Mylex | adapter family over the AMI family. I'm hoping to bring things to a more | equitable state in the coming months, but time alone will tell. Any idea if OEM'd DAC960s work as well? I have a couple of HP 'HPDA' controllers, which are actually Mylex DAC960PLs. They mate nicely with the HP Disk Arrays (5 x 1GB fast SCSI) also cluttering this place. When Linux first began supporting the DAC960s, the driver didn't support 2.x firmware revisions. Mylex were selling upgrades, but they told me mine wasn't upgradable. I'm not sure if the mention of HP earned me a blanket "No" or if there really is something 'different' about these. My experience with other HP OEM'd parts leads me to believe the big difference is in the sticker on the cache RAM and the BIOS splash text.. -- no .sigs due to patent problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 13:27:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id EB6D237B94B; Fri, 28 Apr 2000 13:27:19 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 199f3c0039bf924253955fca0afeedcc) with ESMTP id <20000428202714.CQQQ8821.relay02@chello.nl>; Fri, 28 Apr 2000 22:27:14 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id WAA00610; Fri, 28 Apr 2000 22:27:18 +0200 (CEST) (envelope-from wkb) Date: Fri, 28 Apr 2000 22:27:18 +0200 From: Wilko Bulte To: Shawn Barnhart Cc: Mike Smith , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? Message-ID: <20000428222718.A596@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <200004281749.KAA00403@mass.cdrom.com> <056e01bfb14e$54cefd00$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <056e01bfb14e$54cefd00$b8209fc0@marlowe>; from swb@grasslake.net on Fri, Apr 28, 2000 at 03:14:17PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 28, 2000 at 03:14:17PM -0500, Shawn Barnhart wrote: > | In summary, however, I would at this very moment recommend the Mylex > | adapter family over the AMI family. I'm hoping to bring things to a more > | equitable state in the coming months, but time alone will tell. > > Any idea if OEM'd DAC960s work as well? I have a couple of HP 'HPDA' > controllers, which are actually Mylex DAC960PLs. They mate nicely with the > HP Disk Arrays (5 x 1GB fast SCSI) also cluttering this place. > > When Linux first began supporting the DAC960s, the driver didn't support 2.x > firmware revisions. Mylex were selling upgrades, but they told me mine > wasn't upgradable. I'm not sure if the mention of HP earned me a blanket > "No" or if there really is something 'different' about these. My experience > with other HP OEM'd parts leads me to believe the big difference is in the > sticker on the cache RAM and the BIOS splash text.. Some of the early DAC960s (below a specific buildnr) cannot be upgraded past 2.x firmware. I went through this exercise once with a DEC StorageWorks RAidarray 230 which is also a DAC960 based array. -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 13:38:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 87AAB37B68D; Fri, 28 Apr 2000 13:38:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA66009; Fri, 28 Apr 2000 13:38:27 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 28 Apr 2000 13:38:27 -0700 (PDT) From: Kris Kennaway To: Robert Withrow Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sendmail missing? In-Reply-To: <200004271251.IAA75352@pobox.rwwa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Apr 2000, Robert Withrow wrote: > What I had in mind is that the install program, would install these things > much like it installs Linux compatibility now. This would give you the > best of both worlds: a complete and functional system at installation time, > and easy and modular update-ability/upgrade-ability in the future. > > Just an idea. It's an idea a lot of other people have had as well, but it requires work on sysinstall and possibly our package tools, which no-one has actually done in the last n years despite lots of comments about how good it would be. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 13:40:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 35D3737B988; Fri, 28 Apr 2000 13:40:55 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA67154; Fri, 28 Apr 2000 13:40:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 28 Apr 2000 13:40:54 -0700 (PDT) From: Kris Kennaway To: Alexander Frolkin Cc: Nader Turki , stable@FreeBSD.ORG Subject: Re: 4.x-stable-supfile In-Reply-To: <20000427201455.A749@gamma> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Apr 2000, Alexander Frolkin wrote: > > #cvs-crypto > > #src-crypto > > #src-secure > > #src-sys-crypto > > You need either the first one or the last three. The three src-* collections > make up cvs-crypto. "That is to say, if you want all of the crypto sources then ..." You can get away with: none, "src-crypto and src-secure", "src-sys-crypto" or "all (see above)" depending if you want: none of the crypto code; only userland crypto code; kernel crypto code; or both. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 14: 2:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41]) by hub.freebsd.org (Postfix) with ESMTP id 883D537B8FA; Fri, 28 Apr 2000 14:02:13 -0700 (PDT) (envelope-from sasha@frolkin.demon.co.uk) Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1) id 12lHuv-0002j3-00; Fri, 28 Apr 2000 22:03:17 +0100 Date: Fri, 28 Apr 2000 22:03:16 +0100 From: Alexander Frolkin To: Kris Kennaway Cc: Alexander Frolkin , Nader Turki , stable@FreeBSD.ORG Subject: Re: 4.x-stable-supfile Message-ID: <20000428220316.A10350@gamma> Reply-To: Alexander Frolkin References: <20000427201455.A749@gamma> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Kris Kennaway on Fri, Apr 28, 2000 at 01:40:54PM -0700 X-Operating-System: Linux 2.2.14 X-GPG-Key-Fingerprint: 6C84 3EB2 550E E581 62FA BB0C D510 B042 FD5C E7A7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 28, 2000 at 01:40:54PM -0700, Kris Kennaway wrote: > On Thu, 27 Apr 2000, Alexander Frolkin wrote: > > > > #cvs-crypto > > > #src-crypto > > > #src-secure > > > #src-sys-crypto > > > > You need either the first one or the last three. The three src-* collections > > make up cvs-crypto. > > "That is to say, if you want all of the crypto sources then ..." > > You can get away with: none, "src-crypto and src-secure", "src-sys-crypto" > or "all (see above)" depending if you want: none of the crypto code; only > userland crypto code; kernel crypto code; or both. I thought the crypto and secure sources are required for RELENG_4 (according to src/UPDATING) ? Alexander > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 14:13:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EED2337B552; Fri, 28 Apr 2000 14:13:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA79575; Fri, 28 Apr 2000 14:13:36 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 28 Apr 2000 14:13:36 -0700 (PDT) From: Kris Kennaway To: Alexander Frolkin Cc: Nader Turki , stable@FreeBSD.ORG Subject: Re: 4.x-stable-supfile In-Reply-To: <20000428220316.A10350@gamma> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Alexander Frolkin wrote: > I thought the crypto and secure sources are required for RELENG_4 (according > to src/UPDATING) ? They're "very useful", but I didn't think "mandatory". Crypto sources bring you OpenSSH out of the box, MS-CHAP authentication in PPP, IPSEC in the kernel, etc etc. I certainly recommend people install them unless they have reason not to. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 16: 0: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id CE7FC37BA43 for ; Fri, 28 Apr 2000 16:00:04 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA00828; Fri, 28 Apr 2000 16:08:07 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004282308.QAA00828@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jim King" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Fri, 28 Apr 2000 13:43:04 CDT." <004d01bfb141$96fb5eb0$a44b8486@jking> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Apr 2000 16:08:06 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > In summary, however, I would at this very moment recommend the Mylex > > adapter family over the AMI family. I'm hoping to bring things to a more > > equitable state in the coming months, but time alone will tell. > > Are there any particular Mylex models to avoid, or that are highly > recommended? Some of the older non-Ultra DAC960's are priced attractively > on eBay. Not particularly. As a general rule, you want the 3.x or later firmware, although what testing I've done with the later 2.x revisions hasn't shown anything really bad up. The 4.x firmware also adds the stand-alone array management tools, which are nice to have. One advantage you have with the FreeBSD driver is that we support the 2.x firmware (one flash chip, rather than two), wheras the Linux folks don't. Performance on these low-end adapters is fairly similar between the 2.x and 3.x firmware, so you can sometimes score a real bargain if you're just looking for something to play with. (The 2.x firmware has had a long life largely because it's what Compaq are still using in some of their Alpha systems. I recommend 2.70 at the moment, but a flash upgrade is fairly easy.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 16: 9:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id CF43737BA3C; Fri, 28 Apr 2000 16:09:11 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA00923; Fri, 28 Apr 2000 16:16:42 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004282316.QAA00923@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Shawn Barnhart" Cc: "Mike Smith" , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Fri, 28 Apr 2000 15:14:17 CDT." <056e01bfb14e$54cefd00$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Apr 2000 16:16:42 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | In summary, however, I would at this very moment recommend the Mylex > | adapter family over the AMI family. I'm hoping to bring things to a more > | equitable state in the coming months, but time alone will tell. > > Any idea if OEM'd DAC960s work as well? I have a couple of HP 'HPDA' > controllers, which are actually Mylex DAC960PLs. They mate nicely with the > HP Disk Arrays (5 x 1GB fast SCSI) also cluttering this place. They should, although there are apparently some HP-specific oddities inside the firmware. If you use a non-HP setup utility, it should clear the "HP mode" bit, which will turn it into a standard controller. The AMI driver also supports the later HP NetRAID controllers. > When Linux first began supporting the DAC960s, the driver didn't support 2.x > firmware revisions. Mylex were selling upgrades, but they told me mine > wasn't upgradable. I'm not sure if the mention of HP earned me a blanket > "No" or if there really is something 'different' about these. My experience > with other HP OEM'd parts leads me to believe the big difference is in the > sticker on the cache RAM and the BIOS splash text.. Linux still doesn't, to the best of my knowledge, support the 2.x firmware. I spent quite a bit of time chasing the documentation due to the 2.x firmware's heavy use in Digital/Compaq systems. I'd strongly advise updating to 2.42 or later firmware (2.70 preferable). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 16:10:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 759BF37BFC8; Fri, 28 Apr 2000 16:10:41 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA00966; Fri, 28 Apr 2000 16:18:11 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004282318.QAA00966@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: wc.bulte@chello.nl Cc: Shawn Barnhart , Mike Smith , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Fri, 28 Apr 2000 22:27:18 +0200." <20000428222718.A596@yedi.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Apr 2000 16:18:11 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Some of the early DAC960s (below a specific buildnr) cannot be upgraded past > 2.x firmware. I went through this exercise once with a DEC StorageWorks > RAidarray 230 which is also a DAC960 based array. Actually, the issue is much simpler than this (with the PCI adapters) - the 2.x firmware fits in one flash part, while the 3.x firmware needs two. Many of the 2.x-vintage adapters around have two sockets, but the 2.x firmware doesn't know how to talk to the second one to step you up to 3.x. In other words, unless you go to Mylex and buy a 2.x-3.x upgrade kit (new chips), you have to stay with 2.x. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 17:47:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 2684037BFCE for ; Fri, 28 Apr 2000 17:47:28 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115205>; Sat, 29 Apr 2000 10:47:53 +1000 From: Peter Jeremy Subject: Re: sio interrupt handler problem In-reply-to: <5564.000424@pd.chel.ru>; from lw@pd.chel.ru on Mon, Apr 24, 2000 at 05:34:37PM +1000 To: "Sergey A. Ivanov" Cc: freebsd-stable@FreeBSD.ORG Message-Id: <00Apr29.104753est.115205@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <5564.000424@pd.chel.ru> Date: Sat, 29 Apr 2000 10:47:49 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 24, 2000 at 05:34:37PM +1000, Sergey A. Ivanov wrote: > I have 4.0S installed on old 468dx66. Part of dmesg: > >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >sio0: type 16450 [Gives SILO overflows at 38.4k] I agree that 16450's are best avoided, but this should still work. I can get 38.4k through a 16450 using pppd in 2.2.5 on a 386DX25 (though it won't do 57.6k). A 486dx66 has about 5 times the CPU power, the overall system should be at least twice as fast. I don't believe that 4.0S has more than doubled the interrupt overheads, so there must be some other explanation. What other related activity do you have? Are you loading the other serial port or parallel port? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 17:47:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id BFD9E37BFE8 for ; Fri, 28 Apr 2000 17:47:32 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115210>; Sat, 29 Apr 2000 10:47:53 +1000 From: Peter Jeremy Subject: Re: removed files In-reply-to: ; from domi@saargate.de on Tue, Apr 25, 2000 at 11:57:17PM +1000 To: Dominik Brettnacher Cc: stable@FreeBSD.ORG Message-Id: <00Apr29.104753est.115210@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: Date: Sat, 29 Apr 2000 10:47:52 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 25, 2000 at 11:57:17PM +1000, Dominik Brettnacher wrote: >is there a list available that contains all files/programs which were >removed from FreeBSD? AFAIK, there isn't in this form. You could go through the CVS commit logs looking at what was deleted, but that is probably fairly time consuming. One alternative is "find -x / /usr /var -mtime +N", where N is the number of days since your last installworld. This falls down in /usr/include (where identical files are not updated). Another option (if you've got a recent CD-ROM) is to mount the live filesystem and compare the contents: find -x / /usr /var | sort -o /tmp/myfiles find /cdrom | sort -o /tmp/newfiles diff /tmp/myfiles /tmp/newfiles Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 18:17: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.campbell-mithun.com (Mercury.campbell-mithun.com [192.159.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 4FAE737B682; Fri, 28 Apr 2000 18:17:01 -0700 (PDT) (envelope-from swb@accord.grasslake.net) Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by mercury.campbell-mithun.com (8.9.1a/8.9.1) with ESMTP id UAA03134; Fri, 28 Apr 2000 20:16:58 -0500 Received: from localhost (swb@localhost) by accord.grasslake.net (8.9.3/8.9.3) with ESMTP id UAA57486; Fri, 28 Apr 2000 20:16:40 -0500 (CDT) (envelope-from swb@accord.grasslake.net) Date: Fri, 28 Apr 2000 20:16:39 -0500 (CDT) From: Shawn Barnhart To: Mike Smith Cc: wc.bulte@chello.nl, freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-Reply-To: <200004282318.QAA00966@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Mike Smith wrote: > > Some of the early DAC960s (below a specific buildnr) cannot be upgraded past > > 2.x firmware. I went through this exercise once with a DEC StorageWorks > > RAidarray 230 which is also a DAC960 based array. > > Actually, the issue is much simpler than this (with the PCI adapters) - > the 2.x firmware fits in one flash part, while the 3.x firmware needs > two. Many of the 2.x-vintage adapters around have two sockets, but the > 2.x firmware doesn't know how to talk to the second one to step you up to > 3.x. > > In other words, unless you go to Mylex and buy a 2.x-3.x upgrade kit (new > chips), you have to stay with 2.x. Is it really that simple? I'm noticing that my DAC960PL-2 (HPDA) controller does indeed have two flash slots. Mylex web site claim that you need manufacturer's model number D040347 or later. Mine is D040345. Since I have three of these cards (all PCI HPDA OEM'd, all old firmware) I'm sorely tempted to either try to flash them to 2.73 or just buy an upgrade kit from Mylex and see what it does for me, since it's all of $60. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 21:31:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id 0C1FD37B735 for ; Fri, 28 Apr 2000 21:31:19 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id AAA65796 for freebsd-stable@freebsd.org; Sat, 29 Apr 2000 00:31:14 -0400 (EDT) (envelope-from ray) Date: Sat, 29 Apr 2000 00:31:13 -0400 From: Ray Kohler To: freebsd-stable@freebsd.org Subject: syntax errors in netinet/in.h Message-ID: <20000429003113.A65770@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I discovered that there is something missing from netinet/in.h. Including it in anything causes errors, due to it not knowing about u_int32_t. I would guess that something needs to be included here, but I don't know the include tree well enough to figure out what, not to mention, I certainly can't fix it for everybody else. Anyone want to fix this? -- Ray Kohler FreeBSD -- The Power to Serve God is Dead -- Nietzsche Nietzsche is Dead -- God Nietzsche is God -- The Dead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Apr 28 22:28:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B823437B723 for ; Fri, 28 Apr 2000 22:28:19 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id WAA20059; Fri, 28 Apr 2000 22:28:16 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 28 Apr 2000 22:28:16 -0700 (PDT) From: Doug White To: Cy Schubert - ITSD Open Systems Group Cc: Matthew Dillon , freebsd-stable@FreeBSD.ORG Subject: Re: Linux Emulation Root (was: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday) In-Reply-To: <200004251530.IAA07614@passer.osg.gov.bc.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Apr 2000, Cy Schubert wrote: > > I ran into a similar problem with ADSM -- it would happily back up > > /compat/linux thinking it was backing up /. I patched the linux mode KLD > > to disable the /compat/linux path munging. I tried to submit it back but > > was shot down; the emulation people wanted a more general method, which I > > assume included a way to define your own 'linux root'. The discussion got > > lost some time after that in -emulation. > > Legato for Linux backs up /, it just cannot restore to it. Instead if > you restore for example restore /etc/rc.local, it's restored to > /compat/linux/etc/rc.local. Any redirection using the Legato recover > subcommand relocate to /etc does not work. Mounting a unionfs (or nullfs) > of / on some other directory and redirecting the restore to it does work. You'll want my non-munging linux module patches if you ever want to restore :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 0: 6: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 2513037B747 for ; Sat, 29 Apr 2000 00:05:54 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id AAA04722; Sat, 29 Apr 2000 00:05:51 -0700 (PDT) Date: Sat, 29 Apr 2000 00:05:51 -0700 From: Brooks Davis To: rjk191@psu.edu Cc: freebsd-stable@FreeBSD.ORG Subject: Re: syntax errors in netinet/in.h Message-ID: <20000429000551.A4181@orion.ac.hmc.edu> References: <20000429003113.A65770@rjk191.rh.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000429003113.A65770@rjk191.rh.psu.edu>; from ray@rjk191.rh.psu.edu on Sat, Apr 29, 2000 at 12:31:13AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 29, 2000 at 12:31:13AM -0400, Ray Kohler wrote: > Today I discovered that there is something missing from > netinet/in.h. Including it in anything causes errors, due to it not > knowing about u_int32_t. I would guess that something needs to be > included here, but I don't know the include tree well enough to > figure out what, not to mention, I certainly can't fix it for > everybody else. Anyone want to fix this? You need to include sys/types.h first. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 0:21:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 32A0137B52D for ; Sat, 29 Apr 2000 00:21:10 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12lQ4V-0007HC-00; Sat, 29 Apr 2000 06:45:43 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12lQ4U-000Jp3-00; Sat, 29 Apr 2000 06:45:42 +0100 Date: Sat, 29 Apr 2000 06:45:42 +0100 From: Ben Smithurst To: rjk191@psu.edu Cc: freebsd-stable@freebsd.org Subject: Re: syntax errors in netinet/in.h Message-ID: <20000429064542.K17098@strontium.scientia.demon.co.uk> References: <20000429003113.A65770@rjk191.rh.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000429003113.A65770@rjk191.rh.psu.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ray Kohler wrote: > Today I discovered that there is something missing from > netinet/in.h. Including it in anything causes errors, due to it not > knowing about u_int32_t. I would guess that something needs to be > included here, but I don't know the include tree well enough to > figure out what, not to mention, I certainly can't fix it for > everybody else. Anyone want to fix this? I think you'll need to #include in your program before . Which function are you using whose manpage doesn't state to include before ? That manpage would probably require fixing if there is such an example. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 0:50:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182]) by hub.freebsd.org (Postfix) with ESMTP id 4F7E137B76B for ; Sat, 29 Apr 2000 00:50:16 -0700 (PDT) (envelope-from ray@rjk191.rh.psu.edu) Received: (from ray@localhost) by rjk191.rh.psu.edu (8.9.3/8.9.3) id DAA91611 for freebsd-stable@freebsd.org; Sat, 29 Apr 2000 03:50:10 -0400 (EDT) (envelope-from ray) Date: Sat, 29 Apr 2000 03:50:09 -0400 From: Ray Kohler To: freebsd-stable@freebsd.org Subject: Re: syntax errors in netinet/in.h Message-ID: <20000429035009.A91597@rjk191.rh.psu.edu> Reply-To: rjk191@psu.edu References: <20000429003113.A65770@rjk191.rh.psu.edu> <20000429064542.K17098@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000429064542.K17098@strontium.scientia.demon.co.uk>; from ben@scientia.demon.co.uk on Sat, Apr 29, 2000 at 06:45:42AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 29, 2000 at 06:45:42AM +0100, Ben Smithurst wrote: > Ray Kohler wrote: > > > Today I discovered that there is something missing from > > netinet/in.h. Including it in anything causes errors, due to it not > > knowing about u_int32_t. I would guess that something needs to be > > included here, but I don't know the include tree well enough to > > figure out what, not to mention, I certainly can't fix it for > > everybody else. Anyone want to fix this? > > I think you'll need to #include in your program before > . Which function are you using whose manpage doesn't > state to include before ? That manpage > would probably require fixing if there is such an example. I was trying to compile wine, and wrote a small test program that included without using anything in it because I wanted to investigate some compile errors with wine. It turns out that the problem there was that the files were included in the wrong order, anyway. -- Ray Kohler FreeBSD -- The Power to Serve "The sooner all the animals are dead, the sooner we'll find their money." -- Ed Bluestone, "The National Lampoon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 2: 9:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id B6E2337B646; Sat, 29 Apr 2000 02:09:26 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 199f3c0039bf924253955fca0afeedcc) with ESMTP id <20000429090937.FETK16343.relay01@chello.nl>; Sat, 29 Apr 2000 11:09:37 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id LAA00426; Sat, 29 Apr 2000 11:09:22 +0200 (CEST) (envelope-from wkb) Date: Sat, 29 Apr 2000 11:09:22 +0200 From: Wilko Bulte To: Mike Smith Cc: wc.bulte@chello.nl, Shawn Barnhart , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? Message-ID: <20000429110922.A383@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000428222718.A596@yedi.wbnet> <200004282318.QAA00966@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004282318.QAA00966@mass.cdrom.com>; from msmith@FreeBSD.ORG on Fri, Apr 28, 2000 at 04:18:11PM -0700 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 28, 2000 at 04:18:11PM -0700, Mike Smith wrote: > > Some of the early DAC960s (below a specific buildnr) cannot be upgraded past > > 2.x firmware. I went through this exercise once with a DEC StorageWorks > > RAidarray 230 which is also a DAC960 based array. > > Actually, the issue is much simpler than this (with the PCI adapters) - > the 2.x firmware fits in one flash part, while the 3.x firmware needs > two. Many of the 2.x-vintage adapters around have two sockets, but the > 2.x firmware doesn't know how to talk to the second one to step you up to > 3.x. Most DEC RA230 I have seen only had one flash chip (in a socket). There was no second socket. But you might be lucky and have one with a second socket. Or solder a 2nd onto the board (it is SMD..) -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 5:41: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zmail6.easynet.fr (email.easynet.fr [195.114.64.207]) by hub.freebsd.org (Postfix) with SMTP id 5699537B86D for ; Sat, 29 Apr 2000 05:40:54 -0700 (PDT) (envelope-from fonvi@easynet.fr) Received: (qmail 12174 invoked from network); 29 Apr 2000 12:40:47 -0000 Received: from mailgate2.easynet.fr (192.168.1.3) by mailserver.easynet.fr with QMQP; 29 Apr 2000 12:40:47 -0000 Received: from adsl-92-1-135.pops.easynet.fr (HELO vobiscum.styx.org) (212.11.34.135) by mrelay2.easynet.fr with SMTP; 29 Apr 2000 12:40:47 -0000 Received: (from marc@localhost) by vobiscum.styx.org (8.9.3/8.9.3/ - 6/08/98) id OAA01958; Sat, 29 Apr 2000 14:41:33 +0200 (CEST) (envelope-from marc) Date: Sat, 29 Apr 2000 14:41:33 +0200 From: Marc Fonvieille To: freebsd-stable@freebsd.org Cc: Philippe Thin Subject: "/kernel: invalid state: 0x1" with ipfw under 4.0S Message-ID: <20000429144133.A1225@vobiscum.styx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Useless-Header: Black Metal inc. X-Operating-System: FreeBSD 4.0-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Since, i'm using 4.0, i've got a lot of: /kernel: invalid state: 0x1 or /kernel: invalid state: 0x0 in my logs. I use ipfw's stateful features, here's my rules: 00100 0 0 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 allow ip from 192.168.1.200 to 192.168.1.0/24 out xmit ed1 00400 0 0 allow ip from 192.168.1.0/24 to 192.168.1.200 in recv ed1 00500 0 0 check-state 00600 0 0 allow ip from any to any keep-state out xmit ppp0 00700 0 0 allow ip from any to any via ed0 00800 0 0 deny log logamount 1000 ip from 127.0.0.0/8 to 127.0.0.0/8 in recv ppp0 00900 0 0 deny log logamount 1000 ip from 192.168.0.0/16 to any in recv ppp0 01000 0 0 deny log logamount 1000 ip from 172.16.0.0/12 to any in recv ppp0 01100 0 0 deny log logamount 1000 ip from 10.0.0.0/8 to any in recv ppp0 01200 0 0 deny log logamount 1000 ip from any to 192.168.1.0/24 in recv ppp0 01300 0 0 reset tcp from any to any 113 in recv ppp0 01400 0 0 allow icmp from any to any in recv ppp0 icmptype 3 01500 0 0 allow icmp from any to any in recv ppp0 icmptype 11 01600 0 0 deny tcp from any 80 to any in recv ppp0 65534 0 0 deny log logamount 1000 ip from any to any 65535 0 0 deny ip from any to any I had no problems with these rules under 3.4S I know there was some changes in source of ip_fw.c between 3.4S and 4.0S: in 4.0S: default: /* reset or some invalid combination */ if ( (q->state & ((TH_RST << 8)|TH_RST)) == 0) printf("invalid state: 0x%x\n", q->state); q->expire = time_second + dyn_rst_lifetime ; break ; in 3.4S: default: #if 0 /* reset or some invalid combination, but can also * occur if we use keep-state the wrong way. */ if ( (q->state & ((TH_RST << 8)|TH_RST)) == 0) printf("invalid state: 0x%x\n", q->state); #endif q->expire = time_second + dyn_rst_lifetime ; break ; If i understand this code in 3.4 the #if and #endif avoid the print of invalid state in my logs. So what should i do to avoid these msgs under 4.0S without change the ip_fw.c? Maybe my rules are wrong? Thanks for any advice. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 7:29:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 76DB037B56B for ; Sat, 29 Apr 2000 07:29:13 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA17706; Sat, 29 Apr 2000 07:27:56 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda17704; Sat Apr 29 07:27:46 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA00614; Sat, 29 Apr 2000 07:27:45 -0700 (PDT) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdRdH612; Sat Apr 29 07:26:59 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.10.1/8.9.1) id e3TEQv022436; Sat, 29 Apr 2000 07:26:57 -0700 (PDT) Message-Id: <200004291426.e3TEQv022436@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdz22271; Sat Apr 29 07:26:19 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.0-STABLE X-Sender: cy To: chad@DCFinc.com Cc: andrews@technologist.com (Will Andrews), jim@luna.cdrom.com, stable@FreeBSD.ORG Subject: Re: sendmail missing? In-reply-to: Your message of "Wed, 26 Apr 2000 21:21:49 PDT." <200004270421.VAA00981@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Apr 2000 07:26:19 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004270421.VAA00981@freeway.dcfinc.com>, "Chad R. Larson" writes: > As I recall, Will Andrews wrote: > > I'm sure that if you pony up the port, someone with the inclination > > will add it to the ports tree. You could go look up the archives to > > see whether this sort of thing has been discussed before, and take > > appropriate action. > > I did check the archives, there was no thread that seemed to apply. > > But it makes sense to me to have a port, for the same reason it made > sense to have a port for bind. What started this for me was a > desire to pick up some of features in 8.10, and the base system is > currently using 8.9. > > It's true that grabbing the sources from Sendmail.org into > /usr/local/src and building them is not tricky (especially given > that Eric Allman is a CRSG luminary), but a port could automate > that. An approach the port (or other software) could use is fetch sendmail, bind, whatever, off the Net, as ports normally do, and extract them in the /usr/src/contrib directory. I've done this before with cvs and ipfilter. Just extract sendmail in /usr/src/contrib and your next make world would pick it up, assuming you've set up cvsup correctly. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 9: 8:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 80C2A37B6F8 for ; Sat, 29 Apr 2000 09:08:40 -0700 (PDT) (envelope-from brameld@twave.net) Received: from [208.47.188.65] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ja138823 for ; Sat, 29 Apr 2000 12:08:25 -0400 From: Walter Brameld To: freebsd-stable@freebsd.org Subject: Communication prohibited by filter ?? Date: Sat, 29 Apr 2000 12:03:09 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00042912082400.00428@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After doing a make world a few days ago and again this morning, when I try to run knapster it tells me it can't connect to the server. When I ping the server I get the following message: PING server.napster.com (208.184.216.222): 56 data bytes 36 bytes from 208.184.169.39.napster.com (208.184.169.39): Communication prohibi ted by filter Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 07b0 0 0000 f3 01 89f0 208.47.188.65 208.184.216.222 Can someone give me a clue as to what is causing this? I am not behind a firewall and am running 4.0-STABLE. Thanks in advance. -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: And what does THIS button do?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 9:12:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 8C1DA37B5C0 for ; Sat, 29 Apr 2000 09:12:51 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 709803E47; Sat, 29 Apr 2000 18:12:50 +0200 (CEST) Date: Sat, 29 Apr 2000 18:12:50 +0200 From: Jesper Skriver To: Walter Brameld Cc: freebsd-stable@freebsd.org Subject: Re: Communication prohibited by filter ?? Message-ID: <20000429181250.D30793@skriver.dk> References: <00042912082400.00428@Bozo_3.BozoLand.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <00042912082400.00428@Bozo_3.BozoLand.domain>; from brameld@twave.net on Sat, Apr 29, 2000 at 12:03:09PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 29, 2000 at 12:03:09PM -0400, Walter Brameld wrote: > After doing a make world a few days ago and again this morning, when I > try to run knapster it tells me it can't connect to the server. When I > ping the server I get the following message: > > PING server.napster.com (208.184.216.222): 56 data bytes > 36 bytes from 208.184.169.39.napster.com (208.184.169.39): Communication prohibi > ted by filter > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 5400 07b0 0 0000 f3 01 89f0 208.47.188.65 208.184.216.222 > > Can someone give me a clue as to what is causing this? I am not behind > a firewall and am running 4.0-STABLE. It's 208.184.169.39.napster.com that has a filter that deny your ping, but I cannot help you why knapster isn't working. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 9:17:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id D97E737B58D for ; Sat, 29 Apr 2000 09:17:25 -0700 (PDT) (envelope-from brameld@twave.net) Received: from [208.47.188.65] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ka138876 for ; Sat, 29 Apr 2000 12:17:19 -0400 From: Walter Brameld To: Jesper Skriver Subject: Re: Communication prohibited by filter ?? Date: Sat, 29 Apr 2000 12:16:40 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-stable@freebsd.org References: <00042912082400.00428@Bozo_3.BozoLand.domain> <20000429181250.D30793@skriver.dk> In-Reply-To: <20000429181250.D30793@skriver.dk> MIME-Version: 1.0 Message-Id: <00042912171601.00428@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Apr 2000, in a never-ending search for enlightenment, Jesper Skriver wrote: > On Sat, Apr 29, 2000 at 12:03:09PM -0400, Walter Brameld wrote: > > After doing a make world a few days ago and again this morning, when I > > try to run knapster it tells me it can't connect to the server. When I > > ping the server I get the following message: > > > > PING server.napster.com (208.184.216.222): 56 data bytes > > 36 bytes from 208.184.169.39.napster.com (208.184.169.39): Communication prohibi > > ted by filter > > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > > 4 5 00 5400 07b0 0 0000 f3 01 89f0 208.47.188.65 208.184.216.222 > > > > Can someone give me a clue as to what is causing this? I am not behind > > a firewall and am running 4.0-STABLE. > > It's 208.184.169.39.napster.com that has a filter that deny your ping, > but I cannot help you why knapster isn't working. > > /Jesper So you're saying it's the far end sending me that message, and not my machine? -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: And what does THIS button do?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 9:28:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id 3B62737B6E5 for ; Sat, 29 Apr 2000 09:28:12 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.3/8.9.3) with ESMTP id MAA20236; Sat, 29 Apr 2000 12:28:08 -0400 (EDT) (envelope-from melange@yip.org) Date: Sat, 29 Apr 2000 12:28:08 -0400 (EDT) From: Bob K X-Sender: melange@localhost To: Walter Brameld Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Communication prohibited by filter ?? In-Reply-To: <00042912171601.00428@Bozo_3.BozoLand.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > PING server.napster.com (208.184.216.222): 56 data bytes > > > 36 bytes from 208.184.169.39.napster.com (208.184.169.39): Communication prohibi > > > ted by filter > > > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > > > 4 5 00 5400 07b0 0 0000 f3 01 89f0 208.47.188.65 208.184.216.222 [snip] > So you're saying it's the far end sending me that message, and not my > machine? That is correct - however, all you can tell about this is that 208.184.169.39 is blocking ICMP_ECHO packets, not necessarily other forms of traffic. Do you know what port/protocol knapster is trying to connect to? If it's tcp, you could test that manually with: telnet server.napster.com (insert port # here) and see if it connects. -- Bob "Reality is the only word in the language that should always be used in quotes" - My Life With The Thrill Kill Kult sample To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 9:31:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id D1B4137B6A0 for ; Sat, 29 Apr 2000 09:31:43 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id MAA21331; Sat, 29 Apr 2000 12:31:51 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sat, 29 Apr 2000 12:31:51 -0400 (EDT) From: "Brandon D. Valentine" To: Mark Powell Cc: Joe Karthauser , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Mark Powell wrote: >I appreciate the good work Simon and Mike are doing in this area. However, >I wanted to know what is the current RAID solution of choice for FreeBSD. >As I'm sure you understand I need a proven solution. I can definitely appreciate that. The RAID solution of choice for FreeBSD appears to be SCSI-SCSI RAID adapters as utilized on wcarchive.cdrom.com and ftp.freesoftware.org -- the two busiest ftp archives around and consequently the two busiest disk subsystems around. Both of these configations utilize the latest Adaptec 78xx based PCI SCSI controller attached to a SCSI-SCSI RAID adapter. In the case of wcarchive it is a Mylex DAC960SXI SCSI-SCSI 6 channel RAID controller, w/256MB cache. ftp.freesoftware.org doesn't reveal to us what sort of SCSI-SCSI RAID controller is in use but I would assume it's the same or similiar to wcarchive since TeraSolutins, Inc. had a hand in both systems. This approach does offer a layer of protection from scsi controller obsolesences or driver bitrot. You put a relatively cheap well supported SCSI controller in your machine and interface it to your external RAID canister. That controller can be replaced and upgraded as necessary while still keeping the same disk subsystem behind it. It also allows you to forget about bugs in the raid code or availability of something like mlxcontrol since it's all handled in hardware. You can also attach multiple hosts to the RAID canister, allowing more than one system to use the same disks. That can also come in handy if you need redundant servers but don't want to mirror all of your content. The decision all comes down to just how future proof you need to be and how much money you have to sink into your project. Brandon D. Valentine -- bandix@looksharp.net Illegitimi non carborundum. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 10: 6: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 321B037B787 for ; Sat, 29 Apr 2000 10:05:58 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id TAA24638; Sat, 29 Apr 2000 19:06:24 +0200 (MET DST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 12lah0-0002pq-00 for ; Sat, 29 Apr 2000 19:06:10 +0200 Date: Sat, 29 Apr 2000 19:06:10 +0200 From: Szilveszter Adam To: freebsd-stable@freebsd.org Subject: Re: Communication prohibited by filter ?? Message-ID: <20000429190610.A9052@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-stable@freebsd.org References: <00042912082400.00428@Bozo_3.BozoLand.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <00042912082400.00428@Bozo_3.BozoLand.domain>; from brameld@twave.net on Sat, Apr 29, 2000 at 12:03:09PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Sat, Apr 29, 2000 at 12:03:09PM -0400, Walter Brameld wrote: > After doing a make world a few days ago and again this morning, when I > try to run knapster it tells me it can't connect to the server. When I Well, I have been getting the same error using the console napster client for BSD (nap-0.9b from ports) it says "Error connecting socket". Now, I remembered, that this was last displayed when an upgrade was needed to the client. However, there was no new port available so I went straight to the author's home page only to find that it had an upgarde for Linux (1.1beta) but none for BSD. I downloaded it and installed it, and whooops: everything worked again. So I must assume that the folks at Napster did change the protocol again and so broke backward compatibility, but since they use closed-source sw, they did not tell anyone. And it also led me to conclude that the author of this particular client was somewhat Linux-centric beacuse he updated the Linux client twice already, but the BSD client remained unchanged. I must assume that other clients not officially supported by Napster (that is, all clients apart from the Windows platform) were hit by this, too. Of course, I could use the Linux client just fine, but it has a problem with our syscons somwhere, because it just works great on a Debian 2.1 box over here but on FreeBSD no matter what, it always does this: you enter a character and it automatically starts a new line below the current one. What you typed appears in the new line too. So if you type: /search, you will have 7 lines, with each one having one character more of your input. If you hit "Enter" and the screen gets repainted, everything goes back to normal but as soon as you type it hits again. This is very annoying because these lines can easily take up half of your screen and push the main window out of sight. (NB the same thing happens when I connect to the Linux box via ssh. If I use it via console, it works normally. So it is definately FreeBSD-related. Weird...) Just my observations... Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 10:38:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 3224437B63B for ; Sat, 29 Apr 2000 10:38:47 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA37866; Sat, 29 Apr 2000 19:39:33 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200004291739.TAA37866@info.iet.unipi.it> Subject: Re: "/kernel: invalid state: 0x1" with ipfw under 4.0S In-Reply-To: <20000429144133.A1225@vobiscum.styx.org> from Marc Fonvieille at "Apr 29, 2000 02:41:33 pm" To: Marc Fonvieille Date: Sat, 29 Apr 2000 19:39:33 +0200 (CEST) Cc: freebsd-stable@FreeBSD.ORG, Philippe Thin X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, keep-state is only significant with TCP and to a lesser extent UDP. i think changing your rule 600 from "ip" to "tcp" (and maybe adding another one for UDP) is probably going to fix this problem. But thanks for looking at the diffs between 3.4S and 4.0 -- i forgot to ifdef-out the code in 4.0S (such code is only significant for TCP). cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 12:46:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41]) by hub.freebsd.org (Postfix) with ESMTP id 365DA37B5B6 for ; Sat, 29 Apr 2000 12:46:15 -0700 (PDT) (envelope-from sasha@frolkin.demon.co.uk) Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1) id 12ldCJ-00004p-00; Sat, 29 Apr 2000 20:46:39 +0100 Date: Sat, 29 Apr 2000 20:46:39 +0100 From: Alexander Frolkin To: Brian Somers Cc: stable@freebsd.org Subject: Portmap strangeness Message-ID: <20000429204638.A227@gamma> Reply-To: Alexander Frolkin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Operating-System: Linux 2.2.14 X-GPG-Key-Fingerprint: 6C84 3EB2 550E E581 62FA BB0C D510 B042 FD5C E7A7 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is just to say that I've cvsupped (on the 28th) and portmap is now working normally. Alexander. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 12:58:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-65.dsl.snfc21.pacbell.net [63.202.176.65]) by hub.freebsd.org (Postfix) with ESMTP id ECAE737B6A3 for ; Sat, 29 Apr 2000 12:58:15 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA00970; Sat, 29 Apr 2000 13:04:40 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004292004.NAA00970@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Shawn Barnhart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Fri, 28 Apr 2000 20:16:39 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Apr 2000 13:04:40 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In other words, unless you go to Mylex and buy a 2.x-3.x upgrade kit (new > > chips), you have to stay with 2.x. > > Is it really that simple? I'm noticing that my DAC960PL-2 (HPDA) controller > does indeed have two flash slots. Mylex web site claim that you need > manufacturer's model number D040347 or later. Mine is D040345. If that's what they say, I'd be inclined to believe them. Since I've not encountered any fatal problems with the 2.x firmware, I can't suggest that upgrading would actually win you very much. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 13: 6:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-65.dsl.snfc21.pacbell.net [63.202.176.65]) by hub.freebsd.org (Postfix) with ESMTP id BA20037B5E3 for ; Sat, 29 Apr 2000 13:06:08 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01003; Sat, 29 Apr 2000 13:13:37 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004292013.NAA01003@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Brandon D. Valentine" Cc: Mark Powell , Joe Karthauser , freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Sat, 29 Apr 2000 12:31:51 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Apr 2000 13:13:37 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 28 Apr 2000, Mark Powell wrote: > > >I appreciate the good work Simon and Mike are doing in this area. However, > >I wanted to know what is the current RAID solution of choice for FreeBSD. > >As I'm sure you understand I need a proven solution. > > I can definitely appreciate that. The RAID solution of choice for > FreeBSD appears to be SCSI-SCSI RAID adapters as utilized on > wcarchive.cdrom.com and ftp.freesoftware.org -- the two busiest ftp > archives around and consequently the two busiest disk subsystems around. That's both debatable and highly hyperbolic. It also entirely denies the reality that no one solution is appropriate for an entire class of problems. In many situations, the lower cost and higher performance of an 'embedded' RAID controller make it a much better solution. > Both of these configations utilize the latest Adaptec 78xx based PCI > SCSI controller attached to a SCSI-SCSI RAID adapter. Unless I'm mistaken, neither of them are using U160 controllers. > In the case of > wcarchive it is a Mylex DAC960SXI SCSI-SCSI 6 channel RAID controller, > w/256MB cache. ftp.freesoftware.org doesn't reveal to us what sort of > SCSI-SCSI RAID controller is in use but I would assume it's the same or > similiar to wcarchive since TeraSolutins, Inc. had a hand in both > systems. JFYI, Tera are no longer recommending or using the Mylex SCSI:SCSI controllers. > This approach does offer a layer of protection from scsi > controller obsolesences or driver bitrot. You put a relatively cheap > well supported SCSI controller in your machine and interface it to your > external RAID canister. That controller can be replaced and upgraded as > necessary while still keeping the same disk subsystem behind it. It > also allows you to forget about bugs in the raid code or availability of > something like mlxcontrol since it's all handled in hardware. This isn't the whole picture, unfortunately. - You lose bandwidth and throughput by using a SCSI interface. (You can recover some of this using multiple SCSI busses, but do the math; how many LVD SCSI channels do you need to match a 64-bit 66MHz PCI slot?) - You are still at the mercy of the firmware in the RAID adapter, whether it be internal or external (see above inre: Tera not liking Mylex anymore). - You still need an array management tool. > You can > also attach multiple hosts to the RAID canister, allowing more than one > system to use the same disks. That can also come in handy if you need > redundant servers but don't want to mirror all of your content. This is largely irrelevant, since it's possible to do the same thing with a PCI:SCSI RAID controller, but we lack the filesystem technology to do anything useful about it. > The decision all comes down to just how future proof you need to be and > how much money you have to sink into your project. You leave out "how well you want it to perform" as well. All other things being equal, the PCI:SCSI adapters will give you better bang for your buck. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 14:49:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 32DB837B8F1; Sat, 29 Apr 2000 14:49:19 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id OAA93717; Sat, 29 Apr 2000 14:49:18 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-Reply-To: Message from Mike Smith of "Sat, 29 Apr 2000 13:13:37 PDT." <200004292013.NAA01003@mass.cdrom.com> Organization: CodeGen, Inc. X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Sat, 29 Apr 2000 14:49:18 -0700 Message-ID: <93707.957044958@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Apr 2000 13:13:37 PDT, Mike Smith wrote: > >You leave out "how well you want it to perform" as well. All other >things being equal, the PCI:SCSI adapters will give you better bang for >your buck. Out of curiosity, how would a PCI-RAID (SCSI) adapter compare with vanilla PCI-SCSI cards and vinum? It seems to me that the host CPU(s) are much faster than the processors on the PCI-SCSI adapters. Or are both of these "fast-enough" and thus performance differences are largely an irrelevent consideration? (They both have similar software issues but I suspect vinum is easier to debug. :) -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 15:43:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fuggle.veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id EF56437BA86 for ; Sat, 29 Apr 2000 15:43:29 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from veldy (cascade.veldy.net [192.168.0.1]) by fuggle.veldy.net (Postfix) with SMTP id C177D5B85 for ; Sat, 29 Apr 2000 17:45:30 -0500 (CDT) Message-ID: <004a01bfb22c$80d4d440$0100a8c0@veldy.net> From: "Thomas T. Veldhouse" To: Subject: sendmail installed when it shouldn't during build world Date: Sat, 29 Apr 2000 17:44:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I have NO_SENDMAIL= true # do not build sendmail and related programs in my /etc/make.conf file. I use Postfix instead. I just built the world and sendmail was built anyway and installed right over the links for Postfix. I built on a 20000418-4.0 system and cvsup'd to last nights stable sources. Thanks, Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 15:48:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 28B2437B8DB; Sat, 29 Apr 2000 15:48:11 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA62817; Sat, 29 Apr 2000 15:48:11 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 29 Apr 2000 15:48:10 -0700 (PDT) From: Kris Kennaway To: David Wolfskill Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Don't know how to make ... obj/ ... /src/usr/include/sys/param.h In-Reply-To: <200004261337.e3QDbFw06373@pau-amma.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000, David Wolfskill wrote: > find /usr/src -name .depend -print > > identified the 5 or 6 that were there; I removed each of them, > re-started the buildworld, and it finished successfully by the time I > got up this morning. make cleandir; make cleandir will do this for you (doing it twice is deliberate - the first one deals with /usr/obj links if they exist, the second cleans in the /usr/src directory. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 15:58:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shemp.palomine.net (shemp.palomine.net [205.198.88.200]) by hub.freebsd.org (Postfix) with SMTP id 7BA6C37B931 for ; Sat, 29 Apr 2000 15:58:23 -0700 (PDT) (envelope-from cjohnson@palomine.net) Received: (qmail 94281 invoked by uid 1000); 29 Apr 2000 22:58:20 -0000 Date: Sat, 29 Apr 2000 18:58:20 -0400 From: Chris Johnson To: "Thomas T. Veldhouse" Cc: freebsd-stable@freebsd.org Subject: Re: sendmail installed when it shouldn't during build world Message-ID: <20000429185820.A94264@palomine.net> References: <004a01bfb22c$80d4d440$0100a8c0@veldy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <004a01bfb22c$80d4d440$0100a8c0@veldy.net>; from veldy@veldy.net on Sat, Apr 29, 2000 at 05:44:39PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 29, 2000 at 05:44:39PM -0500, Thomas T. Veldhouse wrote: > Hello. I have > > NO_SENDMAIL= true # do not build sendmail and related programs > > in my /etc/make.conf file. I use Postfix instead. I just built the world > and sendmail was built anyway and installed right over the links for Postfix. > I built on a 20000418-4.0 system and cvsup'd to last nights stable sources. I thought the same thing, but that's not really what happened. See the man page for mailwrapper. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 17: 4:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.campbell-mithun.com (Mercury.campbell-mithun.com [192.159.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 6FFF837C1AE; Sat, 29 Apr 2000 17:04:45 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from accord.grasslake.net (honda.grasslake.net [192.168.1.1]) by mercury.campbell-mithun.com (8.9.1a/8.9.1) with ESMTP id TAA18585; Sat, 29 Apr 2000 19:04:44 -0500 Received: from k6 (k6.grasslake.net [192.168.2.1]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id TAA01113; Sat, 29 Apr 2000 19:03:38 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <001a01bfb237$b2b62490$0102a8c0@k6> From: "Shawn Barnhart" To: "Mike Smith" Cc: References: <200004292004.NAA00970@mass.cdrom.com> Subject: Re: How good is AMI MegaRAID support? Date: Sat, 29 Apr 2000 19:04:47 -0500 Organization: Grasslake.Net MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Mike Smith" | If that's what they say, I'd be inclined to believe them. Since I've not | encountered any fatal problems with the 2.x firmware, I can't suggest | that upgrading would actually win you very much. I'm not even sure the HPDA flavor of cards is supported by FreeBSD to begin with. I hooked up my HPDA DAC960PL to a 4.0-STABLE box (cvsup'd last night) today and during bootup I get: mlx0: port 0xdc80-0xdcff irq 11 at device 13.0 on pci0 mlx0: couldn't allocate mailbox window device_probe_and_attach: mlx0 attach returned 6 The card and cable are good, they were last used with Win2K about two weeks ago. The disk cabinet (an HP "Disk Array" 5x1GB) I'm not sure about, though. When trying to initialize the array with Jetset, the HP DOS tool, and it just hangs there trying to do an inquiry on the drives. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 18:33: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from westhost15.westhost.net (westhost15.westhost.net [216.71.84.69]) by hub.freebsd.org (Postfix) with ESMTP id CE4F437B5E7 for ; Sat, 29 Apr 2000 18:33:01 -0700 (PDT) (envelope-from pahowes@fair-ware.com) Received: from beast (h0020af68b314.ne.mediaone.net [24.218.140.123]) by westhost15.westhost.net (8.8.5/8.8.5) with SMTP id UAA17618 for ; Sat, 29 Apr 2000 20:31:13 -0500 Reply-To: From: "Paul A. Howes" To: Subject: atdisk driver question... Date: Sat, 29 Apr 2000 21:33:07 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently started upgrading several computers from 3.4S to 4.0S. The first one went off without a single problem, and is happily humming right next to me. With that success behind me, I decided to upgrade an old Toshiba Satellite Pro 2400CS notebook computer. It has worked perfectly with 3.3 and 3.4 in the past. I followed all of the instructions for the upgrade process. When I got to the point of rebooting with my spiffy new 4.0 kernel, the trouble began... All of the devices recognize fine. The root partition of the hard drive mounts. Then, I get an error that /dev/wd0s1f is larger than the partition. "fsck" also bombs out, telling me that it cannot read several sectors. If I reboot with my 3.4S kernel, the system comes up without a hitch. And yes, I created ad0, ad0s1[abcdefgh] to match the old "wd" device identifiers. The only difference I can think of between the two computers, is that the server I already upgraded has a 20GB hard drive, and an old BIOS. I had to partition that to get the whole thing recognized by FreeBSD. The notebook computer has the original Toshiba 503MB hard drive, which I used the "dangerously dedicated" option on when I installed. So, the short version of this question is, does the new "ad" driver not handle "dangerously dedicated" systems properly? Has anyone else seen this before? I'm going to try re-installing 3.4S using a "normal" disk partition, and see what happens. But, I wanted to send a message to the list while I'm doing that. Thanks! --Paul A. Howes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 19:24:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yoda.dccnet.com (mail.deltacable.com [207.230.239.70]) by hub.freebsd.org (Postfix) with ESMTP id ED87537B570 for ; Sat, 29 Apr 2000 19:24:32 -0700 (PDT) (envelope-from kg@versys.net) Received: from versys.net (unverified [209.5.131.193]) by yoda.dccnet.com (Rockliffe SMTPRA 3.4.6) with ESMTP id ; Sat, 29 Apr 2000 19:22:51 -0700 Message-ID: <390B996B.A31DEA7D@versys.net> Date: Sat, 29 Apr 2000 19:24:43 -0700 From: "Kevin G. Eliuk" X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: pahowes@fair-ware.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: atdisk driver question... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Paul A. Howes" wrote: > > I recently started upgrading several computers from 3.4S to 4.0S. The first > one went off without a single problem, and is happily humming right next to > me. With that success behind me, I decided to upgrade an old Toshiba > Satellite Pro 2400CS notebook computer. > > It has worked perfectly with 3.3 and 3.4 in the past. I followed all of the > instructions for the upgrade process. When I got to the point of rebooting > with my spiffy new 4.0 kernel, the trouble began... All of the devices > recognize fine. The root partition of the hard drive mounts. Then, I get > an error that /dev/wd0s1f is larger than the partition. "fsck" also bombs > out, telling me that it cannot read several sectors. If I reboot with my > 3.4S kernel, the system comes up without a hitch. And yes, I created ad0, > ad0s1[abcdefgh] to match the old "wd" device identifiers. First reaction would be to ask if you edited "etc/fstab". > The only difference I can think of between the two computers, is that the > server I already upgraded has a 20GB hard drive, and an old BIOS. I had to > partition that to get the whole thing recognized by FreeBSD. The notebook > computer has the original Toshiba 503MB hard drive, which I used the > "dangerously dedicated" option on when I installed. > So, the short version of this question is, does the new "ad" driver not > handle "dangerously dedicated" systems properly? Has anyone else seen this > before? I'm going to try re-installing 3.4S using a "normal" disk > partition, and see what happens. But, I wanted to send a message to the > list while I'm doing that. (I am not sure if this would apply given the error) Was the disk scanned for bad sectors w/bad144 on the initial install? -- Regards, Kevin G. Eliuk Technician | VerSys Communications Ltd. | http://www.versys.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 19:35:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vex.net (vex.net [216.126.72.2]) by hub.freebsd.org (Postfix) with ESMTP id 6773F37BA52 for ; Sat, 29 Apr 2000 19:35:37 -0700 (PDT) (envelope-from roddie@krweb.net) Received: (1320 bytes) by vex.net via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Sat, 29 Apr 2000 22:35:30 -0400 (EDT) (Smail-3.2.0.104 1998-Nov-20 #6 built 1999-Apr-16) Received: from vex.net(216.126.72.2) via SMTP by vex.net, id smtpd17473a; Sat Apr 29 22:35:22 2000 Date: Sat, 29 Apr 2000 21:35:21 -0500 (CDT) From: Roddie Hasan X-Sender: roddie@vex.net To: freebsd-stable@freebsd.org Subject: Disk error and No /boot/loader Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Running 4.0-STABLE (though I had the same issue in 4.0-RELEASE). I've got a 10 gig IDE Hard drive with two FAT32 paritions taking 2 gig and 6 gig, and then a 2.4 gig FreeBSD partition. / - 100 megs /var - 100 megs swap - 268 megs /usr - 1800 megs On bootup, I get the following: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)? boot: /load /boot/loader Disk error 0x1 (lba=0xfc093c) No /boot/loader The system continues to boot /kernel automatically and runs fine from there. (I've patched the kernel per kern/17422 to get top, vmstat etc. working). For the record, /boot/loader *does* exist. I've read an explanation about the 1024 cylinder limit, but I used the exact same configuration with 3.4-STABLE and /boot/loader worked fine. Any assistance would be appreciated. Regards, Roddie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 19:54:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 47B5437BBCB for ; Sat, 29 Apr 2000 19:54:20 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p40-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.105]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id LAA02995; Sun, 30 Apr 2000 11:54:14 +0900 (JST) Message-ID: <390BA0B8.2E02A4CB@newsguy.com> Date: Sun, 30 Apr 2000 11:55:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Roddie Hasan Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Disk error and No /boot/loader References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Booting above 8 Gb is not supported, due to BIOS problems. If you don't believe that, trying booting Windows above 8 Gb... :-) Alas, one developer had some interesting ideas on how to solve this problem recently. There is _unsupported_ options to make this work, but we can't activate them by default because not all hardware/firmware is compatible with it. Roddie Hasan wrote: > > Hi all, > > Running 4.0-STABLE (though I had the same issue in 4.0-RELEASE). I've got > a 10 gig IDE Hard drive with two FAT32 paritions taking 2 gig and 6 gig, > and then a 2.4 gig FreeBSD partition. > > / - 100 megs > /var - 100 megs > swap - 268 megs > /usr - 1800 megs > > On bootup, I get the following: > > >> FreeBSD/i386 BOOT > Default: 0:ad(0,a)? > boot: /load /boot/loader > Disk error 0x1 (lba=0xfc093c) > No /boot/loader > > The system continues to boot /kernel automatically and runs fine from > there. (I've patched the kernel per kern/17422 to get top, vmstat > etc. working). For the record, /boot/loader *does* exist. > > I've read an explanation about the 1024 cylinder limit, but I used the > exact same configuration with 3.4-STABLE and /boot/loader worked fine. > > Any assistance would be appreciated. > > Regards, Roddie > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org dcs@there.is.no.such.thing.as.a.bsdconspiracy.net GPL certainly doesn't meet Janis Joplin's definition of freedom: "Freedom is just another word for nothing left to lose." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 19:59:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vex.net (vex.net [216.126.72.2]) by hub.freebsd.org (Postfix) with ESMTP id 30A9237B7FB for ; Sat, 29 Apr 2000 19:59:48 -0700 (PDT) (envelope-from roddie@krweb.net) Received: (1185 bytes) by vex.net via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Sat, 29 Apr 2000 22:59:40 -0400 (EDT) (Smail-3.2.0.104 1998-Nov-20 #6 built 1999-Apr-16) Received: from vex.net(216.126.72.2) via SMTP by vex.net, id smtpd18381a; Sat Apr 29 22:59:39 2000 Date: Sat, 29 Apr 2000 21:59:39 -0500 (CDT) From: Roddie Hasan X-Sender: roddie@vex.net To: "Daniel C. Sobral" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Disk error and No /boot/loader In-Reply-To: <390BA0B8.2E02A4CB@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Daniel, Thanks for the quick reply.. > Booting above 8 Gb is not supported, due to BIOS problems. If you don't > believe that, trying booting Windows above 8 Gb... :-) Understood - But why would it have worked with 3.4 and the *exact* same configuration? (When I upgraded, I deleted the partition during install, and recreated it the same way). > problem recently. There is _unsupported_ options to make this work, but > we can't activate them by default because not all hardware/firmware is > compatible with it. I'd be happy to test them further.. :) Roddie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 21:23:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57]) by hub.freebsd.org (Postfix) with ESMTP id DA49A37B7A0 for ; Sat, 29 Apr 2000 21:23:40 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00672; Sat, 29 Apr 2000 21:31:50 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004300431.VAA00672@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Parag Patel Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Sat, 29 Apr 2000 14:49:18 PDT." <93707.957044958@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Apr 2000 21:31:50 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 29 Apr 2000 13:13:37 PDT, Mike Smith wrote: > > > >You leave out "how well you want it to perform" as well. All other > >things being equal, the PCI:SCSI adapters will give you better bang for > >your buck. > > Out of curiosity, how would a PCI-RAID (SCSI) adapter compare with > vanilla PCI-SCSI cards and vinum? It seems to me that the host CPU(s) > are much faster than the processors on the PCI-SCSI adapters. Or are > both of these "fast-enough" and thus performance differences are largely > an irrelevent consideration? (They both have similar software issues > but I suspect vinum is easier to debug. :) All other things being equal, software RAID is going to be faster. (ie. same disks, same # of SCSI channels, etc.) The hardware solution's sell there is: - better support/functionality (enclosure management, etc.) - better survivability (battery-backed cache) Plus you get a stack of SCSI channels onboard the card. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Apr 29 21:30:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57]) by hub.freebsd.org (Postfix) with ESMTP id 4418A37BA52 for ; Sat, 29 Apr 2000 21:30:24 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00706; Sat, 29 Apr 2000 21:38:30 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004300438.VAA00706@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Shawn Barnhart" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How good is AMI MegaRAID support? In-reply-to: Your message of "Sat, 29 Apr 2000 19:04:47 CDT." <001a01bfb237$b2b62490$0102a8c0@k6> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Apr 2000 21:38:30 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ----- Original Message ----- > From: "Mike Smith" > > | If that's what they say, I'd be inclined to believe them. Since I've > not > | encountered any fatal problems with the 2.x firmware, I can't suggest > | that upgrading would actually win you very much. > > I'm not even sure the HPDA flavor of cards is supported by FreeBSD to > begin with. I hooked up my HPDA DAC960PL to a 4.0-STABLE box (cvsup'd > last night) today and during bootup I get: > > mlx0: port 0xdc80-0xdcff irq 11 at > device 13.0 on pci0 > mlx0: couldn't allocate mailbox window > device_probe_and_attach: mlx0 attach returned 6 What firmware revision are you running? This looks like your card isn't supporting a memory-mapped region for the mailbox window - I should check for this I guess. I'm fairly sure that 2.42 or later will work. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message