From owner-freebsd-stable Sun Mar 22 00:26:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27936 for freebsd-stable-outgoing; Sun, 22 Mar 1998 00:26:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27909; Sun, 22 Mar 1998 00:26:28 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA19170; Sun, 22 Mar 1998 00:26:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803220826.AAA19170@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joao Carlos Mendes Luis cc: rhh@ct.picker.com (Randall Hopper), multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable In-reply-to: Your message of "Sun, 22 Mar 1998 04:45:05 -0300." <199803220745.EAA04477@gaia.coppe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 00:26:14 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk There is no need to create an ioctl to clear the buffer that can be handle by the driver by prior to initiating a start capture to clear the buffer. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 00:39:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01097 for freebsd-stable-outgoing; Sun, 22 Mar 1998 00:39:49 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01082 for ; Sun, 22 Mar 1998 00:39:44 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id DAA10158; Sun, 22 Mar 1998 03:39:19 -0500 (EST) Date: Sun, 22 Mar 1998 03:39:19 -0500 (EST) From: Derek Flowers To: Wes Peters - Softweyr LLC cc: Drew Derbyshire - UUPC/extended software support , stable@FreeBSD.ORG Subject: Binary package updates, etc. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've done some quick and dirty work on binary package updates and would like some comments on what I've got going, where to go in the future, etc. The files are located at http://portwwwbus.tc.cc.va.us/~djflow/pkginfo Read the README file first to get an idea of what is happening. Basically, I just took the binary distribution off the 2.2.5-RELEASE cd and created a skeleton to get it to work with pkg_add. In theory, any binary updates would work with the same skeleton. There is still the problem with digital signatures and what to do about uninstalls, reverts, etc. but I would like some input before going too far. To create the actual package, download all the files and run the makepkg script. The package it creates is named "bin-2.2.5_RELEASE.pkg". If you plan to experiment with the package, be sure to change the target directory in the makepkg script otherwise IT WILL WIPE OUT YOUR CURRENT BINARY DISTRIBUTION. Let me know what you think. ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 00:47:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03224 for freebsd-stable-outgoing; Sun, 22 Mar 1998 00:47:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tantivy.stanford.edu (techie@tantivy.Stanford.EDU [36.55.0.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03199 for ; Sun, 22 Mar 1998 00:47:06 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.8.8/8.8.5) id AAA09868; Sun, 22 Mar 1998 00:46:32 -0800 (PST) From: Bob Vaughan Message-Id: <199803220846.AAA09868@tantivy.stanford.edu> Subject: Re: Surprise Reboots To: admin@www.megido.inter.net.il (Gilad Rom) Date: Sun, 22 Mar 1998 00:46:28 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: from Gilad Rom at "Mar 22, 98 08:49:42 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I have also experienced a lot of spontaneous reboots and freezes.. sometimes the machine will do a full reboot, and at other times, it just freezes up, and does not respond (except to ping..). this is with a p5-200 on a IWill P55TV motherboard (built-in adaptech 2940au) 64mb ram, 3c905, sb16, another 2940, and a svga card.. hp6020 on the onboard 2940 (ahc0), and 4 disks and another cdrom on the other 2940 (ahc1) currently running 2.2-stable from 980320, but the problem has appeared numerous times since upgrading to 2.2-stable late last year.. I also have a 486dx2-66 running 2.2-stable of 980223, which has not showed the same problem (but is also not used as much.. mostly as a ppp router..) both of these systems are on a UPS, and local utility power has been stable. I leave them up 24x7. NFS is used to export a few filesystems from the pentium to the 486, but not the other way around. most of the reboots have happened during a buildworld, or when a buildworld was left running went I went to bed (and woke up to unclean filesystems) I thought this might be a hardware problem, but i'm not sure.. I have not changed the hardware since this problem first appeared, and the machine was very stable under 2.2.5-release. I cvsup every day or so, and buildworld, if this is successful, then I installworld, build a kernel, and reboot.. if I have to restart buildworld, then I usually cvsup again before doing so.. (possibly unrelated, but I have been able to crash XF86331 on this machine as well, by opening 2 windows with /usr/ucb/mail running, and closing them at the same time.. haven't yet tried it with XF86332..) > I've got a new box, about two weeks ago, to replace my good ol' DX2/66. > This box is an Intel Pentium 200Mhz, has a 430TX Motherboard, 32MB on one > SDRAM chip, and an ESS Soundcard, a x20 IDE CDROM + 4.3GB EIDE Western > Digital Harddrive, and an ATI 3D Rage II. Ofcourse, the minutes I got it > I happily installed FreeBSD on it, from a 2.2.5-RELEASE CD I had burned a > couple of days before. Everything seemed to go fine, when suddenly the box > rebooted. I thought it had to be a power surge or something like that, so > I just carried on. (When I just got the machine it had a 166Mhz CPU in it) > On the past two weeks, the machine has rebooted on me on random times, > Without any warning. Once make buildworld completes, and another time it > simply reboots in the middle of the process. > Thinking it had to be a hardware problem, I have changed the SDRAM chip > and upgraded the CPU to a 200Mhz one. I have also cvsup'd to the latest > -STABLE sources since, and did a 'make world -j4' with the new chips. > it went fine. for the last couple of days, everything seems to be going > fine. Last night, I left my box on at night while downloading xemacs20. > guess what I found out when I got up in the morning? > > mount R/W of / failed - file system is not clean! fun fsck manually > ... > > which means the box had rebooted just like it did before. > I have no explanation for this, except I get kernel double faults > sometimes, right before the reboot. I'd tell ya what they say, except it > reboots right after that. > > Anyway - If someone has similar a similar problem - or similar hardware - > Id really like to know about it. > Thanks. > Gilad Rom. > > > #I know there are no monsters... Then why do they keep chasing me?? > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org | techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 01:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07268 for freebsd-stable-outgoing; Sun, 22 Mar 1998 01:26:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from link.cpt.nsc.iafrica.com (Y6kgy2kJxFriG77j0/Vr+DVZXsIcA5W6@link.cpt.nsc.iafrica.com [196.31.1.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07250 for ; Sun, 22 Mar 1998 01:26:24 -0800 (PST) (envelope-from khetan@link.freebsd.os.org.za) Received: from localhost (khetan@localhost) by link.cpt.nsc.iafrica.com (8.8.8+3.0Wbeta13/8.8.8) with SMTP id LAA22691; Sun, 22 Mar 1998 11:26:13 +0200 (SAT) Date: Sun, 22 Mar 1998 11:26:13 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@link.cpt.nsc.iafrica.com Reply-To: Khetan Gajjar To: Eivind Eklund cc: stable@FreeBSD.ORG Subject: Re: Kerberos IV build problems - anyone ? In-Reply-To: <19980322013529.40240@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Eivind Eklund wrote: >> Is anyone out there having problems in installing Kerberos IV under >> 2.2.6-BETA ? I'm getting include errors. > >Remove /usr/include/kerberosIV (or a directory similarly named). Been there, done that, can't get the T-shirt to fit. 7=[khetan@chain] /usr/include$ ls -alR | grep -i kerberos + colorls -FG -alR + grep -i kerberos 8=[khetan@chain] /usr/include$ --- Khetan Gajjar (!kg1779) khetan@iafrica.com (w); khetan@os.org.za (h) http://www.os.org.za/~khetan | Finger: khetan@chain.freebsd.os.org.za UUNET Internet Africa Support | FreeBSD enthusiast-www2.za.freebsd.org A computer without Microsoft and Intel is like chocolate cake without tomato sauce and mustard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 02:13:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11430 for freebsd-stable-outgoing; Sun, 22 Mar 1998 02:13:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from www.megido.inter.net.il (www.megido.inter.net.il [192.114.190.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11423 for ; Sun, 22 Mar 1998 02:13:24 -0800 (PST) (envelope-from admin@www.megido.inter.net.il) Received: from localhost (admin@localhost) by www.megido.inter.net.il (8.8.8/8.8.7) with SMTP id NAA10346; Sun, 22 Mar 1998 13:08:11 +0300 (IDT) (envelope-from admin@www.megido.inter.net.il) Date: Sun, 22 Mar 1998 13:08:10 +0300 (IDT) From: Gilad Rom To: Bob Vaughan cc: freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots In-Reply-To: <199803220846.AAA09868@tantivy.stanford.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I also have a DX2 box w/8mb of ram and a 270MB hdd, I still have FreeBSD on it, and this trouble had never occured. I had alot of uptime there. Hmm... Really makes me wonder. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 06:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06274 for freebsd-stable-outgoing; Sun, 22 Mar 1998 06:41:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06255; Sun, 22 Mar 1998 06:41:33 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (uQo4gq/hmQLUmaUeVHBc2PcMkzOUmf86@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id QAA15533; Sun, 22 Mar 1998 16:41:26 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (F3cG3FyAKWbCDTtBpZHbrh5dXoERblG6@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id QAA26151; Sun, 22 Mar 1998 16:41:25 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199803221441.QAA26151@greenpeace.grondar.za> To: Randall Hopper cc: Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Date: Sun, 22 Mar 1998 16:41:24 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Randall Hopper wrote: > I hadn't heard the details on the mmap change. Fxtv I believe only reads > from the buffer except when starting a capture for which temporal > decimation is enabled. At that time, it clears out the driver buffer so > that you don't see a stale last frame from the last capture up until the > first frame of the requested capture finally comes along. I have this problem on CURRENT. Only root can watch TV. I use a HAUPPAUGE/BT848 and I have just rebuilt my kernel. This is the first time in about a month I have tried to watch TV on my FBSD box. > 1) Comment out the "|PROT_WRITE" in: > 2) Comment out these few lines: Will try. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 06:47:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07020 for freebsd-stable-outgoing; Sun, 22 Mar 1998 06:47:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA07005; Sun, 22 Mar 1998 06:47:14 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 22 Mar 1998 9:45:04 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA23090; Sun, 22 Mar 98 09:45:02 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id JAA12578; Sun, 22 Mar 1998 09:44:36 -0500 Message-Id: <19980322094436.65505@ct.picker.com> Date: Sun, 22 Mar 1998 09:44:36 -0500 From: Randall Hopper To: Bruce Evans , Joao Carlos Mendes Luis , Amancio Hasty Cc: multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Bruce Evans , Joao Carlos Mendes Luis , Amancio Hasty , multimedia@freebsd.org, stable@FreeBSD.ORG References: <199803220221.NAA18775@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803220221.NAA18775@godzilla.zeta.org.au>; from Bruce Evans on Sun, Mar 22, 1998 at 01:21:39PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Joao Carlos Mendes Luis: |#define quoting(Randall Hopper) |// 1) Comment out the "|PROT_WRITE" in: |// |// c->drv_buf = (TV_UINT8 *) mmap( (caddr_t)0, MAX_MMAP_BUF_SIZE, |// PROT_READ|PROT_WRITE, 0, c->fd, (off_t)0 ); | |Well, if you intend to mmap with PROT_WRITE, why do you open the device |with O_RDONLY ? :) Capture buffer access was originally read-only. When I needed to clear the buffer, I only had to add write on the mmap. I forgot about the open(), and the kernel was fine with the old, so it never got changed. Conceptually, I guess mmap() access now overrides open(). Though like you, seems to me mmap() allowable access probably should be a subset, for read & write at least. Maybe that should apply to PROT_EXEC as well. Thoughts? Wouldn't this also obviate the need for having any special mmap() IS-ROOT? checks for PROT_WRITE access? It does seem a little odd that an app can write to an mmaped buffer related to a device file they don't have write access to. At any rate, in this particular case we should pursue have the driver clear the buffer, so client apps only need to mmap PROT_READ/MAP_SHARED, and open the device O_RDONLY. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 07:03:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08903 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:03:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA08894; Sun, 22 Mar 1998 07:03:33 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 22 Mar 1998 10:01:58 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA23322; Sun, 22 Mar 98 10:01:55 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id KAA12630; Sun, 22 Mar 1998 10:01:29 -0500 Message-Id: <19980322100129.35396@ct.picker.com> Date: Sun, 22 Mar 1998 10:01:29 -0500 From: Randall Hopper To: Joao Carlos Mendes Luis , Amancio Hasty Cc: multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Joao Carlos Mendes Luis , Amancio Hasty , multimedia@freebsd.org, stable@FreeBSD.ORG References: <199803220221.NAA18775@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803220221.NAA18775@godzilla.zeta.org.au>; from Bruce Evans on Sun, Mar 22, 1998 at 01:21:39PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Joao Carlos Mendes Luis: |// /* If TDEC is on, may be a while before old trash gets written on */ |// if ( c->fps != c->fps_max ) |// memset( c->drv_buf, '\0', |// g.w * g.h * c->pix_geom_list[ c->pix_geom_idx ].Bpp ); | |Why do you need to clear the buffer ? I alluded to this in my last msg: |decimation is enabled. At that time, it clears out the driver buffer so |that you don't see a stale last frame from the last capture up until the |first frame of the requested capture finally comes along. "Fxtv" doesn't need to do it necessarily. It just needs to be done. Otherwise, the frame residing in the driver buffer for potentially up to a full second will be the one from the last capture, potentially minutes or hours old. A stale buffer is fine if app is processing the frame on interrupt, but when it knows there's no way it can keep up, having signals issues 30X/sec is pointless extra overhead just for bookkeeping the first frame. Better to just sample as fast as possible up to 30X/sec, and clear the buffer before starting. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 07:20:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10715 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:20:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from venus.os.com (venus.os.com [199.232.136.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA10710 for ; Sun, 22 Mar 1998 07:20:32 -0800 (PST) (envelope-from craigs@os.com) Received: (qmail 26428 invoked from network); 22 Mar 1998 15:20:21 -0000 Received: from ppp1-os-gw.os.com (HELO theranch) (209.113.225.1) by venus.os.com with SMTP; 22 Mar 1998 15:20:21 -0000 Message-Id: <3.0.5.32.19980322101854.007e1840@titan.os.com> X-Sender: craigs@titan.os.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 22 Mar 1998 10:18:54 -0500 To: Gilad Rom , Bob Vaughan From: Craig Shrimpton Subject: Re: Surprise Reboots Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <199803220846.AAA09868@tantivy.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk At 01:08 PM 3/22/98 +0300, Gilad Rom wrote: >I also have a DX2 box w/8mb of ram and a 270MB hdd, I still have FreeBSD >on it, and this trouble had never occured. I had alot of uptime there. >Hmm... Really makes me wonder. > Here'a an SDRAM wierdness story. I have a DFI 586ITXD (ATX)that can take either EDO or DIMMS. If I use NEC memory, I can only put 1 DIMM in the system, If I use two, the system is unstable. Switching to Micron memory, two DIMMS are fine. If I put the NEC memory in the DFI 586ITBD, (AT) it will take both chips without complaint. It is possible that it's the board and not the chips except that certain date codes of NEC memory will work with two DIMMS! -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 07:24:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11079 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:24:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA11073; Sun, 22 Mar 1998 07:24:21 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 22 Mar 1998 10:22:46 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA23604; Sun, 22 Mar 98 10:22:44 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id KAA12674; Sun, 22 Mar 1998 10:22:20 -0500 Message-Id: <19980322102220.55088@ct.picker.com> Date: Sun, 22 Mar 1998 10:22:20 -0500 From: Randall Hopper To: Joao Carlos Mendes Luis , Amancio Hasty Cc: multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Joao Carlos Mendes Luis , Amancio Hasty , multimedia@freebsd.org, stable@FreeBSD.ORG References: <199803220221.NAA18775@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803220221.NAA18775@godzilla.zeta.org.au>; from Bruce Evans on Sun, Mar 22, 1998 at 01:21:39PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Amancio Hasty: |Joao Carlos Mendes Luis: | |Amancio Hasty: | | |There is no need to create an ioctl to clear the buffer that can be | | |handle by the driver by prior to initiating a start capture to clear | | |the buffer. | | | |Isn't it a waste of CPU ? Do you need to clear the buffer everytime ? | |Why do you ever need to clear the buffer ? | |It is not really a waste of cpu cycles to erase the buffer prior to |start of capture for continuous operations since it is called only |once. Summary: I suggest a driver ioctl() to clear the buffer. But I could live with the driver always doing this on capture start ONLY if it doesn't do this when FPS == FPS_MAX. Detail: I suggested an ioctl() for two reasons. First, because IMO this: memset( fd, '\0', 1769472 ); /* Worst case */ is wasteful when it can be happening many times a second. When you're dragging your Fxtv window around with temporal decimation off (FPS = FPS_MAX), this could be happening 10-20 times a second, depending on your window manager. Now this memset is pointless normally (temporal decimation is off), since the user is going to see a new frame in 1/30th of second (aka 3.3 "hundredths" of a second); 1/25th sec for the PAL folks. Thus the conditional I wrap the buffer clear memset() in: if ( c->fps != c->fps_max ) memset( c->drv_buf, '\0', <...frame size...> ); However, when it can be up to almost a full second and the app is polling the buffer, then this gets annoying. Therefore I suggest not making memset something that's done before every capture start. (Second) We could have the driver only memset the buffer when FPS requested != FPS max (as I'm doing in the app now), but you could have clients that are only processing frames on driver interrupt and just don't care what's in the buffer up until the first interrupt. In which case this memset is an extra delay and load, and useless work. So I suggest a driver ioctl() to clear the buffer. But I could live with the driver always doing this on capture start ONLY if it doesn't do this when FPS == FPS_MAX. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 07:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12116 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:30:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA12024; Sun, 22 Mar 1998 07:29:58 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 22 Mar 1998 10:28:09 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA23677; Sun, 22 Mar 98 10:28:06 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id KAA12696; Sun, 22 Mar 1998 10:27:43 -0500 Message-Id: <19980322102742.22635@ct.picker.com> Date: Sun, 22 Mar 1998 10:27:42 -0500 From: Randall Hopper To: Mark Murray Cc: Joao Carlos Mendes Luis , Amancio Hasty , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Mark Murray , Joao Carlos Mendes Luis , Amancio Hasty , multimedia@freebsd.org, stable@freebsd.org References: <199803221441.QAA26151@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803221441.QAA26151@greenpeace.grondar.za>; from Mark Murray on Sun, Mar 22, 1998 at 04:41:24PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Mark Murray: |I have this problem on CURRENT. Only root can watch TV. I use a |HAUPPAUGE/BT848 and I have just rebuilt my kernel. This is the first |time in about a month I have tried to watch TV on my FBSD box. | |> 1) Comment out the "|PROT_WRITE" in: |> 2) Comment out these few lines: | |Will try. ... |This worked in my really current box. Thanks for the report Mark! Now its just a question of ioctl() or default capture start behavior. Then I'll get the fxtv port chg PR in. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 07:38:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13077 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:38:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13066 for ; Sun, 22 Mar 1998 07:38:56 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA07590; Sun, 22 Mar 1998 07:38:41 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Derek Flowers cc: Wes Peters - Softweyr LLC , Drew Derbyshire - UUPC/extended software support , stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-reply-to: Your message of "Sun, 22 Mar 1998 03:39:19 EST." Date: Sun, 22 Mar 1998 07:38:40 -0800 Message-ID: <7587.890581120@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Basically, I just took the binary distribution off the 2.2.5-RELEASE cd > and created a skeleton to get it to work with pkg_add. In theory, any > binary updates would work with the same skeleton. Hmmmm. How does this handle the issue of a /tmp directory that's not big enough to hold the intermediate unpacked copy? That reason is why bin, doc, manpages, etc are not currently distributed as packages. You might look into ``@option extract-in-place'' as a way of getting around that limitation. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 07:40:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13409 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:40:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (0@passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13245 for ; Sun, 22 Mar 1998 07:39:28 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id HAA06815; Sun, 22 Mar 1998 07:39:27 -0800 (PST) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaabAAa; Sun Mar 22 07:39:22 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id HAA01522; Sun, 22 Mar 1998 07:39:18 -0800 (PST) Message-Id: <199803221539.HAA01522@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpd001515; Sun Mar 22 07:38:38 1998 X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Gilad Rom cc: freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots In-reply-to: Your message of "Sun, 22 Mar 1998 08:49:42 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 07:38:35 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk 2.2.5-RELEASE had a couple of problems that exhibited themselves as VM problems that caused the system to panic occasionally. You can either upgrade to 2.2.6-BETA or email me and I will send you a 42K patch that fixes these and various other problems that I had, including a hack to fix a NULLFS panic (PR kern/5355). Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca > I've got a new box, about two weeks ago, to replace my good ol' DX2/66. > This box is an Intel Pentium 200Mhz, has a 430TX Motherboard, 32MB on one > SDRAM chip, and an ESS Soundcard, a x20 IDE CDROM + 4.3GB EIDE Western > Digital Harddrive, and an ATI 3D Rage II. Ofcourse, the minutes I got it > I happily installed FreeBSD on it, from a 2.2.5-RELEASE CD I had burned a > couple of days before. Everything seemed to go fine, when suddenly the box > rebooted. I thought it had to be a power surge or something like that, so > I just carried on. (When I just got the machine it had a 166Mhz CPU in it) > On the past two weeks, the machine has rebooted on me on random times, > Without any warning. Once make buildworld completes, and another time it > simply reboots in the middle of the process. > Thinking it had to be a hardware problem, I have changed the SDRAM chip > and upgraded the CPU to a 200Mhz one. I have also cvsup'd to the latest > -STABLE sources since, and did a 'make world -j4' with the new chips. > it went fine. for the last couple of days, everything seems to be going > fine. Last night, I left my box on at night while downloading xemacs20. > guess what I found out when I got up in the morning? > > mount R/W of / failed - file system is not clean! fun fsck manually > ... > > which means the box had rebooted just like it did before. > I have no explanation for this, except I get kernel double faults > sometimes, right before the reboot. I'd tell ya what they say, except it > reboots right after that. > > Anyway - If someone has similar a similar problem - or similar hardware - > Id really like to know about it. > Thanks. > Gilad Rom. > > > #I know there are no monsters... Then why do they keep chasing me?? > > > > > > > > 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 Mar 22 09:19:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23886 for freebsd-stable-outgoing; Sun, 22 Mar 1998 09:19:07 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23878 for ; Sun, 22 Mar 1998 09:19:01 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.uucp.kew.com (sonata.hh.kew.com [192.168.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with SMTP id MAA05092 for ; Sun, 22 Mar 1998 12:18:55 -0500 (EST) Received: from kew.com by sonata.uucp.kew.com (UUPC/extended 1.12y) with UUCP for stable@freebsd.org; Sun, 22 Mar 1998 12:18:54 -0500 Received: from kew.com by sonata.uucp.kew.com (UUPC/extended 1.12y) with ESMTP for stable@freebsd.org; Sun, 22 Mar 1998 12:18:52 -0500 Message-ID: <351547FB.6B020444@kew.com> Date: Sun, 22 Mar 1998 12:18:51 -0500 From: Drew Derbyshire - UUPC/extended software support Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.04 [en]C-MOENE (WinNT; I) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: FreeBSD can't find 32M of my 48M without help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I came, I downloaded, I installed 2.2.6 beta over the network. (I happened to do it at 1 AM via the cable modem. It flew.) Two minor issues: 1) The disk slice editor doesn't know many of the more arcane partition type numbers. Jordan already saw my PR and fixed it, when the next boot floppy image is ready I'll test it. 2) By default, the kernel only reports I have 16M, when in fact I have 48M. Windows 95 does see the entire 48M, and FreeBSD will see all 48M if I explicitly tell it in the configuration file via MAXMEM. I didn't think the MAXMEM was required for under 64M. Machine is a Compaq P/166. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 09:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25290 for freebsd-stable-outgoing; Sun, 22 Mar 1998 09:27:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.91.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25122 for ; Sun, 22 Mar 1998 09:25:50 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from trojanhorse.pr.watson.org (n235-103.mtholyoke.edu [138.110.235.103]) by fledge.watson.org (8.8.8/8.6.10) with SMTP id MAA19839; Sun, 22 Mar 1998 12:23:07 -0500 (EST) Date: Sun, 22 Mar 1998 12:25:18 -0500 (EST) From: Robert Watson X-Sender: robert@trojanhorse.pr.watson.org Reply-To: Robert Watson To: Derek Flowers cc: Wes Peters - Softweyr LLC , "Daniel O'Callaghan" , stable@FreeBSD.ORG Subject: Re: after the release ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sat, 21 Mar 1998, Derek Flowers wrote: > > > Why not model it after RPM? If the size and md5 do not match, return an > > > error. Allow the user to overide the check if they wish to do so. > > > > > > Just to get a feel for pkg_add, what are the stpes taken to add the > > > software? I'm thinking the check could be done in the install script, > > > assuming it executes a script like make would. > > > > Errr. How do you know that the md5 is right? Digital signatures have to > > come into this somewhere :). Or secure trusted transmission (i.e., the > > HTTPS idea). > > Sorry, forgot to mention that RPM uses PGP fingerprints also. > > The MD5 can be stored on ftp.freebsd.org where everybody can check it. I think you fundamentally misunderstand. MD5's are a one-way hash of the data. They can be used for error checking, or for digital signatures. By default, they merely detect changes in the file -- but you need some way to verify that the hash you retrieve is correct! Two common approaches to this are shared secret and public/private key. In shared secret, there are two approaches: 1) Include the key in the data md5'd -- when verifying, append the shared secret, generate the md5, and compare. 2) Use the key to encrypt the md5, and ship that with the data. To verify, generate an md5, encrypt it with the shared secret, and compare the result. Both ways, you have the have the secret, which has to be distributed somehow. With public private key, they typical approach is to generate the md5, then encrypt that using the private key, and ship it along. When you want to verify, md5 the data, then decrypt the version sent along (using the public key) and compare them. Both ways, you have a key distribution problem. And both ways, you may need code that cannot be exported; at least, not in source code, and probably without a license. Either way, you cannot just "Store the md5s on ftp.freebsd.org" because there is no way to know that they are securely retrieved :). One answer is to use https and your netscape browser's certificate verification (and built in certificates). People download the browser in the clear (foolish), but now that they have it (and apparently trust it), we might as well take advantage of it. Key distribution is a fundamental problem; shipping out the public keys on the CD-ROM might not be a bad idea, btw. Robert Watson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 10:09:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01236 for freebsd-stable-outgoing; Sun, 22 Mar 1998 10:09:15 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01229 for ; Sun, 22 Mar 1998 10:09:09 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: from shell.futuresouth.com (mail.futuresouth.com [207.141.254.21]) by shell.futuresouth.com (8.8.8/8.8.8) with SMTP id MAA03104; Sun, 22 Mar 1998 12:09:02 -0600 (CST) Date: Sun, 22 Mar 1998 12:09:02 -0600 (CST) From: "Matthew D. Fuller" To: Drew Derbyshire - UUPC/extended software support cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-Reply-To: <351547FB.6B020444@kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > I came, I downloaded, I installed 2.2.6 beta over the network. (I happened to > do it at 1 AM via the cable modem. It flew.) > > Two minor issues: > > 1) The disk slice editor doesn't know many of the more arcane partition type > numbers. Jordan already saw my PR and fixed it, when the next boot floppy > image is ready I'll test it. > > 2) By default, the kernel only reports I have 16M, when in fact I have 48M. > Windows 95 does see the entire 48M, and FreeBSD will see all 48M if I > explicitly tell it in the configuration file via MAXMEM. > > I didn't think the MAXMEM was required for under 64M. > > Machine is a Compaq P/166. I think that's a Compaq problem. Compaq sucks... I have 72 megs of RAM, had 24, and GENERIC never saw more than 16. Heck, I have 2 empty SIMM slots, and a few SIMMS, so I *COULD* have 80 megs of ram if the motherboard didn't die at about 75 reliable. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 10:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02247 for freebsd-stable-outgoing; Sun, 22 Mar 1998 10:13:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02208 for ; Sun, 22 Mar 1998 10:13:31 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id NAA10998; Sun, 22 Mar 1998 13:12:52 -0500 (EST) Date: Sun, 22 Mar 1998 13:12:52 -0500 (EST) From: Derek Flowers To: Robert Watson cc: Wes Peters - Softweyr LLC , "Daniel O'Callaghan" , stable@FreeBSD.ORG Subject: Re: after the release ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Robert Watson wrote: > On Sat, 21 Mar 1998, Derek Flowers wrote: > > > > > Why not model it after RPM? If the size and md5 do not match, return an > > > > error. Allow the user to overide the check if they wish to do so. > > > > > > > > Just to get a feel for pkg_add, what are the stpes taken to add the > > > > software? I'm thinking the check could be done in the install script, > > > > assuming it executes a script like make would. > > > > > > Errr. How do you know that the md5 is right? Digital signatures have to > > > come into this somewhere :). Or secure trusted transmission (i.e., the > > > HTTPS idea). > > > > Sorry, forgot to mention that RPM uses PGP fingerprints also. > > > > The MD5 can be stored on ftp.freebsd.org where everybody can check it. > > I think you fundamentally misunderstand. MD5's are a one-way hash of the > data. They can be used for error checking, or for digital signatures. > By default, they merely detect changes in the file -- but you need some > way to verify that the hash you retrieve is correct! Two common > approaches to this are shared secret and public/private key. In shared > secret, there are two approaches: > > 1) Include the key in the data md5'd -- when verifying, append the shared > secret, generate the md5, and compare. > > 2) Use the key to encrypt the md5, and ship that with the data. To > verify, generate an md5, encrypt it with the shared secret, and compare > the result. > > Both ways, you have the have the secret, which has to be distributed > somehow. With public private key, they typical approach is to generate > the md5, then encrypt that using the private key, and ship it along. When > you want to verify, md5 the data, then decrypt the version sent along > (using the public key) and compare them. > > Both ways, you have a key distribution problem. And both ways, you may > need code that cannot be exported; at least, not in source code, and > probably without a license. > > Either way, you cannot just "Store the md5s on ftp.freebsd.org" because > there is no way to know that they are securely retrieved :). > > One answer is to use https and your netscape browser's certificate > verification (and built in certificates). People download the browser in > the clear (foolish), but now that they have it (and apparently trust it), > we might as well take advantage of it. > > Key distribution is a fundamental problem; shipping out the public keys on > the CD-ROM might not be a bad idea, btw. > > Robert Watson I see your point. What I was saying is that the md5 sums can be stored on a site where only the core members can change them. I think gnu is working on a public key encryption system that is free and availabe to people outside the US. Maybe it can be applied here. But you still have the problem of key distribution. You could post the public key on a site, but who is to say you won't have the same problem as with md5 distribution. Until a method of secure transfer is available, I think distributing the md5 sums on a known and reputable site is the best option. ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 10:21:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03413 for freebsd-stable-outgoing; Sun, 22 Mar 1998 10:21:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dog.farm.org (gw-hssi-2.farm.org [209.66.103.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03400 for ; Sun, 22 Mar 1998 10:20:58 -0800 (PST) (envelope-from dog.farm.org!dk) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id KAA19841; Sun, 22 Mar 1998 10:24:12 -0800 (PST) Date: Sun, 22 Mar 1998 10:24:12 -0800 (PST) From: Dmitry Kohmanyuk Message-Id: <199803221824.KAA19841@dog.farm.org> To: mike@smith.net.au (Mike Smith) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Help! Upgrade 2.2.5-RELEASE to 2.2-STABLE. Newsgroups: cs-monolit.gated.lists.freebsd.stable Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <199803140337.TAA03072@dingo.cdrom.com> you wrote: > > I think I'll have to join Paul in questioning whether this breakage is > > going to make 2.2.6 a support nightmare. I don't want this to become > > another ``unknown login class root''-style hailstorm. :-( > If you update /sbin/mount at the same time, it's a no-op. I got bitten > by the two different "dedicated" disk types issue though; that hurt. > The fix is still being tested in -current, but I haven't heard any > complaints about it, so I was planning to bring it over tonight. So, does this change work with BSD-partitioned disks (not Micro$oft- partitioned?) I have 4 production 2.2-x boxes all set in this mode (so no need to bother with BIOS geometry...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 10:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03894 for freebsd-stable-outgoing; Sun, 22 Mar 1998 10:25:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.16.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03886 for ; Sun, 22 Mar 1998 10:24:58 -0800 (PST) (envelope-from fpawlak@execpc.com) Received: from darkstar.connect.com (uranus-44.mdm.mke.execpc.com [169.207.79.107]) by mailgw02.execpc.com (8.8.8) id MAA16259; Sun, 22 Mar 1998 12:24:56 -0600 (CST) Received: (from fpawlak@localhost) by darkstar.connect.com (8.9.0.Beta3/8.8.8) id MAA10574; Sun, 22 Mar 1998 12:25:12 -0600 (CST) From: Frank Pawlak Message-Id: <199803221825.MAA10574@darkstar.connect.com> Date: Sun, 22 Mar 1998 12:25:11 -0600 (CST) To: techie@tantivy.stanford.edu Cc: admin@www.megido.inter.net.il, freebsd-stable@FreeBSD.ORG Subject: Re[2]: Surprise Reboots In-Reply-To: <199803220846.AAA09868@tantivy.stanford.edu> X-Mailer: Ishmail 1.3.2-971023-FreeBSD MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I am running 2.2.6-BETA and I experienced a spontaneous reboot. It was more like a hard reset than a reboot and the video went all to hell, appeared to CGA or something like that. I shutdown the computer and checked that all the boards were seated properly and restarted the computer and it worked fine. It was just a single instance -- go figure. It has benn three days now without any problems. Cheers, Frank Bob Vaughan wrote: > I have also experienced a lot of spontaneous reboots and freezes.. > sometimes the machine will do a full reboot, and at other times, it > just > freezes up, and does not respond (except to ping..). > this is with a p5-200 on a IWill P55TV motherboard (built-in adaptech > 2940au) > 64mb ram, 3c905, sb16, another 2940, and a svga card.. hp6020 on the > onboard > 2940 (ahc0), and 4 disks and another cdrom on the other 2940 (ahc1) > currently running 2.2-stable from 980320, but the problem has appeared > numerous times since upgrading to 2.2-stable late last year.. > > I also have a 486dx2-66 running 2.2-stable of 980223, which has not > showed the same problem (but is also not used as much.. mostly as a > ppp > router..) > > both of these systems are on a UPS, and local utility power has been > stable. > I leave them up 24x7. > > NFS is used to export a few filesystems from the pentium to the 486, > but > not the other way around. > > most of the reboots have happened during a buildworld, or when a > buildworld > was left running went I went to bed (and woke up to unclean > filesystems) > > I thought this might be a hardware problem, but i'm not sure.. I have > not > changed the hardware since this problem first appeared, and the > machine > was very stable under 2.2.5-release. > > I cvsup every day or so, and buildworld, if this is successful, then I > installworld, build a kernel, and reboot.. if I have to restart > buildworld, > then I usually cvsup again before doing so.. > > (possibly unrelated, but I have been able to crash XF86331 on this > machine > as well, by opening 2 windows with /usr/ucb/mail running, and closing > them > at the same time.. haven't yet tried it with XF86332..) > > > > I've got a new box, about two weeks ago, to replace my good ol' > DX2/66. > > This box is an Intel Pentium 200Mhz, has a 430TX Motherboard, 32MB > on one > > SDRAM chip, and an ESS Soundcard, a x20 IDE CDROM + 4.3GB EIDE > Western > > Digital Harddrive, and an ATI 3D Rage II. Ofcourse, the minutes I > got it > > I happily installed FreeBSD on it, from a 2.2.5-RELEASE CD I had > burned a > > couple of days before. Everything seemed to go fine, when suddenly > the box > > rebooted. I thought it had to be a power surge or something like > that, so > > I just carried on. (When I just got the machine it had a 166Mhz CPU > in it) > > On the past two weeks, the machine has rebooted on me on random > times, > > Without any warning. Once make buildworld completes, and another > time it > > simply reboots in the middle of the process. > > Thinking it had to be a hardware problem, I have changed the SDRAM > chip > > and upgraded the CPU to a 200Mhz one. I have also cvsup'd to the > latest > > -STABLE sources since, and did a 'make world -j4' with the new > chips. > > it went fine. for the last couple of days, everything seems to be > going > > fine. Last night, I left my box on at night while downloading > xemacs20. > > guess what I found out when I got up in the morning? > > > > mount R/W of / failed - file system is not clean! fun fsck manually > > ... > > > > which means the box had rebooted just like it did before. > > I have no explanation for this, except I get kernel double faults > > sometimes, right before the reboot. I'd tell ya what they say, > except it > > reboots right after that. > > > > Anyway - If someone has similar a similar problem - or similar > hardware - > > Id really like to know about it. > > Thanks. > > Gilad Rom. > > > > > > #I know there are no monsters... Then why do they keep chasing me?? > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > -- > -- Welcome My Son, Welcome To The Machine -- > Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org > | techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM > | P.O. Box 9792, Stanford, Ca 94309-9792 > -- I am Me, I am only Me, And no one else is Me, What could be > simpler? -- > > 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 Mar 22 10:44:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06434 for freebsd-stable-outgoing; Sun, 22 Mar 1998 10:44:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06427; Sun, 22 Mar 1998 10:44:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA00384; Sun, 22 Mar 1998 10:44:32 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803221844.KAA00384@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper cc: Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable In-reply-to: Your message of "Sun, 22 Mar 1998 10:22:20 EST." <19980322102220.55088@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 10:44:32 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Now, I am more inclined on the application clearing the buffer. Cheers, Amancio > Amancio Hasty: > |Joao Carlos Mendes Luis: > | |Amancio Hasty: > | | |There is no need to create an ioctl to clear the buffer that can be > | | |handle by the driver by prior to initiating a start capture to clear > | | |the buffer. > | | > | |Isn't it a waste of CPU ? Do you need to clear the buffer everytime ? > | |Why do you ever need to clear the buffer ? > | > |It is not really a waste of cpu cycles to erase the buffer prior to > |start of capture for continuous operations since it is called only > |once. > > Summary: > > I suggest a driver ioctl() to clear the buffer. But I could live with > the driver always doing this on capture start ONLY if it doesn't do this > when FPS == FPS_MAX. > > Detail: > > I suggested an ioctl() for two reasons. First, because IMO this: > > memset( fd, '\0', 1769472 ); /* Worst case */ > > is wasteful when it can be happening many times a second. When you're > dragging your Fxtv window around with temporal decimation off (FPS = > FPS_MAX), this could be happening 10-20 times a second, depending on your > window manager. > > Now this memset is pointless normally (temporal decimation is off), since > the user is going to see a new frame in 1/30th of second (aka 3.3 > "hundredths" of a second); 1/25th sec for the PAL folks. Thus the > conditional I wrap the buffer clear memset() in: > > if ( c->fps != c->fps_max ) > memset( c->drv_buf, '\0', <...frame size...> ); > > However, when it can be up to almost a full second and the app is polling > the buffer, then this gets annoying. Therefore I suggest not making memset > something that's done before every capture start. > > (Second) We could have the driver only memset the buffer when FPS requested > != FPS max (as I'm doing in the app now), but you could have clients that > are only processing frames on driver interrupt and just don't care what's > in the buffer up until the first interrupt. In which case this memset is > an extra delay and load, and useless work. > > So I suggest a driver ioctl() to clear the buffer. But I could live with > the driver always doing this on capture start ONLY if it doesn't do this > when FPS == FPS_MAX. > > Randall > Amancio Hasty: > |Joao Carlos Mendes Luis: > | |Amancio Hasty: > | | |There is no need to create an ioctl to clear the buffer that can be > | | |handle by the driver by prior to initiating a start capture to clear > | | |the buffer. > | | > | |Isn't it a waste of CPU ? Do you need to clear the buffer everytime ? > | |Why do you ever need to clear the buffer ? > | > |It is not really a waste of cpu cycles to erase the buffer prior to > |start of capture for continuous operations since it is called only > |once. > > Summary: > > I suggest a driver ioctl() to clear the buffer. But I could live with > the driver always doing this on capture start ONLY if it doesn't do this > when FPS == FPS_MAX. > > Detail: > > I suggested an ioctl() for two reasons. First, because IMO this: > > memset( fd, '\0', 1769472 ); /* Worst case */ > > is wasteful when it can be happening many times a second. When you're > dragging your Fxtv window around with temporal decimation off (FPS = > FPS_MAX), this could be happening 10-20 times a second, depending on your > window manager. > > Now this memset is pointless normally (temporal decimation is off), since > the user is going to see a new frame in 1/30th of second (aka 3.3 > "hundredths" of a second); 1/25th sec for the PAL folks. Thus the > conditional I wrap the buffer clear memset() in: > > if ( c->fps != c->fps_max ) > memset( c->drv_buf, '\0', <...frame size...> ); > > However, when it can be up to almost a full second and the app is polling > the buffer, then this gets annoying. Therefore I suggest not making memset > something that's done before every capture start. > > (Second) We could have the driver only memset the buffer when FPS requested > != FPS max (as I'm doing in the app now), but you could have clients that > are only processing frames on driver interrupt and just don't care what's > in the buffer up until the first interrupt. In which case this memset is > an extra delay and load, and useless work. > > So I suggest a driver ioctl() to clear the buffer. But I could live with > the driver always doing this on capture start ONLY if it doesn't do this > when FPS == FPS_MAX. > > Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 11:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12930 for freebsd-stable-outgoing; Sun, 22 Mar 1998 11:21:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12922 for ; Sun, 22 Mar 1998 11:21:28 -0800 (PST) (envelope-from killyou@ein-hashofet.co.il) Received: from localhost (host42-68.mishkei.org.il [62.0.68.42]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id XAA06208; Sun, 22 Mar 1998 23:19:42 +0300 Date: Sat, 21 Mar 1998 22:22:30 +0000 (GMT) From: "Dr. Feelgood" X-Sender: killyou@localhost Reply-To: "Dr. Feelgood" To: Craig Shrimpton cc: Gilad Rom , freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots In-Reply-To: <3.0.5.32.19980322101854.007e1840@titan.os.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Craig Shrimpton wrote: > At 01:08 PM 3/22/98 +0300, Gilad Rom wrote: > >I also have a DX2 box w/8mb of ram and a 270MB hdd, I still have FreeBSD > >on it, and this trouble had never occured. I had alot of uptime there. > >Hmm... Really makes me wonder. > > > > Here'a an SDRAM wierdness story. I have a DFI 586ITXD (ATX)that can take > either EDO or DIMMS. If I use NEC memory, I can only put 1 DIMM in the > system, If I use two, the system is unstable. Switching to Micron memory, > two DIMMS are fine. > > If I put the NEC memory in the DFI 586ITBD, (AT) it will take both chips > without complaint. It is possible that it's the board and not the chips > except that certain date codes of NEC memory will work with two DIMMS! > > -Craig > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Hmm... Well, Reading your previous reply, I checked to see and my DIMM is made by micron, so thats not the problem. Ive had a wierder problem at work. I use a FreeBSD machine as a NATd gateway to route a campus lan to the internet. The box had only 2x8mb simms, and there came the upgrade time. We bought two new micron sdram chips, 32MB each. When Ive tried to install them both, FreeBSD wont reboot. Ive read something about that in the mailing lists. When I remove one chip, it works perfectly. so I left the two old SIMM's in there and now the box has 48MB of ram. works perfectly running 2.2.6-BETA and has weeks of uptime, Never crashed on me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 11:34:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15954 for freebsd-stable-outgoing; Sun, 22 Mar 1998 11:34:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tweetie.online.barbour-index.co.uk (tweetie-pipex.online.barbour-index.co.uk [194.129.192.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15949 for ; Sun, 22 Mar 1998 11:34:13 -0800 (PST) (envelope-from scot@tweetie.online.barbour-index.co.uk) Received: from localhost (scot@localhost) by tweetie.online.barbour-index.co.uk (8.8.8/8.8.7) with SMTP id TAA00377 for ; Sun, 22 Mar 1998 19:34:12 GMT (envelope-from scot@tweetie.online.barbour-index.co.uk) Date: Sun, 22 Mar 1998 19:34:12 +0000 (GMT) From: Scot Elliott To: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-Reply-To: <351547FB.6B020444@kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > I didn't think the MAXMEM was required for under 64M. > > Machine is a Compaq P/166. > > [ and other stuff ] All my machines with more than 64M (some 128M and 96M machines) report the correct amount of RAM when they boot. Does this mean they're actually using it all? I know you're supposed to put the MAXMEM thing into the kernel config file - but I haven't done this yet because it does report it correctly. So is it OK at the minute or should I tell it how much its got? Cheers. Scot. ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)171 7046777 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 11:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17508 for freebsd-stable-outgoing; Sun, 22 Mar 1998 11:40:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17432 for ; Sun, 22 Mar 1998 11:40:03 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id LAA29275; Sun, 22 Mar 1998 11:40:00 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Scot Elliott cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-reply-to: Your message of "Sun, 22 Mar 1998 19:34:12 GMT." Date: Sun, 22 Mar 1998 11:39:59 -0800 Message-ID: <29268.890595599@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > > > I didn't think the MAXMEM was required for under 64M. > > > > Machine is a Compaq P/166. > > > > [ and other stuff ] > > All my machines with more than 64M (some 128M and 96M machines) report the > correct amount of RAM when they boot. Does this mean they're actually Which is what's supposed to happen. I find Drew's report almost inexplicable and quite disturbing - I'd thought that our memory sizing problems were things of the past. > So is it OK at the minute or should I tell it how much its got? If the size reported is OK, you're OK. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 11:43:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18030 for freebsd-stable-outgoing; Sun, 22 Mar 1998 11:43:07 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA18017 for ; Sun, 22 Mar 1998 11:42:59 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yGqe1-0007KK-00; Sun, 22 Mar 1998 11:42:57 -0800 Date: Sun, 22 Mar 1998 11:42:55 -0800 (PST) From: Tom To: Drew Derbyshire - UUPC/extended software support cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-Reply-To: <351547FB.6B020444@kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > I didn't think the MAXMEM was required for under 64M. > > Machine is a Compaq P/166. It isn't, except for Compaq systems. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 12:10:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24162 for freebsd-stable-outgoing; Sun, 22 Mar 1998 12:10:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23899 for ; Sun, 22 Mar 1998 12:09:32 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.uucp.kew.com (sonata.hh.kew.com [192.168.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with SMTP id PAA05523 for ; Sun, 22 Mar 1998 15:09:19 -0500 (EST) Received: from kew.com by sonata.uucp.kew.com (UUPC/extended 1.12y) with UUCP for stable@FreeBSD.ORG; Sun, 22 Mar 1998 15:09:18 -0500 Received: from kew.com by sonata.uucp.kew.com (UUPC/extended 1.12y) with ESMTP for stable@FreeBSD.ORG; Sun, 22 Mar 1998 15:09:16 -0500 Message-ID: <35156FEB.E940269E@kew.com> Date: Sun, 22 Mar 1998 15:09:15 -0500 From: Drew Derbyshire - UUPC/extended software support Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.04 [en]C-MOENE (WinNT; I) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help References: <29268.890595599@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Jordan K. Hubbard wrote: > > > On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > > > > > I didn't think the MAXMEM was required for under 64M. > > > > > > Machine is a Compaq P/166. > > > > > > [ and other stuff ] > > > > All my machines with more than 64M (some 128M and 96M machines) report the > > correct amount of RAM when they boot. Does this mean they're actually > > Which is what's supposed to happen. I find Drew's report almost > inexplicable and quite disturbing - I'd thought that our memory sizing > problems were things of the past. Well, I checked several times, even it was 1 AM. :-) I'll cut a PR on it. > > So is it OK at the minute or should I tell it how much its got? > > If the size reported is OK, you're OK. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 "Unix? What's that? Is that like Linux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 12:24:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25606 for freebsd-stable-outgoing; Sun, 22 Mar 1998 12:24:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25599 for ; Sun, 22 Mar 1998 12:24:41 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id PAA11231; Sun, 22 Mar 1998 15:24:08 -0500 (EST) Date: Sun, 22 Mar 1998 15:24:08 -0500 (EST) From: Derek Flowers To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-Reply-To: <7587.890581120@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Jordan K. Hubbard wrote: > > Basically, I just took the binary distribution off the 2.2.5-RELEASE cd > > and created a skeleton to get it to work with pkg_add. In theory, any > > binary updates would work with the same skeleton. > > Hmmmm. How does this handle the issue of a /tmp directory that's not > big enough to hold the intermediate unpacked copy? That reason is why > bin, doc, manpages, etc are not currently distributed as packages. > > You might look into ``@option extract-in-place'' as a way of getting > around that limitation. > > Jordan What is a minimum size I can expect for the /tmp directory? The biggest distribution tar file is 17MB (the bin distribution, haven't tried the srcs yet). If I'm not mistaken, ``@option extract-in-place'' will just extract the package tar file in whatever the current directory (as set by @cwd) is. The current way the package is set up, this will place a 17MB bin.tgz along with the md5sum file in that directory. pkg_add will not remove these files, correct? Thanks for the response. ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 12:27:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26116 for freebsd-stable-outgoing; Sun, 22 Mar 1998 12:27:49 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from titan.os.com (titan.os.com [209.113.221.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA26111 for ; Sun, 22 Mar 1998 12:27:44 -0800 (PST) (envelope-from craigs@os.com) Received: from fargo [209.113.221.2] by titan.os.com (SMTPD32-4.03) id A56014D6013E; Sun, 22 Mar 1998 15:32:32 EST5EDT Message-ID: <000301bd55d0$a556f560$02dd71d1@fargo.os.com> From: "Craig Shrimpton" To: Subject: Installworld via NFS Date: Sun, 22 Mar 1998 15:25:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've setup a build machine to install stable via NFS to various other servers. I am able to mount /usr/src and /usr/ojb via NFS to all my machines (even an ancient Linux version) except for the ones I really want to upgrade. The machines in question are 2.1.7 versions. I can mount Linux filesystems and other 2.1.7 systems but I can't mount the 2.2.6-BETA file systems. I get the following message when I try a mount (as root): bash# mount_nfs my.export.host:/usr/obj /usr/obj bash# mount_nfs: can't access /usr/obj: Permission denied I have the filesystem exported on 2.2.6-BETA as: /usr /usr/obj /usr/src -maproot=root host.my.network host2.my.network Has something changed with 2.2.6-BETA's NFS or am I not using the correct mount command? Thanks, Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 12:30:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26877 for freebsd-stable-outgoing; Sun, 22 Mar 1998 12:30:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA26869 for ; Sun, 22 Mar 1998 12:30:32 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yGrNh-0003if-00; Sun, 22 Mar 1998 14:30:09 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Drew Derbyshire - UUPC/extended software support cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-reply-to: Your message of "Sun, 22 Mar 1998 15:09:15 EST." <35156FEB.E940269E@kew.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 14:30:05 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Drew Derbyshire UUPC/extended e-mail: software@kew.com > Telephone: 617-279-9812 > > "Unix? What's that? Is that like Linux?" Aawww, man, I'm too old for this. Well, since the Open Group owns the word Unix, I prefer to call it BSD and let that word die. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 12:45:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28980 for freebsd-stable-outgoing; Sun, 22 Mar 1998 12:45:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from uk1.imdb.com (UK1.IMDb.COM [192.68.174.59]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA28959 for ; Sun, 22 Mar 1998 12:45:03 -0800 (PST) (envelope-from robh@imdb.com) Received: from robh.imdb.com [194.222.68.23] by uk1.imdb.com with esmtp (Exim 1.62 #1) id 0yGraM-00010b-00; Sun, 22 Mar 1998 20:43:14 +0000 Date: Sun, 22 Mar 1998 20:43:05 +0000 (GMT) From: Rob Hartill X-Sender: robh@localhost To: stable@FreeBSD.ORG Subject: no 'Cache' again Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk We now have a brand-new machine running 2.2.6-BETA and it too has top showing no cache.. last pid: 9194; load averages: 0.92, 0.83, 0.69 19:25:53 38 processes: 1 running, 37 sleeping CPU states: 51.4% user, 0.0% nice, 17.9% system, 0.4% interrupt, 30.4% idle Mem: 62M Active, 6292K Inact, 22M Wired, 7087K Buf, 35M Free Swap: 384M Total, 64K Used, 384M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 7839 root 10 0 1692K 1164K wait 0:01 2.65% 2.29% make 188 root 2 0 412K 932K select 0:03 0.00% 0.00% sshd 214 robh 2 0 436K 848K select 0:03 0.00% 0.00% screen-3.7.4 215 robh 18 0 612K 936K pause 0:00 0.00% 0.00% tcsh 550 robh 18 0 612K 900K pause 0:00 0.00% 0.00% tcsh 202 robh 18 0 644K 872K pause 0:00 0.00% 0.00% tcsh 217 root 18 0 636K 872K pause 0:00 0.00% 0.00% tcsh 213 robh 18 0 356K 660K pause 0:00 0.00% 0.00% screen-3.7.4 133 root 18 0 332K 520K pause 0:00 0.00% 0.00% cron 220 root 10 0 504K 548K wait 0:00 0.00% 0.00% make 27184 root 10 0 320K 544K wait 0:00 0.00% 0.00% make 18614 root 10 0 516K 540K wait 0:00 0.00% 0.00% make 226 root 10 0 504K 520K wait 0:00 0.00% 0.00% make 27185 root 10 0 492K 340K wait 0:00 0.00% 0.00% sh 18613 root 10 0 492K 328K wait 0:00 0.00% 0.00% sh 25291 root 10 0 492K 324K wait 0:00 0.00% 0.00% sh it's running "make world" (again, to benchmark the time) on a non-GENERIC kernel. This machine is a Piix333 with 128mb. -- Rob Hartill Internet Movie Database (Ltd) http://www.moviedatabase.com/ .. a site for sore eyes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 14:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19187 for freebsd-stable-outgoing; Sun, 22 Mar 1998 14:45:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19151 for ; Sun, 22 Mar 1998 14:44:59 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA08652; Sun, 22 Mar 1998 14:44:55 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Drew Derbyshire - UUPC/extended software support cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-reply-to: Your message of "Sun, 22 Mar 1998 15:09:15 EST." <35156FEB.E940269E@kew.com> Date: Sun, 22 Mar 1998 14:44:55 -0800 Message-ID: <8649.890606695@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Well, I checked several times, even it was 1 AM. :-) > > I'll cut a PR on it. Actually, I didn't look closely enough to note that it was a Compaq machine. Not so mysterious now. Keep the PR open, however, since it may prove incentive for using Jonathan Lemon's vm86 stuff to get at the memory size information later on. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 14:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19409 for freebsd-stable-outgoing; Sun, 22 Mar 1998 14:46:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19394 for ; Sun, 22 Mar 1998 14:46:30 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA08670; Sun, 22 Mar 1998 14:46:20 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Derek Flowers cc: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-reply-to: Your message of "Sun, 22 Mar 1998 15:24:08 EST." Date: Sun, 22 Mar 1998 14:46:20 -0800 Message-ID: <8667.890606780@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > What is a minimum size I can expect for the /tmp directory? The biggest > distribution tar file is 17MB (the bin distribution, haven't tried the > srcs yet). The *minimum* size? Probably about 5-6MB of free space. It's not rare at all to see the emacs package blow up because of this, though I do search around for additional space if I can find it (e.g. /var/tmp or /usr/tmp are used in preference if I can find the space there). > If I'm not mistaken, ``@option extract-in-place'' will just extract the > package tar file in whatever the current directory (as set by @cwd) is. > The current way the package is set up, this will place a 17MB bin.tgz > along with the md5sum file in that directory. pkg_add will not remove > these files, correct? It will not, no. Not in the extract-in-place scenario. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 16:13:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03073 for freebsd-stable-outgoing; Sun, 22 Mar 1998 16:13:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03064 for ; Sun, 22 Mar 1998 16:13:37 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA28002; Mon, 23 Mar 1998 10:43:01 +1030 (CST) Message-Id: <199803230013.KAA28002@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Drew Derbyshire - UUPC/extended software support , stable@FreeBSD.ORG Subject: Re: okay, I WILL get out and help push In-reply-to: Your message of "Fri, 20 Mar 1998 16:54:54 BST." <19980320165454.44993@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 10:43:01 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > PnP is supported only for a single Ethernet card - the Trust Ethernet > Combo, which is an NE2000 clone. I don't think the code has been > merged to -stable - I wrote it, and I have been having some problems > with that card under -STABLE, so I would really hope not. Well, that is to say, the driver code doesn't understand pnp, but that doesn't matter, as you can configure pnp devices manually if you boot with -c. --------------------------------------------------------------------- |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 Mar 22 16:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03951 for freebsd-stable-outgoing; Sun, 22 Mar 1998 16:17:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03942 for ; Sun, 22 Mar 1998 16:17:18 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id TAA11632; Sun, 22 Mar 1998 19:16:26 -0500 (EST) Date: Sun, 22 Mar 1998 19:16:25 -0500 (EST) From: Derek Flowers To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-Reply-To: <8667.890606780@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Jordan K. Hubbard wrote: > > What is a minimum size I can expect for the /tmp directory? The biggest > > distribution tar file is 17MB (the bin distribution, haven't tried the > > srcs yet). > > The *minimum* size? Probably about 5-6MB of free space. It's not > rare at all to see the emacs package blow up because of this, though I > do search around for additional space if I can find it (e.g. /var/tmp > or /usr/tmp are used in preference if I can find the space there). > > > If I'm not mistaken, ``@option extract-in-place'' will just extract the > > package tar file in whatever the current directory (as set by @cwd) is. > > The current way the package is set up, this will place a 17MB bin.tgz > > along with the md5sum file in that directory. pkg_add will not remove > > these files, correct? > > It will not, no. Not in the extract-in-place scenario. > > Jordan After reading over the manual pages for pkg_add, I discovered that the package is placed in a "staging area" created by mktemp and defaults to "/var/tmp/instmp.XXXXX". What I was reffering to above is that the package contains two files bin.tgz and md5sum along with the comment, description, and install script. The packing list containted the following: @name bin-2.2.5_RELEASE.tgz @cwd / @ignore_inst bin.tgz @ignore_inst md5sum So you see, the pkg_add will not install anything. The install script is doing all the work. All this is naught because I redid my thinking and rewrote the skeleton to create a normal package. But now I am having some problems and was wondering if they were bugs. Apparently, pkg_create was having some problems with the bin distribution. It would work great until hitting the dev directory. Without including the dev directory in the packing list, pkg_create worked fine. It also worked find for all the other distributions. I figured that I could remove the dev entries in the packing list except MAKEDEV and MAKEDEV.local and just run "MAKEDEV all" from the POST-INSTALL section of the installation script. I also tried using the "@option extract-in-place" and found that pkg_add ignores any "@cwd" directives during installation. Is this normal? Here is a copy of the packing list: @option extract-in-place @cwd /tmp/test @srcdir /tmp/games/pkg usr/games/hide/adventure usr/games/hide/arithmetic usr/games/hide/atc usr/games/hide/backgammon usr/games/hide/teachgammon usr/games/hide/battlestar usr/games/hide/bcd usr/games/hide/boggle usr/games/hide/canfield >From this, the files should end up in the /tmp/test directory but instead end up off the / directory. Without the extract-in-place option, they end up where they belong. Even overiding the base directory with pkg_add proved futile. Anyway, as of right now, I have packaged versions of all the distributions for 2.2.5-RELEASE and as soon as I get a chance, I'll test them on a junk machine. ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 16:31:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06306 for freebsd-stable-outgoing; Sun, 22 Mar 1998 16:31:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06288 for ; Sun, 22 Mar 1998 16:31:34 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA28146; Mon, 23 Mar 1998 11:01:05 +1030 (CST) Message-Id: <199803230031.LAA28146@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ted Spradley cc: "Matthew D. Fuller" , Drew Derbyshire - UUPC/extended software support , stable@FreeBSD.ORG Subject: Re: after the release ... In-reply-to: Your message of "Fri, 20 Mar 1998 15:09:16 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 11:01:05 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I have trouble understanding the comfort part here. How does one feel more c > omfortable applying a big binary patch? The point of free (as in freedom) so > ftware is that you get the sources. With a binary patch you get the assuranc > es of a faceless corporation that you will be allowed to spend hours listenin > g to music on the telephone if you have difficulty with the binary patch. Is > that more comfortable than learning to type "make world"? Hmm.... "make world" costs 300mB of HD space :) And you need to keep your sources up to date.. *I* do it, but lots of people don't... --------------------------------------------------------------------- |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 Mar 22 16:33:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06898 for freebsd-stable-outgoing; Sun, 22 Mar 1998 16:33:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06892 for ; Sun, 22 Mar 1998 16:33:12 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.uucp.kew.com (sonata.hh.kew.com [192.168.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with SMTP id TAA06083 for ; Sun, 22 Mar 1998 19:33:06 -0500 (EST) Received: from kew.com by sonata.uucp.kew.com (UUPC/extended 1.12y) with UUCP for stable@freebsd.org; Sun, 22 Mar 1998 19:33:06 -0500 Received: from kew.com by sonata.uucp.kew.com (UUPC/extended 1.12y) with ESMTP for stable@freebsd.org; Sun, 22 Mar 1998 19:33:03 -0500 Message-ID: <3515ADBF.FB39CDFD@kew.com> Date: Sun, 22 Mar 1998 19:33:03 -0500 From: Drew Derbyshire - UUPC/extended software support Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.04 [en]C-MOENE (WinNT; I) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: MSDOSFS (Problem Report kern/2232) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I see in GNATS that above reference problem is still open. Does -stable still have problems with large MS-DOS partitions? (The fantasy-factory is a test machine and willing to Die for the Cause, yes, but isn't down right suicidal.) Did the changes for long file names get merged down? -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 "Unix-to-Unix Copy Program," said PDP-1. "You will never find a more wretched hive of bugs and flamers. We must be cautious." - DECWars To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 17:01:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11741 for freebsd-stable-outgoing; Sun, 22 Mar 1998 17:01:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11723 for ; Sun, 22 Mar 1998 17:01:41 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA28437; Mon, 23 Mar 1998 11:31:08 +1030 (CST) Message-Id: <199803230101.LAA28437@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cy Schubert - ITSD Open Systems Group cc: "Daniel O'Callaghan" , gkshenaut@ucdavis.edu, stable@FreeBSD.ORG Subject: Re: after the release ... In-reply-to: Your message of "Fri, 20 Mar 1998 23:48:52 -0800." <199803210749.XAA15210@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 11:31:08 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Another consideration: What if somebody modifies the O/S at their > site. MVS, for example, uses USERMODS which automatically get dumped > when patches (PTF's or APARFIXES), or new product (FMID's) are applied. > Would those of us maintaining FreeBSD sites be willing to follow a > regimen as specified by the chosen patch philosophy? On the other hand > would Sun's simpler approach work -- if the file's checksum (MD5?) > doesn't match what the patch expects, abort? Well, that is the whole can of worms IMHO.. I mean if you could guarantee that the system would be in a given state then a binary upgrade would be quite easy. The main problem IMHO would be making a system which didn't mangle any custom stuff you've done to your machine.. I see making a 'patch' consist of a group of things to apply/change/suggest which have pre/co-requisites, and if these are wrong(ie the checksum doesn't match or the date is too new/old) then don't apply that group.. ie make each group atomic, so that if part of it fails, then back the whole group out. --------------------------------------------------------------------- |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 Mar 22 18:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24291 for freebsd-stable-outgoing; Sun, 22 Mar 1998 18:22:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24280 for ; Sun, 22 Mar 1998 18:22:45 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt1-139.HiWAAY.net [208.147.147.139]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id UAA28787 for ; Sun, 22 Mar 1998 20:22:43 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id SAA01501 for ; Sun, 22 Mar 1998 18:16:50 -0600 (CST) Message-Id: <199803230016.SAA01501@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-stable@FreeBSD.ORG Subject: "su" segmentation faults From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 18:16:50 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk nospam: {1007} uname -a FreeBSD nospam.hiwaay.net 2.2.6-BETA FreeBSD 2.2.6-BETA #0: Sat Mar 21 19:38:51 CST 1998 root@nospam.hiwaay.net:/usr/src/sys/compile/PPRO200 i386 nospam: {1008} Any idea what's going on? This is probably the first time I've enabled the Kerberos stuff: /etc/make.conf: # Kerberos IV # If you want KerberosIV (KTH eBones), define this: # MAKE_KERBEROS4= yes I'm cvsup'ing src-all, src-crypto, src-eBones, and src-secure into my local /home/ncvs directory, then used "cd /usr/src && cvs -q checkout -P -r RELENG_2_2 src" to make my intial source tree. Since then I've only used "cd src && cvs -q update src" to do updates. Last night was the first "build world", earlier I was only doing "build makeworld" simply to see that it worked. nospam: {1008} su Segmentation fault nospam: {1009} ls -l `which su` -r-sr-xr-x 1 root bin 16384 Mar 22 17:32 /usr/bin/su nospam: {1010} Late breaking news: Commented out "MAKE_KERBEROS4= yes" and re-"make world"'ed. "su" now works. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 21:32:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28416 for freebsd-stable-outgoing; Sun, 22 Mar 1998 21:32:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28406 for ; Sun, 22 Mar 1998 21:32:26 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id AAA27402; Mon, 23 Mar 1998 00:46:24 -0500 (EST) (envelope-from mark) Message-ID: <19980323004623.47042@vmunix.com> Date: Mon, 23 Mar 1998 00:46:23 -0500 From: Mark Mayo To: stable@FreeBSD.ORG Subject: state of NFS in -stable ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi all. I was just curious if the round of changes to NFS (specifically the client) by John Dyson in -CURRENT made it back into -STABLE?? The reason I ask is that I just nuked a -STABLE machine from about 3-4 weeks ago while creating some zip archives as an NFS client.. I didn't get a chance to see the error message, but tomorrow I'll start testing the latest BETA release and see if I can't reproduce the problem (as well as test the rest of -BETA). -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 22:13:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03438 for freebsd-stable-outgoing; Sun, 22 Mar 1998 22:13:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03397; Sun, 22 Mar 1998 22:12:57 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (5wXaPTfBfZ5UilvRQ4gFcAWHEUPK6vNc@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id IAA17389; Mon, 23 Mar 1998 08:12:47 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (sRHF/+SP5jpcvlSm8kgLLrWHjGMS9xbV@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA03716; Mon, 23 Mar 1998 08:12:46 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199803230612.IAA03716@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper cc: Joao Carlos Mendes Luis , Amancio Hasty , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 08:12:45 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Randall Hopper wrote: > Thanks for the report Mark! Now its just a question of ioctl() or default > capture start behavior. Then I'll get the fxtv port chg PR in. I already have it in my local tree looking like a ports patch. Get the word from Satoshi, and I'll commit it in no time :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 22:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06989 for freebsd-stable-outgoing; Sun, 22 Mar 1998 22:35:29 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06976 for ; Sun, 22 Mar 1998 22:35:22 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id RAA28084; Mon, 23 Mar 1998 17:35:10 +1100 (EST) Date: Mon, 23 Mar 1998 17:35:09 +1100 (EST) From: "Daniel O'Callaghan" To: Derek Flowers cc: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I think Derek is doing a great job! Congrats. However, I do also think that Cy Schubert made a very valid point that we need to identify what it is that is going to be updated using this package mechanism. If the pkg mechanism include feature enhancements to the system, then people may be reluctant to use it, lest they change somethin on which their system depends. Alex changed the size of the ipfw structure and created an incompatibility between ipfw(8) and ip_fw.[ch] last November/December. The result was that a kernel upgrade meant a userland upgrade for ipfw(8). This is likely to be a good reason many will shy away from enhancement packages. If the pkg mechanism is only for bug fixes, that's fine, until you need to produce a package for a bug fix in an enhancement. The only way to cater for both scenarios is to flag each package as either ENHANCEMENT or FIX, and make any FIX packages dependent on the ENHANCEMENT package. Of course, if there is a bug fix in (e.g.) ipfw which is unrelated to, but after, an enhancement, we need two packages. As you can see, this is starting to get yucky, and it is a good reason to sit down and work out exactly what it is we want to achieve with this upgrade mechanism. Does anyone else have any ideas? Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 22:41:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08278 for freebsd-stable-outgoing; Sun, 22 Mar 1998 22:41:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA08139 for ; Sun, 22 Mar 1998 22:40:40 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yH0uS-0000NS-00; Sun, 22 Mar 1998 22:40:36 -0800 Date: Sun, 22 Mar 1998 22:40:32 -0800 (PST) From: Tom To: Mark Mayo cc: stable@FreeBSD.ORG Subject: Re: state of NFS in -stable ? In-Reply-To: <19980323004623.47042@vmunix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Mark Mayo wrote: > Hi all. I was just curious if the round of changes to NFS (specifically > the client) by John Dyson in -CURRENT made it back into -STABLE?? I doubt it, as these changes caused some *serious* problems in current. They would likely require extension changes to even apply to stable, assuming that they are relevant. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 22:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10957 for freebsd-stable-outgoing; Sun, 22 Mar 1998 22:59:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bogslab.ucdavis.edu (root@bogslab.ucdavis.edu [128.120.162.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10924 for ; Sun, 22 Mar 1998 22:59:25 -0800 (PST) (envelope-from greg@bogslab.ucdavis.edu) Received: from myrtle1.bogs.org (root@myrtle1.bogs.org [198.137.203.39]) by bogslab.ucdavis.edu (8.7.4/8.7.3) with ESMTP id WAA12283 for ; Sun, 22 Mar 1998 22:59:22 -0800 (PST) Received: from myrtle1.bogs.org (greg@localhost [127.0.0.1]) by myrtle1.bogs.org (8.6.12/8.6.12) with ESMTP id WAA10963 for ; Sun, 22 Mar 1998 22:57:36 -0800 Message-Id: <199803230657.WAA10963@myrtle1.bogs.org> To: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-reply-to: Your message of "Mon, 23 Mar 1998 17:35:09 +1100." Reply-To: gkshenaut@ucdavis.edu Date: Sun, 22 Mar 1998 22:57:12 -0800 From: Greg Shenaut Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In message , "Daniel O'Callaghan" cleopede: > >I think Derek is doing a great job! Congrats. However, I do also think >that Cy Schubert made a very valid point that we need to identify what it >is that is going to be updated using this package mechanism. > >If the pkg mechanism include feature enhancements to the system, then >people may be reluctant to use it, lest they change somethin on >which their system depends. Alex changed the size of the ipfw structure >and created an incompatibility between ipfw(8) and ip_fw.[ch] last >November/December. The result was that a kernel upgrade meant a >userland upgrade for ipfw(8). This is likely to be a good reason many >will shy away from enhancement packages. > >If the pkg mechanism is only for bug fixes, that's fine, until you need >to produce a package for a bug fix in an enhancement. > >The only way to cater for both scenarios is to flag each package as >either ENHANCEMENT or FIX, and make any FIX packages dependent on the >ENHANCEMENT package. I think patches are very different from packages. Packages are optional modules which can be added to a system; patches fix bugs in the system. Packages are distributed with the CD-ROM; it would make no sense for a patch to be distributed with a CD-ROM. It may or may not be the case that a mechanism similar to that which is currently being used for packages could be bent to implement patches, but I can't see what this buys us. I don't think it really matters very much how a particular patch is implemented--it should be up to the developer. What we need to do is to specify the semantics of a patch so that the patches can be distributed and applied with a minimum of fuss. -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 22 23:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20638 for freebsd-stable-outgoing; Sun, 22 Mar 1998 23:40:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20568 for ; Sun, 22 Mar 1998 23:40:06 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA11488; Mon, 23 Mar 1998 18:30:29 +1100 Date: Mon, 23 Mar 1998 18:30:29 +1100 From: Bruce Evans Message-Id: <199803230730.SAA11488@godzilla.zeta.org.au> To: software@kew.com, stable@FreeBSD.ORG Subject: Re: MSDOSFS (Problem Report kern/2232) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >I see in GNATS that above reference problem is still open. > >Does -stable still have problems with large MS-DOS partitions? (The Only 2.1-stable. 2.2 never had it. >Did the changes for long file names get merged down? No. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 00:16:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04083 for freebsd-stable-outgoing; Mon, 23 Mar 1998 00:16:07 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04024 for ; Mon, 23 Mar 1998 00:15:56 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id DAA15803; Mon, 23 Mar 1998 03:15:16 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803230815.DAA15803@dyson.iquest.net> Subject: Re: state of NFS in -stable ? In-Reply-To: from Tom at "Mar 22, 98 10:40:32 pm" To: tom@uniserve.com (Tom) Date: Mon, 23 Mar 1998 03:15:16 -0500 (EST) Cc: mark@vmunix.com, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > On Mon, 23 Mar 1998, Mark Mayo wrote: > > > Hi all. I was just curious if the round of changes to NFS (specifically > > the client) by John Dyson in -CURRENT made it back into -STABLE?? > > I doubt it, as these changes caused some *serious* problems in current. > They would likely require extension changes to even apply to stable, > assuming that they are relevant. > I agree. Even if the fixes are applicable, it is MUCH too late to move into the stable tree for 2.2.6. The complexity of the fixes is too great even for a release in a few months. There is even more to do!!! :-(. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 01:47:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17264 for freebsd-stable-outgoing; Mon, 23 Mar 1998 01:47:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17258 for ; Mon, 23 Mar 1998 01:47:01 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id JAA18568; Mon, 23 Mar 1998 09:46:25 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id JAA22844; Mon, 23 Mar 1998 09:46:13 GMT Message-ID: <19980323094611.21526@iii.co.uk> Date: Mon, 23 Mar 1998 09:46:11 +0000 To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= Cc: "Jordan K. Hubbard" , Mike Smith , stable@FreeBSD.ORG Subject: Re: A day in the life of a hacker (was: Re: 'Code Freeze') References: <11036.890349578@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.85e In-Reply-To: =?iso-8859-1?Q?=3Cxzp4t0sq9f0=2Efsf=40hrotti=2Eifi=2Euio=2Eno=3E=3B_from?= =?iso-8859-1?Q?_Dag-Erling_Coidan_Sm=F8rgrav__on_Sat=2C_Mar_21=2C_1998_a?= =?iso-8859-1?Q?t_05=3A46=3A11PM_+0100?= Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sat, Mar 21, 1998 at 05:46:11PM +0100, Dag-Erling Coidan Smørgrav wrote: > And, well, whaddya know, in slightly less time than it takes me to > read half a chapter - with 128 MB RAM and two 2940s, she's a slow > booter - she's back up, alive and kicking and purring like a cat. Not > a single glitch, not a single complaint, her fan doesn't even miss a > beat. I'd say I'm in love if I didn't suspect it'd lower my chances of > picking up girls. You haven't merged in changes that have been made to the /etc directory. This may bite you later. You also haven't updated the /dev directory, which may also bite you later. is definitely worth a read (typos and all, I've just spotted a couple, rats). N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 03:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24960 for freebsd-stable-outgoing; Mon, 23 Mar 1998 03:17:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA24916; Mon, 23 Mar 1998 03:17:41 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 23 Mar 1998 6:17:07 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA13222; Mon, 23 Mar 98 06:17:05 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id GAA14397; Mon, 23 Mar 1998 06:16:37 -0500 Message-Id: <19980323061637.00745@ct.picker.com> Date: Mon, 23 Mar 1998 06:16:37 -0500 From: Randall Hopper To: Amancio Hasty , Mark Murray , asami@FreeBSD.ORG Cc: Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Amancio Hasty , Mark Murray , asami@FreeBSD.ORG, Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG, committers@FreeBSD.ORG References: <199803230612.IAA03716@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803230612.IAA03716@greenpeace.grondar.za>; from Mark Murray on Mon, Mar 23, 1998 at 08:12:45AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Mark Murray: |Randall Hopper wrote: |> Thanks for the report Mark! Now its just a question of ioctl() or default |> capture start behavior. Then I'll get the fxtv port chg PR in. | |I already have it in my local tree looking like a ports patch. Get the |word from Satoshi, and I'll commit it in no time :-). Mark Murray: |Please may I add the following patch to graphics/fxtv. Without it, fxtv |is useless. If you don't mind doing 2 commits intead of just 1, sure. We still haven't yet resolved who's going to clear that buffer and under what circumstances. Amancio, what do you think about a BT848_CLEAR_ON_START ioctl(). When set to False (the default), behavior is as before -- no clear. When True, the portion of the buffer to be used for captured frames gets cleared before the start is issued. This would avoid having to make fxtv set-uid root or to request signals 1-29 times/sec just to use only the first one for bookkeeping. Thanks, Randall Content-Description: patch-ab |--- ../fxtv-0.46.ORIG/tvcapture.c Tue Oct 28 01:59:41 1997 |+++ tvcapture.c Sun Mar 22 16:43:45 1998 |@@ -1126,7 +1126,7 @@ | /* Just mmap the biggest buffer we'll need and be done with it. */ | /* (Buffer used for non-directvideo captures) */ | c->drv_buf = (TV_UINT8 *) mmap( (caddr_t)0, MAX_MMAP_BUF_SIZE, |- PROT_READ|PROT_WRITE, 0, c->fd, (off_t)0 ); |+ PROT_READ, MAP_SHARED, c->fd, (off_t)0 ); | if ( c->drv_buf == (TV_UINT8 *) -1 ) { | fprintf( stderr, "mmap of driver buffer failed: %s\n", | strerror(errno) ); |@@ -1537,9 +1537,9 @@ | video.ramsize = 0; | | /* If TDEC is on, may be a while before old trash gets written on */ |- if ( c->fps != c->fps_max ) |+/* if ( c->fps != c->fps_max ) | memset( c->drv_buf, '\0', |- g.w * g.h * c->pix_geom_list[ c->pix_geom_idx ].Bpp ); |+ g.w * g.h * c->pix_geom_list[ c->pix_geom_idx ].Bpp ); */ | } | memcpy( &pix_geom, &c->pix_geom_list[ c->pix_geom_idx ], | sizeof( pix_geom ) ); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 03:26:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26140 for freebsd-stable-outgoing; Mon, 23 Mar 1998 03:26:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26081; Mon, 23 Mar 1998 03:26:27 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id DAA12818; Mon, 23 Mar 1998 03:26:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803231126.DAA12818@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper cc: Mark Murray , asami@FreeBSD.ORG, Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Fxtv vs Stable In-reply-to: Your message of "Mon, 23 Mar 1998 06:16:37 EST." <19980323061637.00745@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 03:26:12 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Fine, Feel free to implement BT848_CBUF , must BT848 ioctl commands are of the form BT848_[S|G]FUNCTION for example BT848_SHUE sets the hue and BT848_GHUE gets the hue value. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 03:58:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00554 for freebsd-stable-outgoing; Mon, 23 Mar 1998 03:58:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA00437; Mon, 23 Mar 1998 03:58:39 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 23 Mar 1998 6:56:53 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA13852; Mon, 23 Mar 98 06:56:51 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id GAA14767; Mon, 23 Mar 1998 06:56:24 -0500 Message-Id: <19980323065624.22389@ct.picker.com> Date: Mon, 23 Mar 1998 06:56:24 -0500 From: Randall Hopper To: Amancio Hasty , Mark Murray Cc: asami@FreeBSD.ORG, Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Amancio Hasty , Mark Murray , asami@FreeBSD.ORG, Joao Carlos Mendes Luis , multimedia@FreeBSD.ORG, stable@FreeBSD.ORG, committers@FreeBSD.ORG References: <19980323061637.00745@ct.picker.com> <199803231126.DAA12818@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803231126.DAA12818@rah.star-gate.com>; from Amancio Hasty on Mon, Mar 23, 1998 at 03:26:12AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Amancio Hasty: |Feel free to implement BT848_CBUF , must BT848 ioctl commands |are of the form BT848_[S|G]FUNCTION for example BT848_SHUE sets the hue and |BT848_GHUE gets the hue value. Mark Murray: |Sure - 2.2.6 is going to be released RSN, and it would be a shame |if it was sent out without a functioning FXTV. We may not have the |opportunity to commit a prettier fix later. Ok. Didn't realize it was coming up that quick. I'll implement the clear buf ioctl later this evening and cook driver and fxtv 0.46 patches. If 2.2.6 can't wait that long (I don't know the time constraints), then feel free to commit your fxtv patch Mark. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 05:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15547 for freebsd-stable-outgoing; Mon, 23 Mar 1998 05:40:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15507 for ; Mon, 23 Mar 1998 05:40:01 -0800 (PST) (envelope-from rom_glsa@ein-hashofet.co.il) Received: from mommy (host38-68.mishkei.org.il [62.0.68.38]) by mail.mishkei.org.il (8.8.5/8.8.5) with ESMTP id RAA07469 for ; Mon, 23 Mar 1998 17:38:54 +0300 Message-ID: <35152328.565D654E@ein-hashofet.co.il> Date: Sun, 22 Mar 1998 16:41:44 +0200 From: Gilad Rom X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Surprise Reboots hit again :(( X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hmm... This is getting worse by the minute. When Ive installed FreeBSD 2.2.5-RELEASE from the CD, it rebooted on me. When I cvsup'd to -STABLE/2.2.6-BETA, it rebooted on me too. Last night, I desprately decided to upgrade to -CURRENT. (Ive eliminated the possibility of a hardware bug, ive replaced both cpu and ram). Guess what? -CURRENT reboots every 5 minutes on me. This is really pissing me off, as I have no clue what can go wrong. If there is ANYONE with a 430TX chipset motherboard, please let me know, as its the only hardware compnent I havent replaced yet, which may cause the trouble. I am composing this message in the Win95 version of Netscape, And hope to return to pine as soon as I can. In the meanwhile, my system is completely unusable. If anyone can come up with the most remote possibility - Please mail me. (And yes, Win95 does NOT reboot... too bad.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 06:58:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27334 for freebsd-stable-outgoing; Mon, 23 Mar 1998 06:58:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from versa.eng.comsat.com (versa.eng.comsat.com [134.133.169.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27291 for ; Mon, 23 Mar 1998 06:58:00 -0800 (PST) (envelope-from marc@versa.eng.comsat.com) Received: (from marc@localhost) by versa.eng.comsat.com (8.8.8/8.7.3) id JAA13045; Mon, 23 Mar 1998 09:57:12 -0500 (EST) Date: Mon, 23 Mar 1998 09:57:12 -0500 (EST) From: Marc Giannoni Message-Id: <199803231457.JAA13045@versa.eng.comsat.com> To: freebsd-stable@FreeBSD.ORG, rom_glsa@ein-hashofet.co.il Subject: Re: Surprise Reboots hit again :(( Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Try upgrading to one of the SNAP releases. These are binary compilations (releases) with patches for problems. FreeBSD has been having problems getting Bug Free CDRoms out lately. I have the 2.2.5 CD and there are problems with it, although my 'low end' hardware has been stable. The 430TX(HX) is a good motherboard, you should have no problems. Another thing you should try is CVSUP. Install sources from your CDRom, CVSUP updates from the FreeBSD site. (This will get you all the lates patches to 'stable') and then 'buildworld', followed by 'installworld'. (See the online HTML handbook for details) This has been reported to work well for patching 2.5.5. Remember: 'stable' is what you want if you value a stable system - and 'current' is what you want if you like to get 'under the hood'. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 07:00:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27881 for freebsd-stable-outgoing; Mon, 23 Mar 1998 07:00:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (0@passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27863 for ; Mon, 23 Mar 1998 07:00:50 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id HAA06456; Mon, 23 Mar 1998 07:00:49 -0800 (PST) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaajCBa; Mon Mar 23 07:00:45 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id HAA10455; Mon, 23 Mar 1998 07:00:38 -0800 (PST) Message-Id: <199803231500.HAA10455@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpd010445; Mon Mar 23 07:00:33 1998 X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: "Daniel O'Connor" cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Callaghan" , gkshenaut@ucdavis.edu, stable@FreeBSD.ORG Subject: Re: after the release ... In-reply-to: Your message of "Mon, 23 Mar 1998 11:31:08 +1030." <199803230101.LAA28437@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 07:00:32 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > Another consideration: What if somebody modifies the O/S at their > > site. MVS, for example, uses USERMODS which automatically get dumped > > when patches (PTF's or APARFIXES), or new product (FMID's) are applied. > > Would those of us maintaining FreeBSD sites be willing to follow a > > regimen as specified by the chosen patch philosophy? On the other hand > > would Sun's simpler approach work -- if the file's checksum (MD5?) > > doesn't match what the patch expects, abort? > Well, that is the whole can of worms IMHO.. > I mean if you could guarantee that the system would be in a given state then a > binary upgrade would be quite easy. The main problem IMHO would be making a > system which didn't mangle any custom stuff you've done to your machine.. That's right! That's why a philosophy should be chosen and strictly adhered to. Every sysadmin would need to follow this or he/she would have a mess, e.g. patches would not install if the state was not consistent with what was expected, and a reinstall would be required to get back to a know state. > > I see making a 'patch' consist of a group of things to apply/change/suggest > which have pre/co-requisites, and if these are wrong(ie the checksum doesn't > match or the date is too new/old) then don't apply that group.. ie make each > group atomic, so that if part of it fails, then back the whole group out. That's where the USERMOD would be used. The individual sysadmin would need to tell the system by using a packaged application to modify the system. This way the system would know why any particular binary (or source module) would be inconsistent with expectations. (The USERMOD process would allow modifications but make backup copies of "vendor" supplied binaries and sources in the process.) If a USERMOD was detected, the backup copy would be used and the USERMOD would be verbosely deleted. The sysadmin would need to re-apply their customization. I'm not saying that we need to adopt IBM's approach. We just need to consider _all_ of the ramifications and do it right. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 07:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01250 for freebsd-stable-outgoing; Mon, 23 Mar 1998 07:19:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (0@passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01201 for ; Mon, 23 Mar 1998 07:18:54 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id HAA08026; Mon, 23 Mar 1998 07:18:49 -0800 (PST) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaactma; Mon Mar 23 07:18:41 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id HAA10493; Mon, 23 Mar 1998 07:18:37 -0800 (PST) Message-Id: <199803231518.HAA10493@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpd010486; Mon Mar 23 07:18:14 1998 X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: gkshenaut@ucdavis.edu cc: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-reply-to: Your message of "Sun, 22 Mar 1998 22:57:12 PST." <199803230657.WAA10963@myrtle1.bogs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 07:18:13 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > In message , "Dan iel O'Callaghan" cleopede: > > > >I think Derek is doing a great job! Congrats. However, I do also think > >that Cy Schubert made a very valid point that we need to identify what it > >is that is going to be updated using this package mechanism. > > > >If the pkg mechanism include feature enhancements to the system, then > >people may be reluctant to use it, lest they change somethin on > >which their system depends. Alex changed the size of the ipfw structure > >and created an incompatibility between ipfw(8) and ip_fw.[ch] last > >November/December. The result was that a kernel upgrade meant a > >userland upgrade for ipfw(8). This is likely to be a good reason many > >will shy away from enhancement packages. > > > >If the pkg mechanism is only for bug fixes, that's fine, until you need > >to produce a package for a bug fix in an enhancement. > > > >The only way to cater for both scenarios is to flag each package as > >either ENHANCEMENT or FIX, and make any FIX packages dependent on the > >ENHANCEMENT package. > > I think patches are very different from packages. Packages are > optional modules which can be added to a system; patches fix bugs > in the system. Packages are distributed with the CD-ROM; it would > make no sense for a patch to be distributed with a CD-ROM. It may > or may not be the case that a mechanism similar to that which is > currently being used for packages could be bent to implement patches, > but I can't see what this buys us. I don't think it really matters > very much how a particular patch is implemented--it should be up > to the developer. What we need to do is to specify the semantics > of a patch so that the patches can be distributed and applied with > a minimum of fuss. ... and backed out with a minimum of fuss... Sun basically uses their package software to manage patches. They take checksums (could be MD5 for our purposes) of each binary (could be done with source code patches too) and abort if the checksums don't match. If they have prerequisites, they bundle the prereqs and the patches themselves into a jumbo patch. This is a simpler approach and should work as well. The only problem with their approach is that their software tells me that something doesn't match. It doesn't tell me why it doesn't match. It doesn't matter what we do, packages, RPM's, Sun's approach, IBM's approach, or something that we've dreamed up. What does matter is that carefully choose something that works, and stick with it. You will also notice that the examples I gave, packages, RPM's, Sun's approach, and IBM's approach all manage the base software as a prerequisite. In order to make this work managing the base software using packages or whatever we decide to use is a requirement to doing this successfully. Managing patches is an all or nothing proposition. You either manage the whole system that way or you don't do it at all. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 07:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04664 for freebsd-stable-outgoing; Mon, 23 Mar 1998 07:42:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04627 for ; Mon, 23 Mar 1998 07:42:04 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id JAA14487; Mon, 23 Mar 1998 09:41:27 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 23 Mar 1998 09:41:26 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Drew Derbyshire - UUPC/extended software support cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-Reply-To: <351547FB.6B020444@kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > 2) By default, the kernel only reports I have 16M, when in fact I have 48M. > Windows 95 does see the entire 48M, and FreeBSD will see all 48M if I > explicitly tell it in the configuration file via MAXMEM. > > I didn't think the MAXMEM was required for under 64M. > > Machine is a Compaq P/166. Of the few Compaq machines that I have installed FreeBSD on, RAM over 16MB was never recognized and had to be explicitly set with MAXMEM in the kernel. -- Chris Dillon --- cdillon@inter-linc.net --- cdillon@wolves.k12.mo.us /* Powered by FreeBSD, the best operating system on the planet. Available for Intel x86 and compatible computers. SPARC and Alpha ports currently under development. (http://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 Mar 23 07:57:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08274 for freebsd-stable-outgoing; Mon, 23 Mar 1998 07:57:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08263 for ; Mon, 23 Mar 1998 07:57:28 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA22361; Mon, 23 Mar 1998 16:57:14 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Mon, 23 Mar 1998 16:57:12 +0100 (MET) Mime-Version: 1.0 To: nik@iii.co.uk Cc: "Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= =?iso-8859-1?Q?=2C?= \"Jordan K. Hubbard\"" , Mike Smith , stable@FreeBSD.ORG Subject: Re: A day in the life of a hacker (was: Re: 'Code Freeze') References: <11036.890349578@time.cdrom.com> <19980323094611.21526@iii.co.uk> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 23 Mar 1998 16:57:11 +0100 In-Reply-To: nik@iii.co.uk's message of "Mon, 23 Mar 1998 09:46:11 +0000" Message-ID: Lines: 42 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA08269 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk nik@iii.co.uk writes: > On Sat, Mar 21, 1998 at 05:46:11PM +0100, Dag-Erling Coidan Smørgrav wrote: > > [make world story] > You haven't merged in changes that have been made to the /etc directory. > This may bite you later. You also haven't updated the /dev directory, which > may also bite you later. Oh, yeah, right, I forgot that I am a complete idiot, have no idea how FreeBSD is designed and have never made world before. Gee, sorry, Officer. I'll be more careful in the future. Nik, you are *not* the sole authority on 'make world'. Other people also have brains. Other people also have a long experience with FreeBSD. Other people sometimes even read their cvsup logs and keep track of what has changed since their last make world so they will know what needs to be done. As its subject line suggests, my article was *not* technical. It was simply meant as an entertaining "success story" to cheer up Jordan with. It was not meant to reflect precisely my procedure for 'make world'; it doesn't even get close to telling half the story. I did not tell about reading cvsup logs to see what had changed; I did not tell about diffing /usr/etc/rc* to see what had changed before installing them; I did not tell about making sure my /etc/fstab complied with the new conventions. > > > is definitely worth a read (typos and all, I've just spotted a couple, rats). You forgot to enclose this in ... . Frankly, I find your 'make world' guide (yes, I did read it, at about the time you first put it up) overconservative and overproblematizing, though it contains much useful information. Did it ever occur to you that it might actually scare people away from 'make world' instead of teaching them how to do it? -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 08:04:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09658 for freebsd-stable-outgoing; Mon, 23 Mar 1998 08:04:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netjava.com (Espresso.NetJava.net [204.253.66.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA09651 for ; Mon, 23 Mar 1998 08:04:02 -0800 (PST) (envelope-from jayb@netjava.com) Received: from ssuply.arn.net (ssuply.arn.net [204.177.232.173]) by netjava.com (NTMail 3.02.13) with ESMTP id oa330864 for ; Mon, 23 Mar 1998 10:18:54 -0600 Message-ID: <3516890D.1C25FB46@netjava.com> Date: Mon, 23 Mar 1998 10:08:45 -0600 From: Jay Bratcher X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i586) MIME-Version: 1.0 To: stable@FreeBSD.ORG, Chris Dillon Subject: Re: FreeBSD can't find 32M of my 48M without help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Chris Dillon wrote: > > On Sun, 22 Mar 1998, Drew Derbyshire - UUPC/extended software support wrote: > > > 2) By default, the kernel only reports I have 16M, when in fact I have 48M. > > Windows 95 does see the entire 48M, and FreeBSD will see all 48M if I > > explicitly tell it in the configuration file via MAXMEM. > > > > I didn't think the MAXMEM was required for under 64M. > > > > Machine is a Compaq P/166. > > Of the few Compaq machines that I have installed FreeBSD on, RAM over 16MB > was never recognized and had to be explicitly set with MAXMEM in the > kernel. Incidentally, this is not unique to FreeBSD - Linux suffers from the same problem, at least on the DeskPro 2000 series... Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 08:23:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12584 for freebsd-stable-outgoing; Mon, 23 Mar 1998 08:23:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12540 for ; Mon, 23 Mar 1998 08:23:17 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id IAA04234; Mon, 23 Mar 1998 08:23:06 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Mon, 23 Mar 1998 08:23:06 -0800 (PST) From: Chris Timmons To: Gilad Rom cc: freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots hit again :(( In-Reply-To: <35152328.565D654E@ein-hashofet.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Gilad, Perhaps you have aggressive memory timings set; just for kicks see if you can back the timings off to the most conservative settings (perhaps there is a 70ns setting you could try.) You might also try resetting bios to setup defaults if your bios supports that. The fact that Win95 does not reboot pretty much means that Win95 does not reboot. I had bad memory in an NT system - NT got all of the way installed and would run for a couple hours before dying; FreeBSD could barely get started booting a kernel before it died. The conventional wisdom is that different operating systems tickle the hardware differently or perhaps more intensely. Regards, -Chris On Sun, 22 Mar 1998, Gilad Rom wrote: > Hmm... This is getting worse by the minute. > When Ive installed FreeBSD 2.2.5-RELEASE from the CD, it rebooted on me. > > When I cvsup'd to -STABLE/2.2.6-BETA, it rebooted on me too. > Last night, I desprately decided to upgrade to -CURRENT. > (Ive eliminated the possibility of a hardware bug, ive replaced both cpu > and ram). > Guess what? -CURRENT reboots every 5 minutes on me. > This is really pissing me off, as I have no clue what can go wrong. > If there is ANYONE with a 430TX chipset motherboard, please let me know, > as its > the only hardware compnent I havent replaced yet, which may cause the > trouble. > I am composing this message in the Win95 version of Netscape, And hope > to return > to pine as soon as I can. In the meanwhile, my system is completely > unusable. > If anyone can come up with the most remote possibility - Please mail me. > > (And yes, Win95 does NOT reboot... too bad.) > > > > 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 Mon Mar 23 08:26:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13368 for freebsd-stable-outgoing; Mon, 23 Mar 1998 08:26:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bigbrother ([206.29.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA13336 for ; Mon, 23 Mar 1998 08:26:40 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id MAA06673 for ; Mon, 23 Mar 1998 12:16:16 -0500 Received: from fault.rstcorp.com(206.29.49.18) by bigbrother.rstcorp.com via smap (V2.0) id xma006665; Mon, 23 Mar 98 12:15:22 -0500 Received: (from vshah@localhost) by rstcorp.com (8.8.1/8.8.1) id LAA08899; Mon, 23 Mar 1998 11:24:56 -0500 (EST) Date: Mon, 23 Mar 1998 11:24:56 -0500 (EST) Message-Id: <199803231624.LAA08899@rstcorp.com> MIME-Version: 1.0 From: "Viren R. Shah" To: freebsd-stable@FreeBSD.ORG Subject: 2.2.6-BETA: data point X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk just a report on 2.2.6-BETA: FreeBSD hal 2.2.6-BETA FreeBSD 2.2.6-BETA #0: Thu Mar 12 14:11:10 EST 1998 This machine (Dell PowerEdge 2200/266, single processor w/ 128M) has been happily chugging along as our NFS server for the past 2 weeks, and has been working with a variety of UNIXen NFS clients (Solaris, SunOS, AIX, IRIX, Linux). The only gotchas (which I had already been told of by people on the lists) were: 1. Use NFSv2 (-2 flag to mountd) 2. Start rpc.lockd otherwise certain apps (pine, for example on Solaris 2.4) don't like it. It hasn't been updated since Mar 12, as it is working perfectly well, there's no need to fix it. Thanks to the FreeBSD team, and the release team for keeping -stable stable. Viren -- Viren R. Shah {viren@rstcorp.com} "The key of strategy, little Vor," she explained kindly, "is not to choose _a_ path to victory, but to choose so that _all_ paths lead to a victory." -- Cavilo explains her strategy to Miles (Lois McMaster Bujold, The Vor Game) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 08:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19121 for freebsd-stable-outgoing; Mon, 23 Mar 1998 08:59:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA19064 for ; Mon, 23 Mar 1998 08:59:49 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yHAZc-00040w-00; Mon, 23 Mar 1998 08:59:44 -0800 Date: Mon, 23 Mar 1998 08:59:42 -0800 (PST) From: Tom To: Gilad Rom cc: freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots hit again :(( In-Reply-To: <35152328.565D654E@ein-hashofet.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 22 Mar 1998, Gilad Rom wrote: > (Ive eliminated the possibility of a hardware bug, ive replaced both cpu > and ram). No you haven't. What about the motherboard? What about L2 cache? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 09:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20204 for freebsd-stable-outgoing; Mon, 23 Mar 1998 09:03:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20145 for ; Mon, 23 Mar 1998 09:03:45 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id RAA06245; Mon, 23 Mar 1998 17:03:41 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id RAA02933; Mon, 23 Mar 1998 17:03:39 GMT Message-ID: <19980323170338.16252@iii.co.uk> Date: Mon, 23 Mar 1998 17:03:38 +0000 To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= Cc: stable@FreeBSD.ORG Subject: Re: A day in the life of a hacker (was: Re: 'Code Freeze') References: <11036.890349578@time.cdrom.com> <19980323094611.21526@iii.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.85e In-Reply-To: =?iso-8859-1?Q?=3Cxzpiup58ko8=2Efsf=40gnipahellir=2Eifi=2Euio=2Eno=3E=3B?= =?iso-8859-1?Q?_from_Dag-Erling_Coidan_Sm=F8rgrav__on_Mon=2C_Mar_23=2C_1?= =?iso-8859-1?Q?998_at_04=3A57=3A11PM_+0100?= Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi, On Mon, Mar 23, 1998 at 04:57:11PM +0100, Dag-Erling Coidan Smørgrav wrote: > nik@iii.co.uk writes: > > On Sat, Mar 21, 1998 at 05:46:11PM +0100, Dag-Erling Coidan Smørgrav wrote: > > > [make world story] > > You haven't merged in changes that have been made to the /etc directory. > > This may bite you later. You also haven't updated the /dev directory, which > > may also bite you later. > > Oh, yeah, right, I forgot that I am a complete idiot, have no idea how > FreeBSD is designed and have never made world before. Gee, sorry, > Officer. I'll be more careful in the future. Sat on this side of the keyboard I have no idea of your expertise with FreeBSD. I also have no idea of the level of expertise of anyone else who reads your message and thinks "Oh, that sounds easy, I'll give it a try." And then mails -questions or -stable (or -current) when they have problems. That's why my reply was sent back to the mailing list and not to you (although you will probably have received a cc:). I've already had 2 e-mail messages today as a result of my reply to you from folks basically saying "Nice page, didn't realise there was such a lot to doing 'make world', but you make it pretty clear. I feel more confident about this now." > Nik, you are *not* the sole authority on 'make world'. I couldn't agree more. I am, however, one of very few people who's bothered to try and document the process (as I see it). > Other people > also have brains. Other people also have a long experience with > FreeBSD. Other people sometimes even read their cvsup logs and keep > track of what has changed since their last make world so they will > know what needs to be done. And others don't, and they read messages on the mailing lists that hand wave the process by just saying "You can re-make the world now", or "Now merge in the changes to /etc" without explaining what this actually means. That's my intended audience. Sorry that you caught it this time. > > > > > > is definitely worth a read (typos and all, I've just spotted a couple, rats). > > You forgot to enclose this in ... . Why? What if I'd used instead? > Frankly, I find your 'make world' guide (yes, I did read it, at about > the time you first put it up) If you have the time I'd appreciate you taking another look. It's changed significantly in the past eight months or so. In particular, it talks about more versions of FreeBSD, and some actions that I'd previously suggested were a *must* (such as doing the build in single user mode) are now shown as being ommitable, if the reader is confident. > overconservative and overproblematizing, though it contains much useful > information. Strangely, I don't think you've ever contacted me about this before? I welcome comments and corrections about the tutorial, and as the list of contributors shows, many people have taken the time and trouble to do just that. But generalisations such as yours above don't help me. > Did it ever occur to you that it might actually scare people away from > 'make world' instead of teaching them how to do it? Not really. But then if 38 80x25 screenfulls of text scares someone then they (IMHO) shouldn't be trying to upgrade by recompiling their system, they'll almost certainly be more comfortable with sysinstall's 'Upgrade' option. FWIW, I'm (slowly) working on a way of tagging the information in the tutorial as being aimed at a specific class of user. This will (eventually) allow me to easily produce versions of the tutorial with differing amounts of 'background fluff' as appropriate. But I'm not there yet. Whatever. As I say, sorry you got caught by the 'make-world autoresponse' embedded in my finger tips, I'll try and be less trigger happy in the future. And if you can take the time to look at the latest version of the document, I'd appreciate any suggestions for improvements. N Oh, I have to have 'flame' section huh? Um, er, "Your mother wears Army boots". Gosh, that was fairly pathetic. I think I'd better stick to trying to argue the merits of the documentation, rather than getting all hot and bothered by it. -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 09:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21257 for freebsd-stable-outgoing; Mon, 23 Mar 1998 09:07:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21186 for ; Mon, 23 Mar 1998 09:07:29 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id LAA14814; Mon, 23 Mar 1998 11:07:28 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 23 Mar 1998 11:07:28 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Jay Bratcher cc: stable@FreeBSD.ORG Subject: Re: FreeBSD can't find 32M of my 48M without help In-Reply-To: <3516890D.1C25FB46@netjava.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Jay Bratcher wrote: > Chris Dillon wrote: > > Of the few Compaq machines that I have installed FreeBSD on, RAM over 16MB > > was never recognized and had to be explicitly set with MAXMEM in the > > kernel. > > Incidentally, this is not unique to FreeBSD - Linux suffers from the > same problem, at least on the DeskPro 2000 series... I wouldn't doubt this at all. While Compaq's are sometimes pretty good machines, they sure do throw in their share of proprietary junk. In Compaq's favor, the Prosignia VS server I installed 2.2.5 on has been running flawlessly and has an uptime of 16 days right now and rising (would be about 46 days if I had realized it wasn't plugged into the UPS.. sigh..), and I only set the box up about 48 days ago. :-) The onboard SCSI controller (53c710 I think it was) was not supported, nor was the additional Compaq EISA Wide SCSI controller we have. No big deal, since we already had an Adaptec 2740 for it also. :-) -- Chris Dillon --- cdillon@inter-linc.net --- cdillon@wolves.k12.mo.us /* Powered by FreeBSD, the best operating system on the planet. Available for Intel x86 and compatible computers. SPARC and Alpha ports currently under development. (http://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 Mar 23 09:12:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21993 for freebsd-stable-outgoing; Mon, 23 Mar 1998 09:12:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.wtower.com (lee@[208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21976 for ; Mon, 23 Mar 1998 09:12:06 -0800 (PST) (envelope-from lee@freebie.wtower.com) Received: (from lee@localhost) by freebie.wtower.com (8.8.7/8.8.7) id MAA00382; Mon, 23 Mar 1998 12:11:54 -0500 (EST) (envelope-from lee) Message-ID: <19980323121154.26667@freebie.wtower.com> Date: Mon, 23 Mar 1998 12:11:54 -0500 From: Lee Cremeans To: Tom Cc: Gilad Rom , freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots hit again :(( Reply-To: lcremean@tidalwave.net References: <35152328.565D654E@ein-hashofet.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from Tom on Mon, Mar 23, 1998 at 08:59:42AM -0800 X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, Mar 23, 1998 at 08:59:42AM -0800, Tom wrote: > > On Sun, 22 Mar 1998, Gilad Rom wrote: > > > (Ive eliminated the possibility of a hardware bug, ive replaced both cpu > > and ram). > > No you haven't. What about the motherboard? What about L2 cache? What make is this motherboard? There are some motherboards (notably PCCHips-made ones) with horrible reputations for quality... -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | hcremean (at) vt.edu FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://wakky.dyn.ml.org/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 09:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22968 for freebsd-stable-outgoing; Mon, 23 Mar 1998 09:21:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22962 for ; Mon, 23 Mar 1998 09:21:31 -0800 (PST) (envelope-from softweyr@xmission.xmission.com) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.8/8.7.5) id KAA29543; Mon, 23 Mar 1998 10:20:51 -0700 (MST) From: Wes Peters - Softweyr LLC Message-Id: <199803231720.KAA29543@xmission.xmission.com> Subject: Re: after the release ... To: eivind@yes.no (Eivind Eklund) Date: Mon, 23 Mar 1998 10:20:50 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: <19980321154810.61297@follo.net> from "Eivind Eklund" at Mar 21, 98 03:48:10 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Eivind wrote: > Sure. However, I'm not planning on initially spending time on > anything but checking the signatures; as long as a way exists of > signing those files, it will be usable (and IMO useful :-) It's not so terrible to require you to install the JDK in order to *create* packages; this will probably be one (or a few) person(s) working on "snapshots" of the -STABLE tree. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 09:52:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27384 for freebsd-stable-outgoing; Mon, 23 Mar 1998 09:52:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27379 for ; Mon, 23 Mar 1998 09:52:23 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA11130 for ; Mon, 23 Mar 1998 09:51:54 -0800 (PST) Received: from pau-amma.whistle.com(207.76.205.64) by whistle.com via smap (V1.3) id sma011128; Mon Mar 23 09:51:29 1998 Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.7/8.8.7) id JAA10716 for freebsd-stable@freebsd.org; Mon, 23 Mar 1998 09:51:29 -0800 (PST) (envelope-from dhw) Date: Mon, 23 Mar 1998 09:51:29 -0800 (PST) From: David Wolfskill Message-Id: <199803231751.JAA10716@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: after the release ... Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >From: Cy Schubert - ITSD Open Systems Group >Date: Fri, 20 Mar 1998 23:48:52 -0800 >A LOT of thought needs to be put into this. Very true. >Patch packages would need to support pre-requisites, co-requisites and >be able to superceed other packages; and don't forget a backout process. Agreed. >A simpler approach would be to use Sun's approach which bundles related >patches into jumbo patches (though I'm partial to IBM's approach). I have slightly more experience (both in duration & depth) with the approach IBM use{s,d} with MVS (either /XA or /ESA), and confess to slightly more comfort with that (vs. Sun's approach). >Either way you just can't jump into this. The first step would be to >have the base O/S managed via packages. That would be big chunk of the >work. Then there's designing a patch application (or borrowing one) >and managing patch releases. IBM even has a separate product (SPM/E) to do this... and it's a non-trival resource consumer (read "hog"). >Other questions to be answered would be, what O/S changes would be good >candidates for patches and what could wait for the next release? Who >would make these decisions? Who would package the patches? Well, these seem similar in scope & nature to the issues of deciding when some source gets committed.... >Another consideration: What if somebody modifies the O/S at their >site. MVS, for example, uses USERMODS which automatically get dumped >when patches (PTF's or APARFIXES), or new product (FMID's) are applied. Ummm.... Not necessarily. What we did (when I was an MVS systems programmer) was write USERMODs, and add them to the SPM/E database. What this does (and may be what Cy is referring to) is notify you if there's a conflict between the USERMOD and a patch that needs to be applied. With that knowledge, then, the maintainer would then: * Go look up the docs to see what sort of change there is. Sometimes the change doesn't really affect the operation of the USERMOD, and it's safe to: * Back out ("reject") the USERMOD. * Install ("apply") the patch. * (Possibly) modify the SMP/E packaging for the USERMOD so it will install cleanly. * Install ("apply") the USERMOD. * Sometimes a patch really does change the interface that a USERMOD uses, and in that case, it may be necessary to re-work the USERMOD itself. * Other times, the patch make the whole USERMOD in question either moot or impossible... but at least SMP/E will be rather noisy & let you know about it... so there's some hope you can find out about it beforehand, and make a decision as to what you're going to do. > Would those of us maintaining FreeBSD sites be willing to follow a >regimen as specified by the chosen patch philosophy? On the other hand >would Sun's simpler approach work -- if the file's checksum (MD5?) >doesn't match what the patch expects, abort? The USERMOD approach has some very nice things -- not least of which was the basic design (in MVS), such that if the system found the existence of a load module with a specified name (in a certain restricted list of system libraries, of course!), control would be passed to that module with a documented parameter list, and the module could do certain things -- typically involving returning one of several return codes (to indicate that the operation should continue as if the module had not been called, should be rejected with a whimper, should be re-tried, or aborted). The basic idea is that one makes a clean separation between local code vs. "vendor" code. >I think a lot of thought and discussion needs to be put into this >before we decide if this should be done or when, should it be decided >that we do it, what it should look like and whether the community is >willing to commit using such a tool (there's no sense doing it if no >one will be willing to follow the regimen). There was, in the MVS world, a significant degree of resistance to the use of SMP/E for packaging USERMODs... especially because of a lack of discipline. And it's rather like using RCS: it works well, as long as everyone "plays by the ruules" -- but when somone goes in as root, modifies a file, tries to write it, is told it's a read-only file, and thinks "What do you mean, 'read-only': I'm root, I can change anything!" and writes the change anyway... well, things tend to go downhill.... >Date: Mon, 23 Mar 1998 11:31:08 +1030 >From: "Daniel O'Connor" >I mean if you could guarantee that the system would be in a given state then a >binary upgrade would be quite easy. The main problem IMHO would be making a >system which didn't mangle any custom stuff you've done to your machine.. That's where careful "packaging" of USERMODs comes in: defining *all* of the pre-requisites & co-requisites. >I see making a 'patch' consist of a group of things to apply/change/suggest >which have pre/co-requisites, and if these are wrong(ie the checksum doesn't >match or the date is too new/old) then don't apply that group.. ie make each >group atomic, so that if part of it fails, then back the whole group out. Yes, I think so.... >Date: Sun, 22 Mar 1998 22:57:12 -0800 >From: Greg Shenaut >I think patches are very different from packages. Packages are >optional modules which can be added to a system; patches fix bugs >in the system. I'm comfortable with that terminology, and think that the distinction is useful & valuable. >Packages are distributed with the CD-ROM; it would >make no sense for a patch to be distributed with a CD-ROM. I wouldn't go quite that far, though I'd freely admit that it would make more sense to have the content of the CD be fairly fixed, and have a much more dynamic set of patches (and a somewhat less dynamic list of which patches to apply to the CD to get a stable, working system). Cheers, david -- David Wolfskill dhw@whistle.com (650) 577-7158 pager: (650) 401-0168 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 10:40:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05818 for freebsd-stable-outgoing; Mon, 23 Mar 1998 10:40:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailgw01.execpc.com (sendmail@mailgw01.execpc.com [169.207.16.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05713 for ; Mon, 23 Mar 1998 10:39:41 -0800 (PST) (envelope-from fpawlak@execpc.com) Received: from darkstar.connect.com (mendicat-12.mdm.mke.execpc.com [169.207.79.139]) by mailgw01.execpc.com (8.8.8) id MAA24191; Mon, 23 Mar 1998 12:39:37 -0600 (CST) Received: (from fpawlak@localhost) by darkstar.connect.com (8.8.8/8.8.8) id MAA12427; Mon, 23 Mar 1998 12:40:08 -0600 (CST) From: Frank Pawlak To: nik@iii.co.uk Subject: Re: A day in the life of a hacker (was: Re: 'Code Freeze') Date: Mon, 23 Mar 1998 12:38:00 -0600 X-Mailer: KMail [version 0.5.5] Cc: stable@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <98032312400700.11920@darkstar.connect.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Nik, I for one have found your documentation on make world most useful. I am fairly new to UNIX and FreeBSD, and have completed five or six make worlds. Could not have done them without your docs. Cheers, Frank On Mon, 23 Mar 1998, nik@iii.co.uk wrote: > Hi, > > > > On Mon, Mar 23, 1998 at 04:57:11PM +0100, Dag-Erling Coidan Smørgrav wrote: > > nik@iii.co.uk writes: > > > On Sat, Mar 21, 1998 at 05:46:11PM +0100, Dag-Erling Coidan Smørgrav wrote: > > > > [make world story] > > > You haven't merged in changes that have been made to the /etc directory. > > > This may bite you later. You also haven't updated the /dev directory, which > > > may also bite you later. > > > > Oh, yeah, right, I forgot that I am a complete idiot, have no idea how > > FreeBSD is designed and have never made world before. Gee, sorry, > > Officer. I'll be more careful in the future. > > Sat on this side of the keyboard I have no idea of your expertise with > FreeBSD. I also have no idea of the level of expertise of anyone else who > reads your message and thinks "Oh, that sounds easy, I'll give it a try." > And then mails -questions or -stable (or -current) when they have problems. > > That's why my reply was sent back to the mailing list and not to you > (although you will probably have received a cc:). > > I've already had 2 e-mail messages today as a result of my reply to you from > folks basically saying "Nice page, didn't realise there was such a lot to > doing 'make world', but you make it pretty clear. I feel more confident about > this now." > > > Nik, you are *not* the sole authority on 'make world'. > > I couldn't agree more. I am, however, one of very few people who's bothered > to try and document the process (as I see it). > > > Other people > > also have brains. Other people also have a long experience with > > FreeBSD. Other people sometimes even read their cvsup logs and keep > > track of what has changed since their last make world so they will > > know what needs to be done. > > And others don't, and they read messages on the mailing lists that hand > wave the process by just saying "You can re-make the world now", or "Now > merge in the changes to /etc" without explaining what this actually means. > > That's my intended audience. Sorry that you caught it this time. > > > > > > > > > > is definitely worth a read (typos and all, I've just spotted a couple, rats). > > > > You forgot to enclose this in ... . > > Why? What if I'd used > instead? > > > Frankly, I find your 'make world' guide (yes, I did read it, at about > > the time you first put it up) > > If you have the time I'd appreciate you taking another look. It's changed > significantly in the past eight months or so. In particular, it talks > about more versions of FreeBSD, and some actions that I'd previously > suggested were a *must* (such as doing the build in single user mode) are > now shown as being ommitable, if the reader is confident. > > > overconservative and overproblematizing, though it contains much useful > > information. > > Strangely, I don't think you've ever contacted me about this before? I > welcome comments and corrections about the tutorial, and as the list of > contributors shows, many people have taken the time and trouble to do > just that. > > But generalisations such as yours above don't help me. > > > Did it ever occur to you that it might actually scare people away from > > 'make world' instead of teaching them how to do it? > > Not really. But then if 38 80x25 screenfulls of text scares someone then > they (IMHO) shouldn't be trying to upgrade by recompiling their system, > they'll almost certainly be more comfortable with sysinstall's 'Upgrade' > option. > > FWIW, I'm (slowly) working on a way of tagging the information in the > tutorial as being aimed at a specific class of user. This will (eventually) > allow me to easily produce versions of the tutorial with differing amounts > of 'background fluff' as appropriate. But I'm not there yet. > > Whatever. > > As I say, sorry you got caught by the 'make-world autoresponse' embedded > in my finger tips, I'll try and be less trigger happy in the future. And > if you can take the time to look at the latest version of the document, > I'd appreciate any suggestions for improvements. > > N > > > > > > Oh, I have to have 'flame' section huh? > > Um, er, "Your mother wears Army boots". > > Gosh, that was fairly pathetic. I think I'd better stick to trying to > argue the merits of the documentation, rather than getting all hot and > bothered by it. > > > -- > Work: nik@iii.co.uk | FreeBSD + Perl + Apache > Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need > Play: nik@freebsd.org | Microsoft? > > 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 Mon Mar 23 11:12:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12575 for freebsd-stable-outgoing; Mon, 23 Mar 1998 11:12:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dis.VAZ.ru (dis.vaz.ru [195.144.198.161]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12393 for ; Mon, 23 Mar 1998 11:12:06 -0800 (PST) (envelope-from V.Petrov@VAZ.ru) Received: by dis.VAZ.ru with UUCP id AA22696 (5.65c8/DIS-1.4.4 for freebsd-stable@FreeBSD.ORG); Mon, 23 Mar 1998 23:10:50 +0400 Received: from localhost (vap@localhost) by asm.vaz.ru (8.8.8/8.8.5) with SMTP id XAA02846; Mon, 23 Mar 1998 23:08:32 +0400 (KSK) X-Authentication-Warning: asm.vaz.ru: vap owned process doing -bs Date: Mon, 23 Mar 1998 23:08:28 +0400 (KSK) From: "Vladimir A. Petrov" X-Sender: vap@asm.vaz.ru To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots In-Reply-To: <199803221539.HAA01522@cwsys.cwsent.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Good Day! On Sun, 22 Mar 1998, Cy Schubert - ITSD Open Systems Group wrote: > 2.2.5-RELEASE had a couple of problems that exhibited themselves as VM > problems that caused the system to panic occasionally. You can either > upgrade to 2.2.6-BETA or email me and I will send you a 42K patch that > fixes these and various other problems that I had, including a hack to > fix a NULLFS panic (PR kern/5355). I have a problem like that. Currently I use FreeBSD 2.2.5-STABLE and all works fine until I don't try to do 'make world'. When I start making world my system surprisely reboots after some time. I don't have any ideas about it because I don't found any error messages in log files and all reboots has happened without my presence. By this cause I still can't upgrade to 2.2.6-BETA. I have CVSuped tree but I can't rebuild from it. So, if Your patch may help me in this situation then it will be so kind if You send me Your patch. Thank You. With best regards, Vladimir Petrov. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 11:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20539 for freebsd-stable-outgoing; Mon, 23 Mar 1998 11:38:20 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20367 for ; Mon, 23 Mar 1998 11:37:52 -0800 (PST) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id LAA14250; Mon, 23 Mar 1998 11:37:30 -0800 (PST) Message-Id: <199803231937.LAA14250@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaamcoa; Mon Mar 23 11:37:21 1998 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: "Vladimir A. Petrov" cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots In-reply-to: Your message of "Mon, 23 Mar 1998 23:08:28 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 11:36:50 -0800 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Good Day! > > On Sun, 22 Mar 1998, Cy Schubert - ITSD Open Systems Group wrote: > > > 2.2.5-RELEASE had a couple of problems that exhibited themselves as VM > > problems that caused the system to panic occasionally. You can either > > upgrade to 2.2.6-BETA or email me and I will send you a 42K patch that > > fixes these and various other problems that I had, including a hack to > > fix a NULLFS panic (PR kern/5355). > > I have a problem like that. Currently I use FreeBSD 2.2.5-STABLE and > all works fine until I don't try to do 'make world'. When I start > making world my system surprisely reboots after some time. I don't > have any ideas about it because I don't found any error messages > in log files and all reboots has happened without my presence. > By this cause I still can't upgrade to 2.2.6-BETA. I have CVSuped > tree but I can't rebuild from it. So, if Your patch may help me > in this situation then it will be so kind if You send me Your > patch. Since I've received a number of requests for the patches, here they are. They are a collection of stuff from the -stable CVS tree, an email I received from John Dyson (I hope I've spelled John's name correctly) about vfs_bio.c, two patches of my own to fix a FDESC filesystem fix (I believe committed in -stable or -current quite some time ago) and a NULLFS hack, various security fixes, some patches from the 2.2.5 Errata, and some other odds and sodds to fix various other problems I've had. All of the patches I am enclosing, except for two of them, have been committed to the either the -stable or -current branches. The two that have not been committed to the -stable or -current branches are my NULLFS hack (much discussion continues on the best way to solve this) and John's vfs_bio.c that he emailed me back in December to fix kern/4844 and other related VM problems. Prior to applying to some of the patches below the systems would panic at least every 36 hours. Now they stay up until I reboot them (days or weeks). I believe that the VM patches and the vfs_bio.c patches are the ones These patches should ONLY be applied to 2.2.5-RELEASE and should not be installed on anything else unless reworked for those systems. These patches have made my systems stable. Please discard any patches in the following that have already been incorporated in -stable. diff -ur src/gnu/usr.bin/gzip/gzip.c src/gnu/usr.bin/gzip/gzip.c --- src/gnu/usr.bin/gzip/gzip.c Mon May 29 22:00:33 1995 +++ src/gnu/usr.bin/gzip/gzip.c Sun Dec 28 09:22:42 1997 @@ -1006,6 +1006,13 @@ char *dot; /* pointer to ifname extension, or NULL */ #endif + if (strlen(iname) >= sizeof(ifname) - 3) { + errno = ENAMETOOLONG; + perror(iname); + exit_code = ERROR; + return ERROR; + } + strcpy(ifname, iname); /* If input file exists, return OK. */ diff -ur src/gnu/usr.bin/gzip/inflate.c src/gnu/usr.bin/gzip/inflate.c --- src/gnu/usr.bin/gzip/inflate.c Mon May 29 22:00:37 1995 +++ src/gnu/usr.bin/gzip/inflate.c Sun Dec 28 09:22:43 1997 @@ -767,6 +767,8 @@ return i; /* incomplete code set */ } + if (tl == NULL) /* Grrrhhh */ + return 2; /* read in literal and distance code lengths */ n = nl + nd; diff -ur src/lib/libc/gen/getpass.c src/lib/libc/gen/getpass.c --- src/lib/libc/gen/getpass.c Fri Jul 12 11:53:47 1996 +++ src/lib/libc/gen/getpass.c Wed Feb 25 20:25:16 1998 @@ -44,38 +44,8 @@ #include static struct termios oterm, term; -static sig_t ointhandler, oquithandler, otstphandler, oconthandler; static FILE *fp; -static void -sighandler(int signo) -{ - /* restore tty state */ - (void)tcsetattr(fileno(fp), TCSAFLUSH|TCSASOFT, &oterm); - - /* restore old sig handlers */ - (void)signal(SIGINT, ointhandler); - (void)signal(SIGQUIT, oquithandler); - (void)signal(SIGTSTP, otstphandler); - - /* resend us this signal */ - (void)kill(getpid(), signo); -} - -/* ARGSUSED */ -static void -sigconthandler(int signo) -{ - /* re-install our signal handlers */ - ointhandler = signal(SIGINT, sighandler); - oquithandler = signal(SIGQUIT, sighandler); - otstphandler = signal(SIGTSTP, sighandler); - - /* turn off echo again */ - (void)tcsetattr(fileno(fp), TCSAFLUSH|TCSASOFT, &term); -} - - char * getpass(prompt) const char *prompt; @@ -84,6 +54,7 @@ register char *p; FILE *outfp; static char buf[_PASSWORD_LEN + 1]; + sigset_t oset, nset; /* * read and write to /dev/tty if possible; else read from @@ -94,11 +65,15 @@ fp = stdin; } - ointhandler = signal(SIGINT, sighandler); - oquithandler = signal(SIGQUIT, sighandler); - otstphandler = signal(SIGTSTP, sighandler); - oconthandler = signal(SIGCONT, sigconthandler); - + /* + * note - blocking signals isn't necessarily the + * right thing, but we leave it for now. + */ + sigemptyset(&nset); + sigaddset(&nset, SIGINT); + sigaddset(&nset, SIGTSTP); + (void)sigprocmask(SIG_BLOCK, &nset, &oset); + (void)tcgetattr(fileno(fp), &oterm); term = oterm; term.c_lflag &= ~ECHO; @@ -112,11 +87,7 @@ (void)write(fileno(outfp), "\n", 1); (void)tcsetattr(fileno(fp), TCSAFLUSH|TCSASOFT, &oterm); - /* restore old sig handlers */ - (void)signal(SIGINT, ointhandler); - (void)signal(SIGQUIT, oquithandler); - (void)signal(SIGTSTP, otstphandler); - (void)signal(SIGCONT, oconthandler); + (void)sigprocmask(SIG_SETMASK, &oset, NULL); if (fp != stdin) (void)fclose(fp); diff -ur src/sbin/ccdconfig/ccdconfig.c src/sbin/ccdconfig/ccdconfig.c --- src/sbin/ccdconfig/ccdconfig.c Tue Jun 10 23:58:39 1997 +++ src/sbin/ccdconfig/ccdconfig.c Thu Jan 1 09:19:35 1998 @@ -1,4 +1,4 @@ -/* $Id: ccdconfig.c,v 1.4.4.1 1997/06/11 06:58:39 charnier Exp $ */ +/* $Id: ccdconfig.c,v 1.4.4.2 1997/12/30 05:15:13 imp Exp $ */ /* $NetBSD: ccdconfig.c,v 1.2.2.1 1995/11/11 02:43:35 thorpej Exp $ */ @@ -161,6 +161,15 @@ if (options > 1) usage(); + /* + * Discard setgid privileges if not the running kernel so that bad + * guys can't print interesting stuff from kernel memory. + */ + if (core != NULL || kernel != NULL || action != CCD_DUMP) { + setegid(getgid()); + setgid(getgid()); + } + switch (action) { case CCD_CONFIG: case CCD_UNCONFIG: @@ -307,11 +316,16 @@ char line[_POSIX2_LINE_MAX]; char *cp, **argv; int argc, rval; + gid_t egid; + egid = getegid(); + setegid(getgid()); if ((f = fopen(ccdconf, "r")) == NULL) { + setegid(egid); warn("fopen: %s", ccdconf); return (1); } + setegid(egid); while (fgets(line, sizeof(line), f) != NULL) { argc = 0; diff -ur src/sbin/restore/tape.c src/sbin/restore/tape.c --- src/sbin/restore/tape.c Sun Mar 2 06:43:51 1997 +++ src/sbin/restore/tape.c Tue Mar 3 18:54:46 1998 @@ -231,7 +231,9 @@ fprintf(stderr, "cannot stat .: %s\n", strerror(errno)); done(1); } - if (stbuf.st_blksize > 0 && stbuf.st_blksize <= MAXBSIZE) + if (stbuf.st_blksize > 0 && stbuf.st_blksize < TP_BSIZE ) + fssize = TP_BSIZE; + if (stbuf.st_blksize >= TP_BSIZE && stbuf.st_blksize <= MAXBSIZE) fssize = stbuf.st_blksize; if (((fssize - 1) & fssize) != 0) { fprintf(stderr, "bad block size %d\n", fssize); diff -ur src/sys/i386/i386/identcpu.c src/sys/i386/i386/identcpu.c --- src/sys/i386/i386/identcpu.c Fri Oct 3 07:29:48 1997 +++ src/sys/i386/i386/identcpu.c Wed Dec 24 11:15:57 1997 @@ -91,6 +91,10 @@ { "Cyrix 486S/DX", CPUCLASS_486 }, /* CPU_CY486DX */ }; +#if defined(I586_CPU) && !defined(NO_F00F_HACK) +int has_f00f_bug = 0; +#endif + void printcpuinfo(void) { @@ -119,6 +123,14 @@ break; case 0x500: strcat(cpu_model, "Pentium"); /* nb no space */ +#if defined(I586_CPU) && !defined(NO_F00F_HACK) + /* + * XXX - If/when Intel fixes the bug, this + * should also check the version of the + * CPU, not just that it's a Pentium. + */ + has_f00f_bug = 1; +#endif break; case 0x600: strcat(cpu_model, "Pentium Pro"); diff -ur src/sys/i386/i386/machdep.c src/sys/i386/i386/machdep.c --- src/sys/i386/i386/machdep.c Thu Sep 25 08:50:53 1997 +++ src/sys/i386/i386/machdep.c Wed Dec 24 11:15:57 1997 @@ -40,6 +40,7 @@ #include "npx.h" #include "opt_sysvipc.h" +#include "opt_cpu.h" #include "opt_ddb.h" #include "opt_bounce.h" #include "opt_machdep.h" @@ -743,6 +744,11 @@ struct gate_descriptor idt[NIDT]; /* interrupt descriptor table */ union descriptor ldt[NLDT]; /* local descriptor table */ +#if defined(I586_CPU) && !defined(NO_F00F_HACK) +struct gate_descriptor *t_idt; +int has_f00f_bug; +#endif + static struct i386tss dblfault_tss; static char dblfault_stack[PAGE_SIZE]; @@ -1360,6 +1366,41 @@ proc0.p_addr->u_pcb.pcb_flags = 0; proc0.p_addr->u_pcb.pcb_cr3 = IdlePTD; } + +#if defined(I586_CPU) && !defined(NO_F00F_HACK) +void f00f_hack(void); +SYSINIT(f00f_hack, SI_SUB_INTRINSIC, SI_ORDER_FIRST, f00f_hack, NULL); + +void +f00f_hack(void) { + struct region_descriptor r_idt; + unsigned char *tmp; + int i; + unsigned *pte; + + if (!has_f00f_bug) + return; + + printf("Intel Pentium F00F detected, installing workaround\n"); + + r_idt.rd_limit = sizeof(idt) - 1; + + tmp = kmem_alloc(kernel_map, PAGE_SIZE * 2); + if (tmp == 0) + panic("kmem_alloc returned 0"); + if (((unsigned int)tmp) & PAGE_SIZE - 1) + panic("kern_alloc returned non-page-aligned memory"); + /* Put the first seven entries in the lower page */ + t_idt = (struct gate_descriptor*)(tmp + PAGE_SIZE - (7*8)); + bcopy(idt, t_idt, sizeof(idt)); + r_idt.rd_base = (int)t_idt; + lidt(&r_idt); + if (vm_map_protect(kernel_map, tmp, tmp + PAGE_SIZE, + VM_PROT_READ, FALSE) != KERN_SUCCESS) + panic("vm_map_protect failed"); + return; +} +#endif /* NO_F00F_HACK */ /* * The registers are in the frame; the frame is in the user area of diff -ur src/sys/i386/i386/mem.c src/sys/i386/i386/mem.c --- src/sys/i386/i386/mem.c Fri Sep 27 06:25:06 1996 +++ src/sys/i386/i386/mem.c Wed Dec 24 11:15:30 1997 @@ -169,6 +169,7 @@ int fmt; struct proc *p; { + int error; struct trapframe *fp; switch (minor(dev)) { @@ -179,6 +180,11 @@ return ENODEV; #endif case 14: + error = suser(p->p_ucred, &p->p_acflag); + if (error != 0) + return (error); + if (securelevel > 0) + return (EPERM); fp = (struct trapframe *)curproc->p_md.md_regs; fp->tf_eflags |= PSL_IOPL; break; diff -ur src/sys/i386/i386/trap.c src/sys/i386/i386/trap.c --- src/sys/i386/i386/trap.c Wed Feb 12 23:51:53 1997 +++ src/sys/i386/i386/trap.c Wed Dec 24 11:15:57 1997 @@ -42,6 +42,7 @@ * 386 Trap and System call handling */ +#include "opt_cpu.h" #include "opt_ktrace.h" #include "opt_ddb.h" @@ -133,6 +134,11 @@ static void userret __P((struct proc *p, struct trapframe *frame, u_quad_t oticks)); +#if defined(I586_CPU) && !defined(NO_F00F_HACK) +extern struct gate_descriptor *t_idt; +extern int has_f00f_bug; +#endif + static inline void userret(p, frame, oticks) struct proc *p; @@ -189,6 +195,9 @@ u_long eva; #endif +#if defined(I586_CPU) && !defined(NO_F00F_HACK) +restart: +#endif type = frame.tf_trapno; code = frame.tf_err; @@ -239,6 +248,10 @@ i = trap_pfault(&frame, TRUE); if (i == -1) return; +#if defined(I586_CPU) && !defined(NO_F00F_HACK) + if (i == -2) + goto restart; +#endif if (i == 0) goto out; @@ -585,7 +598,18 @@ if (va >= KERNBASE) { /* * Don't allow user-mode faults in kernel address space. + * An exception: if the faulting address is the invalid + * instruction entry in the IDT, then the Intel Pentium + * F00F bug workaround was triggered, and we need to + * treat it is as an illegal instruction, and not a page + * fault. */ +#if defined(I586_CPU) && !defined(NO_F00F_HACK) + if ((eva == (unsigned int)&t_idt[6]) && has_f00f_bug) { + frame->tf_trapno = T_PRIVINFLT; + return -2; + } +#endif if (usermode) goto nogo; diff -ur src/sys/kern/vfs_bio.c src/sys/kern/vfs_bio.c --- src/sys/kern/vfs_bio.c Mon Sep 1 16:23:08 1997 +++ src/sys/kern/vfs_bio.c Fri Mar 13 18:02:08 1998 @@ -18,7 +18,7 @@ * 5. Modifications may be freely made to this file if the above conditions * are met. * - * $Id: vfs_bio.c,v 1.104.2.7 1997/09/01 23:23:08 tegge Exp $ + * $Id: vfs_bio.c,v 1.104.2.8 1998/03/05 12:20:08 dg Exp $ */ /* @@ -597,10 +597,6 @@ LIST_REMOVE(bp, b_hash); LIST_INSERT_HEAD(&invalhash, bp, b_hash); bp->b_dev = NODEV; - /* - * Get rid of the kva allocation *now* - */ - bfreekva(bp); if (needsbuffer) { wakeup(&needsbuffer); needsbuffer=0; @@ -853,7 +849,7 @@ static struct buf * getnewbuf(int slpflag, int slptimeo, int size, int maxsize) { - struct buf *bp; + struct buf *bp, *bp1; int nbyteswritten = 0; vm_offset_t addr; @@ -981,11 +977,23 @@ if (maxsize != bp->b_kvasize) { bfreekva(bp); +findkvaspace: /* * See if we have buffer kva space */ if (vm_map_findspace(buffer_map, vm_map_min(buffer_map), maxsize, &addr)) { + int tfree = 0; + for (bp1 = TAILQ_FIRST(&bufqueues[QUEUE_EMPTY]); + bp1 != NULL; bp1 = TAILQ_NEXT(bp1, b_freelist)) + if (bp1->b_kvasize != 0) { + tfree += bp1->b_kvasize; + bremfree(bp1); + bfreekva(bp1); + brelse(bp1); + if (tfree >= maxsize) + goto findkvaspace; + } bp->b_flags |= B_INVAL; brelse(bp); goto trytofreespace; @@ -1842,7 +1850,7 @@ vm_ooffset_t sv, ev; off = off - pageno * PAGE_SIZE; sv = off + ((bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); - ev = off + (bp->b_validend & ~(DEV_BSIZE - 1)); + ev = off + ((bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); soff = max(sv, soff); eoff = min(ev, eoff); } diff -ur src/sys/kern/vfs_syscalls.c src/sys/kern/vfs_syscalls.c --- src/sys/kern/vfs_syscalls.c Tue Sep 30 23:23:48 1997 +++ src/sys/kern/vfs_syscalls.c Wed Dec 24 11:15:12 1997 @@ -688,11 +688,13 @@ struct flock lf; struct nameidata nd; + flags = FFLAGS(uap->flags); + if ((flags & FREAD + FWRITE) == 0) + return (EINVAL); error = falloc(p, &nfp, &indx); if (error) return (error); fp = nfp; - flags = FFLAGS(uap->flags); cmode = ((uap->mode &~ fdp->fd_cmask) & ALLPERMS) &~ S_ISTXT; NDINIT(&nd, LOOKUP, FOLLOW, UIO_USERSPACE, uap->path, p); p->p_dupfd = -indx - 1; /* XXX check for fdopen */ diff -ur src/sys/miscfs/fdesc/fdesc_vnops.c src/sys/miscfs/fdesc/fdesc_v nops.c --- src/sys/miscfs/fdesc/fdesc_vnops.c Sat Dec 21 11:04:28 1996 +++ src/sys/miscfs/fdesc/fdesc_vnops.c Fri Jan 2 09:43:09 1998 @@ -409,11 +409,18 @@ } break; + case DTYPE_PIPE: case DTYPE_SOCKET: - error = soo_stat((struct socket *)fp->f_data, &stb); + if (fp->f_type == DTYPE_SOCKET) + error = soo_stat((struct socket *)fp->f_data, &stb); + else + error = pipe_stat((struct pipe *)fp->f_data, &stb); if (error == 0) { vattr_null(vap); - vap->va_type = VSOCK; + if (fp->f_type == DTYPE_SOCKET) + vap->va_type = VSOCK; + else + vap->va_type = VFIFO; vap->va_mode = stb.st_mode; vap->va_nlink = stb.st_nlink; vap->va_uid = stb.st_uid; @@ -557,6 +564,7 @@ error = VOP_SETATTR((struct vnode *) fp->f_data, ap->a_vap, ap-> a_cred, ap->a_p); break; + case DTYPE_PIPE: case DTYPE_SOCKET: error = 0; break; diff -ur src/sys/net/if_ethersubr.c src/sys/net/if_ethersubr.c --- src/sys/net/if_ethersubr.c Tue Sep 30 05:29:00 1997 +++ src/sys/net/if_ethersubr.c Wed Dec 24 11:52:22 1997 @@ -194,21 +194,46 @@ #endif #ifdef NETATALK case AF_APPLETALK: - if (!aarpresolve(ac, m, (struct sockaddr_at *)dst, edst)) { + { + struct sockaddr_at *sat = (struct sockaddr_at *)dst; + + /* + * super hack.. + * Most of this loopback code should move into the appletalk + * code, but it's here for now.. remember to move it! [JRE] + * This may not get the same interface we started with + * fix asap. XXX + */ + aa = at_ifawithnet( sat ); + if (aa == NULL) { + goto bad; + } + if( aa->aa_ifa.ifa_ifp != ifp ) { + (*aa->aa_ifa.ifa_ifp->if_output)(aa->aa_ifa.ifa_ifp, + m,dst,rt); + } + if (((sat->sat_addr.s_net == ATADDR_ANYNET) + && (sat->sat_addr.s_node == ATADDR_ANYNODE)) + || ((sat->sat_addr.s_net == aa->aa_addr.sat_addr.s_net ) + && (sat->sat_addr.s_node == aa->aa_addr.sat_addr.s_node))) { + (void) looutput(ifp, m, dst, rt); + return(0); + } + + if (!aarpresolve(ac, m, (struct sockaddr_at *)dst, edst)) { #ifdef NETATALKDEBUG - extern char *prsockaddr(struct sockaddr *); - printf("aarpresolv: failed for %s\n", prsockaddr(dst)); + extern char *prsockaddr(struct sockaddr *); + printf("aarpresolv: failed for %s\n", prsockaddr(dst)); #endif NETATALKDEBUG - return (0); - } - /* - * ifaddr is the first thing in at_ifaddr - */ - if ((aa = (struct at_ifaddr *)at_ifawithnet( - (struct sockaddr_at *)dst, ifp->if_addrlist)) - == 0) - goto bad; - + return (0); + } + + /* + * If broadcasting on a simplex interface, loopback a copy + */ + if ((m->m_flags & M_BCAST) && (ifp->if_flags & IFF_SIMPLEX)) + mcopy = m_copy(m, 0, (int)M_COPYALL); + } /* * In the phase 2 case, we need to prepend an mbuf for the llc header. * Since we must preserve the value of m, which is passed to us by diff -ur src/sys/netatalk/aarp.c src/sys/netatalk/aarp.c --- src/sys/netatalk/aarp.c Thu Aug 29 16:16:29 1996 +++ src/sys/netatalk/aarp.c Wed Dec 24 11:52:22 1997 @@ -94,30 +94,24 @@ * the given network.. remember to take netranges into * consideration. */ -struct ifaddr * -at_ifawithnet( sat, ifa ) - struct sockaddr_at *sat; - struct ifaddr *ifa; +struct at_ifaddr * +at_ifawithnet(struct sockaddr_at *sat ) { + struct at_ifaddr *aa; struct sockaddr_at *sat2; - struct netrange *nr; - for (; ifa; ifa = ifa->ifa_next ) { - if ( ifa->ifa_addr->sa_family != AF_APPLETALK ) { - continue; - } - sat2 = satosat( ifa->ifa_addr ); - if ( sat2->sat_addr.s_net == sat->sat_addr.s_net ) { - break; + for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { + sat2 = &(aa->aa_addr); + if ( sat2->sat_addr.s_net == sat->sat_addr.s_net ) { + break; + } + if( (aa->aa_flags & AFA_PHASE2 ) + && (ntohs(aa->aa_firstnet) <= ntohs(sat->sat_addr.s_net)) + && (ntohs(aa->aa_lastnet) >= ntohs(sat->sat_addr.s_net))) { + break; + } } - nr = (struct netrange *)(sat2->sat_zero); - if( (nr->nr_phase == 2 ) - && (nr->nr_firstnet <= sat->sat_addr.s_net) - && (nr->nr_lastnet >= sat->sat_addr.s_net)) { - break; - } - } - return( ifa ); + return( aa ); } static void @@ -155,8 +149,7 @@ * interface with the same address as we're looking for. If the * net is phase 2, generate an 802.2 and SNAP header. */ - if (( aa = (struct at_ifaddr *)at_ifawithnet( sat, ac-> ac_if.if_addrlist )) - == NULL ) { + if (( aa = at_ifawithnet( sat )) == NULL ) { m_freem( m ); return; } @@ -213,8 +206,8 @@ int s; if ( at_broadcast( destsat )) { - if (( aa = (struct at_ifaddr *)at_ifawithnet( destsat, - ((struct ifnet *)ac)->if_addrlist )) == NULL ) { + m->m_flags |= M_BCAST; + if (( aa = at_ifawithnet( destsat )) == NULL ) { m_freem( m ); return( 0 ); } @@ -325,8 +318,7 @@ sat.sat_len = sizeof(struct sockaddr_at); sat.sat_family = AF_APPLETALK; sat.sat_addr.s_net = net; - if (( aa = (struct at_ifaddr *)at_ifawithnet( &sat, - ac->ac_if.if_addrlist )) == NULL ) { + if (( aa = at_ifawithnet( &sat )) == NULL ) { m_freem( m ); return; } diff -ur src/sys/netatalk/at_control.c src/sys/netatalk/at_control.c --- src/sys/netatalk/at_control.c Sun Oct 5 14:41:06 1997 +++ src/sys/netatalk/at_control.c Wed Dec 24 11:52:22 1997 @@ -882,10 +882,10 @@ */ if ((addr->sat_addr.s_net == gw->sat_addr.s_net) || ((addr->sat_range.r_netrange.nr_lastnet) - && (gw->sat_addr.s_net - >= addr->sat_range.r_netrange.nr_firstnet ) - && (gw->sat_addr.s_net - <= addr->sat_range.r_netrange.nr_lastnet ))) { + && (ntohs(gw->sat_addr.s_net) + >= ntohs(addr->sat_range.r_netrange.nr_firstnet )) + && (ntohs(gw->sat_addr.s_net) + <= ntohs(addr->sat_range.r_netrange.nr_lastnet )))) { return 1; } break; diff -ur src/sys/netatalk/at_extern.h src/sys/netatalk/at_extern.h --- src/sys/netatalk/at_extern.h Thu May 23 18:35:23 1996 +++ src/sys/netatalk/at_extern.h Wed Dec 24 11:52:22 1997 @@ -24,8 +24,7 @@ struct mbuf *addr, struct mbuf *rights)); extern void ddp_init __P((void )); -extern struct ifaddr *at_ifawithnet __P((struct sockaddr_at *, - struct ifaddr *)); +extern struct at_ifaddr *at_ifawithnet __P((struct sockaddr_at *)); #ifdef _NETATALK_DDP_VAR_H_ extern int ddp_output __P(( struct ddpcb *ddp, struct mbuf *m)); #endif diff -ur src/sys/netatalk/ddp_input.c src/sys/netatalk/ddp_input.c --- src/sys/netatalk/ddp_input.c Tue Sep 10 01:23:11 1996 +++ src/sys/netatalk/ddp_input.c Wed Dec 24 11:52:22 1997 @@ -41,6 +41,9 @@ struct at_ifaddr *aa; int s; + /* + * First pull off all the phase 2 packets. + */ for (;;) { s = splimp(); @@ -53,19 +56,12 @@ } ifp = m->m_pkthdr.rcvif; - for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { - if ( aa->aa_ifp == ifp && ( aa->aa_flags & AFA_PHASE2 )) { - break; - } - } - if ( aa == NULL ) { /* ifp not an appletalk interface */ - m_freem( m ); - continue; - } - ddp_input( m, ifp, (struct elaphdr *)NULL, 2 ); } + /* + * Then pull off all the phase 1 packets. + */ for (;;) { s = splimp(); @@ -78,15 +74,6 @@ } ifp = m->m_pkthdr.rcvif; - for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { - if ( aa->aa_ifp == ifp && ( aa->aa_flags & AFA_PHASE2 ) == 0 ) { - break; - } - } - if ( aa == NULL ) { /* ifp not an appletalk interface */ - m_freem( m ); - continue; - } if ( m->m_len < SZ_ELAPHDR && (( m = m_pullup( m, SZ_ELAPHDR )) == 0 )) { @@ -94,6 +81,9 @@ continue; } + /* + * this seems a little dubios, but I don't know phase 1 so leave it. + */ elhp = mtod( m, struct elaphdr *); m_adj( m, SZ_ELAPHDR ); @@ -127,7 +117,14 @@ u_short cksum = 0; bzero( (caddr_t)&from, sizeof( struct sockaddr_at )); + bzero( (caddr_t)&to, sizeof( struct sockaddr_at )); if ( elh ) { + /* + * Extract the information in the short header. + * netowrk information is defaulted to ATADDR_ANYNET + * and node information comes from the elh info. + * We must be phase 1. + */ ddpstat.ddps_short++; if ( m->m_len < sizeof( struct ddpshdr ) && @@ -148,18 +145,32 @@ from.sat_addr.s_node = elh->el_snode; from.sat_port = ddps.dsh_sport; + /* + * Make sure that we point to the phase1 ifaddr info + * and that it's valid for this packet. + */ for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { - if ( aa->aa_ifp == ifp && ( aa->aa_flags & AFA_PHASE2 ) == 0 && - ( AA_SAT( aa )->sat_addr.s_node == to.sat_addr.s_node || - to.sat_addr.s_node == ATADDR_BCAST )) { + if ( (aa->aa_ifp == ifp) + && ( (aa->aa_flags & AFA_PHASE2) == 0) + && ( (to.sat_addr.s_node == AA_SAT( aa )->sat_addr.s_node) + || (to.sat_addr.s_node == ATADDR_BCAST))) { break; } } + /* + * maybe we got a broadcast not meant for us.. ditch it. + */ if ( aa == NULL ) { m_freem( m ); return; } } else { + /* + * There was no 'elh' passed on. This could still be + * either phase1 or phase2. + * We have a long header, but we may be running on a pahse 1 net. + * Extract out all the info regarding this packet's src & dst. + */ ddpstat.ddps_long++; if ( m->m_len < sizeof( struct ddpehdr ) && @@ -185,6 +196,18 @@ to.sat_port = ddpe.deh_dport; if ( to.sat_addr.s_net == ATADDR_ANYNET ) { + /* + * The TO address doesn't specify a net, + * So by definition it's for this net. + * Try find ifaddr info with the right phase, + * the right interface, and either to our node, a bradcast, + * or looped back (though that SHOULD be covered in the other + * cases). + * + * XXX If we have multiple interfaces, then the first with + * this node number will match (which may NOT be what we want, + * but it's probably safe in 99.999% of cases. + */ for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { if ( phase == 1 && ( aa->aa_flags & AFA_PHASE2 )) { continue; @@ -192,27 +215,47 @@ if ( phase == 2 && ( aa->aa_flags & AFA_PHASE2 ) == 0 ) { continue; } - if ( aa->aa_ifp == ifp && - ( AA_SAT( aa )->sat_addr.s_node == to.sat_addr.s_node || - to.sat_addr.s_node == ATADDR_BCAST || - ( ifp->if_flags & IFF_LOOPBACK ))) { + if ( (aa->aa_ifp == ifp) + && ( (to.sat_addr.s_node == AA_SAT( aa )->sat_addr.s_node) + || (to.sat_addr.s_node == ATADDR_BCAST) + || (ifp->if_flags & IFF_LOOPBACK))) { break; } } } else { + /* + * A destination network was given. We just try to find + * which ifaddr info matches it. + */ for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { + /* + * This is a kludge. Accept packets that are + * for any router on a local netrange. + */ if ( to.sat_addr.s_net == aa->aa_firstnet && to.sat_addr.s_node == 0 ) { break; } - if (( ntohs( to.sat_addr.s_net ) < ntohs( aa->aa_firstnet ) || - ntohs( to.sat_addr.s_net ) > ntohs( aa->aa_lastnet )) && - ( ntohs( to.sat_addr.s_net ) < ntohs( 0xff00 ) || - ntohs( to.sat_addr.s_net ) > ntohs( 0xfffe ))) { + /* + * Don't use ifaddr info for which we are totally outside the + * netrange, and it's not a startup packet. + * Startup packets are always implicitly allowed on to + * the next test. + */ + if ((( ntohs( to.sat_addr.s_net ) < ntohs( aa->aa_firstnet )) + || (ntohs( to.sat_addr.s_net ) > ntohs( aa->aa_lastnet ))) + && (( ntohs( to.sat_addr.s_net ) < ntohs( 0xff00 )) + || (ntohs( to.sat_addr.s_net ) > ntohs( 0xfffe )))) { continue; } - if ( to.sat_addr.s_node != AA_SAT( aa )->sat_addr.s_node && - to.sat_addr.s_node != ATADDR_BCAST ) { + + /* + * Don't record a match either if we just don't have a match + * in the node address. This can have if the interface + * is in promiscuous mode for example. + */ + if (( to.sat_addr.s_node != AA_SAT( aa )->sat_addr.s_node) + && (to.sat_addr.s_node != ATADDR_BCAST) ) { continue; } break; @@ -236,43 +279,75 @@ } /* - * XXX Should we deliver broadcasts locally, also, or rely on the - * link layer to give us a copy? For the moment, the latter. + * If it aint for a net on any of our interfaces, + * or it IS for a net on a different interface than it came in on, + * (and it is not looped back) then consider if we shoulf forward it. + * As we a re not really a router this is a bit cheaky, but it may be + * useful some day. */ - if ( aa == NULL || ( to.sat_addr.s_node == ATADDR_BCAST && - aa->aa_ifp != ifp && ( ifp->if_flags & IFF_LOOPBACK ) == 0 )) { + if ( (aa == NULL) + || ( (to.sat_addr.s_node == ATADDR_BCAST) + && (aa->aa_ifp != ifp) + && (( ifp->if_flags & IFF_LOOPBACK ) == 0 ))) { + /* + * If we've explicitly disabled it, don't route anything + */ if ( ddp_forward == 0 ) { m_freem( m ); return; } - if ( forwro.ro_rt && ( satosat( &forwro.ro_dst )->sat_addr.s_net != - to.sat_addr.s_net || - satosat( &forwro.ro_dst )->sat_addr.s_node != - to.sat_addr.s_node )) { + /* + * If the cached forwarding route is still valid, use it. + */ + if ( forwro.ro_rt + && ( satosat(&forwro.ro_dst)->sat_addr.s_net != to.sat_addr.s_net + || satosat(&forwro.ro_dst)->sat_addr.s_node != to.sat_addr.s_node )) { RTFREE( forwro.ro_rt ); forwro.ro_rt = (struct rtentry *)0; } - if ( forwro.ro_rt == (struct rtentry *)0 || - forwro.ro_rt->rt_ifp == (struct ifnet *)0 ) { + + /* + * If we don't have a cached one (any more) or it's useless, + * Then get a new route. + * XXX this could cause a 'route leak'. check this! + */ + if ( forwro.ro_rt == (struct rtentry *)0 + || forwro.ro_rt->rt_ifp == (struct ifnet *)0 ) { forwro.ro_dst.sa_len = sizeof( struct sockaddr_at ); forwro.ro_dst.sa_family = AF_APPLETALK; - satosat( &forwro.ro_dst )->sat_addr.s_net = to.sat_addr.s_net; - satosat( &forwro.ro_dst )->sat_addr.s_node = to.sat_addr.s_node; - rtalloc( &forwro ); + satosat(&forwro.ro_dst)->sat_addr.s_net = to.sat_addr.s_net; + satosat(&forwro.ro_dst)->sat_addr.s_node = to.sat_addr.s_node; + rtalloc(&forwro); } - if ( to.sat_addr.s_net != satosat( &forwro.ro_dst )->sat_addr.s_net && - ddpe.deh_hops == DDP_MAXHOPS ) { + /* + * If it's not going to get there on this hop, and it's + * already done too many hops, then throw it away. + */ + if ( (to.sat_addr.s_net != satosat( &forwro.ro_dst )->sat_addr.s_net) + && (ddpe.deh_hops == DDP_MAXHOPS) ) { m_freem( m ); return; } - if ( ddp_firewall && - ( forwro.ro_rt == NULL || forwro.ro_rt->rt_ifp != ifp )) { + /* + * A ddp router might use the same interface + * to forward the packet, which this would not effect. + * Don't allow packets to cross from one interface to another however. + */ + if ( ddp_firewall + && ( (forwro.ro_rt == NULL) + || (forwro.ro_rt->rt_ifp != ifp))) { m_freem( m ); return; } + /* + * Adjust the header. + * If it was a short header then it would have not gotten here, + * so we can assume there is room to drop the header in. + * XXX what about promiscuous mode, etc... + */ ddpe.deh_hops++; ddpe.deh_bytes = htonl( ddpe.deh_bytes ); bcopy( (caddr_t)&ddpe, (caddr_t)deh, sizeof( u_short )); /* XXX deh? */ @@ -284,9 +359,16 @@ return; } + /* + * It was for us, and we have an ifaddr to use with it. + */ from.sat_len = sizeof( struct sockaddr_at ); from.sat_family = AF_APPLETALK; + /* + * We are no longer interested in the link layer. + * so cut it off. + */ if ( elh ) { m_adj( m, sizeof( struct ddpshdr )); } else { @@ -298,21 +380,36 @@ m_adj( m, sizeof( struct ddpehdr )); } + /* + * Search for ddp protocol control blocks that match these + * addresses. + */ if (( ddp = ddp_search( &from, &to, aa )) == NULL ) { m_freem( m ); return; } + /* + * If we found one, deliver th epacket to the socket + */ if ( sbappendaddr( &ddp->ddp_socket->so_rcv, (struct sockaddr *)&from, m, (struct mbuf *)0 ) == 0 ) { + /* + * If the socket is full (or similar error) dump the packet. + */ ddpstat.ddps_nosockspace++; m_freem( m ); return; } + /* + * And wake up whatever might be waiting for it + */ sorwakeup( ddp->ddp_socket ); } #if 0 +/* As if we haven't got enough of this sort of think floating +around the kernel :) */ #define BPXLEN 48 #define BPALEN 16 diff -ur src/sys/netatalk/ddp_output.c src/sys/netatalk/ddp_output.c --- src/sys/netatalk/ddp_output.c Sun Oct 5 14:41:06 1997 +++ src/sys/netatalk/ddp_output.c Wed Dec 24 11:52:23 1997 @@ -128,11 +128,11 @@ if ( (ro->ro_rt != NULL) && ( ro->ro_rt->rt_ifa ) && ( ifp = ro->ro_rt->rt_ifa->ifa_ifp )) { - net = satosat(ro->ro_rt->rt_gateway)->sat_addr.s_net; + net = ntohs(satosat(ro->ro_rt->rt_gateway)->sat_addr.s_net); for ( aa = at_ifaddr; aa; aa = aa->aa_next ) { if (((net == 0) || (aa->aa_ifp == ifp)) && - ntohs( net ) >= ntohs( aa->aa_firstnet ) && - ntohs( net ) <= ntohs( aa->aa_lastnet )) { + net >= ntohs( aa->aa_firstnet ) && + net <= ntohs( aa->aa_lastnet )) { break; } } diff -ur src/sys/netinet/in.h src/sys/netinet/in.h --- src/sys/netinet/in.h Mon Nov 11 15:40:37 1996 +++ src/sys/netinet/in.h Thu Feb 26 17:20:46 1998 @@ -301,7 +301,8 @@ #define IPCTL_DIRECTEDBROADCAST 9 /* may re-broadcast received packets */ #define IPCTL_INTRQMAXLEN 10 /* max length of netisr queue */ #define IPCTL_INTRQDROPS 11 /* number of netisr q drops */ -#define IPCTL_MAXID 12 +#define IPCTL_ACCEPTSOURCEROUTE 13 /* may accept source routed packets */ +#define IPCTL_MAXID 13 #define IPCTL_NAMES { \ { 0, 0 }, \ @@ -316,6 +317,7 @@ { "directed-broadcast", CTLTYPE_INT }, \ { "intr-queue-maxlen", CTLTYPE_INT }, \ { "intr-queue-drops", CTLTYPE_INT }, \ + { "accept_sourceroute", CTLTYPE_INT }, \ } diff -ur src/sys/netinet/ip_fw.c src/sys/netinet/ip_fw.c --- src/sys/netinet/ip_fw.c Sat Aug 23 07:31:52 1997 +++ src/sys/netinet/ip_fw.c Wed Dec 24 11:51:59 1997 @@ -576,23 +576,24 @@ { struct tcphdr *const tcp = (struct tcphdr *) ((u_long *)ip + ip->ip_hl); - struct tcpiphdr ti; + struct tcpiphdr ti, *const tip = (struct tcpiphdr *) ip; if (offset != 0 || (tcp->th_flags & TH_RST)) break; ti.ti_i = *((struct ipovly *) ip); ti.ti_t = *tcp; - NTOHL(ti.ti_seq); - NTOHL(ti.ti_ack); - ti.ti_len = ip->ip_len - hlen - (ti.ti_off << 2); + bcopy(&ti, ip, sizeof(ti)); + NTOHL(tip->ti_seq); + NTOHL(tip->ti_ack); + tip->ti_len = ip->ip_len - hlen - (tip->ti_off << 2); if (tcp->th_flags & TH_ACK) { - tcp_respond(NULL, &ti, *m, + tcp_respond(NULL, tip, *m, (tcp_seq)0, ntohl(tcp->th_ack), TH_RST); } else { if (tcp->th_flags & TH_SYN) - ti.ti_len++; - tcp_respond(NULL, &ti, *m, ti.ti_seq - + ti.ti_len, (tcp_seq)0, TH_RST|TH_ACK); + tip->ti_len++; + tcp_respond(NULL, tip, *m, tip->ti_seq + + tip->ti_len, (tcp_seq)0, TH_RST|TH_ACK); } *m = NULL; break; diff -ur src/sys/netinet/ip_input.c src/sys/netinet/ip_input.c --- src/sys/netinet/ip_input.c Mon Sep 15 16:10:55 1997 +++ src/sys/netinet/ip_input.c Thu Feb 26 17:20:46 1998 @@ -94,6 +94,10 @@ static int ip_dosourceroute = 0; SYSCTL_INT(_net_inet_ip, IPCTL_SOURCEROUTE, sourceroute, CTLFLAG_RW, &ip_dosourceroute, 0, ""); + +static int ip_acceptsourceroute = 0; +SYSCTL_INT(_net_inet_ip, IPCTL_ACCEPTSOURCEROUTE, accept_sourceroute, + CTLFLAG_RW, &ip_acceptsourceroute, 0, ""); #ifdef DIAGNOSTIC static int ipprintfs = 0; #endif @@ -923,6 +927,8 @@ code = ICMP_UNREACH_SRCFAIL; goto bad; } + if (!ip_dosourceroute) + goto nosourcerouting; /* * Loose routing, and not at next destination * yet; nothing to do except forward. @@ -934,14 +940,17 @@ /* * End of source route. Should be for us. */ + if (!ip_acceptsourceroute) + goto nosourcerouting; save_rte(cp, ip->ip_src); break; } if (!ip_dosourceroute) { char buf[4*sizeof "123"]; - strcpy(buf, inet_ntoa(ip->ip_dst)); +nosourcerouting: + strcpy(buf, inet_ntoa(ip->ip_dst)); log(LOG_WARNING, "attempted source route from %s to %s\n", inet_ntoa(ip->ip_src), buf); @@ -1056,7 +1065,7 @@ ipt->ipt_ptr += sizeof(n_time); } } - if (forward) { + if (forward && ipforwarding) { ip_forward(m, 1); return (1); } diff -ur src/sys/netinet/tcp_input.c src/sys/netinet/tcp_input.c --- src/sys/netinet/tcp_input.c Sat Oct 4 01:54:12 1997 +++ src/sys/netinet/tcp_input.c Thu Mar 12 19:39:56 1998 @@ -614,6 +614,7 @@ * If the state is LISTEN then ignore segment if it contains an RST. * If the segment contains an ACK then it is bad and send a RST. * If it does not contain a SYN then it is not interesting; drop it. + * If it is from this socket, drop it, it must be forged. * Don't bother responding if the destination was a broadcast. * Otherwise initialize tp->rcv_nxt, and tp->irs, select an initial * tp->iss, and send a segment: @@ -633,6 +634,9 @@ goto dropwithreset; if ((tiflags & TH_SYN) == 0) goto drop; + if ((ti->ti_dport == ti->ti_sport) && + (ti->ti_dst.s_addr == ti->ti_src.s_addr)) + goto drop; /* * RFC1122 4.2.3.10, p. 104: discard bcast/mcast SYN * in_broadcast() should never return true on a received @@ -752,6 +756,23 @@ } /* + * If the state is SYN_RECEIVED: + * if seg contains SYN/ACK, send a RST. + * if seg contains an ACK, but not for our SYN/ACK, send a RST. + */ + case TCPS_SYN_RECEIVED: + if (tiflags & TH_ACK) { + if (tiflags & TH_SYN) { + tcpstat.tcps_badsyn++; + goto dropwithreset; + } + if (SEQ_LEQ(ti->ti_ack, tp->snd_una) || + SEQ_GT(ti->ti_ack, tp->snd_max)) + goto dropwithreset; + } + break; + + /* * If the state is SYN_SENT: * if seg contains an ACK, but not for our SYN, drop the input. * if seg contains a RST, then drop the connection. @@ -1166,14 +1187,11 @@ switch (tp->t_state) { /* - * In SYN_RECEIVED state if the ack ACKs our SYN then enter - * ESTABLISHED state and continue processing, otherwise - * send an RST. + * In SYN_RECEIVED state, the ack ACKs our SYN, so enter + * ESTABLISHED state and continue processing. + * The ACK was checked above. */ case TCPS_SYN_RECEIVED: - if (SEQ_GT(tp->snd_una, ti->ti_ack) || - SEQ_GT(ti->ti_ack, tp->snd_max)) - goto dropwithreset; tcpstat.tcps_connects++; soisconnected(so); diff -ur src/sys/netinet/tcp_subr.c src/sys/netinet/tcp_subr.c --- src/sys/netinet/tcp_subr.c Tue Sep 30 09:25:11 1997 +++ src/sys/netinet/tcp_subr.c Wed Dec 24 11:51:59 1997 @@ -168,6 +168,8 @@ * * In any case the ack and sequence number of the transmitted * segment are as specified by the parameters. + * + * NOTE: If m != NULL, then ti must point to *inside* the mbuf. */ void tcp_respond(tp, ti, m, ack, seq, flags) diff -ur src/sys/vm/vm_map.c src/sys/vm/vm_map.c --- src/sys/vm/vm_map.c Mon Mar 24 20:54:26 1997 +++ src/sys/vm/vm_map.c Sat Dec 27 23:39:36 1997 @@ -61,7 +61,7 @@ * any improvements or extensions that they make and grant Carnegie the * rights to redistribute these changes. * - * $Id: vm_map.c,v 1.57.2.4 1997/03/25 04:54:26 dyson Exp $ + * $Id: vm_map.c,v 1.57.2.5 1997/11/04 09:02:38 dyson Exp $ */ /* @@ -283,9 +283,9 @@ if (kmem_map == NULL) { result = kmap_free; - kmap_free = (vm_map_t) result->header.next; if (result == NULL) panic("vm_map_create: out of maps"); + kmap_free = (vm_map_t) result->header.next; } else MALLOC(result, vm_map_t, sizeof(struct vm_map), M_VMMAP, M_WAITOK); @@ -935,6 +935,23 @@ vm_map_simplify_entry(map, entry); + /* + * If there is no object backing this entry, we might as well create + * one now. If we defer it, an object can get created after the map + * is clipped, and individual objects will be created for the split-up + * map. This is a bit of a hack, but is also about the best place to + * put this improvement. + */ + + if (entry->object.vm_object == NULL) { + vm_object_t object; + + object = vm_object_allocate(OBJT_DEFAULT, + OFF_TO_IDX(entry->end - entry->start)); + entry->object.vm_object = object; + entry->offset = 0; + } + new_entry = vm_map_entry_create(map); *new_entry = *entry; @@ -977,6 +994,23 @@ register vm_map_entry_t new_entry; /* + * If there is no object backing this entry, we might as well create + * one now. If we defer it, an object can get created after the map + * is clipped, and individual objects will be created for the split-up + * map. This is a bit of a hack, but is also about the best place to + * put this improvement. + */ + + if (entry->object.vm_object == NULL) { + vm_object_t object; + + object = vm_object_allocate(OBJT_DEFAULT, + OFF_TO_IDX(entry->end - entry->start)); + entry->object.vm_object = object; + entry->offset = 0; + } + + /* * Create a new entry and insert it AFTER the specified entry */ @@ -1174,10 +1208,12 @@ #undef max #undef MASK } + + vm_map_simplify_entry(map, current); + current = current->next; } - vm_map_simplify_entry(map, entry); vm_map_unlock(map); return (KERN_SUCCESS); } @@ -1455,8 +1491,7 @@ } lock_clear_recursive(&map->lock); - vm_map_unlock(map); - vm_map_lock(map); + lock_read_to_write(&map->lock); goto rescan; } diff -ur src/sys/vm/vm_mmap.c src/sys/vm/vm_mmap.c --- src/sys/vm/vm_mmap.c Mon Mar 24 20:54:29 1997 +++ src/sys/vm/vm_mmap.c Thu Mar 12 19:33:04 1998 @@ -157,6 +157,9 @@ vm_prot_t prot, maxprot; caddr_t handle; int flags, error; + int disablexworkaround; + + addr = (vm_offset_t) uap->addr; prot = uap->prot & VM_PROT_ALL; flags = uap->flags; @@ -230,6 +233,26 @@ flags |= MAP_ANON; } else { /* + * cdevs does not provide private mappings of any kind. + */ + /* + * However, for XIG X server to continue to work, + * we should allow the superuser to do it anyway. + * We only allow it at securelevel < 1. + * (Because the XIG X server writes directly to video + * memory via /dev/mem, it should never work at any + * other securelevel. + * XXX this will have to go + */ + if (securelevel >= 1) + disablexworkaround = 1; + else + disablexworkaround = suser(p->p_ucred, + &p->p_acflag); + if (vp->v_type == VCHR && disablexworkaround && + (flags & (MAP_PRIVATE|MAP_COPY))) + return (EINVAL); + /* * Ensure that file and memory protections are * compatible. Note that we only worry about * writability if mapping is shared; in this case, @@ -243,12 +266,20 @@ maxprot |= VM_PROT_READ; else if (prot & PROT_READ) return (EACCES); - if (flags & MAP_SHARED) { - if (fp->f_flag & FWRITE) - maxprot |= VM_PROT_WRITE; - else if (prot & PROT_WRITE) - return (EACCES); - } else + /* + * If we are sharing potential changes (either via + * MAP_SHARED or via the implicit sharing of character + * device mappings), and we are trying to get write + * permission although we opened it without asking + * for it, bail out. Check for superuser, only if + * we're at securelevel < 1, to allow the XIG X server + * to continue to work. + */ + if (((flags & MAP_SHARED) != 0 || + (vp->v_type == VCHR && disablexworkaround)) && + (fp->f_flag & FWRITE) == 0 && (prot & PROT_WRITE) != 0) + return (EACCES); + else maxprot |= VM_PROT_WRITE; handle = (caddr_t) vp; } diff -ur src/sys/vm/vm_page.c src/sys/vm/vm_page.c --- src/sys/vm/vm_page.c Mon Mar 24 20:54:35 1997 +++ src/sys/vm/vm_page.c Sat Dec 27 22:56:18 1997 @@ -34,7 +34,7 @@ * SUCH DAMAGE. * * from: @(#)vm_page.c 7.4 (Berkeley) 5/7/91 - * $Id: vm_page.c,v 1.69.2.3 1997/03/25 04:54:35 dyson Exp $ + * $Id: vm_page.c,v 1.69.2.5 1997/11/06 04:33:01 dyson Exp $ */ /* @@ -577,7 +577,7 @@ TAILQ_REMOVE(pq->pl, m, pageq); --(*pq->cnt); --(*pq->lcnt); - if ((m->queue - m->pc) == PQ_CACHE) { + if ((queue - m->pc) == PQ_CACHE) { if ((cnt.v_cache_count + cnt.v_free_count) < (cnt.v_free_reserved + cnt.v_cache_min)) pagedaemon_wakeup(); @@ -600,7 +600,7 @@ for(j = 0; j < PQ_L1_SIZE; j++) { for(i = (PQ_L2_SIZE/2) - (PQ_L1_SIZE - 1); - i >= 0; + (i+j) >= 0; i -= PQ_L1_SIZE) { hindex = (index + (i+j)) & PQ_L2_MASK; m = TAILQ_FIRST(vm_page_queues[basequeue + hindex].pl); diff -ur src/sys/vm/vnode_pager.c src/sys/vm/vnode_pager.c --- src/sys/vm/vnode_pager.c Wed May 28 11:26:46 1997 +++ src/sys/vm/vnode_pager.c Wed Dec 24 11:54:40 1997 @@ -231,10 +231,12 @@ blocksperpage = 0; if (pagesperblock > 0) { reqblock = pindex / pagesperblock; - } else { + } else if (bsize > 0) { blocksperpage = (PAGE_SIZE / bsize); reqblock = pindex * blocksperpage; - } + } else + return FALSE; + err = VOP_BMAP(vp, reqblock, (struct vnode **) 0, &bn, after, before); if (err) diff -ur src/usr.sbin/lpr/common_source/displayq.c src/usr.sbin/lpr/common_source/displayq.c --- src/usr.sbin/lpr/common_source/displayq.c Wed Oct 15 05:25:35 1997 +++ src/usr.sbin/lpr/common_source/displayq.c Wed Dec 24 11:48:50 1997 @@ -242,6 +242,7 @@ savealrm = signal(SIGALRM, alarmhandler); alarm(CT); fd = getport(RM, 0); + alarm(0); (void)signal(SIGALRM, savealrm); if (fd < 0) { if (from != host) diff -ur src/usr.sbin/lpr/lpd/printjob.c src/usr.sbin/lpr/lpd/printjob.c --- src/usr.sbin/lpr/lpd/printjob.c Wed Oct 15 02:56:00 1997 +++ src/usr.sbin/lpr/lpd/printjob.c Wed Dec 24 11:49:10 1997 @@ -1474,6 +1474,7 @@ savealrm = signal(SIGALRM, alarmhandler); alarm(CT); pfd = getport(cp, port); + alarm(0); (void)signal(SIGALRM, savealrm); if (pfd < 0 && errno == ECONNREFUSED) resp = 1; @@ -1541,6 +1542,7 @@ savealrm = signal(SIGALRM, alarmhandler); alarm(CT); pfd = getport(RM, 0); + alarm(0); (void)signal(SIGALRM, savealrm); if (pfd >= 0) { (void) snprintf(line, sizeof(line), "\2%s\n", RP); Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 11:43:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22143 for freebsd-stable-outgoing; Mon, 23 Mar 1998 11:43:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21998 for ; Mon, 23 Mar 1998 11:43:08 -0800 (PST) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id LAA07832; Mon, 23 Mar 1998 11:42:20 -0800 (PST) Message-Id: <199803231942.LAA07832@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaaodla; Mon Mar 23 11:42:16 1998 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: "Daniel O'Connor" cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Callaghan" , gkshenaut@ucdavis.edu, stable@FreeBSD.ORG Subject: Re: after the release ... In-reply-to: Your message of "Mon, 23 Mar 1998 11:31:08 +1030." <199803230101.LAA28437@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 11:41:25 -0800 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > > Another consideration: What if somebody modifies the O/S at their > > site. MVS, for example, uses USERMODS which automatically get dumped > > when patches (PTF's or APARFIXES), or new product (FMID's) are applied. > > Would those of us maintaining FreeBSD sites be willing to follow a > > regimen as specified by the chosen patch philosophy? On the other hand > > would Sun's simpler approach work -- if the file's checksum (MD5?) > > doesn't match what the patch expects, abort? > Well, that is the whole can of worms IMHO.. > I mean if you could guarantee that the system would be in a given state then a > binary upgrade would be quite easy. The main problem IMHO would be making a > system which didn't mangle any custom stuff you've done to your machine.. > > I see making a 'patch' consist of a group of things to apply/change/suggest > which have pre/co-requisites, and if these are wrong(ie the checksum doesn't > match or the date is too new/old) then don't apply that group.. ie make each > group atomic, so that if part of it fails, then back the whole group out. If a user modification to the system has been logged and MD5 or some other checksum is used, you can be reasonably sure that the binary (or source) file being patched is the one you want. My suggestion would notify you that you've patched a backup version of the binary and that you would need to reapply your modification to the system. Normally this would be a two pass process, identifying the files to be updated and performing the update. During the identification phase, if a file has been found to be inconsistent and a user modification has been found in the database, then the modification can be identified, reported, and the user has the option of forcing the patch in, based on the original binary kept in backup, or aborting the patch. If the user forces the patch in, it would be up to the user to re-apply any user modifications. If on the other hand the user modification is not in the database, any user modification cannot be identified and the patch will need to be aborted. Then it's up to the user to figure out what went wrong. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 11:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23975 for freebsd-stable-outgoing; Mon, 23 Mar 1998 11:49:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23778 for ; Mon, 23 Mar 1998 11:48:38 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA16966; Mon, 23 Mar 1998 11:48:30 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3516BC8D.A02E77D@dal.net> Date: Mon, 23 Mar 1998 11:48:29 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0316 i386) MIME-Version: 1.0 To: "Dag-Erling Coidan Smørgrav" CC: stable@FreeBSD.ORG Subject: Re: A day in the life of a hacker (was: Re: 'Code Freeze') References: <11036.890349578@time.cdrom.com> <19980323094611.21526@iii.co.uk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Dag-Erling Coidan Smørgrav wrote: > > Oh, yeah, right, I forgot that I am a complete idiot, Clearly, however there is no need to spew the reminder to the list. Nik was trying to help you. If you don't need the help the polite response is to thank him and explain that it is not needed. Alternatively you could take him up on his offer to suggest specific changes that will help make the tutorial more useful from your perspective. Flaming someone for trying to help you only serves to remind us of what you claim to have forgotten. Have a nice day, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 12:13:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29136 for freebsd-stable-outgoing; Mon, 23 Mar 1998 12:13:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29117 for ; Mon, 23 Mar 1998 12:12:52 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id MAA26230 for ; Mon, 23 Mar 1998 12:13:02 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: stable@FreeBSD.ORG Subject: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 Date: Mon, 23 Mar 1998 12:13:01 -0800 Message-ID: <26223.890683981@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk The 2.2.6 release will be going out as scheduled and the tag will be laid down no later than 1:00AM, 13 hours from now. Please make sure that any outstanding issues with the 2.2-stable branch are raised with me ASAP since it will be too late once the tag has been applied (well, critical emergencies can get the tags rolled forward on those files which specifically require it, but I can't really imagine such a situation arising at this point). The 2.2 packages collection will be fetched from ftp.freebsd.org sometime in the 24 hours following the tag operation so that the CDROM release can be created, so let the ports folk count that as a "heads up!" also. Thanks! Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 12:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02514 for freebsd-stable-outgoing; Mon, 23 Mar 1998 12:42:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dis.VAZ.ru (dis.vaz.ru [195.144.198.161]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA02468 for ; Mon, 23 Mar 1998 12:42:36 -0800 (PST) (envelope-from V.Petrov@VAZ.ru) Received: by dis.VAZ.ru with UUCP id AA24590 (5.65c8/DIS-1.4.4 for freebsd-stable@freebsd.org); Tue, 24 Mar 1998 00:40:43 +0400 Received: from localhost (vap@localhost) by asm.vaz.ru (8.8.8/8.8.5) with SMTP id AAA02057; Tue, 24 Mar 1998 00:39:59 +0400 (KSK) X-Authentication-Warning: asm.vaz.ru: vap owned process doing -bs Date: Tue, 24 Mar 1998 00:39:59 +0400 (KSK) From: "Vladimir A. Petrov" X-Sender: vap@asm.vaz.ru To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Surprise Reboots In-Reply-To: <199803231937.LAA14250@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 Good day! On Mon, 23 Mar 1998, Cy Schubert - ITSD Open Systems Group wrote: > > > upgrade to 2.2.6-BETA or email me and I will send you a 42K patch that > > > > tree but I can't rebuild from it. So, if Your patch may help me > > in this situation then it will be so kind if You send me Your > > patch. > > Since I've received a number of requests for the patches, here they > are. They are a collection of stuff from the -stable CVS tree, an Thank You for Your time! With best regards, Vladimir Petrov. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 12:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03656 for freebsd-stable-outgoing; Mon, 23 Mar 1998 12:48:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03632 for ; Mon, 23 Mar 1998 12:48:29 -0800 (PST) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.8/8.8.8) with SMTP id MAA27786; Mon, 23 Mar 1998 12:48:26 -0800 (PST) (envelope-from ejs@bfd.com) Date: Mon, 23 Mar 1998 12:48:26 -0800 (PST) From: "Eric J. Schwertfeger" To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-Reply-To: <26223.890683981@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Jordan K. Hubbard wrote: > The 2.2.6 release will be going out as scheduled and the tag will be > laid down no later than 1:00AM, 13 hours from now. Since I was rather loud in announcing the problem, I'll be almost as loud (but not as verbose) in thanking whoever fixed the problem I was seeing with recent snapshots not seeing existing disk labels. I selected upgrade on a 2.2.6-980323-BETA install disk (the first 2.2.6 BETA on current.freebsd.org since 980315), and it saw everything it was supposed to. Again, thank you very much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 12:49:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04049 for freebsd-stable-outgoing; Mon, 23 Mar 1998 12:49:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03970 for ; Mon, 23 Mar 1998 12:49:08 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id PAA13695; Mon, 23 Mar 1998 15:46:50 -0500 (EST) Date: Mon, 23 Mar 1998 15:46:50 -0500 (EST) From: Derek Flowers To: "Daniel O'Callaghan" cc: stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Daniel O'Callaghan wrote: > > I think Derek is doing a great job! Congrats. However, I do also think > that Cy Schubert made a very valid point that we need to identify what it > is that is going to be updated using this package mechanism. > > If the pkg mechanism include feature enhancements to the system, then > people may be reluctant to use it, lest they change somethin on > which their system depends. Alex changed the size of the ipfw structure > and created an incompatibility between ipfw(8) and ip_fw.[ch] last > November/December. The result was that a kernel upgrade meant a > userland upgrade for ipfw(8). This is likely to be a good reason many > will shy away from enhancement packages. > > If the pkg mechanism is only for bug fixes, that's fine, until you need > to produce a package for a bug fix in an enhancement. > > The only way to cater for both scenarios is to flag each package as > either ENHANCEMENT or FIX, and make any FIX packages dependent on the > ENHANCEMENT package. > > Of course, if there is a bug fix in (e.g.) ipfw which is unrelated to, > but after, an enhancement, we need two packages. > > As you can see, this is starting to get yucky, and it is a good reason to > sit down and work out exactly what it is we want to achieve with this > upgrade mechanism. > > Does anyone else have any ideas? > > Danny I originally wanted to do this to cover patches that correct bugs in the release distributions. An example would be the lpr fix for 2.2.5-RELEASE. It seems like a simple idea, instead of having to install the sources, apply the diffs, and recompile, why not just have a patch that contained the already compiled patch and use it to repair the fix. There is no reason why the same idea cannot be applied to the overall OS for updating, patching, installing, etc. Right now, I'm working on converting the distributions over to package format, mainly to use the package database as a means of confirming what version is installed. After getting this done, I can work on updates and the problems that go with them such as uninstall options, version checking, etc. The main problem to face after I get the package format to work is creating an install disk to work with the package format. I am clueless on how to go about doing this. Right now, I am testing the packages by installing a minimal distribution to the test computer and using pkg_add to add all the distribution packages to the system. There is also the ``staging area'' problem that I haven't been able to solve. I hope this answered your question. ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 12:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05234 for freebsd-stable-outgoing; Mon, 23 Mar 1998 12:53:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA05191 for ; Mon, 23 Mar 1998 12:52:44 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Mar 98 20:52:43 +0000 (GMT) To: "Jordan K. Hubbard" cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Mon, 23 Mar 1998 12:13:01 PST." <26223.890683981@time.cdrom.com> Date: Mon, 23 Mar 1998 20:52:43 +0000 From: David Malone Message-ID: <9803232052.aa01569@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Any chance of applying the fact that restore coredumps on filesystems with a blocksize of 512? I tried to get John Dyson to apply the patch but he seems too busy. The gnats tag is bin/5704. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 13:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07196 for freebsd-stable-outgoing; Mon, 23 Mar 1998 13:01:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chain.freebsd.os.org.za (VfdFHKg8sppAx2B8NSCexph2C/DC1qJg@chain.freebsd.os.org.za [196.7.74.174]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07104 for ; Mon, 23 Mar 1998 13:01:34 -0800 (PST) (envelope-from khetan@chain.freebsd.os.org.za) Received: from localhost (khetan@localhost) by chain.freebsd.os.org.za (8.8.8+3.0Wbeta13/8.8.8) with SMTP id XAA04321 for ; Mon, 23 Mar 1998 23:01:26 +0200 (SAT) Date: Mon, 23 Mar 1998 23:01:26 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@chain Reply-To: Khetan Gajjar To: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-Reply-To: <26223.890683981@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Jordan K. Hubbard wrote: >Please make sure that any outstanding issues with the 2.2-stable >branch are raised with me ASAP since it will be too late once the tag Has anyone managed to get kerberos IV to build successfully under 2.2.6-BETA ? I've tried, and haven't been successful. --- Khetan Gajjar (!kg1779) khetan@iafrica.com (w); khetan@os.org.za (h) http://www.os.org.za/~khetan | Finger: khetan@chain.freebsd.os.org.za UUNET Internet Africa Support | FreeBSD enthusiast-www2.za.freebsd.org A computer without Microsoft and Intel is like chocolate cake without tomato sauce and mustard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 13:50:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19625 for freebsd-stable-outgoing; Mon, 23 Mar 1998 13:50:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19504 for ; Mon, 23 Mar 1998 13:50:31 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id PAA13706; Mon, 23 Mar 1998 15:52:03 -0500 (EST) Date: Mon, 23 Mar 1998 15:52:03 -0500 (EST) From: Derek Flowers To: Cy Schubert - ITSD Open Systems Group cc: "Daniel O'Connor" , "Daniel O'Callaghan" , gkshenaut@ucdavis.edu, stable@FreeBSD.ORG Subject: Re: after the release ... In-Reply-To: <199803231500.HAA10455@cwsys.cwsent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Cy Schubert - ITSD Open Systems Group wrote: > > > > > Another consideration: What if somebody modifies the O/S at their > > > site. MVS, for example, uses USERMODS which automatically get dumped > > > when patches (PTF's or APARFIXES), or new product (FMID's) are applied. > > > Would those of us maintaining FreeBSD sites be willing to follow a > > > regimen as specified by the chosen patch philosophy? On the other hand > > > would Sun's simpler approach work -- if the file's checksum (MD5?) > > > doesn't match what the patch expects, abort? > > Well, that is the whole can of worms IMHO.. > > I mean if you could guarantee that the system would be in a given state then > a > > binary upgrade would be quite easy. The main problem IMHO would be making a > > system which didn't mangle any custom stuff you've done to your machine.. > > That's right! That's why a philosophy should be chosen and strictly > adhered to. Every sysadmin would need to follow this or he/she would > have a mess, e.g. patches would not install if the state was not > consistent with what was expected, and a reinstall would be required to > get back to a know state. > > > > > I see making a 'patch' consist of a group of things to apply/change/suggest > > which have pre/co-requisites, and if these are wrong(ie the checksum doesn't > > match or the date is too new/old) then don't apply that group.. ie make each > > group atomic, so that if part of it fails, then back the whole group out. > > That's where the USERMOD would be used. The individual sysadmin would > need to tell the system by using a packaged application to modify the > system. This way the system would know why any particular binary (or > source module) would be inconsistent with expectations. (The USERMOD > process would allow modifications but make backup copies of "vendor" > supplied binaries and sources in the process.) If a USERMOD was > detected, the backup copy would be used and the USERMOD would be > verbosely deleted. The sysadmin would need to re-apply their > customization. > > I'm not saying that we need to adopt IBM's approach. We just need to > consider _all_ of the ramifications and do it right. > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > UNIX Support OV/VM: BCSC02(CSCHUBER) > ITSD BITNET: CSCHUBER@BCSC02.BITNET > Government of BC Internet: cschuber@uumail.gov.bc.ca > Cy.Schubert@gems8.gov.bc.ca The best way to go on custom changes is that the patch checks the md5 checksum of the file it is going to replace and if it does not match, abort the installation. It seems to me that someone doing custom work on files should have the sources and the time to patch stuff manually. A binary patch system is mainly for those who do not have the space or the time to install the sources, make the changes, recompile, and reinstall. ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 14:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23523 for freebsd-stable-outgoing; Mon, 23 Mar 1998 14:11:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23127 for ; Mon, 23 Mar 1998 14:09:55 -0800 (PST) (envelope-from softweyr@xmission.xmission.com) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.8/8.7.5) id PAA27779; Mon, 23 Mar 1998 15:09:28 -0700 (MST) From: Wes Peters - Softweyr LLC Message-Id: <199803232209.PAA27779@xmission.xmission.com> Subject: Re: Binary package updates, etc. To: djflow@portwwwbus.tc.cc.va.us (Derek Flowers) Date: Mon, 23 Mar 1998 15:09:27 -0700 (MST) Cc: softweyr@xmission.com, software@kew.com, stable@FreeBSD.ORG In-Reply-To: from "Derek Flowers" at Mar 22, 98 03:39:19 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Derek Flowers asked: > I've done some quick and dirty work on binary package updates and would > like some comments on what I've got going, where to go in the future, etc. Thanks for diving right in. I've been reading this thread, and have tried to summarize the current state of questions, comments and concerns thusly: So far, it seems we have the following points to ponder in our thumbnail design. I've interspersed my comments on each point, you may feel free to agree, disagree, or ignore them; this is a *discussion*. ;^) o Are patches designed to just fix problems, to add features, or what? Both. Past experience in -stable branches has shown that there are periods of activity when one of our developers fixes a bug or updates a subsystem, followed by periods of inactivity. I propose that patches be created to update systems to "snapshots" of the -stable tree that roughly reflect these periods of relative inactivity. For instance, when a security bug is noticed, there is generally quite a bit of discussion, and one to several commits on the -stable tree related to fixing the bug. When consensus has been reached that the bug is closed and the system stable, the activity dies down. At that time it would be appropriate to create an UPDATE that fixes this problem. The same cycle tends to apply to an update of a system utility, i.e. the recent fix for disk slice names. Updating to known (and perhaps CVS-labelled) sync points on the FreeBSD stable tree also makes it somewhat easier to report problems, since what you end up with is a system equivalent to a known point on the -stable tree. This means each UPDATE would require *every* previous UPDATE as a pre-requisite. This may be a major flaw in this approach, but it does simplify the design considerably. o Are we patching (or replacing) executables, the kernel, source code, or what? All of the above, with limitations. Ideally, we'll be able to detect what you have installed on your system and update those parts. We'll need to update, at a minimum: - Binary executables - Man page sources - Kernel object files - Files, devices, etc., in the kernel source tree - GENERIC and LINT kernel configurations - /kernel.GENERIC - system configuration files in /etc, etc. (pun intended) Obviously, if anything inside the kernel is modified, the user should be encouraged to review their kernel configuration against the new GENERIC and LINT and rebuild their kernel. o Who is going to make these patches? As with all other FreeBSD jobs, whoever volunteers. Ideally, this would be SEVERAL someones who use FreeBSD-stable in their daily work and really need this feature. If they're willing to commit the updates to their systems, the updates are probably in good hands. o Where do we save the files we are replacing, so we can back out the patch? In the same place pkg_add already puts this kind of information? I don't know, this is a good question. I'd like to see all of the replacements for a particular update stored in a gzipped tarball to save space and inodes, personally. o How do we authenticate the packages so we can be sure we're not installing the new FreeBSD kernel virus from Chaos? The JAR signing mechanism mentioned by Eivind sounds like a great methodology, if package users are not required to install the JDK. If packages creators have to install the JDK in order to build the signature, that should be acceptable. o Should we use binary diffs? (What are binary diffs?) Binary diffs mean that we could send out just the bytes in any changed file, rather than the whole file. For many updates, where you are changing only a few small features in a large binary, the diff could be quite a bit smaller. This is a cool idea, and would save users a lot of download time in the future. On the other hand, binary diff utilities are non-trivial to create. I'd say if we can find binary diff and patch utilities to add to the system, use them, but it's not worth delaying the implementation to wait for this feature. We can always add it in the future, as an update. ;^) o What do we do if the user has modified some source on their system? (Either kernel or userland source.) Politely explain to them we designed this tool for binary-only systems that don't have source installed, and invite them to use CVSup and 'make world.' Seriously, handling kernel (or userland) patches to the source tree is a little beyond the scope of this utility. For users with large numbers of systems, ideally we provide them the facility to make their own updates, where they can CVSup on their 'configuration' machine and make updates to push out to their remote binary-only machines. These local updates would, of course, include their local changes. o What about a GUI for this? As I said before, write a little Tk program with an 'update' button that goes to the stable ftp server, figures out what the highest update available is, and passes it to pkg_add. Any prerequisites not installed locally will be automagically brought over and installed by pkg_add. Maybe we can write a simple 'current update level' server running on port 244, which reports the highest update level posted as an unsigned 16-bit number for each connection, and run it on the server. JMB recommends calling this tool 'DAS', for the class of user it is intended for. Being acronymically enabled, I'll vote for 'Do Update Maintenance Bull****', or 'dumb' for short. Gee, with a little more thought, I could probably even come up with an acronym for 'dummy-up'. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 14:30:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27482 for freebsd-stable-outgoing; Mon, 23 Mar 1998 14:30:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27365; Mon, 23 Mar 1998 14:30:05 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA14677; Mon, 23 Mar 1998 14:30:05 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3516E26C.C8F6EA1D@dal.net> Date: Mon, 23 Mar 1998 14:30:04 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0316 i386) MIME-Version: 1.0 To: FreeBSD-Stable@FreeBSD.ORG, "Jordan K. Hubbard" Subject: Important questions regarding the new slice code Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I'm working on the final revision of the FOO.TXT stuff and it dawned on me that I was unclear on something. Let's say that a user has a 2.2.5 system with a customized 2.2.5 kernel, the "upgrade from sysintstall" method will obviously update mount, but will it update the kernel? If not, what are the possible repercussions? I am planning to go with the following text regarding this issue in IMPORTNT.TXT since Mike never got back to me with updated information. In the 2.2.6-Release version of FreeBSD new disk slice code has been introduced. The new code should not cause problems with the vast majority of installations providing that you follow a few simple instructions. 1. If you are doing a new installation of FreeBSD there is nothing to worry about, all of the appropriate steps will be handled for you automatically. 2. If you are planning to upgrade to 2.2.6 using the "make world" method, you MUST make the world first, THEN compile the new kernel, THEN reboot. This is good practice in general for make world upgrades. 3. If you are using sysintall to upgrade to 2.2.6, ..... PLEASE FILL IN THE BLANK Thanks, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 14:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28891 for freebsd-stable-outgoing; Mon, 23 Mar 1998 14:37:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28869 for ; Mon, 23 Mar 1998 14:37:17 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA07272; Mon, 23 Mar 1998 22:36:43 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA20374; Mon, 23 Mar 1998 23:36:39 +0100 (MET) Message-ID: <19980323233639.18183@follo.net> Date: Mon, 23 Mar 1998 23:36:39 +0100 From: Eivind Eklund To: Wes Peters - Softweyr LLC , Derek Flowers Cc: software@kew.com, stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. References: <199803232209.PAA27779@xmission.xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803232209.PAA27779@xmission.xmission.com>; from Wes Peters - Softweyr LLC on Mon, Mar 23, 1998 at 03:09:27PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, Mar 23, 1998 at 03:09:27PM -0700, Wes Peters - Softweyr LLC wrote: > o Should we use binary diffs? (What are binary diffs?) > > Binary diffs mean that we could send out just the bytes in any changed > file, rather than the whole file. For many updates, where you are > changing only a few small features in a large binary, the diff could > be quite a bit smaller. > > This is a cool idea, and would save users a lot of download time in > the future. On the other hand, binary diff utilities are non-trivial > to create. I'd say if we can find binary diff and patch utilities to > add to the system, use them, but it's not worth delaying the > implementation to wait for this feature. We can always add it in the > future, as an update. ;^) I've not been able to find any Open Source binary diff/patch systems. Implementing one is actually not too hard. You do an LZ77 (or LZW, but that strands you in patent-land) compression with the old executable considered a string pool. It should be only an evening or two's worth of work, if you've done LZ-compression before and know the tricks. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 14:38:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29292 for freebsd-stable-outgoing; Mon, 23 Mar 1998 14:38:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29152 for ; Mon, 23 Mar 1998 14:38:13 -0800 (PST) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id OAA16235; Mon, 23 Mar 1998 14:36:52 -0800 (PST) Message-Id: <199803232236.OAA16235@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaakeba; Mon Mar 23 14:36:42 1998 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: Derek Flowers cc: Cy Schubert - ITSD Open Systems Group , "Daniel O'Connor" , "Daniel O'Callaghan" , gkshenaut@ucdavis.edu, stable@FreeBSD.ORG Subject: Re: after the release ... In-reply-to: Your message of "Mon, 23 Mar 1998 15:52:03 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 14:35:37 -0800 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > On Mon, 23 Mar 1998, Cy Schubert - ITSD Open Systems Group wrote: > > > > > > > > Another consideration: What if somebody modifies the O/S at their > > > > site. MVS, for example, uses USERMODS which automatically get dumped > > > > when patches (PTF's or APARFIXES), or new product (FMID's) are applied. > > > > Would those of us maintaining FreeBSD sites be willing to follow a > > > > regimen as specified by the chosen patch philosophy? On the other hand > > > > would Sun's simpler approach work -- if the file's checksum (MD5?) > > > > doesn't match what the patch expects, abort? > > > Well, that is the whole can of worms IMHO.. > > > I mean if you could guarantee that the system would be in a given state t hen > > a > > > binary upgrade would be quite easy. The main problem IMHO would be making a > > > system which didn't mangle any custom stuff you've done to your machine.. > > > > That's right! That's why a philosophy should be chosen and strictly > > adhered to. Every sysadmin would need to follow this or he/she would > > have a mess, e.g. patches would not install if the state was not > > consistent with what was expected, and a reinstall would be required to > > get back to a know state. > > > > > > > > I see making a 'patch' consist of a group of things to apply/change/sugge st > > > which have pre/co-requisites, and if these are wrong(ie the checksum does n't > > > match or the date is too new/old) then don't apply that group.. ie make e ach > > > group atomic, so that if part of it fails, then back the whole group out. > > > > That's where the USERMOD would be used. The individual sysadmin would > > need to tell the system by using a packaged application to modify the > > system. This way the system would know why any particular binary (or > > source module) would be inconsistent with expectations. (The USERMOD > > process would allow modifications but make backup copies of "vendor" > > supplied binaries and sources in the process.) If a USERMOD was > > detected, the backup copy would be used and the USERMOD would be > > verbosely deleted. The sysadmin would need to re-apply their > > customization. > > > > I'm not saying that we need to adopt IBM's approach. We just need to > > consider _all_ of the ramifications and do it right. > > > > > > Regards, Phone: (250)387-8437 > > Cy Schubert Fax: (250)387-5766 > > UNIX Support OV/VM: BCSC02(CSCHUBER) > > ITSD BITNET: CSCHUBER@BCSC02.BITNET > > Government of BC Internet: cschuber@uumail.gov.bc.ca > > Cy.Schubert@gems8.gov.bc.ca > > The best way to go on custom changes is that the patch checks the md5 > checksum of the file it is going to replace and if it does not match, > abort the installation. It seems to me that someone doing custom work on > files should have the sources and the time to patch stuff manually. ... which is what Sun does. > > A binary patch system is mainly for those who do not have the space or the > time to install the sources, make the changes, recompile, and reinstall. > > ---------------------------------------- > Derek Flowers > djflow@erols.com > http://portwwwbus.tc.cc.va.us/~djflow Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 14:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29660 for freebsd-stable-outgoing; Mon, 23 Mar 1998 14:39:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29575; Mon, 23 Mar 1998 14:39:38 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA07307; Mon, 23 Mar 1998 22:39:13 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA20391; Mon, 23 Mar 1998 23:39:13 +0100 (MET) Message-ID: <19980323233913.57544@follo.net> Date: Mon, 23 Mar 1998 23:39:13 +0100 From: Eivind Eklund To: Studded , FreeBSD-Stable@FreeBSD.ORG, "Jordan K. Hubbard" Subject: Re: Important questions regarding the new slice code References: <3516E26C.C8F6EA1D@dal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <3516E26C.C8F6EA1D@dal.net>; from Studded on Mon, Mar 23, 1998 at 02:30:04PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, Mar 23, 1998 at 02:30:04PM -0800, Studded wrote: > I'm working on the final revision of the FOO.TXT stuff and it dawned on > me that I was unclear on something. Let's say that a user has a 2.2.5 > system with a customized 2.2.5 kernel, the "upgrade from sysintstall" > method will obviously update mount, but will it update the kernel? It will update the kernel. The only thing you should be clued about here is updating /etc/fstab (maybe this is re-written for you, too - I don't remember). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 14:57:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02619 for freebsd-stable-outgoing; Mon, 23 Mar 1998 14:57:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02578 for ; Mon, 23 Mar 1998 14:57:05 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (22lAWo1VNaIeoGlMu94ItXV/hGPKD7GZ@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id AAA19319; Tue, 24 Mar 1998 00:57:00 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (/mR9Q7dv+ydu8+Ttj2MaxKH0f7sqPta/@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id AAA02023; Tue, 24 Mar 1998 00:56:55 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199803232256.AAA02023@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Khetan Gajjar cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Mar 1998 00:56:55 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Khetan Gajjar wrote: > On Mon, 23 Mar 1998, Jordan K. Hubbard wrote: > > >Please make sure that any outstanding issues with the 2.2-stable > >branch are raised with me ASAP since it will be too late once the tag > > Has anyone managed to get kerberos IV to build successfully under > 2.2.6-BETA ? > > I've tried, and haven't been successful. Khetan, see me at work tomorrow. Dont't bug the list. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 15:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05786 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:13:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05734 for ; Mon, 23 Mar 1998 15:13:16 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA27113; Mon, 23 Mar 1998 15:13:22 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: "Eric J. Schwertfeger" cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Mon, 23 Mar 1998 12:48:26 PST." Date: Mon, 23 Mar 1998 15:13:22 -0800 Message-ID: <27109.890694802@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Since I was rather loud in announcing the problem, I'll be almost as loud > (but not as verbose) in thanking whoever fixed the problem I was seeing Yes, thank you for reporting that - I finally figured it out and fixed it a couple of days ago. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 15:22:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08459 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:22:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08284 for ; Mon, 23 Mar 1998 15:21:23 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA27192; Mon, 23 Mar 1998 15:21:13 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: David Malone cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Mon, 23 Mar 1998 20:52:43 GMT." <9803232052.aa01569@salmon.maths.tcd.ie> Date: Mon, 23 Mar 1998 15:21:13 -0800 Message-ID: <27187.890695273@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Any chance of applying the fact that restore coredumps on filesystems > with a blocksize of 512? I tried to get John Dyson to apply the patch > but he seems too busy. The gnats tag is bin/5704. Argh. It never even got committed to -current, which meant that it got no shake-out period. I've applied it to -current and closed the PR. If nobody reports a problem with it in -current, I'll merge the change into the 2.2 branch after the release. Sorry, but it's just too close to the wire to bring in a change to restore that I don't understand the full ramifications of. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 15:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09168 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:23:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09019 for ; Mon, 23 Mar 1998 15:23:14 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA27221; Mon, 23 Mar 1998 15:23:07 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Khetan Gajjar cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Sat, 23 Mar 1998 23:01:26 +0200." Date: Mon, 23 Mar 1998 15:23:07 -0800 Message-ID: <27218.890695387@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > Has anyone managed to get kerberos IV to build successfully under > 2.2.6-BETA ? Works for me, after I cleaned out the old cruft from my include directory. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 15:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11811 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:30:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA11717 for ; Mon, 23 Mar 1998 15:29:54 -0800 (PST) (envelope-from trost@cloud.rain.com) Received: (qmail 6739 invoked by uid 4); 23 Mar 1998 23:29:22 -0000 Message-ID: <19980323232922.6738.qmail@jli.com> Received: (qmail 17596 invoked from network); 23 Mar 1998 23:23:30 -0000 Received: from localhost.cloud.rain.com (127.0.0.1) by localhost.cloud.rain.com with SMTP; 23 Mar 1998 23:23:29 -0000 To: stable@FreeBSD.ORG Subject: Re: problems with PPP References: <199803151535.PAA19627@awfulhak.org> In-reply-to: Your message of Sun, 15 Mar 1998 15:35:34 GMT. <199803151535.PAA19627@awfulhak.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17592.890695409.1@cloud.rain.com> Date: Mon, 23 Mar 1998 15:23:29 -0800 From: Bill Trost Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Brian Somers writes: > Brian Somers writes: > This looks like a ``first connection'' problem. There's a bit in the > FAQ about it. > > I don't think that is the problem. If I run ping or dig after the link > has come up, it's still using 0.0.0.0 as the source address. I'm sorry to say, but AFAIK, this is impossible, and even if it *is* actually happening, it's nothing to do with ppp :-( That's what I thought, too. I added a ppp.linkup per your conversation with Nate, and everything now appears to work fine. I do not really understand why this is the case. Could it be that the default route entry got stuck with an old version of the interface pointer, and that was what was polluting the outgoing packets? Thanks for the help, Brian (and Nate (-: ). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 15:51:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15657 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:51:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15649 for ; Mon, 23 Mar 1998 15:51:37 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA27536; Mon, 23 Mar 1998 15:51:46 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Studded cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Important questions regarding the new slice code In-reply-to: Your message of "Mon, 23 Mar 1998 14:30:04 PST." <3516E26C.C8F6EA1D@dal.net> Date: Mon, 23 Mar 1998 15:51:46 -0800 Message-ID: <27531.890697106@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I'm working on the final revision of the FOO.TXT stuff and it dawned on > me that I was unclear on something. Let's say that a user has a 2.2.5 > system with a customized 2.2.5 kernel, the "upgrade from sysintstall" > method will obviously update mount, but will it update the kernel? If > not, what are the possible repercussions? It will update the kernel in that it will splat the new GENERIC one right on top. If the user had heavily customized it, there will of course be repercussions. > I am planning to go with the following text regarding this issue in > IMPORTNT.TXT since Mike never got back to me with updated information. Hmmm. I agree that this should be covered, I'm just still not exactly sure where. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 15:53:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16127 for freebsd-stable-outgoing; Mon, 23 Mar 1998 15:53:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16037; Mon, 23 Mar 1998 15:53:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA27569; Mon, 23 Mar 1998 15:52:52 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: Studded , FreeBSD-Stable@FreeBSD.ORG, "Jordan K. Hubbard" Subject: Re: Important questions regarding the new slice code In-reply-to: Your message of "Mon, 23 Mar 1998 23:39:13 +0100." <19980323233913.57544@follo.net> Date: Mon, 23 Mar 1998 15:52:51 -0800 Message-ID: <27566.890697171@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > The only thing you should be clued about here is updating /etc/fstab > (maybe this is re-written for you, too - I don't remember). It is not, and the clue about updating was just added to the final confirmation dialog. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 16:44:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26778 for freebsd-stable-outgoing; Mon, 23 Mar 1998 16:44:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from proxyb2.san.rr.com (proxyb2-atm.san.rr.com [204.210.0.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26577; Mon, 23 Mar 1998 16:41:57 -0800 (PST) (envelope-from Studded@dal.net) Received: from dt050n33.san.rr.com (dt050n33.san.rr.com [204.210.31.51]) by proxyb2.san.rr.com (8.8.7/8.8.8) with SMTP id QAA08850; Mon, 23 Mar 1998 16:41:15 -0800 (PST) Message-Id: <199803240041.QAA08850@proxyb2.san.rr.com> From: "Studded" To: "jkh@freebsd.org" , "Jordan K. Hubbard" Cc: "FreeBSD-Stable@FreeBSD.ORG" Date: Mon, 23 Mar 98 16:41:11 -0800 Reply-To: "Studded" X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Important questions regarding the new slice code Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998 15:51:46 -0800, Jordan K. Hubbard wrote: >> I'm working on the final revision of the FOO.TXT stuff and it dawned on >> me that I was unclear on something. Let's say that a user has a 2.2.5 >> system with a customized 2.2.5 kernel, the "upgrade from sysintstall" >> method will obviously update mount, but will it update the kernel? If >> not, what are the possible repercussions? > >It will update the kernel in that it will splat the new GENERIC one >right on top. If the user had heavily customized it, there will >of course be repercussions. Thanks, that's what I needed to know. >> I am planning to go with the following text regarding this issue in >> IMPORTNT.TXT since Mike never got back to me with updated information. > >Hmmm. I agree that this should be covered, I'm just still not exactly >sure where. Here's the layout I'm using per my previous post about this. I should have things basically laid out and knocked into a final form in a couple hours. ROAD MAP: README.TXT This file RELNOTES.TXT Release Notes - what's new & different in this release ABOUT.TXT All about FreeBSD including contact information OVERVIEW.TXT Details about what's contained in this distribution HARDWARE.TXT Information about supported hardware IMPORTNT.TXT Important information you should read before doing an upgrade or new installation INSTALL.TXT How to make a new installation of FreeBSD on your PC using the data you see here UPGRADE.TXT How to upgrade your existing FreeBSD installation *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 4,710 clients and still growing. :-) *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) *** Part of the DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 17:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01820 for freebsd-stable-outgoing; Mon, 23 Mar 1998 17:14:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01805 for ; Mon, 23 Mar 1998 17:14:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA14594 for ; Mon, 23 Mar 1998 17:11:07 -0800 (PST) Message-Id: <199803240111.RAA14594@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Important questions regarding the new slice code In-reply-to: Your message of "Mon, 23 Mar 1998 15:52:51 PST." <27566.890697171@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 17:11:05 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > The only thing you should be clued about here is updating /etc/fstab > > (maybe this is re-written for you, too - I don't remember). > > It is not, and the clue about updating was just added to the final > confirmation dialog. :) Just to clarify here; the original plan was to have it automagically updated, but there are some unpleasant corner cases here where the result would be a plastered configuration, and I don't think anyone wants that. So instead, here's some text to explain the situation. It needs to be somewhere prominent (for upgraders anyway). ---- FreeBSD 2.2.6 introduces a change in the naming of the device from which the root filesystem is mounted. This change affects all systems, however user intervention is only required for systems undergoing an upgrade installation. Previously, the root filesystem was always mounted from the compatability slice, while other partitions on the same disk were mounted from their true slice. This might, for example, have resulted in an /etc/fstab file like: # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0a / ufs rw 1 1 /dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 For FreeBSD 2.2.6 and later, this format changes so that the device for '/' is consistent with others, ie. # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0s2a / ufs rw 1 1 /dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 On a new installation, this change is handled automatically by Sysinstall. For an upgrade where the local configuration information is preserved, the user must make this change manually, by editing /etc/fstab. THIS CHANGE IS EXTREMELY IMPORTANT. If /etc/fstab is not updated manually in this case, the system will issue a warning message whenever / is mounted (normally at startup) indicating the change that must be made. In addition, trouble may be experienced if the root filesystem is not correctly unmounted, whereby the root filesystem will not be marked clean at the next reboot. ---- Note that whilst the procedure for the not-clean problem is reasonably straightforward, this is probably not the place to document it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 23 17:36:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05336 for freebsd-stable-outgoing; Mon, 23 Mar 1998 17:36:28 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05307 for ; Mon, 23 Mar 1998 17:36:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA14665 for ; Mon, 23 Mar 1998 17:33:05 -0800 (PST) Message-Id: <199803240133.RAA14665@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@FreeBSD.ORG Subject: NOTICE - Re: slice changes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 17:33:04 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Apologies for the delay; we have been pursuing a number of technical issues relating to the recent root filesystem mount changes. After taking into consideration the numerous submissions on the topic, the changes stay. That is, the changes relating to the device from which the root filesystem is mounted will _not_ be backed out from -stable. They will be present in the 2.2.6-RELEASE version. The following outstanding issues are worthy of some discussion, as they may affect some users updating from systems predating these changes: - The misleading "changing root filesystem" message has been corrected, as per -current. - Users with _truly_ dedicated SCSI disks (those prepared with "disklabel -auto") should check to ensure that the disk type in their disk label is set correctly. If this is incorrect, boot failure _will_ occur. It is not harmful to change this field on other disks. Determine the disk type by executing "disklabel sdX" where X is the unit number of your boot disk. The 'type:' field is the second line output. This should be 'SCSI' for SCSI disks, and 'ESDI' for IDE disks. If the value is incorrect, it can be edited by executing "disklabel -re sdX". - If the entry for / in /etc/fstab is not updated, and the root filesystem is not unmounted cleanly, fsck can't locate the correct device to clean. This requires the user to clean the correct device manually, and then reboot. There is no working heuristic to get this right without potentially damaging the system. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Mar 23 18:48:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17452 for freebsd-stable-outgoing; Mon, 23 Mar 1998 18:48:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA17443; Mon, 23 Mar 1998 18:48:15 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 23 Mar 1998 21:46:33 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA14262; Mon, 23 Mar 98 21:46:31 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id VAA20458; Mon, 23 Mar 1998 21:46:04 -0500 Message-Id: <19980323214603.15285@ct.picker.com> Date: Mon, 23 Mar 1998 21:46:03 -0500 From: Randall Hopper To: Amancio Hasty , Mark Murray Cc: asami@FreeBSD.ORG, multimedia@FreeBSD.ORG, committers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Amancio Hasty , Mark Murray , asami@FreeBSD.ORG, multimedia@freebsd.org, committers@FreeBSD.ORG, stable@FreeBSD.ORG References: <19980323065624.22389@ct.picker.com> <199803231847.KAA14308@rah.star-gate.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="TB36FDmn/VVEgNH/" X-Mailer: Mutt 0.89.1i In-Reply-To: <199803231847.KAA14308@rah.star-gate.com>; from Amancio Hasty on Mon, Mar 23, 1998 at 10:47:57AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii ... ... Ok. Here are the patches for the discussed method of dealing with the mmap() PROT_WRITE root-only changes recently in -current and -stable as pertains to Fxtv and the bktr driver. As 2.2.6 is the hot topic, these are against stable. Attached is a bktr driver patch (bktr-stable.patch) which adds the trivial BT848[SG]CBUF ioctls, and a replacement "patch-ab" for the Fxtv port. As I don't have 2.2.6-beta installed here, I'd be grateful Mark if you could double-check these, and barring any unexpected problems, commit the changes to -current and -stable. Thanks, Randall --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="bktr-stable.patch" --- sys/i386/include/ioctl_bt848.h-2.2.6-ORIG Mon Mar 23 19:01:02 1998 +++ sys/i386/include/ioctl_bt848.h Mon Mar 23 20:49:52 1998 @@ -193,6 +193,10 @@ #define BT848SFMT _IOW('x', 67, unsigned long ) #define BT848GFMT _IOR('x', 67, unsigned long ) +/* set clear-buffer-on-start */ +#define BT848SCBUF _IOW('x', 68, int) +#define BT848GCBUF _IOR('x', 68, int) + /* Read/Write the BT848's I2C bus directly * b7-b0: data (read/write) * b15-b8: internal peripheral register (write) --- sys/pci/brktree_reg.h-2.2.6-ORIG Mon Mar 23 19:01:02 1998 +++ sys/pci/brktree_reg.h Mon Mar 23 19:42:37 1998 @@ -369,6 +369,7 @@ int alloc_pages; /* number of pages in bigbuf */ struct proc *proc; /* process to receive raised signal */ int signal; /* signal to send to process */ + int clr_on_start; /* clear cap buf on capture start? */ #define METEOR_SIG_MODE_MASK 0xffff0000 #define METEOR_SIG_FIELD_MODE 0x00010000 #define METEOR_SIG_FRAME_MODE 0x00000000 --- sys/pci/brooktree848.c-2.2.6-ORIG Mon Mar 23 19:01:02 1998 +++ sys/pci/brooktree848.c Mon Mar 23 21:25:26 1998 @@ -879,6 +879,7 @@ bt848->int_mask = ALL_INTS_DISABLED; bt848->gpio_dma_ctl = FIFO_RISC_DISABLED; } + bktr->clr_on_start = FALSE; /* defaults for the tuner section of the card */ bktr->tflags = TUNER_INITALIZED; @@ -1731,6 +1732,14 @@ *(u_char *)arg = (u_char)((temp >> 1) & 0xff); break; + case BT848SCBUF: /* set Clear-Buffer-on-start flag */ + bktr->clr_on_start = (*(int *)arg != 0); + break; + + case BT848GCBUF: /* get Clear-Buffer-on-start flag */ + *(int *)arg = (int) bktr->clr_on_start; + break; + case METEORSSIGNAL: if(*(int *)arg == 0 || *(int *)arg >= NSIG) { return( EINVAL ); @@ -3343,6 +3352,13 @@ struct format_params *fp; fp = &format_params[bktr->format_params]; + + /* If requested, clear out capture buf first */ + if (bktr->clr_on_start && (bktr->video.addr == 0)) { + bzero((caddr_t)bktr->bigbuf, + (size_t)bktr->rows * bktr->cols * bktr->frames * + pixfmt_table[ bktr->pixfmt ].public.Bpp); + } bt848 = bktr->base; --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-ab.fxtv" --- ORIG/tvcapture.c Mon Oct 27 23:59:41 1997 +++ tvcapture.c Mon Mar 23 21:29:10 1998 @@ -1126,7 +1126,7 @@ /* Just mmap the biggest buffer we'll need and be done with it. */ /* (Buffer used for non-directvideo captures) */ c->drv_buf = (TV_UINT8 *) mmap( (caddr_t)0, MAX_MMAP_BUF_SIZE, - PROT_READ|PROT_WRITE, 0, c->fd, (off_t)0 ); + PROT_READ, MAP_SHARED, c->fd, (off_t)0 ); if ( c->drv_buf == (TV_UINT8 *) -1 ) { fprintf( stderr, "mmap of driver buffer failed: %s\n", strerror(errno) ); @@ -1474,7 +1474,8 @@ TV_INT32 Bpp, idx; char *cfg_fail_msg; - TV_BOOL audio_mute; + TV_BOOL audio_mute, + flush_buf; DRVPRINTF(( "\tCAPTURE Start %s\n", c->cap_mode == TV_CAPTURE_CONTINUOUS ? "Continuous":"Single")); @@ -1499,6 +1500,7 @@ geom.columns = g.w; geom.rows = g.h; geom.frames = 1; + flush_buf = FALSE; if ( c->xfer_mode == TV_TRANSFER_DIRECT ) { TV_BOOL swap_b, @@ -1536,10 +1538,11 @@ video.banksize = 0, video.ramsize = 0; - /* If TDEC is on, may be a while before old trash gets written on */ + /* If TDEC is on, may be a while before old trash gets written on. */ + /* So tell the driver to flush the frame buffer before starting */ + /* capture. */ if ( c->fps != c->fps_max ) - memset( c->drv_buf, '\0', - g.w * g.h * c->pix_geom_list[ c->pix_geom_idx ].Bpp ); + flush_buf = TRUE; } memcpy( &pix_geom, &c->pix_geom_list[ c->pix_geom_idx ], sizeof( pix_geom ) ); @@ -1564,6 +1567,12 @@ } if ( ioctl( c->fd, METEORSACTPIXFMT, &pix_geom.index ) < 0 ) { DO_IOCTL_SERR( "METEORSACTPIXFMT", &geom ); + return; + } + + larg = flush_buf; + if ( ioctl( c->fd, BT848SCBUF, &larg ) < 0 ) { + DO_IOCTL_SERR( "BT848SCBUF", larg ); return; } --TB36FDmn/VVEgNH/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 19:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25816 for freebsd-stable-outgoing; Mon, 23 Mar 1998 19:40:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25806 for ; Mon, 23 Mar 1998 19:40:02 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from bubble.didi.com (tfx-us4-21.ix.netcom.com [204.30.67.149]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id TAA07338; Mon, 23 Mar 1998 19:40:01 -0800 (PST) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.8) id WAA01358; Mon, 23 Mar 1998 22:39:54 -0500 (EST) (envelope-from asami) Date: Mon, 23 Mar 1998 22:39:54 -0500 (EST) Message-Id: <199803240339.WAA01358@bubble.didi.com> To: jkh@time.cdrom.com CC: stable@FreeBSD.ORG In-reply-to: <26223.890683981@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk * The 2.2.6 release will be going out as scheduled and the tag will be * laid down no later than 1:00AM, 13 hours from now. Hey, you said "Tuesday night late" when I asked you! :< Sorry, but the ports and packages won't be ready until then. Please do not copy them or lay down tags on the ports tree until I say they are ready. I don't have time to fix stuff tonight. By the way, the packages will be in wcarchive's "packages-2.2.6" directory and distfiles in freefall's /e/users/asami/2.2.6R directory. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 19:51:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27857 for freebsd-stable-outgoing; Mon, 23 Mar 1998 19:51:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27851; Mon, 23 Mar 1998 19:51:50 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id TAA20981; Mon, 23 Mar 1998 19:52:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: asami@FreeBSD.ORG (Satoshi Asami) cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Mon, 23 Mar 1998 22:39:54 EST." <199803240339.WAA01358@bubble.didi.com> Date: Mon, 23 Mar 1998 19:52:00 -0800 Message-ID: <20977.890711520@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > * The 2.2.6 release will be going out as scheduled and the tag will be > * laid down no later than 1:00AM, 13 hours from now. > > Hey, you said "Tuesday night late" when I asked you! :< Nope, read my announcement in -stable again; the tag was always scheduled for 1am. If you're referring to ports/packages then, indeed, it's "tuesday night late" just as I indicated in my update ("ports/packages will be grabbed 24 hours after that"). > Sorry, but the ports and packages won't be ready until then. Please > do not copy them or lay down tags on the ports tree until I say they > are ready. I don't have time to fix stuff tonight. Ummmm. Hang on a sec - this tag op has been scheduled for weeks now. I'm sorry, but it's all going down tonite whether the ports tree is ready or not and it's not like you and the ports team haven't had huge amounts of warning. I'm sorry if any misunderstanding led to a belief that the ports tree would somehow be tagged as a separate operation but that was _never_ my intention. In order for the tag to have any meaning, it has to be done at the same time since the ports distribution tarball is built at the same time as the release and the release is being done *tonite*, not tomorrow, *tonite*. :-) Oh well. I wouldn't exactly say that the ports are in bad shape and there are 1181 packages in packages-2.2.6 on wcarchive, so I wouldn't say we're doing too badly there either. You also have another 24 hours or so to do the packaging so that's not an issue, you just can't defer the tagging of ports. That will happen at 1am, ready or not. > By the way, the packages will be in wcarchive's "packages-2.2.6" > directory and distfiles in freefall's /e/users/asami/2.2.6R directory. Got it, thanks. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 19:58:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29597 for freebsd-stable-outgoing; Mon, 23 Mar 1998 19:58:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29532; Mon, 23 Mar 1998 19:57:56 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from bubble.didi.com (tfx-us4-21.ix.netcom.com [204.30.67.149]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id TAA07366; Mon, 23 Mar 1998 19:57:55 -0800 (PST) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.8) id WAA01426; Mon, 23 Mar 1998 22:57:43 -0500 (EST) (envelope-from asami) Date: Mon, 23 Mar 1998 22:57:43 -0500 (EST) Message-Id: <199803240357.WAA01426@bubble.didi.com> To: jkh@time.cdrom.com CC: stable@FreeBSD.ORG, obrien@FreeBSD.ORG In-reply-to: <20977.890711520@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk * Nope, read my announcement in -stable again; the tag was always * scheduled for 1am. If you're referring to ports/packages then, This is what you said when I asked last week for definite confirmation of the schedule. ;) === From: "Jordan K. Hubbard" I expect to be putting the tag down on Tuesday night late. > I'm currently building the 2.2.6R packages now. Jordan, what's the > exact timeline for the release? (Down to the hours please, I'm > leaving tomorrow morning at 9am.) > > Satoshi === Oh well. The only outstanding issue as far as the ports *tree* is concerned is the misc/plan breakage. I really need to do some other things for the conference starting tomorrow and I also am dead sleepy, but I'll see if I can fix that. I haven't run a md5 check on distfiles and packages yet, but those can wait until tomorrow, right? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 20:17:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04518 for freebsd-stable-outgoing; Mon, 23 Mar 1998 20:17:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04504; Mon, 23 Mar 1998 20:17:44 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA21140; Mon, 23 Mar 1998 20:17:55 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: asami@FreeBSD.ORG (Satoshi Asami) cc: stable@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-reply-to: Your message of "Mon, 23 Mar 1998 22:57:43 EST." <199803240357.WAA01426@bubble.didi.com> Date: Mon, 23 Mar 1998 20:17:55 -0800 Message-ID: <21136.890713075@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > * Nope, read my announcement in -stable again; the tag was always > * scheduled for 1am. If you're referring to ports/packages then, > > This is what you said when I asked last week for definite > confirmation of the schedule. ;) > > === > From: "Jordan K. Hubbard" > > I expect to be putting the tag down on Tuesday night late. Sorry, I was thinking "monday night late / tuesday early" (depending on whether you're a stickler for the day transition at midnight) and what came out was a mixup between the two. I had to check my own original email to see what my announced deadline was (1am) and then went by that when I sent my last "heads up". My apologies for the confusion. In any case, I've cancelled appointments scheduled for tonite and have conflicting engagements tomorrow, so we really should do it at the scheduled time. > Oh well. The only outstanding issue as far as the ports *tree* is > concerned is the misc/plan breakage. I really need to do some other > things for the conference starting tomorrow and I also am dead sleepy, > but I'll see if I can fix that. OK, sounds like we can go forward with the release as planned then. Thanks. > I haven't run a md5 check on distfiles and packages yet, but those can > wait until tomorrow, right? Right - we won't actually have all the bits FTP'd over until then anyway. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 20:44:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08788 for freebsd-stable-outgoing; Mon, 23 Mar 1998 20:44:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08745 for ; Mon, 23 Mar 1998 20:44:14 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA10482; Tue, 24 Mar 1998 15:13:31 +1030 (CST) Message-Id: <199803240443.PAA10482@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cy Schubert - ITSD Open Systems Group cc: "Daniel O'Callaghan" , gkshenaut@ucdavis.edu, stable@FreeBSD.ORG Subject: Re: after the release ... In-reply-to: Your message of "Mon, 23 Mar 1998 11:41:25 -0800." <199803231942.LAA07832@passer.osg.gov.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Mar 1998 15:13:31 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > reported, and the user has the option of forcing the patch in, based on > the original binary kept in backup, or aborting the patch. If the user > forces the patch in, it would be up to the user to re-apply any user > modifications. > If on the other hand the user modification is not in the database, any > user modification cannot be identified and the patch will need to be > aborted. Then it's up to the user to figure out what went wrong. This sounds like a good approach.. OK so who is going to code it? :) --------------------------------------------------------------------- |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 Mon Mar 23 20:59:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11507 for freebsd-stable-outgoing; Mon, 23 Mar 1998 20:59:15 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11498 for ; Mon, 23 Mar 1998 20:59:04 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id PAA10623; Tue, 24 Mar 1998 15:28:36 +1030 (CST) Message-Id: <199803240458.PAA10623@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Studded , FreeBSD-Stable@FreeBSD.ORG Subject: Re: Important questions regarding the new slice code In-reply-to: Your message of "Mon, 23 Mar 1998 15:51:46 -0800." <27531.890697106@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Mar 1998 15:28:36 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > not, what are the possible repercussions? > It will update the kernel in that it will splat the new GENERIC one > right on top. If the user had heavily customized it, there will > of course be repercussions. Ahh, but if they have a custom kernel, then by iplication they have access to the source and are capable of compiling it (yes I know they could have got their clued up friends to do it, but sheesh..). So the kernel patches would be a source level patch. So this case reduces to the source patch one (ie issues regarding customised files etc) --------------------------------------------------------------------- |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 Mon Mar 23 21:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12705 for freebsd-stable-outgoing; Mon, 23 Mar 1998 21:03:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from proxyb1.san.rr.com (proxyb1-atm.san.rr.com [204.210.0.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12695; Mon, 23 Mar 1998 21:03:24 -0800 (PST) (envelope-from Studded@dal.net) Received: from dt050n33.san.rr.com (dt050n33.san.rr.com [204.210.31.51]) by proxyb1.san.rr.com (8.8.7/8.8.8) with SMTP id VAA24588; Mon, 23 Mar 1998 21:02:49 -0800 (PST) Message-Id: <199803240502.VAA24588@proxyb1.san.rr.com> From: "Studded" To: "jkh@freebsd.org" Cc: "freebsd-doc@freebsd.org" , "FreeBSD Stable List" Date: Mon, 23 Mar 98 21:02:46 -0800 Reply-To: "Studded" X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: New FOO.TXT docs available for review Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I'm done with what I think is a pretty good draft of the various FOO.TXT documents for the root directory of the CD. Basically what I did was edit the exisiting information. I put it in a more consistent format (and reformatted a bit to make printing in DOS easier) and reorganized the files with all similar information in the same file. No information from the original files was omitted, however numerous small typos and inaccuracies were corrected. I've put them up at http://home.san.rr.com/freebsd. The are available now by typing in the names of the files (below). In a few minutes I'll have an html interface available at http://home.san.rr.com/freebsd/readme.html. You need to type the filenames in lower case. I can send the whole package tgz'ed if desired. Please direct any feedback to -stable. I'll be on tonight and I can make changes as desired. Enjoy, Doug ROAD MAP: README.TXT This file ABOUT.TXT All about FreeBSD, including contact information RELNOTES.TXT Release Notes - what's new & different in this release OVERVIEW.TXT Information about the layout of the release directory. If you are installing from floppies, it is especially important that you *read this section!* HARDWARE.TXT Information about the configuration of the GENERIC kernel and supported hardware IMPORTNT.TXT Important information you should read before doing an upgrade or new installation INSTALL.TXT How to make a new installation of FreeBSD on your PC using the data you see here UPGRADE.TXT How to upgrade your existing FreeBSD installation TROUBLE.TXT Troubleshooting information *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 4,710 clients and still growing. :-) *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) *** Part of the DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 21:09:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13783 for freebsd-stable-outgoing; Mon, 23 Mar 1998 21:09:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from portwwwbus.tc.cc.va.us (portwwwbus.tc.cc.va.us [164.106.211.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13775 for ; Mon, 23 Mar 1998 21:09:21 -0800 (PST) (envelope-from djflow@portwwwbus.tc.cc.va.us) Received: from localhost (djflow@localhost) by portwwwbus.tc.cc.va.us (8.8.5/8.8.5) with SMTP id AAA14534; Tue, 24 Mar 1998 00:08:41 -0500 (EST) Date: Tue, 24 Mar 1998 00:08:40 -0500 (EST) From: Derek Flowers To: Wes Peters - Softweyr LLC cc: software@kew.com, stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. In-Reply-To: <199803232209.PAA27779@xmission.xmission.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 Mar 1998, Wes Peters - Softweyr LLC wrote: > Derek Flowers asked: > > I've done some quick and dirty work on binary package updates and would > > like some comments on what I've got going, where to go in the future, etc. > > Thanks for diving right in. I've been reading this thread, and have > tried to summarize the current state of questions, comments and > concerns thusly: > > So far, it seems we have the following points to ponder in our > thumbnail design. I've interspersed my comments on each point, you > may feel free to agree, disagree, or ignore them; this is a > *discussion*. ;^) > > o Are patches designed to just fix problems, to add features, or > what? > > Both. Past experience in -stable branches has shown that there are > periods of activity when one of our developers fixes a bug or updates > a subsystem, followed by periods of inactivity. I propose that > patches be created to update systems to "snapshots" of the -stable > tree that roughly reflect these periods of relative inactivity. For > instance, when a security bug is noticed, there is generally quite a > bit of discussion, and one to several commits on the -stable tree > related to fixing the bug. When consensus has been reached that the > bug is closed and the system stable, the activity dies down. At that > time it would be appropriate to create an UPDATE that fixes this > problem. > > The same cycle tends to apply to an update of a system utility, > i.e. the recent fix for disk slice names. > > Updating to known (and perhaps CVS-labelled) sync points on the > FreeBSD stable tree also makes it somewhat easier to report problems, > since what you end up with is a system equivalent to a known point on > the -stable tree. > > This means each UPDATE would require *every* previous UPDATE as a > pre-requisite. This may be a major flaw in this approach, but it does > simplify the design considerably. To make it simplistic as possible, we could just diff 2.2-SNAPxxxx and 2.2-SNAPxxxx-1. The result is the daily changes for the -stable branch. We could also diff 2.2.SNAPxxxx and 2.2.X-RELEASE getting all the changes since the RELEASE was tagged. > o Are we patching (or replacing) executables, the kernel, source > code, or what? > > All of the above, with limitations. Ideally, we'll be able to detect > what you have installed on your system and update those parts. > > We'll need to update, at a minimum: > > - Binary executables > - Man page sources No problem. > - Kernel object files > - Files, devices, etc., in the kernel source tree > - GENERIC and LINT kernel configurations Aren't the kernel object files located in the kernel sources? At this point, someone should just CVSup the kernel sources and make a new kernel. Since kernels are custom built, updating them in place is next to impossible. I'm not for changing anything in the kernel with patches right now. Maybe we can work on creating kernel updates that contain not only the sources but the object files necessay to build them. Even with this method, user intervention is necessary to configure and compile the kernel. > - /kernel.GENERIC > - system configuration files in /etc, etc. (pun intended) Again, no problem. > Obviously, if anything inside the kernel is modified, the user should > be encouraged to review their kernel configuration against the new > GENERIC and LINT and rebuild their kernel. > o Who is going to make these patches? > > As with all other FreeBSD jobs, whoever volunteers. Ideally, this > would be SEVERAL someones who use FreeBSD-stable in their daily work > and really need this feature. If they're willing to commit the > updates to their systems, the updates are probably in good hands. If we stick to doing snapshots, this can be an automated process done at the same time the SNAPxxxxxx snapshots are rolled out. > o Where do we save the files we are replacing, so we can back out the > patch? > > In the same place pkg_add already puts this kind of information? I > don't know, this is a good question. I'd like to see all of the > replacements for a particular update stored in a gzipped tarball to > save space and inodes, personally. Maybe something like /var/updates? Wherever they go, there needs to be plenty of room. > o How do we authenticate the packages so we can be sure we're not > installing the new FreeBSD kernel virus from Chaos? > > The JAR signing mechanism mentioned by Eivind sounds like a great > methodology, if package users are not required to install the JDK. If > packages creators have to install the JDK in order to build the > signature, that should be acceptable. Not too familiar with the JAR signing mechanism, but we need to be careful of ITAR regulations. I believe GNU is doing some work on a PGP work-alike that is available outside the U.S., it may be useful here. > o Should we use binary diffs? (What are binary diffs?) > > Binary diffs mean that we could send out just the bytes in any changed > file, rather than the whole file. For many updates, where you are > changing only a few small features in a large binary, the diff could > be quite a bit smaller. > > This is a cool idea, and would save users a lot of download time in > the future. On the other hand, binary diff utilities are non-trivial > to create. I'd say if we can find binary diff and patch utilities to > add to the system, use them, but it's not worth delaying the > implementation to wait for this feature. We can always add it in the > future, as an update. ;^) > > o What do we do if the user has modified some source on their system? > (Either kernel or userland source.) > > Politely explain to them we designed this tool for binary-only systems > that don't have source installed, and invite them to use CVSup and > 'make world.' > > Seriously, handling kernel (or userland) patches to the source tree is > a little beyond the scope of this utility. For users with large > numbers of systems, ideally we provide them the facility to make their > own updates, where they can CVSup on their 'configuration' machine and > make updates to push out to their remote binary-only machines. These > local updates would, of course, include their local changes. > > o What about a GUI for this? > > As I said before, write a little Tk program with an 'update' button > that goes to the stable ftp server, figures out what the highest > update available is, and passes it to pkg_add. Any prerequisites not > installed locally will be automagically brought over and installed by > pkg_add. > > Maybe we can write a simple 'current update level' server running on > port 244, which reports the highest update level posted as an unsigned > 16-bit number for each connection, and run it on the server. > > JMB recommends calling this tool 'DAS', for the class of user it is > intended for. Being acronymically enabled, I'll vote for 'Do Update > Maintenance Bull****', or 'dumb' for short. Gee, with a little more > thought, I could probably even come up with an acronym for > 'dummy-up'. ;^) Real Men (T) don't know the meaning of the word ``GUI''. Unfortunately, my skills at XWindows interface programming are naught. At it's simplest, it could fetch a list of all current updates and allow the user to choose to install those not already on the system. > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://www.xmission.com/~softweyr softweyr@xmission.com I finally got my testbed machine up and have applied the distribution packages. Any comments on what I should look for while testing? ---------------------------------------- Derek Flowers djflow@erols.com http://portwwwbus.tc.cc.va.us/~djflow "640K ought to be enough for anybody." -Bill Gates, circa 1981 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 21:16:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15666 for freebsd-stable-outgoing; Mon, 23 Mar 1998 21:16:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.2.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15595 for ; Mon, 23 Mar 1998 21:16:07 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id VAA03682 for stable@freebsd.org; Mon, 23 Mar 1998 21:38:49 -0700 (MST) From: "Chad R. Larson" Message-Id: <199803240438.VAA03682@freebie.dcfinc.com> Subject: traffic To: stable@FreeBSD.ORG Date: Mon, 23 Mar 1998 21:38:49 -0700 (MST) Reply-to: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Jeez, and to think that only a couple of weeks ago folks were wondering if this list was still active... -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-953-1392 chad@dcfinc.com chad@anasazi.com larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 21:24:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18443 for freebsd-stable-outgoing; Mon, 23 Mar 1998 21:24:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18370; Mon, 23 Mar 1998 21:23:47 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from bubble.didi.com (tfx-us3-06.ix.netcom.com [204.30.67.102]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id VAA07471; Mon, 23 Mar 1998 21:23:44 -0800 (PST) Received: (from asami@localhost) by bubble.didi.com (8.8.7/8.8.8) id AAA01759; Tue, 24 Mar 1998 00:23:36 -0500 (EST) (envelope-from asami) Date: Tue, 24 Mar 1998 00:23:36 -0500 (EST) Message-Id: <199803240523.AAA01759@bubble.didi.com> To: jkh@time.cdrom.com CC: stable@FreeBSD.ORG, obrien@FreeBSD.ORG In-reply-to: <21136.890713075@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk * > I expect to be putting the tag down on Tuesday night late. * * Sorry, I was thinking "monday night late / tuesday early" (depending * on whether you're a stickler for the day transition at midnight) and * what came out was a mixup between the two. I had to check my own ;) * original email to see what my announced deadline was (1am) and then * went by that when I sent my last "heads up". My apologies for the * confusion. Apology accepted. Just an hour or so of lost sleep for me, so no big deal. * OK, sounds like we can go forward with the release as planned then. * Thanks. Yes. I just committed the INDEX file, so the ports tree should be ready. Please lay down the RELEASE_2_2_6 tag on the tree when you tag the src tree too. * Right - we won't actually have all the bits FTP'd over until then * anyway. Ok. I'll let you know when the distfiles and packages are ready. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 22:20:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26197 for freebsd-stable-outgoing; Mon, 23 Mar 1998 22:20:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26009; Mon, 23 Mar 1998 22:19:55 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (tiMFBJHmB+chHm1Qo9UpYtK/CgnjWFBG@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id IAA20305; Tue, 24 Mar 1998 08:19:27 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (+K5lPAwY2PzOOdd/+8EFcVXCWOXYeWef@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA03871; Tue, 24 Mar 1998 08:19:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199803240619.IAA03871@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper cc: Amancio Hasty , asami@FreeBSD.ORG, multimedia@FreeBSD.ORG, committers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Mar 1998 08:18:40 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Randall Hopper wrote: > As I don't have 2.2.6-beta installed here, I'd be grateful Mark if you > could double-check these, and barring any unexpected problems, commit the > changes to -current and -stable. They look good, but we missed the window :-(. I'll commit it all once the various freezes are lifted. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 22:26:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27577 for freebsd-stable-outgoing; Mon, 23 Mar 1998 22:26:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27505; Mon, 23 Mar 1998 22:25:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA27693; Mon, 23 Mar 1998 22:25:31 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803240625.WAA27693@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: Randall Hopper , asami@FreeBSD.ORG, multimedia@FreeBSD.ORG, committers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable In-reply-to: Your message of "Tue, 24 Mar 1998 08:18:40 +0200." <199803240619.IAA03871@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 22:25:31 -0800 From: Amancio Hasty Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Just talk to Jordan and Asami in private. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 22:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00655 for freebsd-stable-outgoing; Mon, 23 Mar 1998 22:40:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00605 for ; Mon, 23 Mar 1998 22:40:53 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id WAA01662; Mon, 23 Mar 1998 22:40:43 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3517556A.55EF2B68@dal.net> Date: Mon, 23 Mar 1998 22:40:42 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0316 i386) MIME-Version: 1.0 To: Greg Lehey CC: freebsd-stable@FreeBSD.ORG Subject: Re: The Complete FreeBSD p.237 References: <199803232203.PAA29082@spot.zyx.net> <19980324103802.22923@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Greg Lehey wrote: > The background to this was that the book was published after the 2.2.5 > CD-ROM, and we didn't want to stick to the location that had > (accidentally) been chosen on the 2.2.5 CD-ROM because it was > inconvenient. This actually leads me to a question I meant to ask previously. Is the 2.2.6 CD going to be bent to fit the book? I think this would greatly reduce the number of -questions posts about it. We've seen a lot of them already and I think a lot of people are doing the same thing I am, namely waiting for 2.2.6 to get the package deal (sorry Greg, if I could afford to pay full price I would). Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 23 23:47:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11940 for freebsd-stable-outgoing; Mon, 23 Mar 1998 23:47:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from link.cpt.nsc.iafrica.com (ikgnobjrOmPQnlWfXjhqB7CYwFVl+mlE@link.cpt.nsc.iafrica.com [196.31.1.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11930 for ; Mon, 23 Mar 1998 23:47:32 -0800 (PST) (envelope-from khetan@link.freebsd.os.org.za) Received: from localhost (khetan@localhost) by link.cpt.nsc.iafrica.com (8.8.8+3.0Wbeta13/8.8.8) with SMTP id JAA16127; Tue, 24 Mar 1998 09:47:25 +0200 (SAT) Date: Tue, 24 Mar 1998 09:47:25 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@link.cpt.nsc.iafrica.com Reply-To: Khetan Gajjar To: Mark Murray cc: stable@FreeBSD.ORG Subject: Re: Reminder: 2.2.6-RELEASE tag going down at 0100 PST, 98/03/24 In-Reply-To: <199803232256.AAA02023@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 24 Mar 1998, Mark Murray wrote: >> I've tried, and haven't been successful. > >Khetan, see me at work tomorrow. Dont't bug the list. I've seen two complaints in comp.os.misc.bsd.freebsd, and no-one has come back and said that they've managed to build it under 2.2.6 I'll come and see you some time this week. --- Khetan Gajjar (!kg1779) khetan@iafrica.com (w); khetan@os.org.za (h) http://www.os.org.za/~khetan | Finger: khetan@chain.freebsd.os.org.za UUNET Internet Africa Support | FreeBSD enthusiast-www2.za.freebsd.org A computer without Microsoft and Intel is like chocolate cake without tomato sauce and mustard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 00:00:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13757 for freebsd-stable-outgoing; Tue, 24 Mar 1998 00:00:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13735; Tue, 24 Mar 1998 00:00:42 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id AAA02114; Tue, 24 Mar 1998 00:00:43 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3517682B.E65AFD3@dal.net> Date: Tue, 24 Mar 1998 00:00:43 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0316 i386) MIME-Version: 1.0 To: "jkh@freebsd.org" , FreeBSD Stable List Subject: Re: New FOO.TXT docs available for review References: <199803240502.VAA24588@proxyb1.san.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Studded wrote: > > I'm done with what I think is a pretty good draft of the various > FOO.TXT documents for the root directory of the CD. Ok, I'm done with the final nitpicking. I added a couple paragraphs, did a spelling and consistency check and I think it's in pretty good shape. :) > Basically what I did > was edit the exisiting information. I put it in a more consistent format > (and reformatted a bit to make printing in DOS easier) and reorganized the > files with all similar information in the same file. No information from > the original files was omitted, however numerous small typos and > inaccuracies were corrected. I have an html interface available at http://home.san.rr.com/freebsd/readme.html. If you've looked at them already tonight please reload each file as I've fixed some nits in all of them since I announced them being available earlier. I can send the whole package tgz'ed if desired. > Please direct any feedback to -stable. I'll be on tonight and I > can make changes as desired. Enjoy, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 00:02:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14057 for freebsd-stable-outgoing; Tue, 24 Mar 1998 00:02:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14043 for ; Tue, 24 Mar 1998 00:02:09 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id SAA20303; Tue, 24 Mar 1998 18:32:06 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id SAA19353; Tue, 24 Mar 1998 18:32:05 +1030 (CST) (envelope-from grog) Message-ID: <19980324183205.54110@freebie.lemis.com> Date: Tue, 24 Mar 1998 18:32:05 +1030 From: Greg Lehey To: Studded Cc: freebsd-stable@FreeBSD.ORG Subject: Re: The Complete FreeBSD p.237 References: <19980324103802.22923@freebie.lemis.com> <3517556A.55EF2B68@dal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <3517556A.55EF2B68@dal.net>; from Studded on Mon, Mar 23, 1998 at 10:40:42PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, 23 March 1998 at 22:40:42 -0800, Studded wrote: > Greg Lehey wrote: > >> The background to this was that the book was published after the 2.2.5 >> CD-ROM, and we didn't want to stick to the location that had >> (accidentally) been chosen on the 2.2.5 CD-ROM because it was >> inconvenient. > > This actually leads me to a question I meant to ask previously. Is the > 2.2.6 CD going to be bent to fit the book? Yes. If we had intended to leave things the way they were in the 2.2.5 CD-ROM, we could have changed the book to fit the CD-ROM. The problem is that everything was on /xperiment in a single tar.gz file, not what we want to confront new users with. > I think this would greatly reduce the number of -questions posts > about it. We've seen a lot of them already and I think a lot of > people are doing the same thing I am, namely waiting for 2.2.6 to > get the package deal (sorry Greg, if I could afford to pay full > price I would). No worries. If I had to pay, I'd do the same thing. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 00:18:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17886 for freebsd-stable-outgoing; Tue, 24 Mar 1998 00:18:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17876 for ; Tue, 24 Mar 1998 00:18:14 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.8.5/8.8.5) id TAA07397; Tue, 24 Mar 1998 19:17:49 +1100 (EST) Message-ID: <19980324191745.31039@welearn.com.au> Date: Tue, 24 Mar 1998 19:17:45 +1100 From: Sue Blake To: Studded Cc: FreeBSD Stable List Subject: Re: New FOO.TXT docs available for review References: <199803240502.VAA24588@proxyb1.san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199803240502.VAA24588@proxyb1.san.rr.com>; from Studded on Mon, Mar 23, 1998 at 09:02:46PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Call me slow... This one's still there on reload (?) but it's not too important. RELNOTES.TXT Typo: There's an i missing, third dot point, third line driver) but t does have much better support for PNP sound driver) but it does have much better support for PNP sound I was also going to suggest listing IMPORTNT.TXT first, but it probably wouldn't help :-( -- Regards, -*Sue*- find / -name "*.conf" |more To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 00:57:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23224 for freebsd-stable-outgoing; Tue, 24 Mar 1998 00:57:45 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from proxyb2.san.rr.com (proxyb2-atm.san.rr.com [204.210.0.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23213 for ; Tue, 24 Mar 1998 00:57:41 -0800 (PST) (envelope-from Studded@dal.net) Received: from dt050n33.san.rr.com (dt050n33.san.rr.com [204.210.31.51]) by proxyb2.san.rr.com (8.8.7/8.8.8) with SMTP id AAA19226; Tue, 24 Mar 1998 00:56:33 -0800 (PST) Message-Id: <199803240856.AAA19226@proxyb2.san.rr.com> From: "Studded" To: "Sue Blake" Cc: "FreeBSD Stable List" Date: Tue, 24 Mar 98 00:56:29 -0800 Reply-To: "Studded" X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: New FOO.TXT docs available for review Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 24 Mar 1998 19:17:45 +1100, Sue Blake wrote: > >Call me slow... >This one's still there on reload (?) but it's not too important. > >RELNOTES.TXT >Typo: There's an i missing, third dot point, third line > driver) but t does have much better support for PNP sound > driver) but it does have much better support for PNP sound OK, found and fixed, thanks. FWIW, I also "DOS-ified" all of the files since my last post. That is I loaded and saved them in windows notepad to avoid formatting problems. Doug *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 4,710 clients and still growing. :-) *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) *** Part of the DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 01:28:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28091 for freebsd-stable-outgoing; Tue, 24 Mar 1998 01:28:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28084 for ; Tue, 24 Mar 1998 01:28:19 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id EAA02416; Tue, 24 Mar 1998 04:29:04 -0500 (EST) (envelope-from mark) Message-ID: <19980324042904.59941@vmunix.com> Date: Tue, 24 Mar 1998 04:29:04 -0500 From: Mark Mayo To: Studded Cc: stable@FreeBSD.ORG Subject: Re: New FOO.TXT docs available for review References: <199803240502.VAA24588@proxyb1.san.rr.com> <3517682B.E65AFD3@dal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <3517682B.E65AFD3@dal.net>; from Studded on Tue, Mar 24, 1998 at 12:00:43AM -0800 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, Mar 24, 1998 at 12:00:43AM -0800, Studded wrote: > Studded wrote: > > > > I'm done with what I think is a pretty good draft of the various > > FOO.TXT documents for the root directory of the CD. > > Ok, I'm done with the final nitpicking. I added a couple paragraphs, > did a spelling and consistency check and I think it's in pretty good > shape. :) > > Please direct any feedback to -stable. I'll be on tonight and I > > can make changes as desired. Looks good to me! :) Actually, here's a question for ya.. will the slice changes affect me if I have additional (i.e. non boot) disks using "compatible" slices? For example: Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd0a 98462 28236 62350 31% / /dev/sd0s1f 2723846 2438626 67314 97% /usr /dev/sd0s1e 892286 41284 779620 5% /var /dev/sd1c 8217434 4721042 2838998 62% /d2 /dev/sd2c 4286692 530430 3413328 13% /d3 Obviously I'll need to update my fstab entry for '/', but how about for /d2 and /d3 ?? I think the answer to this question might be appropriate material for IMPORTNT.TXT :-) At least, it's non-obvious to me, and therefore might not be obvious to others... -Mark > > Enjoy, > > Doug > > -- > *** Chief Operations Officer, DALnet IRC network *** > *** Proud operator, designer and maintainer of the world's largest > *** Internet Relay Chat server. 5,328 clients and still growing. > *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 02:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04082 for freebsd-stable-outgoing; Tue, 24 Mar 1998 02:13:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04073; Tue, 24 Mar 1998 02:12:59 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id CAA23062; Tue, 24 Mar 1998 02:13:09 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: "Studded" cc: "jkh@freebsd.org" , "freebsd-doc@freebsd.org" , "FreeBSD Stable List" Subject: Re: New FOO.TXT docs available for review In-reply-to: Your message of "Mon, 23 Mar 1998 21:02:46 PST." <199803240502.VAA24588@proxyb1.san.rr.com> Date: Tue, 24 Mar 1998 02:13:07 -0800 Message-ID: <23058.890734387@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I'm done with what I think is a pretty good draft of the various > FOO.TXT documents for the root directory of the CD. Basically what I did Thanks! I've grabbed these and, after exercising just a bit of editorial license, committed them. Mike Smith also rewrote the upgrade section from scratch & I created a seed ERRATA to start with this time. I think what we have there now looks a lot better. Thanks again! Better late than never in this instance. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 03:42:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14357 for freebsd-stable-outgoing; Tue, 24 Mar 1998 03:42:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14351; Tue, 24 Mar 1998 03:42:02 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id DAA14056; Tue, 24 Mar 1998 03:42:03 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <35179C0A.C1E9E93A@dal.net> Date: Tue, 24 Mar 1998 03:42:02 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0316 i386) MIME-Version: 1.0 To: "jkh@freebsd.org" CC: FreeBSD Stable List Subject: Re: New FOO.TXT docs available for review References: <23058.890734387@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Jordan K. Hubbard wrote: > > > I'm done with what I think is a pretty good draft of the various > > FOO.TXT documents for the root directory of the CD. Basically what I did > > Thanks! I've grabbed these and, after exercising just a bit of > editorial license, committed them. *Nod nod* I figured you'd want to touch them up a bit. The changes look good. > Mike Smith also rewrote the upgrade section from scratch Yes, he did a lot more with it than I could have. I have never used sysinstall to upgrade. His stuff looks great, thanks Mike. :) There was one question directed to me already (and I think cc'ed to the list) namely what happens if you have more than just the root slice labeled in fstab with compatibility mode. Here's the example: Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd0a 98462 28236 62350 31% / /dev/sd0s1f 2723846 2438626 67314 97% /usr /dev/sd0s1e 892286 41284 779620 5% /var /dev/sd1c 8217434 4721042 2838998 62% /d2 /dev/sd2c 4286692 530430 3413328 13% /d3 I couldn't even hazard a guess, so I'll leave this to y'all. :) > & I created a seed ERRATA to start with this time. *Nod* I thought about that quite a bit, whether it was better to reinforce the habit of looking at ERRATA.TXT as the one and only place for info. I think Mike solved the immediate problem of the new slice stuff well with his upgrade doc. > I think what we have there now looks a lot better. Thanks again! You're welcome. :) Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 07:59:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13298 for freebsd-stable-outgoing; Tue, 24 Mar 1998 07:59:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13285 for ; Tue, 24 Mar 1998 07:59:17 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id PAA24018; Tue, 24 Mar 1998 15:58:48 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id QAA00505; Tue, 24 Mar 1998 16:58:46 +0100 (MET) Message-ID: <19980324165846.10465@follo.net> Date: Tue, 24 Mar 1998 16:58:46 +0100 From: Eivind Eklund To: Derek Flowers , Wes Peters - Softweyr LLC Cc: software@kew.com, stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. References: <199803232209.PAA27779@xmission.xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Derek Flowers on Tue, Mar 24, 1998 at 12:08:40AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, Mar 24, 1998 at 12:08:40AM -0500, Derek Flowers wrote: > > o How do we authenticate the packages so we can be sure we're not > > installing the new FreeBSD kernel virus from Chaos? > > > > The JAR signing mechanism mentioned by Eivind sounds like a great > > methodology, if package users are not required to install the JDK. If > > packages creators have to install the JDK in order to build the > > signature, that should be acceptable. > > Not too familiar with the JAR signing mechanism, but we need to be careful > of ITAR regulations. I believe GNU is doing some work on a PGP work-alike > that is available outside the U.S., it may be useful here. The JAR manifests do not force a particular signing methodology. The standard mention PGP, x509 and DSS (aka DSA) as viable signing methods. The standard determine how checksums etc should stored, to allow multiple signing methods, multiple signatures on a single package, packages that are partially signed, and packages that have different parts signed by different parties. It looks very nice, though there are some loose details in the spec. E.g - it talks about MD5ing entries in a text file, but it does not talk about how to decide what is the start and end of an entry. References: http://www.javasoft.com/products/jdk/1.2/docs/guide/jar/manifest.html http://java.sun.com:81/security/usingJavakey.html My intention is to use libeay (aka libcrypto) to verify the signatures; it have taken care of the export restrictions. Using it would mean packages would have their signatures checked if it was installed, and would emit large warnings if it wasn't installed. This should of course be dynmaically linked, the same way libalias is with IIJ-PPP. It should also be possible to use libcrypto to verify PGP signatures; if I've understood correctly, PGP can link against it to get hold of all crypto bits, making it possible to export a crypto-free PGP. A neat addition would be to use libcrypto if installed, with a fallback to PGP, with a fallback to no verification. This would use the best signing possible WRT the normally installed tools. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 08:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18668 for freebsd-stable-outgoing; Tue, 24 Mar 1998 08:43:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from the.oneinsane.net (root@link2.oneinsane.net [207.113.133.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18641 for ; Tue, 24 Mar 1998 08:42:57 -0800 (PST) (envelope-from insane@oneinsane.net) Received: from killa.oneinsane.net (killa.oneinsane.net [207.113.133.242]) Message-Id: <3.0.5.32.19980324084128.038fb3d0@the.oneinsane.net> X-Sender: insane@the.oneinsane.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 24 Mar 1998 08:41:28 -0800 To: stable@FreeBSD.ORG From: Ron Rosson Subject: Re: traffic In-Reply-To: <199803240438.VAA03682@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Looks like good things never die the y just slow down till there time comes and then they perform flawlessly. (Like FreeBSD) Ron At 09:38 PM 3/23/98 -0700, Chad R. Larson wrote: >Jeez, and to think that only a couple of weeks ago folks were wondering >if this list was still active... > > -crl >-- >Chad R. Larson (CRL22) Brother, can you paradigm? >602-953-1392 chad@dcfinc.com chad@anasazi.com larson1@home.com >DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > -------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void -------------------------------------------------------- It's so nice to be insane, nobody asks you to explain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 14:27:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10936 for freebsd-stable-outgoing; Tue, 24 Mar 1998 14:27:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mx.infotrans.or.jp (root@bardman.infotrans.or.jp [203.179.55.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10805 for ; Tue, 24 Mar 1998 14:27:04 -0800 (PST) (envelope-from moroq@infotrans.or.jp) Received: from infotrans.or.jp (dialup043.infotrans.or.jp [203.179.55.172]) by mx.infotrans.or.jp (8.8.7/3.5Wpl7-bardman.infotrans) with ESMTP id HAA27489 for ; Wed, 25 Mar 1998 07:26:52 +0900 (JST) Message-ID: <351832C4.25630EFA@infotrans.or.jp> Date: Wed, 25 Mar 1998 07:25:08 +0900 From: "=?iso-2022-jp?B?GyRCJGIkbSNRGyhC?=" X-Mailer: Mozilla 4.03 [ja] (Win95; I) MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: unsubscribe Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk unsubscribe end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 14:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13664 for freebsd-stable-outgoing; Tue, 24 Mar 1998 14:46:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13644 for ; Tue, 24 Mar 1998 14:46:30 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA03700 for ; Tue, 24 Mar 1998 14:46:43 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: stable@FreeBSD.ORG Subject: Code freeze status in 2.2-stable branch is now ended. Date: Tue, 24 Mar 1998 14:46:41 -0800 Message-ID: <3696.890779601@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk This currently applies ONLY to the src tree. The ports are not finished tagging yet nor has Satoshi given his go-ahead to lift the ports freeze, so please don't take this as a notice that the ports freeze is lifted too - it's not. 2.2.6 is on schedule and should be rolling off the release machine and onto the FTP site sometime in the next 12 hours, depending on how fast things build and transfer. Please try to wait for my release announcement before jumping on ftp.freebsd.org since I'll also try and give the mirrors a chance to catch up before sending the announcement out - this is for your own good, trust me! :-) Thanks! Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 19:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21114 for freebsd-stable-outgoing; Tue, 24 Mar 1998 19:17:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21073; Tue, 24 Mar 1998 19:16:35 -0800 (PST) (envelope-from hetzels@mail.westbend.net) From: hetzels@mail.westbend.net Received: (from hetzels@localhost) by mail.westbend.net (8.8.8/8.8.8) id VAA18367; Tue, 24 Mar 1998 21:16:36 -0600 (CST) (envelope-from hetzels) Date: Tue, 24 Mar 1998 21:16:36 -0600 (CST) Message-Id: <199803250316.VAA18367@mail.westbend.net> To: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Links not re-created in MAKEDEV Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I have seen a problem with MAKEDEV for a while on both current and stable systems, in that it will not re-create links for these devices: fd0a-h, rfd0a-h, fd1a-h, rfd1a-h, ft0a, rft0a, rst0, nrst0, erst0 The error I see is: ln: {device}: file exists The following patch corrects the problem for both current and stable MAKDEV files: *** MAKEDEV.orig Thu Mar 5 08:49:36 1998 --- MAKEDEV Tue Mar 24 20:42:37 1998 *************** *** 342,409 **** # Fake BSD partitions for i in a b c d e f g h do ! ln ${name}${unit} ${name}${unit}$i ! ln r${name}${unit} r${name}${unit}$i done # User-readable and programmer-readable name sets mknod ${name}${unit}.1720 b $blk `expr $unit '*' 64 + 1` mknod r${name}${unit}.1720 c $chr `expr $unit '*' 64 + 1` ! # ln ${name}${unit}.1720 ${name}${unit}135hs21 ! # ln r${name}${unit}.1720 r${name}${unit}135hs21 mknod ${name}${unit}.1480 b $blk `expr $unit '*' 64 + 2` mknod r${name}${unit}.1480 c $chr `expr $unit '*' 64 + 2` ! # ln ${name}${unit}.1480 ${name}${unit}135hs18 ! # ln r${name}${unit}.1480 r${name}${unit}135hs18 ! # ln ${name}${unit}.1480 ${name}${unit}96hs18 ! # ln r${name}${unit}.1480 r${name}${unit}96hs18 mknod ${name}${unit}.1440 b $blk `expr $unit '*' 64 + 3` mknod r${name}${unit}.1440 c $chr `expr $unit '*' 64 + 3` ! # ln ${name}${unit}.1440 ${name}${unit}135 ! # ln r${name}${unit}.1440 r${name}${unit}135 ! # ln ${name}${unit}.1440 ${name}${unit}135ds18 ! # ln r${name}${unit}.1440 r${name}${unit}135ds18 ! # ln ${name}${unit}.1440 ${name}${unit}96ds18 ! # ln r${name}${unit}.1440 r${name}${unit}96ds18 mknod ${name}${unit}.1200 b $blk `expr $unit '*' 64 + 4` mknod r${name}${unit}.1200 c $chr `expr $unit '*' 64 + 4` ! # ln ${name}${unit}.1200 ${name}${unit}96 ! # ln r${name}${unit}.1200 r${name}${unit}96 ! # ln ${name}${unit}.1200 ${name}${unit}96ds15 ! # ln r${name}${unit}.1200 r${name}${unit}96ds15 ! # ln ${name}${unit}.1200 ${name}${unit}135ds15 ! # ln r${name}${unit}.1200 r${name}${unit}135ds15 mknod ${name}${unit}.820 b $blk `expr $unit '*' 64 + 5` mknod r${name}${unit}.820 c $chr `expr $unit '*' 64 + 5` ! # ln ${name}${unit}.820 ${name}${unit}96hs10 ! # ln r${name}${unit}.820 r${name}${unit}96hs10 ! # ln ${name}${unit}.820 ${name}${unit}135hs10 ! # ln r${name}${unit}.820 r${name}${unit}135hs10 mknod ${name}${unit}.800 b $blk `expr $unit '*' 64 + 6` mknod r${name}${unit}.800 c $chr `expr $unit '*' 64 + 6` ! # ln ${name}${unit}.800 ${name}${unit}96ds10 ! # ln r${name}${unit}.800 r${name}${unit}96ds10 ! # ln ${name}${unit}.800 ${name}${unit}135ds10 ! # ln r${name}${unit}.800 r${name}${unit}135ds10 mknod ${name}${unit}.720 b $blk `expr $unit '*' 64 + 7` mknod r${name}${unit}.720 c $chr `expr $unit '*' 64 + 7` ! # ln ${name}${unit}.720 ${name}${unit}96ds9 ! # ln r${name}${unit}.720 r${name}${unit}96ds9 ! # ln ${name}${unit}.720 ${name}${unit}135ds9 ! # ln r${name}${unit}.720 r${name}${unit}135ds9 mknod ${name}${unit}.360 b $blk `expr $unit '*' 64 + 8` mknod r${name}${unit}.360 c $chr `expr $unit '*' 64 + 8` ! # ln ${name}${unit}.360 ${name}${unit}48 ! # ln r${name}${unit}.360 r${name}${unit}48 ! # ln ${name}${unit}.360 ${name}${unit}48ds9 ! # ln r${name}${unit}.360 r${name}${unit}48ds9 chgrp operator ${name}${unit}* r${name}${unit}* ;; --- 342,409 ---- # Fake BSD partitions for i in a b c d e f g h do ! ln -f ${name}${unit} ${name}${unit}$i ! ln -f r${name}${unit} r${name}${unit}$i done # User-readable and programmer-readable name sets mknod ${name}${unit}.1720 b $blk `expr $unit '*' 64 + 1` mknod r${name}${unit}.1720 c $chr `expr $unit '*' 64 + 1` ! # ln -f ${name}${unit}.1720 ${name}${unit}135hs21 ! # ln -f r${name}${unit}.1720 r${name}${unit}135hs21 mknod ${name}${unit}.1480 b $blk `expr $unit '*' 64 + 2` mknod r${name}${unit}.1480 c $chr `expr $unit '*' 64 + 2` ! # ln -f ${name}${unit}.1480 ${name}${unit}135hs18 ! # ln -f r${name}${unit}.1480 r${name}${unit}135hs18 ! # ln -f ${name}${unit}.1480 ${name}${unit}96hs18 ! # ln -f r${name}${unit}.1480 r${name}${unit}96hs18 mknod ${name}${unit}.1440 b $blk `expr $unit '*' 64 + 3` mknod r${name}${unit}.1440 c $chr `expr $unit '*' 64 + 3` ! # ln -f ${name}${unit}.1440 ${name}${unit}135 ! # ln -f r${name}${unit}.1440 r${name}${unit}135 ! # ln -f ${name}${unit}.1440 ${name}${unit}135ds18 ! # ln -f r${name}${unit}.1440 r${name}${unit}135ds18 ! # ln -f ${name}${unit}.1440 ${name}${unit}96ds18 ! # ln -f r${name}${unit}.1440 r${name}${unit}96ds18 mknod ${name}${unit}.1200 b $blk `expr $unit '*' 64 + 4` mknod r${name}${unit}.1200 c $chr `expr $unit '*' 64 + 4` ! # ln -f ${name}${unit}.1200 ${name}${unit}96 ! # ln -f r${name}${unit}.1200 r${name}${unit}96 ! # ln -f ${name}${unit}.1200 ${name}${unit}96ds15 ! # ln -f r${name}${unit}.1200 r${name}${unit}96ds15 ! # ln -f ${name}${unit}.1200 ${name}${unit}135ds15 ! # ln -f r${name}${unit}.1200 r${name}${unit}135ds15 mknod ${name}${unit}.820 b $blk `expr $unit '*' 64 + 5` mknod r${name}${unit}.820 c $chr `expr $unit '*' 64 + 5` ! # ln -f ${name}${unit}.820 ${name}${unit}96hs10 ! # ln -f r${name}${unit}.820 r${name}${unit}96hs10 ! # ln -f ${name}${unit}.820 ${name}${unit}135hs10 ! # ln -f r${name}${unit}.820 r${name}${unit}135hs10 mknod ${name}${unit}.800 b $blk `expr $unit '*' 64 + 6` mknod r${name}${unit}.800 c $chr `expr $unit '*' 64 + 6` ! # ln -f ${name}${unit}.800 ${name}${unit}96ds10 ! # ln -f r${name}${unit}.800 r${name}${unit}96ds10 ! # ln -f ${name}${unit}.800 ${name}${unit}135ds10 ! # ln -f r${name}${unit}.800 r${name}${unit}135ds10 mknod ${name}${unit}.720 b $blk `expr $unit '*' 64 + 7` mknod r${name}${unit}.720 c $chr `expr $unit '*' 64 + 7` ! # ln -f ${name}${unit}.720 ${name}${unit}96ds9 ! # ln -f r${name}${unit}.720 r${name}${unit}96ds9 ! # ln -f ${name}${unit}.720 ${name}${unit}135ds9 ! # ln -f r${name}${unit}.720 r${name}${unit}135ds9 mknod ${name}${unit}.360 b $blk `expr $unit '*' 64 + 8` mknod r${name}${unit}.360 c $chr `expr $unit '*' 64 + 8` ! # ln -f ${name}${unit}.360 ${name}${unit}48 ! # ln -f r${name}${unit}.360 r${name}${unit}48 ! # ln -f ${name}${unit}.360 ${name}${unit}48ds9 ! # ln -f r${name}${unit}.360 r${name}${unit}48ds9 chgrp operator ${name}${unit}* r${name}${unit}* ;; *************** *** 422,429 **** 0|1|2|3) mknod ${name}${unit} b $blk `expr $unit '*' 64 + 32` mknod r${name}${unit} c $chr `expr $unit '*' 64 + 32` ! ln ${name}${unit} ${name}${unit}a ! ln r${name}${unit} r${name}${unit}a chgrp operator ${name}${unit}* r${name}${unit}* ;; *) --- 422,429 ---- 0|1|2|3) mknod ${name}${unit} b $blk `expr $unit '*' 64 + 32` mknod r${name}${unit} c $chr `expr $unit '*' 64 + 32` ! ln -f ${name}${unit} ${name}${unit}a ! ln -f r${name}${unit} r${name}${unit}a chgrp operator ${name}${unit}* r${name}${unit}* ;; *) *************** *** 586,594 **** mknod rst${unit}.ctl c $chr `expr $unit '*' 16 + $scsictl ` chmod 600 rst${unit}.ctl ! ln rst${unit}.0 rst${unit} ! ln nrst${unit}.0 nrst${unit} ! ln erst${unit}.0 erst${unit} ;; *) echo bad unit for tape in: $i --- 586,594 ---- mknod rst${unit}.ctl c $chr `expr $unit '*' 16 + $scsictl ` chmod 600 rst${unit}.ctl ! ln -f rst${unit}.0 rst${unit} ! ln -f nrst${unit}.0 nrst${unit} ! ln -f erst${unit}.0 erst${unit} ;; *) echo bad unit for tape in: $i To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 24 21:51:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12507 for freebsd-stable-outgoing; Tue, 24 Mar 1998 21:51:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA12487 for ; Tue, 24 Mar 1998 21:50:51 -0800 (PST) (envelope-from softweyr@xmission.com) Received: from slc418h.modem.xmission.com.2.70.166.in-addr.arpa (xmission.com) [166.70.2.164] by mail.xmission.com with esmtp (Exim 1.82 #1) id 0yHj5M-0006QS-00; Tue, 24 Mar 1998 22:50:48 -0700 Message-ID: <35189C4F.BB17496F@xmission.com> Date: Tue, 24 Mar 1998 22:55:27 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Derek Flowers CC: software@kew.com, stable@FreeBSD.ORG Subject: Re: Binary package updates, etc. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Derek Flowers wrote: > > On Mon, 23 Mar 1998, Wes Peters - Softweyr LLC wrote: > > > o Are we patching (or replacing) executables, the kernel, source > > code, or what? > > > > All of the above, with limitations. Ideally, we'll be able to detect > > what you have installed on your system and update those parts. > > > > We'll need to update, at a minimum: > > > > - Binary executables > > - Man page sources > > No problem. > > > - Kernel object files > > - Files, devices, etc., in the kernel source tree > > - GENERIC and LINT kernel configurations > > Aren't the kernel object files located in the kernel sources? At this > point, someone should just CVSup the kernel sources and make a new kernel. This is an excellent idea -- I hadn't thought of supping just kernel source. Since that will/does work fine, let's not replace it. > Since kernels are custom built, updating them in place is next to > impossible. I'm not for changing anything in the kernel with patches > right now. Maybe we can work on creating kernel updates that contain not > only the sources but the object files necessay to build them. Even with > this method, user intervention is necessary to configure and compile the > kernel. Precisely my worries in this area as well. I didn't want to leave 'out in the cold' those users to wish to track -STABLE, wisely modify their kernel to remove drivers, etc., they don't have, but cannot "make world" for what- ever reason. I like your solution better -- they can CVSup the kernel source and use our update packages to fill in the userland binaries, config files, etc. > > - /kernel.GENERIC > > - system configuration files in /etc, etc. (pun intended) > > Again, no problem. Is there any way to pick up the userconfig changes in the currently booted kernel and apply them to /kernel.GENERIC, so the user won't lose their userconfig changes? That'd be a neat trick, but certainly not necessary. > > o Who is going to make these patches? > > > > As with all other FreeBSD jobs, whoever volunteers. Ideally, this > > would be SEVERAL someones who use FreeBSD-stable in their daily work > > and really need this feature. If they're willing to commit the > > updates to their systems, the updates are probably in good hands. > > If we stick to doing snapshots, this can be an automated process done at > the same time the SNAPxxxxxx snapshots are rolled out. That should work fine. I can see the setup now: a simple machine with two identical disks. When SNAPxxxx is created, the 'updater' installs it on 'disk 2', boots that, and diffs the filesystem against SNAPxxxx-1 installed on 'disk 1'. The files that differ are used to roll the update. > > > o Where do we save the files we are replacing, so we can back out the > > patch? > > > > In the same place pkg_add already puts this kind of information? I > > don't know, this is a good question. I'd like to see all of the > > replacements for a particular update stored in a gzipped tarball to > > save space and inodes, personally. > > Maybe something like /var/updates? Wherever they go, there needs to be > plenty of room. Yeah, something like that. For those who are space-challenged, symlink can swoop to the rescue at a moments notice. > Real Men (T) don't know the meaning of the word ``GUI''. Really Real Men (tm) don't needs GUIs because they can type 120 wpm. ;^) (And use Bash for those unfortunate little misteaks^H^H^H^Hakes.) > Unfortunately, my skills at XWindows interface programming are naught. At > it's simplest, it could fetch a list of all current updates and allow the > user to choose to install those not already on the system. Tk is your friend here. What I had proposed was writing a Tk applet that displayed a simple 'update my system' button; when the user pushed the button it would essentially spawn 'cvsup; cd /usr/src; make world; make install". JMB decided we should call it DAS, because anyone who needed such a tool would necessarily be "Dumb As Sh*t." ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 00:28:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00925 for freebsd-stable-outgoing; Wed, 25 Mar 1998 00:28:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00920 for ; Wed, 25 Mar 1998 00:28:22 -0800 (PST) (envelope-from steve@gordian.com) Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.8.7/8.8.7) with ESMTP id AAA27803 for ; Wed, 25 Mar 1998 00:28:23 -0800 (PST) Received: from gordian.com (zelda [207.211.233.199]) by delphi.gordian.com (8.7.2/8.6.9) with ESMTP id AAA16183 for ; Wed, 25 Mar 1998 00:28:21 -0800 (PST) Message-ID: <3518C04C.542F8CB2@gordian.com> Date: Wed, 25 Mar 1998 00:29:00 -0800 From: Steve Khoo X-Mailer: Mozilla 4.04 [en] (X11; U; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: problem with rlogin/rsh in 2.2.6-STABLE cvsup'd on 3/24/98 9PM PST Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Has anyone seen this probelm? I'm seeing an interesting problem with rsh/rlogin on 2.2.6-STABLE system cvsup'd on 3/24/98 9PM PST. When I rlogin from this 2.2.6-STABLE system to a remote host command line get echo'd twice. Here' an example: /> cd /tmp cd /tmp /tmp> pwd pwd /tmp /tmp> I'm seeing this problem when I rlogin/rsh to IRIX 5.3, SunOS 4.1.3 and FreeBSD 2.2.5-STABLE Feb 5 1998 system. If I use telnet instead, I do not see this problem. I'd appreciate any advise. Thanks! SEK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 01:45:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08947 for freebsd-stable-outgoing; Wed, 25 Mar 1998 01:45:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.zip.com.au (root@mail.zip.com.au [203.12.97.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08917 for ; Wed, 25 Mar 1998 01:45:21 -0800 (PST) (envelope-from jp@zip.com.au) Received: from zip.com.au (blazer50.zip.com.au [203.62.150.114]) by mail.zip.com.au (8.8.7/8.8.5) with ESMTP id UAA06913; Wed, 25 Mar 1998 20:37:00 +1100 Message-ID: <3516C909.8D9EE568@zip.com.au> Date: Tue, 24 Mar 1998 07:41:46 +1100 From: John Paul Lonie X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: Jay Nelson CC: Robert Withrow , "Michael V. Harding" , stable@FreeBSD.ORG Subject: Re: 'Code Freeze' References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Jay Nelson wrote: > Let me add my paltry two bits in concurrance. From what I've seen. > 2.1.7 is _stable_ though ignored. 2.2.X seems to be current and 3.0, > or whatever is beyond, seems to be a work in progress. Truth is, 2.1.7 > does everything I need done. If I had to make a choice of versions to > put into a demanding environment for which I had to take > responsibility, it would be 2.1.7. We have a 2.1.7 box running as a web server which has had 410 days uptime. It is the most stable bit of hardware we have. Even our cisco 4000M has less uptime (mainly because the cpu in it failed) and boy wasn't that fun ... not To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 08:45:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07896 for freebsd-stable-outgoing; Wed, 25 Mar 1998 08:45:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07386; Wed, 25 Mar 1998 08:43:29 -0800 (PST) (envelope-from mdtancsa@sentex.net) Received: (from mdtancsa@localhost) by granite.sentex.net (8.8.6/8.6.9) id LAA04676; Wed, 25 Mar 1998 11:43:20 -0500 (EST) From: Mike D Tancsa Message-Id: <199803251643.LAA04676@granite.sentex.net> Subject: boot disk gets stuck probing wd0 with 2.2.6 floppy To: stable@FreeBSD.ORG Date: Wed, 25 Mar 1998 11:43:19 -0500 (EST) Cc: questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I dont know if its just my wonky hardware or not, but I downloaded the new 2.2.6 boot floppy with the intention of upgrading my stable box to the release version. All seems to boot fine, but when it goes to the "probing devices", the system seems to get stuck in a loop. When I booted with the -v, the message that keeps coming up forever is wd0s1: type 0xa5, Start 63, end=4124705, size 4124673:OK When I boot the old system, here is all the hardware info FreeBSD 2.2-980304-SNAP #0: Wed Mar 18 13:22:30 EST 1998 mdtancsa@sand2.sentex.ca:/usr/src/sys/compile/sand2 CPU: i486DX (486-class CPU) real memory = 50331648 (49152K bytes) avail memory = 46612480 (45520K bytes) Probing for devices on PCI bus 0: vga0 rev 20 int a irq ?? on pci0:12 wdc0 rev 2 int a irq 14 on pci0:15 chip0 rev 1 on pci0:16 chip1 rev 1 on pci0:18 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:40:33:33:f8:ee, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: CMD640B workaround enabled wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S npx0 flags 0x1 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, logging limited to 10000 packets/entry % mount /dev/wd0a on / (local) /dev/wd0s1f on /usr (asynchronous, local, noatime) /dev/wd0s1e on /var (asynchronous, local, noatime) # /dev/rwd0c: type: ESDI disk: wd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 192 sectors/cylinder: 12096 cylinders: 340 sectors/unit: 4124673 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 143360 0 4.2BSD 0 0 0 # (Cyl. 0 - 11*) b: 393216 143360 swap # (Cyl. 11*- 44*) c: 4124673 0 unused 0 0 # (Cyl. 0 - 340*) e: 409600 536576 4.2BSD 0 0 0 # (Cyl. 44*- 78*) f: 3178497 946176 4.2BSD 0 0 0 # (Cyl. 78*- 340*) sand2# fdisk wd0 ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=341 heads=192 sectors/track=63 (12096 blks/cyl) parameters to be used for BIOS calculations are: cylinders=341 heads=192 sectors/track=63 (12096 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 4124673 (2014 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 340/ sector 63/ head 191 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 09:28:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18491 for freebsd-stable-outgoing; Wed, 25 Mar 1998 09:28:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18474 for ; Wed, 25 Mar 1998 09:28:21 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 5277 invoked by uid 1000); 25 Mar 1998 17:28:46 -0000 Message-ID: <19980325182846.35033@paert.tse-online.de> Date: Wed, 25 Mar 1998 18:28:46 +0100 From: Andreas Braukmann To: freebsd-stable@FreeBSD.ORG Subject: Re: MySQL on 2.2.6-BETA References: <199803181608.TAA14010@amsoft.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803181608.TAA14010@amsoft.ru>; from Andrew Maltsev on Wed, Mar 18, 1998 at 07:08:23PM +0300 Organization: TSE TeleService GmbH Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hello, On Wed, Mar 18, 1998 at 07:08:23PM +0300, Andrew Maltsev wrote: > Is there anybody successfully using MySQL on 2.2.6-beta with libc_r > threads? I mean MySQL 3.21.26. > All compiles ok, and appears to work ok for some time, but: hmm. I'm not able to build MySQL 3.21.25-gamma (from the ports) on my 2.2.6-beta (from today) with libc_r: ug -L../regex -lregex -L../strings -lmystrings -lm -lcompat -lc_r thr_alarm.o: Undefined symbol `_pthread_signal' referenced from text segment thr_alarm.o: Undefined symbol `_pthread_attr_setscope' referenced from text segment thr_alarm.o: Undefined symbol `_pthread_signal' referenced from text segment gmake[2]: *** [mysqld] Error 1 I've changed the arguments for configure in the port's makefile to: CONFIGURE_ARGS= --localstatedir=/var/db/mysql \ --with-named-thread-libs=-lc_r \ !!!!! --with-MAKE=gmake \ --without-perl \ --without-debug \ --without-readline Any tips available? TIA, Andreas -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 09:40:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20986 for freebsd-stable-outgoing; Wed, 25 Mar 1998 09:40:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from uranus.planet-three.com (homer.duff-beer.com [194.207.51.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20951 for ; Wed, 25 Mar 1998 09:40:11 -0800 (PST) (envelope-from scot@poptart.org) Received: from localhost (scot@localhost) by uranus.planet-three.com (8.8.8/8.8.5) with SMTP id RAA14775; Wed, 25 Mar 1998 17:39:50 GMT Date: Wed, 25 Mar 1998 17:39:49 +0000 (GMT) From: Scot Elliott To: Andreas Braukmann cc: freebsd-stable@FreeBSD.ORG Subject: Re: MySQL on 2.2.6-BETA In-Reply-To: <19980325182846.35033@paert.tse-online.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I got this when I had previously built without the FreeBSD thread libraries. If you've done this, then be sure to do a make clean to get rid of all the old config stuff and makefiles. As a side note though - has anyone been able to get the p5-DBD stuff working with MySQL on FreeBSD? I've got hold of the latest source from ftp.tcx.se - and it installs fine, but when I try to use it, perl spews with: install_driver(mysql) failed: Can't load '/usr/local/lib/perl5/site_perl/i386-fr eebsd/auto/DBD/mysql/mysql.so' for module DBD::mysql: Undefined symbol "___error" in perl:/usr/local/lib/perl5/site_perl/i386-freebsd/auto/DBD/mysql/mysql.so at /usr/local/lib/perl5/i386-freebsd/5.00404/DynaLoader.pm line 166. at (eval 1) line 2 DBI::install_driver('DBI', 'mysql') called at /usr/local/lib/perl5/site_ perl/DBI.pm line 329 DBI::connect('DBI', 'DBI:mysql:mysql:uranus:3306', 'scot', 'xxxx') called at ./testDBI.pl line 12 Thanks a lot all Scot. On Wed, 25 Mar 1998, Andreas Braukmann wrote: > Date: Wed, 25 Mar 1998 18:28:46 +0100 > From: Andreas Braukmann > To: freebsd-stable@FreeBSD.ORG > Subject: Re: MySQL on 2.2.6-BETA > > Hello, > > On Wed, Mar 18, 1998 at 07:08:23PM +0300, Andrew Maltsev wrote: > > Is there anybody successfully using MySQL on 2.2.6-beta with libc_r > > threads? I mean MySQL 3.21.26. > > All compiles ok, and appears to work ok for some time, but: > > hmm. I'm not able to build MySQL 3.21.25-gamma (from the ports) on > my 2.2.6-beta (from today) with libc_r: > > ug -L../regex -lregex -L../strings -lmystrings -lm -lcompat -lc_r > thr_alarm.o: Undefined symbol `_pthread_signal' referenced from text segment > thr_alarm.o: Undefined symbol `_pthread_attr_setscope' referenced from text segment > thr_alarm.o: Undefined symbol `_pthread_signal' referenced from text segment > gmake[2]: *** [mysqld] Error 1 > > I've changed the arguments for configure in the port's makefile to: > CONFIGURE_ARGS= --localstatedir=/var/db/mysql \ > --with-named-thread-libs=-lc_r \ !!!!! > --with-MAKE=gmake \ > --without-perl \ > --without-debug \ > --without-readline > > Any tips available? > > TIA, > Andreas > > -- > /// TSE TeleService GmbH | Gsf: Arne Reuter | > /// Hovestrasse 14 | Andreas Braukmann | We do it with > /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP > /// ------------------------------------------------------------------- > /// PGP-Key: http://www.tse-online.de/~ab/public-key > /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)171 7046777 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 11:26:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13800 for freebsd-stable-outgoing; Wed, 25 Mar 1998 11:26:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from Masters.leader-group.com (masters.leader-group.com [12.10.238.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13791 for ; Wed, 25 Mar 1998 11:26:13 -0800 (PST) (envelope-from bmccloskey@leader-group.com) Received: from leader-group.com ([172.20.149.128]) by Masters.leader-group.com (Netscape Messaging Server 3.0) with ESMTP id AAA18310 for ; Wed, 25 Mar 1998 12:23:12 -0700 Message-ID: <351959CD.53E25A2E@leader-group.com> Date: Wed, 25 Mar 1998 12:23:58 -0700 From: "Brian McCloskey" Organization: Leader Group X-Mailer: Mozilla 4.02 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Adaptec 7895 On-Board SCSI Controller and CAM Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Good afternoon, I just got done searching for information at www.freebsd.org and found the CAM patch that is said to provide support for the Adaptec AIC-7895 On-Board SCSI Controller. The directions tell the user how to apply this patch to a currently running system, however I have not yet been able to get FreeBSD on my system as the drivers on the boot floppy do not support this controller, and I can't see my SCSI hard disk. Currently, all of my drives are on my Adaptec controller, so I was wondering if anybody had any information on applying the cam software, or some other devices/patches to my boot floppy so that I can get the system to see the drive so that I can install FreeBSD (version I have is 2.2.5). Thanks for any information, Brian -- ________________________________________________ Brian McCloskey | Leader Group Consultant | 5200 DTC Parkway ph: 303-773-9700 | Suite 500 fax: 303-773-9610 | Englewood, CO 8011 ____________________________|___________________ http://www.leader-group.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 12:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00568 for freebsd-stable-outgoing; Wed, 25 Mar 1998 12:49:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from caddis.mt.sri.com (caddis.mt.sri.com [206.127.76.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00551 for ; Wed, 25 Mar 1998 12:49:16 -0800 (PST) (envelope-from nate@caddis.mt.sri.com) Received: (from nate@localhost) by caddis.mt.sri.com (8.8.8/8.8.5) id NAA09409; Wed, 25 Mar 1998 13:48:09 -0700 (MST) Date: Wed, 25 Mar 1998 13:48:09 -0700 (MST) Message-Id: <199803252048.NAA09409@caddis.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bill Trost Cc: stable@FreeBSD.ORG Subject: Re: problems with PPP In-Reply-To: <19980323232922.6738.qmail@jli.com> References: <199803151535.PAA19627@awfulhak.org> <19980323232922.6738.qmail@jli.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Nate Williams" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > I don't think that is the problem. If I run ping or dig after the link > > has come up, it's still using 0.0.0.0 as the source address. > > I'm sorry to say, but AFAIK, this is impossible, and even if it *is* > actually happening, it's nothing to do with ppp :-( > .. > I added a ppp.linkup per your conversation with Nate, and everything now > appears to work fine. I do not really understand why this is the case. Could > it be that the default route entry got stuck with an old version of the > interface pointer, and that was what was polluting the outgoing packets? > > Thanks for the help, Brian (and Nate (-: ). No problem. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 14:38:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23399 for freebsd-stable-outgoing; Wed, 25 Mar 1998 14:38:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from slug.EUnet.pt (sj3-p7.telepac.pt [194.65.177.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23179 for ; Wed, 25 Mar 1998 14:37:39 -0800 (PST) (envelope-from j@bug.fe.up.pt) Received: from localhost (jmg@localhost) by slug.EUnet.pt (8.8.8/8.8.8) with SMTP id WAA06358 for ; Wed, 25 Mar 1998 22:36:36 GMT (envelope-from j@bug.fe.up.pt) X-Authentication-Warning: slug.EUnet.pt: jmg owned process doing -bs Date: Wed, 25 Mar 1998 22:36:36 +0000 (WET) From: freebsd@bug.fe.up.pt X-Sender: jmg@slug.EUnet.pt To: freebsd-stable@FreeBSD.ORG Subject: Staying -STABLE with make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk As the subject says I am trying to track -STABLE but I've some questions about the most efective method to do it. So where are my questions: I've installed the 2.2.2 sources from CD on a spare partition named /stable then I CVSup'ed the RELENG_2_2 branch and it merged with the 2.2.2 sources resulting in the 2.2.6-STABLE sources. I've also made a symlink from /usr/src to /stable/src. 1. Should I update the sources every night and in the morning check the logs and remake the changed programs? Or, should I upgrade the sources once in a while and do a full make world? 2. If I customize any file in the tree that will be updated by CVSup what will happen if that file must be changed by the cvsup program? Can it merge the new version with the one I've changed? If not what will happen? Or do I need to keep an unmodified version of -STABLE and copy all the tree to change my files and compile from this new modified tree? (I need to add support for my parallel zip drive) If anyone has any ideas about this method or wants to tell me how you do it please fell free (and I'll be grateful) to email me privately and I'll make a digest of the answers and will post it to this list. The machine I am talking about is a shell server so if anyone from best.com is listening (Matt Dillon?) I'd like to know how they do it. Thanks, Jorge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 16:39:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10075 for freebsd-stable-outgoing; Wed, 25 Mar 1998 16:39:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gulf.csc.UVic.CA (gulf.csc.UVic.CA [142.104.105.200]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA09994 for ; Wed, 25 Mar 1998 16:39:18 -0800 (PST) (envelope-from jake@checker.org) Received: from whatever.net (dial137.bc1.com) by gulf.csc.UVic.CA (4.1/SMI-4.1-csc.UVic.CA) id AA25222; Wed, 25 Mar 98 16:39:16 PST Message-Id: <3518C390.41C67EA6@checker.org> Date: Wed, 25 Mar 1998 00:42:56 -0800 From: Jake X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-CURRENT i386) Mime-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: dma driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Has the IDE DMA driver from -current made its way into -stable yet? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 25 16:46:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11284 for freebsd-stable-outgoing; Wed, 25 Mar 1998 16:46:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11274 for ; Wed, 25 Mar 1998 16:46:42 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yI0o8-000315-00; Wed, 25 Mar 1998 16:46:12 -0800 Date: Wed, 25 Mar 1998 16:46:09 -0800 (PST) From: Tom To: freebsd@bug.fe.up.pt cc: freebsd-stable@FreeBSD.ORG Subject: Re: Staying -STABLE with make world In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Mar 1998 freebsd@bug.fe.up.pt wrote: > As the subject says I am trying to track -STABLE but I've some > questions about the most efective method to do it. So where are > my questions: > > I've installed the 2.2.2 sources from CD on a spare partition > named /stable then I CVSup'ed the RELENG_2_2 branch and it > merged with the 2.2.2 sources resulting in the 2.2.6-STABLE > sources. I've also made a symlink from /usr/src to /stable/src. > > 1. Should I update the sources every night and in the morning > check the logs and remake the changed programs? Or, > should I upgrade the sources once in a while and do a full > make world? > 2. If I customize any file in the tree that will be updated > by CVSup what will happen if that file must be changed by > the cvsup program? Can it merge the new version with the > one I've changed? If not what will happen? Or do I need > to keep an unmodified version of -STABLE and copy all the > tree to change my files and compile from this new modified > tree? (I need to add support for my parallel zip drive) > > If anyone has any ideas about this method or wants to tell me > how you do it please fell free (and I'll be grateful) to email > me privately and I'll make a digest of the answers and will > post it to this list. > > The machine I am talking about is a shell server so if anyone I would never put sources or the build environment on a shell server. Too much of a target. I would never rebuild anything, unless you have a need for it. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 04:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27530 for freebsd-stable-outgoing; Thu, 26 Mar 1998 04:30:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA27519 for ; Thu, 26 Mar 1998 04:30:37 -0800 (PST) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id HAA04807; Thu, 26 Mar 1998 07:28:31 -0500 (EST) Date: Thu, 26 Mar 1998 07:28:30 -0500 (EST) From: Charles Owens To: Scot Elliott cc: Andreas Braukmann , freebsd-stable@FreeBSD.ORG Subject: Re: MySQL on 2.2.6-BETA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Wed, 25 Mar 1998, Scot Elliott wrote: > I got this when I had previously built without the FreeBSD thread > libraries. If you've done this, then be sure to do a make clean to get > rid of all the old config stuff and makefiles. My build of mysql dies TODAY (2.2.6-STABLE - make world'd 2 hours ago). I DO have libc_r present, and, as you suggested I first did a make clean. The build died with the same errors that Andreas saw (quoted below). Actually, I only get the last two "Undefined symbol" errors that he lists. The first one doesn't seem to be a problem any more. BTW, I get the same build failure with a CURRENT system (March 13 vintage). So... those of you have been able to get mysql to build with proper libc_r thread support... what's the trick? (Or what has become broken?) Chuck > As a side note though - has anyone been able to get the p5-DBD stuff > working with MySQL on FreeBSD? I've got hold of the latest source from > ftp.tcx.se - and it installs fine, but when I try to use it, perl spews > with: > > install_driver(mysql) failed: Can't load '/usr/local/lib/perl5/site_perl/i386-fr > eebsd/auto/DBD/mysql/mysql.so' for module DBD::mysql: Undefined symbol > "___error" in > perl:/usr/local/lib/perl5/site_perl/i386-freebsd/auto/DBD/mysql/mysql.so > at /usr/local/lib/perl5/i386-freebsd/5.00404/DynaLoader.pm line 166. > > at (eval 1) line 2 > > DBI::install_driver('DBI', 'mysql') called at /usr/local/lib/perl5/site_ > perl/DBI.pm line 329 > DBI::connect('DBI', 'DBI:mysql:mysql:uranus:3306', 'scot', 'xxxx') > called at ./testDBI.pl line 12 > > > > Thanks a lot all > > Scot. > > > On Wed, 25 Mar 1998, Andreas Braukmann wrote: > > > Date: Wed, 25 Mar 1998 18:28:46 +0100 > > From: Andreas Braukmann > > To: freebsd-stable@FreeBSD.ORG > > Subject: Re: MySQL on 2.2.6-BETA > > > > Hello, > > > > On Wed, Mar 18, 1998 at 07:08:23PM +0300, Andrew Maltsev wrote: > > > Is there anybody successfully using MySQL on 2.2.6-beta with libc_r > > > threads? I mean MySQL 3.21.26. > > > All compiles ok, and appears to work ok for some time, but: > > > > hmm. I'm not able to build MySQL 3.21.25-gamma (from the ports) on > > my 2.2.6-beta (from today) with libc_r: > > > > ug -L../regex -lregex -L../strings -lmystrings -lm -lcompat -lc_r > > thr_alarm.o: Undefined symbol `_pthread_signal' referenced from text segment > > thr_alarm.o: Undefined symbol `_pthread_attr_setscope' referenced from text segment > > thr_alarm.o: Undefined symbol `_pthread_signal' referenced from text segment > > gmake[2]: *** [mysqld] Error 1 > > > > I've changed the arguments for configure in the port's makefile to: > > CONFIGURE_ARGS= --localstatedir=/var/db/mysql \ > > --with-named-thread-libs=-lc_r \ !!!!! > > --with-MAKE=gmake \ > > --without-perl \ > > --without-debug \ > > --without-readline > > > > Any tips available? > > > > TIA, > > Andreas > > > > -- > > /// TSE TeleService GmbH | Gsf: Arne Reuter | > > /// Hovestrasse 14 | Andreas Braukmann | We do it with > > /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP > > /// ------------------------------------------------------------------- > > /// PGP-Key: http://www.tse-online.de/~ab/public-key > > /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > ----------------------------------------------------------------------------- > Scot Elliott (scot@poptart.org) | Work: +44 (0)171 7046777 > PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 > ----------------------------------------------------------------------------- > Public key available by finger at: finger scot@poptart.org > or at: http://www.poptart.org/pgpkey.html > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 06:16:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11128 for freebsd-stable-outgoing; Thu, 26 Mar 1998 06:16:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from uk1.imdb.com (UK1.IMDb.COM [192.68.174.59]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA11119 for ; Thu, 26 Mar 1998 06:16:17 -0800 (PST) (envelope-from robh@imdb.com) Received: from robh.imdb.com [194.222.68.23] by uk1.imdb.com with esmtp (Exim 1.62 #1) id 0yIDMq-0005JA-00; Thu, 26 Mar 1998 14:10:53 +0000 Date: Thu, 26 Mar 1998 14:11:29 +0000 (GMT) From: Rob Hartill X-Sender: robh@localhost To: stable@FreeBSD.ORG Subject: MFS size problem. 2.2.6-BETA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk After a reboot: # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/sd0s1b none swap sw 0 0 /dev/sd0s1a / ufs rw 1 1 /dev/sd0s1e /usr ufs rw,noatime 2 2 proc /proc procfs rw 0 0 /dev/sd0s1b /tmp mfs rw,-s=524288 0 0 # swapinfo Device 1024-blocks Used Avail Capacity Type /dev/sd0s1b 393216 0 393152 0% Interleaved # df /tmp Filesystem 1024-blocks Used Avail Capacity Mounted on mfs:24 31411 1 28898 0% /tmp # umount /tmp # mount /tmp # df /tmp Filesystem 1024-blocks Used Avail Capacity Mounted on mfs:230 253955 1 233638 0% /tmp -=-= What did I screw up ? cheers rob -- Rob Hartill Internet Movie Database (Ltd) http://www.moviedatabase.com/ .. a site for sore eyes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 06:38:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16210 for freebsd-stable-outgoing; Thu, 26 Mar 1998 06:38:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA16186 for ; Thu, 26 Mar 1998 06:38:18 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA15246; Thu, 26 Mar 1998 14:02:37 +0100 From: Luigi Rizzo Message-Id: <199803261302.OAA15246@labinfo.iet.unipi.it> Subject: Re: MFS size problem. 2.2.6-BETA To: robh@imdb.com (Rob Hartill) Date: Thu, 26 Mar 1998 14:02:36 +0100 (MET) Cc: stable@FreeBSD.ORG In-Reply-To: from "Rob Hartill" at Mar 26, 98 02:11:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk could it be that for whatever reason the mfs partition is mounted before swapon, so your mfs partition only gets as large as the available RAM ? a related thing: I guess there is no way to specify the mount order in /etc/fstab ? I'd need this for some diskless machine configuration, but i suppose i have to hardwire things into /etc/rc ... cheers luigi > After a reboot: > > # cat /etc/fstab > # Device Mountpoint FStype Options Dump Pass# > /dev/sd0s1b none swap sw 0 0 > /dev/sd0s1a / ufs rw 1 1 > /dev/sd0s1e /usr ufs rw,noatime 2 2 > proc /proc procfs rw 0 0 > /dev/sd0s1b /tmp mfs rw,-s=524288 0 0 > > # swapinfo > Device 1024-blocks Used Avail Capacity Type > /dev/sd0s1b 393216 0 393152 0% Interleaved > > # df /tmp > Filesystem 1024-blocks Used Avail Capacity Mounted on > mfs:24 31411 1 28898 0% /tmp > > # umount /tmp > # mount /tmp > > # df /tmp > Filesystem 1024-blocks Used Avail Capacity Mounted on > mfs:230 253955 1 233638 0% /tmp -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 07:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22177 for freebsd-stable-outgoing; Thu, 26 Mar 1998 07:14:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from five-bells.plsys.co.uk (root@five-bells.plsys.co.uk [195.224.29.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22172 for ; Thu, 26 Mar 1998 07:14:20 -0800 (PST) (envelope-from Matthew_Seaman@plsys.co.uk) Received: from ivyhouse.plsys.co.uk (matthew@ivyhouse.plsys.co.uk [195.224.29.12]) by five-bells.plsys.co.uk (8.8.8/8.8.8) with ESMTP id PAA11586; Thu, 26 Mar 1998 15:14:01 GMT Received: (from matthew@localhost) by ivyhouse.plsys.co.uk (8.8.8/8.8.8) id PAA27672; Thu, 26 Mar 1998 15:14:00 GMT Message-Id: <199803261514.PAA27672@ivyhouse.plsys.co.uk> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <199803261302.OAA15246@labinfo.iet.unipi.it> X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.1) Received: by NeXT.Mailer (1.148) From: Matthew Seaman Date: Thu, 26 Mar 98 15:13:54 GMT To: Luigi Rizzo Subject: Re: MFS size problem. 2.2.6-BETA cc: robh@imdb.com (Rob Hartill), stable@FreeBSD.ORG References: <199803261302.OAA15246@labinfo.iet.unipi.it> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Luigi Rizzo wrote: > could it be that for whatever reason the mfs partition is mounted > before swapon, so your mfs partition only gets as large as the > available RAM ? > > a related thing: > I guess there is no way to specify the mount order in /etc/fstab ? > I'd need this for some diskless machine configuration, but i > suppose i have to hardwire things into /etc/rc ... It's a login.conf thing: to fix you simply need to raise the `datasize' limit on the daemon login class, run cap_mkdb /etc/login.conf and reboot. Cheers, Matthew -- Certe, Toto, sentio nos in Kansate nin iam adesse. Matthew Seaman P&L Systems, 12 The Broadway, Amersham, Bucks., HP7 0HP, UK Tel: +44 1494 432422 Fax: +44 1494 432478 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 09:25:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18449 for freebsd-stable-outgoing; Thu, 26 Mar 1998 09:25:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18444 for ; Thu, 26 Mar 1998 09:25:23 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yIGP0-0006SP-00; Thu, 26 Mar 1998 11:25:18 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Rob Hartill cc: stable@FreeBSD.ORG Subject: Re: MFS size problem. 2.2.6-BETA In-reply-to: Your message of "Thu, 26 Mar 1998 14:11:29 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Mar 1998 11:25:18 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk As I was writing I figured it out, I think. Check your kernel configuration for MAXDSIZ. Hmmm. LINT says the default is 128 Megabytes, but I believe my /tmp was only 32M bytes before I changed it. I've seen similar things. On my 2.2.6-BETA machine: servalan$ df -k /tmp Filesystem 1K-blocks Used Avail Capacity Mounted on mfs:27 127151 1 116978 0% /tmp servalan$ swapinfo Device 1K-blocks Used Avail Capacity Type /dev/sd0b 131072 9396 121612 7% Interleaved /dev/sd1b 131072 9280 121728 7% Interleaved Total 262016 18676 243340 7% Well, OK, I'm not surprised at this, since fstab has only: servalan$ grep tmp /etc/fstab /dev/sd0s1b /tmp mfs rw 0 0 But I have another machine running 3.0-971006-SNAP: set$ df -k /tmp Filesystem 1K-blocks Used Avail Capacity Mounted on mfs:22 253703 703 232704 0% /tmp set$ swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 512000 60132 451804 12% Interleaved set$ grep tmp /etc/fstab /dev/wd0s1b /tmp mfs rw 0 0 Woops! I think I found it, in my kernel configuration file: options "MAXMEM=(512*1024)" options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" I bet that MAXDSIZ limits the size of the mfs process. Check yours. > > After a reboot: > > # cat /etc/fstab > # Device Mountpoint FStype Options Dump Pass# > /dev/sd0s1b none swap sw 0 0 > /dev/sd0s1a / ufs rw 1 1 > /dev/sd0s1e /usr ufs rw,noatime 2 2 > proc /proc procfs rw 0 0 > /dev/sd0s1b /tmp mfs rw,-s=524288 0 0 > > # swapinfo > Device 1024-blocks Used Avail Capacity Type > /dev/sd0s1b 393216 0 393152 0% Interleaved > > # df /tmp > Filesystem 1024-blocks Used Avail Capacity Mounted on > mfs:24 31411 1 28898 0% /tmp > > # umount /tmp > # mount /tmp > > # df /tmp > Filesystem 1024-blocks Used Avail Capacity Mounted on > mfs:230 253955 1 233638 0% /tmp > > -=-= > > What did I screw up ? > > cheers > rob > -- > Rob Hartill Internet Movie Database (Ltd) > http://www.moviedatabase.com/ .. a site for sore eyes. > > > 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 Thu Mar 26 09:33:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19903 for freebsd-stable-outgoing; Thu, 26 Mar 1998 09:33:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19896 for ; Thu, 26 Mar 1998 09:33:27 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id MAA18190 for ; Thu, 26 Mar 1998 12:33:17 -0500 (EST) Date: Thu, 26 Mar 1998 12:33:17 -0500 (EST) From: Snob Art Genre To: stable@FreeBSD.ORG Subject: changing root device to st0s1a Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > uname -a FreeBSD ben.tapehouse.net 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Thu Mar 26 12:21:12 EST 1998 root@ben.tapehouse.net:/usr/src/sys/compile/0NAPPLE i386 I cvsup'd yesterday, made world last night and rebuilt my kernel just now. Why does my kernel say it's booting off a tape drive? Note that everything works just fine. Do I need to change my fstab or something? Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 09:59:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24178 for freebsd-stable-outgoing; Thu, 26 Mar 1998 09:59:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from azaria.cdrom.com (azaria.cdrom.com.28.216.204.in-addr.arpa [204.216.28.183] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24141 for ; Thu, 26 Mar 1998 09:59:34 -0800 (PST) (envelope-from msmith@azaria.cdrom.com) Received: from azaria.cdrom.com (localhost.cdrom.com [127.0.0.1]) by azaria.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA09128; Thu, 26 Mar 1998 10:01:26 -0800 (PST) (envelope-from msmith@azaria.cdrom.com) Message-Id: <199803261801.KAA09128@azaria.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Snob Art Genre cc: stable@FreeBSD.ORG Subject: Re: changing root device to st0s1a In-reply-to: Your message of "Thu, 26 Mar 1998 12:33:17 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Mar 1998 10:01:26 -0800 From: Michael Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > uname -a > FreeBSD ben.tapehouse.net 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Thu Mar > 26 12:21:12 EST 1998 > root@ben.tapehouse.net:/usr/src/sys/compile/0NAPPLE i386 > > I cvsup'd yesterday, made world last night and rebuilt my kernel just > now. Why does my kernel say it's booting off a tape drive? Note that > everything works just fine. Do I need to change my fstab or something? There's a typo in the (hardcoded 8( ) table of names used to generate that message. You can safely ignore it; as you observed everything works OK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 10:25:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00603 for freebsd-stable-outgoing; Thu, 26 Mar 1998 10:25:28 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from uk1.imdb.com (UK1.IMDb.COM [192.68.174.59]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA00585 for ; Thu, 26 Mar 1998 10:25:13 -0800 (PST) (envelope-from robh@imdb.com) Received: from robh.imdb.com [194.222.68.23] by uk1.imdb.com with esmtp (Exim 1.62 #1) id 0yIHHW-0006Uv-00; Thu, 26 Mar 1998 18:21:40 +0000 Date: Thu, 26 Mar 1998 18:22:13 +0000 (GMT) From: Rob Hartill X-Sender: robh@localhost To: stable@FreeBSD.ORG Subject: Re: MFS size problem. 2.2.6-BETA In-Reply-To: <199803261514.PAA27672@ivyhouse.plsys.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Thu, 26 Mar 1998, Matthew Seaman wrote: > It's a login.conf thing: to fix you simply need to raise the `datasize' > limit on the daemon login class, run cap_mkdb /etc/login.conf and reboot. that did the trick. thanks. -- Rob Hartill Internet Movie Database (Ltd) http://www.moviedatabase.com/ .. a site for sore eyes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 10:54:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04097 for freebsd-stable-outgoing; Thu, 26 Mar 1998 10:54:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04088 for ; Thu, 26 Mar 1998 10:54:04 -0800 (PST) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id NAA09884; Thu, 26 Mar 1998 13:51:40 -0500 (EST) Date: Thu, 26 Mar 1998 13:51:40 -0500 (EST) From: Charles Owens To: Tom cc: Scot Elliott , Andreas Braukmann , FreeBSD Stable List Subject: Re: MySQL on 2.2.6-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 On Thu, 26 Mar 1998, Tom wrote: > > On Thu, 26 Mar 1998, Charles Owens wrote: > > > My build of mysql dies TODAY (2.2.6-STABLE - make world'd 2 hours ago). I > > DO have libc_r present, and, as you suggested I first did a make clean. > > "make clean" isn't always effective on the MySQL tree. I have had "make > clean" error out on me. Remove the directory, and then do a configure and > make. Hmmm... I wish it was that simple. Question: are you not using the mysql port? I am. With the port, doing a 'make clean' from /usr/ports/database/mysql _always_ results in the "work" subdir, which contains the mysql tree, getting toasted. When I then type make again, the tarball is extracted and patched and the build begins again... and dies with the usual "undefined symbol" error. If you're building from the stock mysql source with no trouble then my guess is that the port is messed up such that "configure" somehow isn't seeing the --with-named-thread-libs=-lc_r flag, even though I've done the obvious and editted the port Makefile to include this: CONFIGURE_ARGS= --localstatedir=/var/db/mysql \ --with-named-thread-libs=-lc_r \ # <--- --with-MAKE=gmake \ --without-perl \ --without-debug \ --without-readline Further comments? --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 15:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15892 for freebsd-stable-outgoing; Thu, 26 Mar 1998 15:58:45 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA15875 for ; Thu, 26 Mar 1998 15:58:39 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 11134 invoked by uid 1000); 26 Mar 1998 23:59:58 -0000 Message-ID: <19980327005958.17626@paert.tse-online.de> Date: Fri, 27 Mar 1998 00:59:58 +0100 From: Andreas Braukmann To: FreeBSD Stable List Subject: Re: MySQL on 2.2.6-STABLE References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Charles Owens on Thu, Mar 26, 1998 at 01:51:40PM -0500 Organization: TSE TeleService GmbH Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hello, sorry for giving this feedback so late. > Hmmm... I wish it was that simple. Question: are you not using the mysql > port? I am. With the port, doing a 'make clean' from > /usr/ports/database/mysql _always_ results in the "work" subdir, which > contains the mysql tree, getting toasted. After the tip "do a make clean, first" I did it the save way and toasted the work directory manually. Then I built the port again with the updated 'configure arguments'. 'mysqld' got linked without further errors. > When I then type make again, the tarball is extracted and patched and the > build begins again... and dies with the usual "undefined symbol" error. > If you're building from the stock mysql source with no trouble then my > guess is that the port is messed up such that "configure" somehow isn't > seeing the --with-named-thread-libs=-lc_r flag, even though I've done the > obvious and editted the port Makefile to include this: > > CONFIGURE_ARGS= --localstatedir=/var/db/mysql \ > --with-named-thread-libs=-lc_r \ # <--- > --with-MAKE=gmake \ > --without-perl \ > --without-debug \ > --without-readline > > Further comments? ... nope. Just happy that the tip did its trick for me. I didn't tested the fresh mysql, yet, ... though ... Regards, Andreas -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 26 16:10:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18043 for freebsd-stable-outgoing; Thu, 26 Mar 1998 16:10:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA18034 for ; Thu, 26 Mar 1998 16:10:46 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yIMjC-00007Q-00; Thu, 26 Mar 1998 16:10:34 -0800 Date: Thu, 26 Mar 1998 16:10:32 -0800 (PST) From: Tom To: Andreas Braukmann cc: FreeBSD Stable List Subject: Re: MySQL on 2.2.6-STABLE In-Reply-To: <19980327005958.17626@paert.tse-online.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 27 Mar 1998, Andreas Braukmann wrote: > I didn't tested the fresh mysql, yet, ... though ... You will quickly determine that mysql with native FreeBSD threads, that "mysqladmin shutdown" does not work. Presuably due to buggy signal/alarm handling in libc_r. Also, libc_r is slow. Using the "run-all-tests" in the sql-bench directory results in significantly faster times when using mit-pthreads, as opposed to FreeBSD's native threads. > Regards, > Andreas Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 01:48:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27065 for freebsd-stable-outgoing; Fri, 27 Mar 1998 01:48:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from five-bells.plsys.co.uk (root@five-bells.plsys.co.uk [195.224.29.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27050 for ; Fri, 27 Mar 1998 01:48:40 -0800 (PST) (envelope-from Matthew_Seaman@plsys.co.uk) Received: from ivyhouse.plsys.co.uk (matthew@ivyhouse.plsys.co.uk [195.224.29.12]) by five-bells.plsys.co.uk (8.8.8/8.8.8) with ESMTP id JAA18881; Fri, 27 Mar 1998 09:48:20 GMT Received: (from matthew@localhost) by ivyhouse.plsys.co.uk (8.8.8/8.8.8) id JAA00387; Fri, 27 Mar 1998 09:48:20 GMT Message-Id: <199803270948.JAA00387@ivyhouse.plsys.co.uk> MIME-Version: 1.0 (NeXT Mail 4.2mach v148) Content-Type: text/enriched; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.1) Received: by NeXT.Mailer (1.148) From: Matthew Seaman Date: Fri, 27 Mar 98 09:48:14 GMT To: stable@FreeBSD.ORG Subject: Re: MFS size problem. 2.2.6-BETA cc: Rob Hartill References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Rob Hartill wrote: > On Thu, 26 Mar 1998, Matthew Seaman wrote: > > > It's a login.conf thing: to fix you simply need to raise the `datasize' > > limit on the daemon login class, run cap_mkdb /etc/login.conf and reboot. > > that did the trick. thanks. Hmmm... Thinking about this, I wonder if having the MFS obey the datasize limits of the daemon class is really a good idea. Doesn't it mean that should you run foul of a memory-leaking daemon process started from /etc/rc*, it's potentially going to chew up all your swap space before the system puts it out of its misery? Matthew -- Certe, Toto, sentio nos in Kansate nin iam adesse. Matthew Seaman P&L Systems, 12 The Broadway, Amersham, Bucks., HP7 0HP, UK Tel: +44 1494 432422 Fax: +44 1494 432478 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 02:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04422 for freebsd-stable-outgoing; Fri, 27 Mar 1998 02:48:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chong.ihug.co.nz (root@chong.ihug.co.nz [203.29.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04412; Fri, 27 Mar 1998 02:48:21 -0800 (PST) (envelope-from marki@ihug.co.nz) Received: from evileye.rf.org (p49-max1.auck.ihug.co.nz [202.49.255.49]) by chong.ihug.co.nz (8.8.8/8.8.8) with SMTP id WAA32094; Fri, 27 Mar 1998 22:48:12 +1200 Message-ID: <000601bd596e$00c49600$0201a8c0@evileye.rf.org> From: "Mark Ibell" To: Cc: Subject: 2.2.6 Help Date: Fri, 27 Mar 1998 22:49:17 +1200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hi, I've just CVsup'd to 2.2.6 Release and thought I might try updating /etc & /dev as well as doing a standard make world. Oops... I have FreeBSD on the second partition (wd0s2) but made the entries for wd0s1 instead. By that I mean wd0s1a ... wd0s1h. Now only the root partition mounts, and in read only mode so I can't make the proper /dev entries. So am I like totally f####d or what? Thanks, Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 02:58:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06452 for freebsd-stable-outgoing; Fri, 27 Mar 1998 02:58:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tyree.iii.co.uk ([195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06442; Fri, 27 Mar 1998 02:57:53 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id KAA02510; Fri, 27 Mar 1998 10:57:42 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id KAA03065; Fri, 27 Mar 1998 10:57:35 GMT Message-ID: <19980327105734.02518@iii.co.uk> Date: Fri, 27 Mar 1998 10:57:34 +0000 To: Mark Ibell Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 Help References: <000601bd596e$00c49600$0201a8c0@evileye.rf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <000601bd596e$00c49600$0201a8c0@evileye.rf.org>; from Mark Ibell on Fri, Mar 27, 1998 at 10:49:17PM +1200 Organization: interactive investor Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, Mar 27, 1998 at 10:49:17PM +1200, Mark Ibell wrote: > I've just CVsup'd to 2.2.6 Release and thought I might try updating > /etc & /dev as well as doing a standard make world. Oops... I have > FreeBSD on the second partition (wd0s2) but made the entries for wd0s1 > instead. By that I mean wd0s1a ... wd0s1h. Now only the root > partition mounts, and in read only mode so I can't make the proper > /dev entries. So am I like totally f####d or what? To remount the / as read-write, just # mount -u / after you've booted single user. You can then go and edit /etc/fstab as normal. Note that the only editor you'll have available is 'ed', which is not particularly user friendly. You probably want to remount your /usr partition by hand, to pick up vi and friends in /usr/bin. Something like # mount /dev/wd0s2? /usr where '?' is whatever partition you store /usr on. N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 03:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09159 for freebsd-stable-outgoing; Fri, 27 Mar 1998 03:20:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09146 for ; Fri, 27 Mar 1998 03:20:40 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id MAA00500; Fri, 27 Mar 1998 12:20:28 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 27 Mar 1998 12:20:27 +0100 (MET) Mime-Version: 1.0 To: Kyle Mestery Cc: freebsd-stable@FreeBSD.ORG Subject: Setting the correct locale (was: Fxtv no longer works for me.) References: Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Mar 1998 12:20:26 +0100 In-Reply-To: Kyle Mestery's message of "Tue, 24 Mar 1998 18:06:51 -0600 (CST)" Message-ID: Lines: 42 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA09152 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >From -multimedia: Kyle Mestery writes: > hope.winternet.com$ fxtv > Warning: locale not supported by C library, locale unchanged > open("/dev/bktr0") failed: Device not configured This (i.e. that second line in the quote above) is a common problem for non-American FreeBSD boxes, because /etc/profile just doesn't do the Right Thing (tm). The comments in /etc/profile suggest the following: # Uncomment next two lines to activate Italian locale # LANG=it_IT.ISO_8859-1; export LANG # MM_CHARSET=ISO-8859-1; export MM_CHARSET But this is not enough; it doesn't set the locale correctly for most X software (e.g. Emacs) or even Perl 5. In fact, I'm not even sure it makes *any* sense at all; I don't know of any software that actually uses $LANG and/or $MM_CHARSET¹. IMHO the Right Thing (tm) to do (according to e.g. 'man setlocale') is the following: LC_ALL=it_IT.ISO_8859-1; export LC_ALL This will stop Emacs, Perl 5 and a bunch of other apps from complaining about an unsupported locale. All my FreeBSD boxes have a similar line, and no LANG or MM_CHARSET, in their /etc/profile². ¹ but a quick 'grep -l MM_CHARSET /usr/local/bin' gives mailto, mailto-hebrew, metamail, rtin, shownonascii and tin. Not one of my boxes though; I don't use any of this stuff except MetaMail. init(8) also contains the string MM_CHARSET but I suspect that's because it's statically linked. ² Actually, I use en_US instead of no_NO because I don't want the system to speak Norwegian to me and I can't be buggered to use separate locale settings; what I *should* do is set LC_TIME to en_US and everything else - or at least LC_COLLATE and LC_CTYPE - to no_NO -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 03:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10515 for freebsd-stable-outgoing; Fri, 27 Mar 1998 03:35:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10491 for ; Fri, 27 Mar 1998 03:34:57 -0800 (PST) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.7.1/8.7.1) id MAA05507; Fri, 27 Mar 1998 12:34:45 +0100 (MEZ) Date: Fri, 27 Mar 1998 12:34:45 +0100 (MEZ) Message-Id: <199803271134.MAA05507@king.ki.informatik.uni-frankfurt.de> From: Marko Schuetz MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: freebsd-stable@FreeBSD.ORG Subject: Setting the correct locale (was: Fxtv no longer works for me.) In-Reply-To: References: X-Mailer: VM 6.34 under Emacs 20.2.1 Reply-To: marko@cs.uni-frankfurt.de Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA10509 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >>>>> "Dag-Erling" == Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= writes: >> From -multimedia: Dag-Erling> Kyle Mestery writes: >> hope.winternet.com$ fxtv >> Warning: locale not supported by C library, locale unchanged >> open("/dev/bktr0") failed: Device not configured Dag-Erling> This (i.e. that second line in the quote above) is a common problem Dag-Erling> for non-American FreeBSD boxes, because /etc/profile just doesn't do Dag-Erling> the Right Thing (tm). Dag-Erling> The comments in /etc/profile suggest the following: Dag-Erling> # Uncomment next two lines to activate Italian locale Dag-Erling> # LANG=it_IT.ISO_8859-1; export LANG Dag-Erling> # MM_CHARSET=ISO-8859-1; export MM_CHARSET Dag-Erling> But this is not enough; it doesn't set the locale correctly for most X Dag-Erling> software (e.g. Emacs) or even Perl 5. In fact, I'm not even sure it Dag-Erling> makes *any* sense at all; I don't know of any software that actually Dag-Erling> uses $LANG and/or $MM_CHARSET¹. IMHO the Right Thing (tm) to do Dag-Erling> (according to e.g. 'man setlocale') is the following: Dag-Erling> LC_ALL=it_IT.ISO_8859-1; export LC_ALL Dag-Erling> This will stop Emacs, Perl 5 and a bunch of other apps from Dag-Erling> complaining about an unsupported locale. All my FreeBSD boxes have a Dag-Erling> similar line, and no LANG or MM_CHARSET, in their /etc/profile². It's a bit off topic, but there is another problem regarding locale and Emacs (19.34b) that I saw: setting LC_ALL can make ls output month names which dired cannot parse. I have not verified that this problem persists in 20.x. Maybe someone else has and would like to comment. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 05:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22534 for freebsd-stable-outgoing; Fri, 27 Mar 1998 05:15:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bigbrother ([206.29.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA22506 for ; Fri, 27 Mar 1998 05:14:56 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id JAA06069 for ; Fri, 27 Mar 1998 09:04:38 -0500 Received: from fault.rstcorp.com(206.29.49.18) by bigbrother.rstcorp.com via smap (V2.0) id xma006067; Fri, 27 Mar 98 09:04:14 -0500 Received: (from vshah@localhost) by rstcorp.com (8.8.1/8.8.1) id IAA00448; Fri, 27 Mar 1998 08:13:59 -0500 (EST) Date: Fri, 27 Mar 1998 08:13:59 -0500 (EST) Message-Id: <199803271313.IAA00448@rstcorp.com> MIME-Version: 1.0 From: "Viren R. Shah" To: freebsd-stable@FreeBSD.ORG Subject: using 2.2.5 kernel with 2.2.6? X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Is it possible to use a 2.2.5 kernel with a 2.2.6 system? I'm using an alternate boot floppy (made by Mark Dawson that includes a driver for the Compaq RAID controller), and am thinking of downloading 2.2.6 to install. My plan is to : 1. Install 2.2.6 using the 2.2.5 boot floppy 2. Try and merge the Compaq RAID driver into the 2.2.6 kernel sources 3. then compile a 2.2.6 kernel and boot from it. Is this feasible, or should I just stick to 2.2.5? Viren -- Viren R. Shah viren @ rstcorp . com "If the right side of the brain controls the left side of the body...then only left-handed people are in their right minds!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 05:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23671 for freebsd-stable-outgoing; Fri, 27 Mar 1998 05:21:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from horton.iaces.com (horton.iaces.com [204.147.87.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23663; Fri, 27 Mar 1998 05:21:02 -0800 (PST) (envelope-from proot@horton.iaces.com) Received: (from proot@localhost) by horton.iaces.com (8.8.7/8.8.7) id HAA25063; Fri, 27 Mar 1998 07:19:35 -0600 (CST) From: "Paul T. Root" Message-Id: <199803271319.HAA25063@horton.iaces.com> Subject: Re: 2.2.6 Help To: marki@ihug.co.nz (Mark Ibell) Date: Fri, 27 Mar 1998 07:19:35 -0600 (CST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <000601bd596e$00c49600$0201a8c0@evileye.rf.org> from Mark Ibell at "Mar 27, 98 10:49:17 pm" X-Organization: USWEST !nterprise Networking - ACES X-Phone: (612) 664-3385 X-Fax: (612) 664-4779 X-Page: (800) SKY-PAGE PIN: 537-7270 X-Address: 600 Stinson Blvd, Fl 1S X-Address: Minneapolis, MN 55413 X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In a previous message, Mark Ibell said: > Hi, > I've just CVsup'd to 2.2.6 Release and thought I might try updating > /etc & /dev as well as doing a standard make world. Oops... I have > FreeBSD on the second partition (wd0s2) but made the entries for wd0s1 > instead. By that I mean wd0s1a ... wd0s1h. Now only the root > partition mounts, and in read only mode so I can't make the proper > /dev entries. So am I like totally f####d or what? No, in single user mode, simply remount root (mount /) then you can edit your fstab. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 05:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24206 for freebsd-stable-outgoing; Fri, 27 Mar 1998 05:23:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24157 for ; Fri, 27 Mar 1998 05:22:57 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA25439; Fri, 27 Mar 1998 13:22:47 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id OAA14360; Fri, 27 Mar 1998 14:22:46 +0100 (MET) Message-ID: <19980327142246.09824@follo.net> Date: Fri, 27 Mar 1998 14:22:46 +0100 From: Eivind Eklund To: "Viren R. Shah" , freebsd-stable@FreeBSD.ORG Subject: Re: using 2.2.5 kernel with 2.2.6? References: <199803271313.IAA00448@rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803271313.IAA00448@rstcorp.com>; from Viren R. Shah on Fri, Mar 27, 1998 at 08:13:59AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, Mar 27, 1998 at 08:13:59AM -0500, Viren R. Shah wrote: > > Is it possible to use a 2.2.5 kernel with a 2.2.6 system? > > I'm using an alternate boot floppy (made by Mark Dawson that includes > a driver for the Compaq RAID controller), and am thinking of > downloading 2.2.6 to install. My plan is to : > 1. Install 2.2.6 using the 2.2.5 boot floppy > 2. Try and merge the Compaq RAID driver into the 2.2.6 kernel sources > 3. then compile a 2.2.6 kernel and boot from it. > > Is this feasible, or should I just stick to 2.2.5? The only problem I know of with this is that 2.2.5 and 2.2.6 has incompatible IPFWs. If you avoid IPFW, you should probably be fine. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 05:25:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25342 for freebsd-stable-outgoing; Fri, 27 Mar 1998 05:25:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (root@host-32-96-40-203.atl.bellsouth.net [32.96.40.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25275 for ; Fri, 27 Mar 1998 05:25:27 -0800 (PST) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id IAA00367; Fri, 27 Mar 1998 08:20:36 -0500 (EST) (envelope-from dex@wankers.net) Date: Fri, 27 Mar 1998 08:20:35 -0500 (EST) From: Dexnation Holodream X-Sender: dex@localhost To: "Viren R. Shah" cc: freebsd-stable@FreeBSD.ORG Subject: Re: using 2.2.5 kernel with 2.2.6? In-Reply-To: <199803271313.IAA00448@rstcorp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Actually, it IS possible...I ran into the oh, SO very wonderful /dev/sd0a problem, and had to run my 2.2.5 kernel to get the details on fixing it, and to actually fix it. As for the driver, well, I can't guarantee THAT will work, but your boot should. On the other hand, 2.2.6 is a minor version, so the driver will most likely work (but, since I don't have the details, don't take my word for it). -Jon Mischo On Fri, 27 Mar 1998, Viren R. Shah wrote: > > Is it possible to use a 2.2.5 kernel with a 2.2.6 system? > > I'm using an alternate boot floppy (made by Mark Dawson that includes > a driver for the Compaq RAID controller), and am thinking of > downloading 2.2.6 to install. My plan is to : > 1. Install 2.2.6 using the 2.2.5 boot floppy > 2. Try and merge the Compaq RAID driver into the 2.2.6 kernel sources > 3. then compile a 2.2.6 kernel and boot from it. > > Is this feasible, or should I just stick to 2.2.5? > > Viren > -- > Viren R. Shah > viren @ rstcorp . com > "If the right side of the brain controls the left side of the > body...then only left-handed people are in their right minds!" > > 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 Mar 27 05:34:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26939 for freebsd-stable-outgoing; Fri, 27 Mar 1998 05:34:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bigbrother ([206.29.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA26934 for ; Fri, 27 Mar 1998 05:34:36 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id JAA06207; Fri, 27 Mar 1998 09:23:40 -0500 Received: from fault.rstcorp.com(206.29.49.18) by bigbrother.rstcorp.com via smap (V2.0) id xma006203; Fri, 27 Mar 98 09:23:34 -0500 Received: (from vshah@localhost) by rstcorp.com (8.8.1/8.8.1) id IAA00491; Fri, 27 Mar 1998 08:33:19 -0500 (EST) Date: Fri, 27 Mar 1998 08:33:19 -0500 (EST) Message-Id: <199803271333.IAA00491@rstcorp.com> MIME-Version: 1.0 From: "Viren R. Shah" To: Dexnation Holodream Cc: freebsd-stable@FreeBSD.ORG Subject: Re: using 2.2.5 kernel with 2.2.6? In-Reply-To: References: <199803271313.IAA00448@rstcorp.com> X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >>>>> "dex" == Dexnation Holodream writes: dex> Actually, it IS possible...I ran into the oh, SO very wonderful /dev/sd0a Good. I've gotten other replies which indicate the same. dex> As for the driver, well, I can't guarantee THAT will work, but your boot dex> should. On the other hand, 2.2.6 is a minor version, so the driver will dex> most likely work (but, since I don't have the details, don't take my word dex> for it). I'm going to have to take my chances on that, but I hope it will work since that machine will be practically useless without having both my Compaq RAID controller and my ISA PnP (the reason I need 2.2.6) modem working. Thanks for the reply. dex> -Jon Mischo >> I'm using an alternate boot floppy (made by Mark Dawson that includes >> a driver for the Compaq RAID controller), and am thinking of >> downloading 2.2.6 to install. My plan is to : >> 1. Install 2.2.6 using the 2.2.5 boot floppy >> 2. Try and merge the Compaq RAID driver into the 2.2.6 kernel sources >> 3. then compile a 2.2.6 kernel and boot from it. >> Thanks Viren -- Viren R. Shah | viren@rstcorp.com Research Associate | viren@viren.org Reliable Software Technologies | http://www.rstcorp.com/~vshah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 07:49:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16400 for freebsd-stable-outgoing; Fri, 27 Mar 1998 07:49:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pc-algier-p.dgms.com (pc-algier-p.dgms.com [206.67.30.153]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16386; Fri, 27 Mar 1998 07:49:41 -0800 (PST) (envelope-from gaa@dgms.com) Received: from dgms.com (localhost [127.0.0.1]) by pc-algier-p.dgms.com (8.8.8/8.8.8) with ESMTP id KAA01280; Fri, 27 Mar 1998 10:49:19 -0500 (EST) (envelope-from gaa@dgms.com) Message-ID: <351BCA7F.26F53343@dgms.com> Date: Fri, 27 Mar 1998 10:49:19 -0500 From: Gary Algier X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Mark Ibell CC: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 Help References: <000601bd596e$00c49600$0201a8c0@evileye.rf.org> <19980327105734.02518@iii.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk owner-freebsd-stable@FreeBSD.ORG wrote: > > On Fri, Mar 27, 1998 at 10:49:17PM +1200, Mark Ibell wrote: > > I've just CVsup'd to 2.2.6 Release and thought I might try updating > > /etc & /dev as well as doing a standard make world. Oops... I have > > FreeBSD on the second partition (wd0s2) but made the entries for wd0s1 > > instead. By that I mean wd0s1a ... wd0s1h. Now only the root > > partition mounts, and in read only mode so I can't make the proper > > /dev entries. So am I like totally f####d or what? > > To remount the / as read-write, just > > # mount -u / > [...] I had the same problem. The command "mount -u /" will fail with the message: Specified device does not match mounted device. Specifying "mount -u /dev/wd0s3a /" fails because /dev/wd0s3a does not exist and can't be created until it is mounted read-write. My work around was to mount another file system that could mount correctly via the compatability devices (my zip drive: /dev/sd0) and create the appropriate entries as: /zip/dev/ I was then able to do "mount -u /zip/dev/wd0s3a /" and from there I could edit /etc/fstab and do a "MAKEDEV wd0s3{a,b,c,d,e,f,g,h}". Perhaps you could put floppy in /dev/fd0 and make the devices there. (I just happened to have a freebsd zip disk handy, but not a freebsd floppy disk). Now my question: I can sort of understand why the devs are not created when one does a "MAKEDEV all" (72 entries for wd0 alone!), but why aren't they created when one does "MAKEDEV wd0s3". The latter only creates one (useless) entry: wd0s3. -- Gary Algier, WB2FWZ gary.algier@srtc.com +1 609 608 2758 DGM&S Telecom, 1025 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 609 866 8850 Paul Petzoldt on the renaming of Mount Washington: "I Call it the New England Booby Trap. We see Ph.D.'s from private schools taking kids up there in shorts. People die like flies up there!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 08:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18921 for freebsd-stable-outgoing; Fri, 27 Mar 1998 08:04:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wankers.net (root@host-32-96-41-161.atl.bellsouth.net [32.96.41.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18912; Fri, 27 Mar 1998 08:04:49 -0800 (PST) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id KAA06918; Fri, 27 Mar 1998 10:57:50 -0500 (EST) (envelope-from dex@wankers.net) Date: Fri, 27 Mar 1998 10:57:48 -0500 (EST) From: Dexnation Holodream X-Sender: dex@localhost To: Gary Algier cc: Mark Ibell , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 Help In-Reply-To: <351BCA7F.26F53343@dgms.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Ok...here's the final word: There are 3 ways you are guaranteed to suceed...the way mentioned here, booting from a floppy, or booting your old kernel, making your changes, and booting the new kernel again. All are valid methods. Pick your poison :) -Jon :) On Fri, 27 Mar 1998, Gary Algier wrote: > owner-freebsd-stable@FreeBSD.ORG wrote: > > > > On Fri, Mar 27, 1998 at 10:49:17PM +1200, Mark Ibell wrote: > > > I've just CVsup'd to 2.2.6 Release and thought I might try updating > > > /etc & /dev as well as doing a standard make world. Oops... I have > > > FreeBSD on the second partition (wd0s2) but made the entries for wd0s1 > > > instead. By that I mean wd0s1a ... wd0s1h. Now only the root > > > partition mounts, and in read only mode so I can't make the proper > > > /dev entries. So am I like totally f####d or what? > > > > To remount the / as read-write, just > > > > # mount -u / > > > [...] > > I had the same problem. The command "mount -u /" will fail with the > message: > Specified device does not match mounted device. > Specifying "mount -u /dev/wd0s3a /" fails because /dev/wd0s3a does > not exist and can't be created until it is mounted read-write. > > My work around was to mount another file system that could mount > correctly via the compatability devices (my zip drive: /dev/sd0) > and create the appropriate entries as: > /zip/dev/ > I was then able to do "mount -u /zip/dev/wd0s3a /" and from there > I could edit /etc/fstab and do a "MAKEDEV wd0s3{a,b,c,d,e,f,g,h}". > Perhaps you could put floppy in /dev/fd0 and make the devices > there. (I just happened to have a freebsd zip disk handy, but not > a freebsd floppy disk). > > Now my question: I can sort of understand why the devs are not created > when one does a "MAKEDEV all" (72 entries for wd0 alone!), but why > aren't they created when one does "MAKEDEV wd0s3". The latter only > creates one (useless) entry: wd0s3. > > -- > Gary Algier, WB2FWZ gary.algier@srtc.com +1 609 608 2758 > DGM&S Telecom, 1025 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 609 866 8850 > Paul Petzoldt on the renaming of Mount Washington: > "I Call it the New England Booby Trap. We see Ph.D.'s from private schools > taking kids up there in shorts. People die like flies up there!" > > 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 Mar 27 08:16:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20651 for freebsd-stable-outgoing; Fri, 27 Mar 1998 08:16:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20565 for ; Fri, 27 Mar 1998 08:15:25 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from ringhorni.ifi.uio.no (2602@ringhorni.ifi.uio.no [129.240.64.75]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA10698; Fri, 27 Mar 1998 17:15:15 +0100 (MET) Received: (from dag-erli@localhost) by ringhorni.ifi.uio.no ; Fri, 27 Mar 1998 17:15:14 +0100 (MET) Mime-Version: 1.0 To: marko@cs.uni-frankfurt.de Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Setting the correct locale (was: Fxtv no longer works for me.) References: <199803271134.MAA05507@king.ki.informatik.uni-frankfurt.de> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Mar 1998 17:15:14 +0100 In-Reply-To: Marko Schuetz's message of "Fri, 27 Mar 1998 12:34:45 +0100 (MEZ)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Marko Schuetz writes: > It's a bit off topic, but there is another problem regarding locale > and Emacs (19.34b) that I saw: setting LC_ALL can make ls output month > names which dired cannot parse. I have not verified that this problem > persists in 20.x. Maybe someone else has and would like to comment. No, it's the same problem. FreeBSD will use e.g. norwegian month names if you set LC_ALL to e.g. no_NO, which is why I suggested setting LC_TIME to en_US and the rest to no_NO. Of course dired doesn't know norwegian month names (and expects english ones). -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 08:28:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22882 for freebsd-stable-outgoing; Fri, 27 Mar 1998 08:28:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA22876 for ; Fri, 27 Mar 1998 08:28:51 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yIbzX-0007JJ-00; Fri, 27 Mar 1998 10:28:27 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: "Viren R. Shah" cc: Dexnation Holodream , freebsd-stable@FreeBSD.ORG Subject: Re: using 2.2.5 kernel with 2.2.6? In-reply-to: Your message of "Fri, 27 Mar 1998 08:33:19 EST." <199803271333.IAA00491@rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Mar 1998 10:28:26 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I ran a 2.2.5 kernel on a 2.2.6 system for a while, from the time that "make world" completed until I booted a 2.2.6 kernel. During that time I configured and compiled and installed a new kernel (the 2.2.6 one). Actually, I did this on my NFS server, and it continued to serve my home directory all the while the make world and kernel build was going on. I didn't logout until I was ready to reboot. > >>>>> "dex" == Dexnation Holodream writes: > > dex> Actually, it IS possible...I ran into the oh, SO very wonderful /dev/sd0a > > Good. I've gotten other replies which indicate the same. > > dex> As for the driver, well, I can't guarantee THAT will work, but your boot > dex> should. On the other hand, 2.2.6 is a minor version, so the driver will > dex> most likely work (but, since I don't have the details, don't take my word > dex> for it). > > I'm going to have to take my chances on that, but I hope it will work > since that machine will be practically useless without having both my > Compaq RAID controller and my ISA PnP (the reason I need 2.2.6) modem > working. > Thanks for the reply. > dex> -Jon Mischo > > >> I'm using an alternate boot floppy (made by Mark Dawson that includes > >> a driver for the Compaq RAID controller), and am thinking of > >> downloading 2.2.6 to install. My plan is to : > >> 1. Install 2.2.6 using the 2.2.5 boot floppy > >> 2. Try and merge the Compaq RAID driver into the 2.2.6 kernel sources > >> 3. then compile a 2.2.6 kernel and boot from it. > >> > > Thanks > Viren > -- > Viren R. Shah | viren@rstcorp.com > Research Associate | viren@viren.org > Reliable Software Technologies | http://www.rstcorp.com/~vshah > > > 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 Mar 27 09:16:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26365 for freebsd-stable-outgoing; Fri, 27 Mar 1998 09:16:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from adsdevelop2.autodebit.com ([204.50.245.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26357 for ; Fri, 27 Mar 1998 09:16:35 -0800 (PST) (envelope-from davidg@autodebit.com) Received: by adsdevelop2.autodebit.com with Internet Mail Service (5.0.1457.3) id ; Fri, 27 Mar 1998 09:10:37 -0800 Message-ID: <71D507C37988D11182ED0000F80462AC0720C6@adsdevelop2.autodebit.com> From: David Green-Seed To: freebsd-stable@FreeBSD.ORG Subject: Promise Ultra-33 Date: Fri, 27 Mar 1998 09:10:36 -0800 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've just obtained a Promise Ultra-33 pci ide controller, and I was wondering if anyone has had success with it and FreeBSD 2.2-STABLE I haven't been able to get it to work - although I'm pretty much a beginner when it comes to configuring a FreeBSD kernel properly. The card has proprietary drivers for windows 95/NT, both of which think that it's a SCSI RAID controller. It has an on-board BIOS, too. DOS doesn't appear to need special drivers for it. Thanks in advance for any help. Dave. _________________________ David Green-Seed davidg@autodebit.com Automated Debit Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 10:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08195 for freebsd-stable-outgoing; Fri, 27 Mar 1998 10:34:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from voicenet.com (mail11.voicenet.com [207.103.0.37]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA08182 for ; Fri, 27 Mar 1998 10:34:48 -0800 (PST) (envelope-from schwenk@voicenet.com) Received: (qmail 10546 invoked from network); 27 Mar 1998 18:34:49 -0000 Received: from omni1.voicenet.com (207.103.0.31) by mail11.voicenet.com with SMTP; 27 Mar 1998 18:34:49 -0000 Received: (qmail 5225 invoked by uid 14559); 27 Mar 1998 18:34:47 -0000 Date: Fri, 27 Mar 1998 13:34:46 -0500 (EST) From: Peter Schwenk X-Sender: schwenk@omni1 To: David Green-Seed cc: freebsd-stable@FreeBSD.ORG Subject: Re: Promise Ultra-33 In-Reply-To: <71D507C37988D11182ED0000F80462AC0720C6@adsdevelop2.autodebit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Ultra-DMA IDE is not supported in FreeBSD (2.2.x-Release) On Fri, 27 Mar 1998, David Green-Seed wrote: > I've just obtained a Promise Ultra-33 pci ide controller, and I was > wondering if anyone has had success with it and FreeBSD 2.2-STABLE > > I haven't been able to get it to work - although I'm pretty much a > beginner when it comes to configuring a FreeBSD kernel properly. > > The card has proprietary drivers for windows 95/NT, both of which think > that it's a SCSI RAID controller. It has an on-board BIOS, too. > DOS doesn't appear to need special drivers for it. > > Thanks in advance for any help. > > Dave. > _________________________ > David Green-Seed > davidg@autodebit.com > Automated Debit Systems > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > - Peter Schwenk - schwenk@voicenet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 11:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26113 for freebsd-stable-outgoing; Fri, 27 Mar 1998 11:47:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26088 for ; Fri, 27 Mar 1998 11:46:49 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id UAA00522; Fri, 27 Mar 1998 20:46:48 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 27 Mar 1998 20:46:47 +0100 (MET) Mime-Version: 1.0 To: marko@cs.uni-frankfurt.de Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Setting the correct locale (was: Fxtv no longer works for me.) References: <199803271134.MAA05507@king.ki.informatik.uni-frankfurt.de> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 Mar 1998 20:46:47 +0100 In-Reply-To: dag-erli@ifi.uio.no's message of "27 Mar 1998 17:15:14 +0100" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA26094 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I submitted PR conf/6145 about this (including a patch). It's now up to the powers-that-be to do the Right Thing¹ with that PR ;) ¹ The Right Thing and all likenesses thereof are registered trademarks of the School of Life, Inc. and are used in this article with their permission. -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 11:58:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29153 for freebsd-stable-outgoing; Fri, 27 Mar 1998 11:58:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29051 for ; Fri, 27 Mar 1998 11:57:47 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00406; Fri, 27 Mar 1998 14:57:35 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803271957.OAA00406@dyson.iquest.net> Subject: Re: Promise Ultra-33 In-Reply-To: <71D507C37988D11182ED0000F80462AC0720C6@adsdevelop2.autodebit.com> from David Green-Seed at "Mar 27, 98 09:10:36 am" To: davidg@autodebit.com (David Green-Seed) Date: Fri, 27 Mar 1998 14:57:35 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I've just obtained a Promise Ultra-33 pci ide controller, and I was > wondering if anyone has had success with it and FreeBSD 2.2-STABLE > > I haven't been able to get it to work - although I'm pretty much a > beginner when it comes to configuring a FreeBSD kernel properly. > > The card has proprietary drivers for windows 95/NT, both of which think > that it's a SCSI RAID controller. It has an on-board BIOS, too. > DOS doesn't appear to need special drivers for it. > > Thanks in advance for any help. > It works in -current. The Promise controller is a little bit odd, but works with some mods to the driver. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 14:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24546 for freebsd-stable-outgoing; Fri, 27 Mar 1998 14:12:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mylanders.com (mylanders.com [206.252.160.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24343 for ; Fri, 27 Mar 1998 14:12:01 -0800 (PST) (envelope-from nat@mylanders.com) Received: from localhost (nat@localhost) by mylanders.com (8.8.8/8.8.5) with SMTP id QAA02440 for ; Fri, 27 Mar 1998 16:23:15 -0600 (CST) Date: Fri, 27 Mar 1998 16:23:14 -0600 (CST) From: John Frader To: freebsd-stable@FreeBSD.ORG Subject: Error after upgrading to 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 I have upgraded to 2.2.6 and now when I log in or su or when a cron job runs I get this error login_getclass: retrieving class information: Permission denied Could someone tell me what this error means.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 14:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02842 for freebsd-stable-outgoing; Fri, 27 Mar 1998 14:31:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chong.ihug.co.nz (root@chong.ihug.co.nz [203.29.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02826; Fri, 27 Mar 1998 14:31:20 -0800 (PST) (envelope-from marki@ihug.co.nz) Received: from evileye.rf.org (p54-max37.auck.ihug.co.nz [209.76.103.182]) by chong.ihug.co.nz (8.8.8/8.8.8) with SMTP id KAA17296; Sat, 28 Mar 1998 10:30:56 +1200 Message-ID: <351C28E6.41C67EA6@ihug.co.nz> Date: Sat, 28 Mar 1998 10:32:06 +1200 From: Mark Ibell X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Mark Ibell CC: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 Help References: <000601bd596e$00c49600$0201a8c0@evileye.rf.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Mark Ibell wrote: > > Hi, > I've just CVsup'd to 2.2.6 Release and thought I might try updating > /etc & /dev as well as doing a standard make world. Oops... I have > FreeBSD on the second partition (wd0s2) but made the entries for wd0s1 > instead. By that I mean wd0s1a ... wd0s1h. Now only the root > partition mounts, and in read only mode so I can't make the proper > /dev entries. So am I like totally f####d or what? > > Thanks, > Mark > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Thanks to all who helped. I ended up doing '# mount -u -w /dev.old/wd0s2a /' It didn't occur to me until this morning that I could use /dev.old directly. Phew! P.S. There's a cool 'bsd review at: http://www.cnet.com/Content/Reviews/Compare/AltOS/?st.cn.fd.acol.re To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 14:41:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04367 for freebsd-stable-outgoing; Fri, 27 Mar 1998 14:41:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA04343 for ; Fri, 27 Mar 1998 14:41:02 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yIhnq-0007YI-00; Fri, 27 Mar 1998 16:40:46 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: John Frader cc: freebsd-stable@FreeBSD.ORG Subject: Re: Error after upgrading to stable In-reply-to: Your message of "Fri, 27 Mar 1998 16:23:14 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Mar 1998 16:40:45 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > I have upgraded to 2.2.6 and now when I log in or su or when > a cron job runs I get this error > > login_getclass: retrieving class information: Permission denied I'm just guessing, but the first thing I'd do is look at the permissions on /etc/login.conf, make sure it's readable by the world. Then I'd start grepping through the sources to find where that message comes from. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 27 18:05:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09962 for freebsd-stable-outgoing; Fri, 27 Mar 1998 18:05:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09943; Fri, 27 Mar 1998 18:05:18 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA13110; Sat, 28 Mar 1998 13:03:39 +1100 Date: Sat, 28 Mar 1998 13:03:39 +1100 From: Bruce Evans Message-Id: <199803280203.NAA13110@godzilla.zeta.org.au> To: gaa@dgms.com, marki@ihug.co.nz Subject: Re: 2.2.6 Help Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk >My work around was to mount another file system that could mount >correctly via the compatability devices (my zip drive: /dev/sd0) >and create the appropriate entries as: > /zip/dev/ >I was then able to do "mount -u /zip/dev/wd0s3a /" and from there >I could edit /etc/fstab and do a "MAKEDEV wd0s3{a,b,c,d,e,f,g,h}". >Perhaps you could put floppy in /dev/fd0 and make the devices >there. (I just happened to have a freebsd zip disk handy, but not >a freebsd floppy disk). This method is the most general. It always works if you have writable media (newfs the media if necessary). Booting with -r is simpler if the builtin root device (default wd0a) matches the actual root device (the slice number is ignored in this case). >Now my question: I can sort of understand why the devs are not created >when one does a "MAKEDEV all" (72 entries for wd0 alone!), but why Really making them all would give about 256K device nodes for sd alone (512 drives * about 32 slices * 8 partitions * (raw and buffered)). >aren't they created when one does "MAKEDEV wd0s3". The latter only >creates one (useless) entry: wd0s3. wd0sN is mostly for internal use by MAKEDEV to help create only the (useful) devices wd0s[1-4] for `MAKEDEV all'. Use `MAKEDEV wd0s3a' to create all the partitions. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 28 20:30:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25519 for freebsd-stable-outgoing; Sat, 28 Mar 1998 20:30:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25512 for ; Sat, 28 Mar 1998 20:30:43 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id UAA00846 for stable@freebsd.org; Sat, 28 Mar 1998 20:30:44 -0800 (PST) (envelope-from sef) Date: Sat, 28 Mar 1998 20:30:44 -0800 (PST) From: Sean Eric Fagan Message-Id: <199803290430.UAA00846@kithrup.com> To: stable@FreeBSD.ORG Subject: Just upgraded to 2.2.6 via cvs update Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk And kerberos is quite broken. Well, it is not necessarily broken, but it no longer works with the old files. So now I have to figure out what the new file locations are. Yay. Sean. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 28 20:32:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25580 for freebsd-stable-outgoing; Sat, 28 Mar 1998 20:32:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA25567 for ; Sat, 28 Mar 1998 20:32:02 -0800 (PST) (envelope-from jeays@statcan.ca) Received: (from root@localhost) by stcgate.statcan.ca (8.6.11/8.6.9) id XAA12726 for ; Sat, 28 Mar 1998 23:35:48 -0500 Received: from stcinet.statcan.ca(142.206.128.146) by stcgate via smap (V1.3) id sma012722; Sun Mar 29 04:35:33 1998 Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id XAA22417; Sat, 28 Mar 1998 23:34:03 -0500 Date: Sat, 28 Mar 1998 23:29:13 -0500 (EST) From: Mike Jeays X-Sender: jeays@austral To: freebsd-stable@FreeBSD.ORG Subject: ATAPI Zip drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I downloaded 2.2.6-RELEASE, and upgraded my 2.2.1 system with no trouble - the /etc/fstab changes are handled very well. Everything seems to work well, with the exception of my Iomega Zip 100MB ATAPI drive. My second IDE controller has a CD-ROM as master, and the Zip drive as slave. They are both detected at boot time,as below: wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 1627MB (3332448 sectors), 3306 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked wdc1: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) ## There WAS a disk in it! ## wfd0: buggy Zip drive, 64-block transfer limit set ie0: unknown board_id: f000 I rebuilt the kernel with the following: options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device wfd0 #Iomega Zip drive When I attempt to mount either the CD-ROM or the ZIP drive, mount hangs, and I have to interrupt it with ctrl-C. If I do this a second time, the system crashes. (X stops. Attempts to log on through another tty don't work - characters entered after the login prompt just get echoed to the screen. It is big red switch time!) If I disconnect the CD-ROM and make the Zip drive the master, things seems a tiny bit better. When I attempt a disklabel, I get: /home/mike% disklabel -r -w wfd0 auto disklabel: /dev/rwfd0c: Undefined error: 0 The light on the drive blinks once. mount -t msdos /dev/wfd0 /mnt doesn't work either. There was a disk in the drive at all times. Both drives work under Win95, to my distress. Any suggestions, please? 2.2.6 doesn't seem much better to me than 2.2.5 for handling this drive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 28 20:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28369 for freebsd-stable-outgoing; Sat, 28 Mar 1998 20:50:20 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mph124.rh.psu.edu (mph@MPH124.rh.psu.edu [128.118.126.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28310 for ; Sat, 28 Mar 1998 20:50:00 -0800 (PST) (envelope-from mph@mph124.rh.psu.edu) Received: (from mph@localhost) by mph124.rh.psu.edu (8.8.8/8.8.8) id XAA26166; Sat, 28 Mar 1998 23:49:52 -0500 (EST) (envelope-from mph) Message-ID: <19980328234952.28743@mph124.rh.psu.edu> Date: Sat, 28 Mar 1998 23:49:52 -0500 From: Matthew Hunt To: Sean Eric Fagan , stable@FreeBSD.ORG Subject: Re: Just upgraded to 2.2.6 via cvs update References: <199803290430.UAA00846@kithrup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803290430.UAA00846@kithrup.com>; from Sean Eric Fagan on Sat, Mar 28, 1998 at 08:30:44PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sat, Mar 28, 1998 at 08:30:44PM -0800, Sean Eric Fagan wrote: > And kerberos is quite broken. Well, it is not necessarily broken, but > it no longer works with the old files. So now I have to figure out > what the new file locations are. Yay. http://www.freebsd.org/cgi/getmsg.cgi?fetch=344866+346982+/usr/local/www/db/text/1998/freebsd-stable/19980215.freebsd-stable -- Matthew Hunt * Think locally, act globally. http://mph124.rh.psu.edu/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 28 22:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09977 for freebsd-stable-outgoing; Sat, 28 Mar 1998 22:40:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09810 for ; Sat, 28 Mar 1998 22:40:43 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (R+45GwO+lqOQvE52WbMQXUb58m2qjFOi@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id IAA08644; Sun, 29 Mar 1998 08:40:39 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (lHm44NVSXNbGm4nEOftCUDJRd6uHGTcO@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA04071; Sun, 29 Mar 1998 08:40:39 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199803290640.IAA04071@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Sean Eric Fagan cc: stable@FreeBSD.ORG Subject: Re: Just upgraded to 2.2.6 via cvs update Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Mar 1998 08:40:38 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Sean Eric Fagan wrote: > And kerberos is quite broken. Well, it is not necessarily broken, but > it no longer works with the old files. So now I have to figure out > what the new file locations are. Yay. The config files krb.* and srvtab don't move. The database is in /var/db/kerberos/. You'll need to kdb_util dump/kdb_util load the new db. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 28 23:02:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13241 for freebsd-stable-outgoing; Sat, 28 Mar 1998 23:02:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13142 for ; Sat, 28 Mar 1998 23:01:52 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id XAA11364 for stable@freebsd.org; Sat, 28 Mar 1998 23:01:54 -0800 (PST) (envelope-from sef) Date: Sat, 28 Mar 1998 23:01:54 -0800 (PST) From: Sean Eric Fagan Message-Id: <199803290701.XAA11364@kithrup.com> To: stable@FreeBSD.ORG Subject: More on 2.2.6 upgrade Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Okay, as I said, the kerberos stuff was the stuff that bit me most. What I didn't mention was having to do a second 'make world' because my /etc/make.conf used EBONES, not KERBEROS4... But I should have checked, I suppose. I spent more time on dealing with merging /etc than I did anything else. We do that kind of stuff automatically, at work... I keep forgetting how much of a pain it is :). In the meanwhile, one of the bugs I had open is now *fixed*. yay! This was one involving more core-dumping when suspended, if invoked from mail and $SHELL=tcsh. So the upgrade was worthwhile. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message