From owner-freebsd-stable Mon Mar 9 11:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17392 for freebsd-stable-outgoing; Mon, 9 Mar 1998 11:47:07 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17322 for ; Mon, 9 Mar 1998 11:46:43 -0800 (PST) (envelope-from root@eyelab.psy.msu.edu) Received: from default (pntcmi137060.voyager.net [209.153.137.60]) by eyelab.psy.msu.edu (8.8.8/8.8.7) with SMTP id OAA01358 for ; Mon, 9 Mar 1998 14:24:26 -0500 (EST) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <199803091924.OAA01358@eyelab.psy.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 09 Mar 1998 14:17:12 -0500 To: freebsd-stable@FreeBSD.ORG From: Gary Schrock Subject: Re: *HEADS UP* Correction to previous postings. In-Reply-To: <199803091020.VAA22972@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk This is making me very concerned. We get about 3 hours warning on this, and are told that for the time being as long as you update mount you shouldn't have problems. Then later we get corrections to who this change really affects. How well tested is this change? How do I *know* I'm not going to have problems because something might have been missed? For that matter, why did this need to be put in freebsd-STABLE instead of current? To me it makes more sense to have put it there, because at least there one expects changes that might break things. I also find the attitude about people who have to do remote updates a bit disconcerting. Some of us have no choice. When your machine exists by the grace of the people at the other end, and you have to pay obscene rates to get someone to do work on it if something goes wrong, you have a right to be concerned about how this will affect things. Not everyone can have someone local to the machine that's available to go in if something gets screwed up. In our case, the closest person to the machine is a couple hours away, and can only get in during regular business hours, a time which when he's busy at his regular job. How long is the backwards compatability going to be in? Can we at least assume that it won't be removed in the life of 2.2? If I don't have to worry about the compatability disappearing in 2.2, then I can safely just leave it in until we have a time when we can get someone to go to the machine in case something happens. Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message