From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 24 19:20:18 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FF0916A406 for ; Mon, 24 Apr 2006 19:20:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E83FE43D64 for ; Mon, 24 Apr 2006 19:20:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3OJKHjV071411 for ; Mon, 24 Apr 2006 19:20:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3OJKHpS071410; Mon, 24 Apr 2006 19:20:17 GMT (envelope-from gnats) Date: Mon, 24 Apr 2006 19:20:17 GMT Message-Id: <200604241920.k3OJKHpS071410@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Maxim Konovalov Cc: Subject: Re: bin/96248: vipw fail on RO /etc X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maxim Konovalov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2006 19:20:18 -0000 The following reply was made to PR bin/96248; it has been noted by GNATS. From: Maxim Konovalov To: Alex Kozlov Cc: bug-followup@freebsd.org Subject: Re: bin/96248: vipw fail on RO /etc Date: Mon, 24 Apr 2006 23:16:01 +0400 (MSD) On Mon, 24 Apr 2006, 21:46+0300, Alex Kozlov wrote: > Hi, Maxim > > No need to touch pw_util. > > Have pw_tmp in one certain place will be nice, but different fs problem... > Hmm. > > Much easier to teach vipw call PAGER if pw_edit fall on RO fs. > > This patch can be accepted? If no, you may close PR. I haven't seen any patches yet but personally don't see much sense in such subtle mechanism. I believe a simple script could solve the problem in your environment. -- Maxim Konovalov