From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id QLIUA31WKGbwRgAA62LTzQ:P1 (envelope-from ) for ; Wed, 24 Apr 2024 02:46:53 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id QLIUA31WKGbwRgAA62LTzQ (envelope-from ) for ; Wed, 24 Apr 2024 02:46:53 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=freakingpenguin.com header.s=x header.b=IWv6JjPO; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1713919612; a=rsa-sha256; cv=none; b=TJvVAH3sNJFcTuk6ZsceqfRygvZ9xcqdaYng1KGanPeTzMsFeMR6gJxS8QoPPbcBDSwKUY m1N9r119dmglKlX729y+nyaIoE1RPcji4TLgSeuGb9kR5rljByG86q3sF0e8XqkoF8EuPf fM0DT5nzO7yBB1SsMcHL3NIXPewhC1k+VXb780r3zRMtAbWNCn+YdxtxPoUQI8GuoU4yvG RHJYE3NJLBJ19fFayouQFCmYRuECO/JkdyjJd+WUDaqMLWVi+sTDea3aX910iv35gdvrXA Aalism5Z8xrDCdVwon33zzDIuhK80S3cQ7qrwzbARrCnEtohOeE69+rzNzNPpg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=freakingpenguin.com header.s=x header.b=IWv6JjPO; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1713919612; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=m9M826//UdvZ1dJq1+kEnqYBeLB9cfo3ATF8jG5J3CY=; b=mqtNNtZRTMelUDNNfhrcVQiGWq0pTGjM8vHNAGRkCnjrVJDq7FhXj22Pf5MfIKgl7Sa1s8 /PG146bguxcJxAEcp5btxNchDc7fkWPxh7uH3fUEd1BRRKxwm76e6Mc7j/43WXZfWuID8z CkIhNbhd4SNapOBMeJEaCOp6kX20ZHf6QctKFdOZgvOfhEN5N+PJIy0yDivCbDJcqvLwNS Edtw3XVRI5hzIH7TMyig3j6wkgFd7D4mfmpvbh/do33y0MZlkvD0U8iMeNQzNC0SSEQdl2 9NVbdeNUR89TI5HMmkyS4AIlRBnrSJW7sFOfDJIDW/cMAk/YrkSA1rsEadE7Zg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id E3988EAB6 for ; Wed, 24 Apr 2024 02:46:51 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rzQmC-00064d-JP; Tue, 23 Apr 2024 20:46:21 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rzQm6-00064K-5i for guix-devel@gnu.org; Tue, 23 Apr 2024 20:46:14 -0400 Received: from mail-108-mta183.mxroute.com ([136.175.108.183]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rzQm4-0001EH-9N for guix-devel@gnu.org; Tue, 23 Apr 2024 20:46:13 -0400 Received: from filter006.mxroute.com ([136.175.111.2] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta183.mxroute.com (ZoneMTA) with ESMTPSA id 18f0d911fd50003bea.001 for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Wed, 24 Apr 2024 00:46:05 +0000 X-Zone-Loop: 03730325bb5741812571f1b16c487ffe19f40de11594 X-Originating-IP: [136.175.111.2] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=freakingpenguin.com; s=x; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=m9M826//UdvZ1dJq1+kEnqYBeLB9cfo3ATF8jG5J3CY=; b=IWv6JjPOf534PrgmGNrNPxb031 jK6vg5+aay15Do7N9yuBdV7Oj0u3CehI9PnngQAvglW/DjH/5k1ihg3FqNEweAxwvZavViprTB8zQ olEkFkXwN87Rpw1OWZnPEp5NXgTOtvu8UHPd7MaBfyLRRSurAtcBPtfikycQOOnrwfEhcvT67iwm7 7TLbBpcaUeq222erfS4HzuJUwn1fGtrgXJnh44kq0KIHWQEpfli3Xh8Sc2RD0TX5KR3r2PcdLNo9m uYA8E9C4LbndcsFqm9avQUyTwdMiBRnw5OFG/5dW9SDMnRrzxKo5UitG2bHTZorIhNdfaKVj8VTBm khQFzQqg==; From: Richard Sent To: Felix Lechner Cc: guix-devel@gnu.org Subject: Re: Value in adding Shepherd requirements to file-systems entries? In-Reply-To: <87h6fs4s4g.fsf@lease-up.com> (Felix Lechner's message of "Mon, 22 Apr 2024 21:31:27 -0700") References: <87le54hhfu.fsf@freakingpenguin.com> <87h6fs4s4g.fsf@lease-up.com> User-Agent: Gnus/5.13 (Gnus v5.13) Date: Tue, 23 Apr 2024 20:45:47 -0400 Message-ID: <87mspjoaf8.fsf@freakingpenguin.com> MIME-Version: 1.0 Content-Type: text/plain X-Authenticated-Id: richard@freakingpenguin.com Received-SPF: pass client-ip=136.175.108.183; envelope-from=richard@freakingpenguin.com; helo=mail-108-mta183.mxroute.com X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Spam-Score: -5.39 X-Migadu-Queue-Id: E3988EAB6 X-Migadu-Spam-Score: -5.39 X-Migadu-Scanner: mx10.migadu.com X-TUID: 2azRQyhosTtD Hi Felix, > Someone once gave me this service [1] to mount a file-system declared > with (mount? #f). [2] It's been working ever since. Thanks! I know custom services can be made that can work on a case-by-case basis. I was curious about the value of encapsulating that logic within an operating-system file-systems field and reusing the existing code of file-system-shepherd-service in (gnu services base) and mount-file-system in (gnu build file-system). My comment on NFS support is more about how mount-file-system supports mounting NFS file-system records, but the existing code that actually uses mount-file-system tries mounting all file systems before networking has begun. Ergo, the fact that mount-file-system supports NFS seems a bit extraneous at present, at least insofar as I can decipher. I submitted a patch for what I'm thinking at https://issues.guix.gnu.org/70542. If this winds up merged I believe your code could be rewritten to remove [1] and replace [2] with --8<---------------cut here---------------start------------->8--- (file-system (device "wallace-server.local:/acct") (mount-point "/acct") (type "nfs") (requirement '(avahi-daemon)) ;resolve .local ;; (flags '(no-atime no-dev no-exec read-only)) ;; (options "proto=tcp6,timeo=300,nolock") (check? #f) (mount-may-fail? #t) (create-mount-point? #t)) --8<---------------cut here---------------end--------------->8--- (I don't have an NFS system on my LAN to test so no promises) Hopefully that shows what I'm thinking. If anyone has thoughts I'd love to hear it, either here or in the patch depending on what's appropriate. -- Take it easy, Richard Sent Making my computer weirder one commit at a time.