From owner-freebsd-ports@freebsd.org Wed Apr 29 19:14:44 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E30A62BFA5B for ; Wed, 29 Apr 2020 19:14:44 +0000 (UTC) (envelope-from rde@tavi.co.uk) Received: from kipling.tavi.co.uk (kipling.tavi.co.uk [81.187.145.130]) by mx1.freebsd.org (Postfix) with ESMTP id 49C7Vq3vmrz3CFt for ; Wed, 29 Apr 2020 19:14:43 +0000 (UTC) (envelope-from rde@tavi.co.uk) Received: from kipling.tavi.co.uk (localhost [127.0.0.1]) by kipling.tavi.co.uk (Postfix) with ESMTP id 6D968139D1 for ; Wed, 29 Apr 2020 20:14:41 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=tavi.co.uk; h=date:from:to :subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=selector1; bh=qAVeBMt Yp2U/2CCSuhGqBAel6yU=; b=TmeBvkK0EHIk47t7Kg79PCCBh3m8aMoStRxHj7z htDSNZSGvv3TwrgE/mAhV0IW0uIRozfDATTxEYJwwC+hVbnovN+fuwNdnZHCwssr 1WPmaojBLXtR4fqjmhesu4IwdmnF1f6UVjHxw+RhD97g1evogRlbJLHKYgY1E/EY J5aQ= Received: from raksha.tavi.co.uk (raksha.tavi.co.uk [81.187.145.139]) (Authenticated sender: rde@tavi.co.uk) by kipling.tavi.co.uk (Postfix) with ESMTPA id 39BF3139A9 for ; Wed, 29 Apr 2020 20:14:41 +0100 (BST) Date: Wed, 29 Apr 2020 20:14:40 +0100 From: Bob Eager To: freebsd-ports@freebsd.org Subject: Re: smartmontools and update-smart-drivedb Message-ID: <20200429201440.7afbcf93@raksha.tavi.co.uk> In-Reply-To: <20200429181755.GA2481@elch.exwg.net> References: <20200429181755.GA2481@elch.exwg.net> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd12.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUwXjFLc0vD0cS7y7zw9PDZ4tkWSRaVrZZ+m39qi2tXfVj////7+/utwK4IPggAOAAJUUA7AAABKklEQVQ4jWPYjQMwDFYJp0NKEKCNJmEf9h8CsimXiL2e33s3/e7F7K2Cs3f3dCMkQkMKj4YuCY3K3iR+e7fMaiSjvkX0/5cFGrWpe2uLzOpaExUVqMS/8PX/Re5ey960OLBTZpFA8+IlSBKPQ92zNyUUBsosN58uIY0k8f+/ONCoYytkVuhWzVwNkYiYbqk5M3NmOVBi41YZ8RsGF7shEtFb5KJ3r969CyixM7OTPeFUxG2IxLO8/9/SvqXlc+/x3h295YzLlj2nIRJQj//nRvc5TEIal8RsXBLVuCQwIgoq/u80DomP6HEOk/iOS+IJLonZOCT+ReOQ+Lkbh0QKLonbOCR+7MYhsRqHBJrVcIl/1TgklqKLQyQ+tGKIgyQOqXpjig94diZRAgAXmDX6jyWafAAAAABJRU5ErkJggg====== MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49C7Vq3vmrz3CFt X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tavi.co.uk header.s=selector1 header.b=TmeBvkK0; dmarc=pass (policy=none) header.from=tavi.co.uk; spf=pass (mx1.freebsd.org: domain of rde@tavi.co.uk designates 81.187.145.130 as permitted sender) smtp.mailfrom=rde@tavi.co.uk X-Spamd-Result: default: False [-6.55 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[tavi.co.uk:s=selector1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:kipling.tavi.co.uk:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[tavi.co.uk:+]; DMARC_POLICY_ALLOW(-0.50)[tavi.co.uk,none]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-3.65)[ip: (-9.66), ipnet: 81.187.0.0/16(-4.79), asn: 20712(-3.75), country: GB(-0.07)]; ASN(0.00)[asn:20712, ipnet:81.187.0.0/16, country:GB] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2020 19:14:44 -0000 On Wed, 29 Apr 2020 20:17:55 +0200 Christoph Moench-Tegeder wrote: > ## Carmel NY (carmel_ny@outlook.com): > > > 1) Why is the "update" procedure deliberately removed from the > > port? > > The svn history does mention it: > https://svnweb.freebsd.org/ports?view=revision&revision=527607 > "Remove drivedb update binary as it will modify tracked files" > A port has no business modifying itself once installed - if > installed files have to be updated at runtime, these files should > live in /var/db/. > An acceptable solution in this case would be moving that drive db > to /var/db/smartmontools/ (or similar). When I start thinking about > that... perhaps the original (shipped) drive db should be kept as a > fallback, in case the user did not download (or delete) the updateable > drive db: I haven't seen any complaints about missing drive db updates > until now, which makes me suspect that for most people (me included) > the shipped drive db is "good enough" and few people ever tried to > update the drive db at all. Indeed. In all these years, I've only had to do it ONCE [1]. I leave it until a drive isn't recognised. I certainly wouldn't bother doing it on a regular basis - I wait until a drive isn't recognised. [1] And I wish I hadn't bothered. The drives I downloaded the update for are going back - they are two of the submarined SMR drives from Western Digital.