From nobody Fri Sep 26 17:25:36 2025 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cYHYD5T9yz68cGf for ; Fri, 26 Sep 2025 17:25:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cYHYB6cfPz3xR4 for ; Fri, 26 Sep 2025 17:25:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=StJeqCFF; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::102c) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-32ed19ce5a3so2096859a91.0 for ; Fri, 26 Sep 2025 10:25:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1758907548; x=1759512348; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=S6ou3MY8NKR5Ihe4UdbVmLnLt6esnRlcKJbXN1kLGlk=; b=StJeqCFFUl+H3qMttuNHRv3zYaD0/v25uQHeae2WWOSOUnkrBou74tU5Ir4U4CHUmu 3jMWH3YgNJgIw3XKJcUGFdCa1HcZiVBGgUTje8Sw0t+uxlMKIgm8l6qNestvQ/Fw3RW+ iSk4bvcd+FKhGDfShMAmvZMozCWuD/UoxowR9sbC7o34zt3zdG8ACRxRu/d/uZXC1Xma +WiCz3OMcFKa698/iWW0CqE6tiUJwNKeqMpFuUrjd3jhLQSKpYM3p9Nkbznlgatbzxg7 qI4n5axuV5iVIslz8PMod3UhV0bajr0TIyadk9yhpkYWad2LXNfSyvCZn3nmQomKJcoc tlig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758907548; x=1759512348; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=S6ou3MY8NKR5Ihe4UdbVmLnLt6esnRlcKJbXN1kLGlk=; b=VTluLEGIxHQ7OL5eZrB8gjyoQ4vKlEkuTD/YBmGCR+R5hDF8bcjAtyjDLPMyVB1nMK eOrPnYfyLSsDHHC4jV4OS5D+yndE3NseRombqtF89TSwE21toyXn4lVowh944vHF/jGL IN+xaePMn95fmHKJHC2+DN1UoEyysYW6XpZVgMD0IG7yLerww72wHdA8RexGV1JWwiPD UCdyvtFghstE8Y4/KkMvkM4JWJoce3+GE6IfAFxPA2P2cF/yy/dytkA2fUTprRvfbgMQ FJKyAcYUM4ZXKi0HWZ4YBMIa3t4ao1GZgKct/Mg9bAOELmnzz2tSi4KnqlWe/GnTap4b 5SsA== X-Gm-Message-State: AOJu0YzbqQnSU5Vh7es8FVAuf3HdRYF5CDLrDn3p3J8ITcuchcQxs8FW 0sxLglTONrIMkfktBrlixJ8JZXHhHULShi38P5NRA3PyXLm7lvsqakbJZaOf4Yn4xeZ52uTLVBp gnveNRrSwilQOZUy+SPPKrCNNN2bKAvj1LVqEpVg7Yg== X-Gm-Gg: ASbGncuU3YAXclTD+h6nS7+rUxks2PekD630kFOfd704pWqKq5frek5HCT2r12s0I8h KOjaRIUs9zSmN4FsU8+5XpTzQy3kvTXb+YSPs7YEErElKIzhQYbwURK2ScbOS62e1QnT7jPyimb yMbuuR+5xQPMmzIfmb/aYBH8UH94H+1N17hin7tv55xqkO/HzVB5I2oe4wvo8pawXkHQGadsXbV TAG0RaanL0/imsPd+IFCPlNnOMyS4T2nNw/tG0= X-Google-Smtp-Source: AGHT+IFXfe0YVpgeeOlmNlr+MKM3/yBAnAtTZdrP3flY0CpTKlUVDpyKtnepSCyOU7qEHup6FlWYSmZOwZqScE0GfaE= X-Received: by 2002:a17:90b:554d:b0:32d:f352:f764 with SMTP id 98e67ed59e1d1-3342a235abamr7707540a91.2.1758907547980; Fri, 26 Sep 2025 10:25:47 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Fri, 26 Sep 2025 11:25:36 -0600 X-Gm-Features: AS18NWAV1OtU2z2EMEB-H5TuGjwpozdS3fg057IhCYju5UdhjcyhxgiYH_FQ2yk Message-ID: Subject: Re: rc.d/tmp: tmpfs support not entirely complete? To: Andriy Gapon Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000972384063fb793a0" X-Spamd-Bar: - X-Spamd-Result: default: False [-1.98 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.98)[-0.982]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::102c:from]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; MLMMJ_DEST(0.00)[current@freebsd.org]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4cYHYB6cfPz3xR4 --000000000000972384063fb793a0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Sep 25, 2025 at 8:10=E2=80=AFAM Andriy Gapon wrot= e: > > I've just had a quick look at rc.d/tmp and noticed that it uses mount_md > function for the actual mounting. The function is quite smart and can us= e > either tmpfs or a memory disk depending on the configuration. > But mount_tmpmfs in rc.d/tmp tests only for an md device when it checks > whether > /tmp is already a "memory filesystem". > That sounds wrong to me... Warner --000000000000972384063fb793a0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Sep 25,= 2025 at 8:10=E2=80=AFAM Andriy Gapon <avg@freebsd.org> wrote:

I've just had a quick look at rc.d/tmp and noticed that it uses mount_m= d
function for the actual mounting.=C2=A0 The function is quite smart and can= use
either tmpfs or a memory disk depending on the configuration.
But mount_tmpmfs in rc.d/tmp tests only for an md device when it checks whe= ther
/tmp is already a "memory filesystem".

<= /div>
That sounds wrong to me...=C2=A0

Warner= =C2=A0
--000000000000972384063fb793a0--