From nobody Fri Jul 26 18:22:43 2024 X-Original-To: freebsd-fs@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 4WVx2H6TvZz5R6Cm for ; Fri, 26 Jul 2024 18:23:03 +0000 (UTC) (envelope-from 678yym@gmail.com) Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 4WVx2H0zwjz4TBW for ; Fri, 26 Jul 2024 18:23:03 +0000 (UTC) (envelope-from 678yym@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=boOtyVko; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of 678yym@gmail.com designates 2a00:1450:4864:20::62a as permitted sender) smtp.mailfrom=678yym@gmail.com Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-a7ac469e4c4so354672966b.0 for ; Fri, 26 Jul 2024 11:23:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722018181; x=1722622981; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=bAbV1lFcmV0P5HuhAc0ieh9xts6eDAxa6JlBhSalZrQ=; b=boOtyVko1Pbl4sUDgLRJyRCa6++YZ35ApntAL9uex5iG9AcYfjejPMY7TdsXPXPW3g tTu15rV0phRJ6+9hj6cmTpJptf6Xvl3VwlY8eSNWcAV4ZQXw0vIeS22S6PsFVJAzF9E4 0EBb62/YIQ0hQMWJQNs98sjO8HmMnAJitRdoVAAW+VY804guopldTDp3RWixPDJWsS94 JYR0hprycRUcghpHrlJmBHuwYD2X/yFekIDdyF3vagXsGAADf8WVaBEoQwPGSoyIPOi/ alfiptbI/ob6Td2TUsOPWcrcJ74IJvf4MWklM1jPdvJfaY4MPV4Gg6FA9UduVpuDVkNl x5Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722018181; x=1722622981; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bAbV1lFcmV0P5HuhAc0ieh9xts6eDAxa6JlBhSalZrQ=; b=IC6S3IpWbav9D3x2H26n+cZfIspIkmYlxwmHwEO78IkA/7YPkyG9UkkGBOblaS4cFw HwCVOB3a7WeXq/Z8X/v0lUYZ8RTjrRpSCWjqkGiZ7kLzb9bb4CSFZCrCGoFult4UfR4O nNUrQks9gPDUH6j1wzvl2RfoBZbioU9+M7PDJ5U0abkZrtAKqMs1KCwwijwnxfkJC6zD s8jdhj88um3Wm2jQgFmTzTPL9LNmnI/T4rJn+lqv1hN/RBSSn+eLis2C6c+YKgvdc1zP r+LKxXTgnmj69+BGTx3C5FHB2GfQGFpvrBCmG+HjOuayGHNtWGpZIAowNIKQV2MHaxsv pmbA== X-Gm-Message-State: AOJu0Yzr1zJiqFa+LzOYbvMw79KwI03BZspuHyX2LnNyk/W4xSklcFHN TOQ0VmhI9NoVG4rv5+XR1/MFRF+3rdrTkFtc80CzaBjJm/qvadf3nkzvjDnyBuHrMBo+triuGcx TnlRgUniz/YVSz6WmOgVv69eGbi5vMw== X-Google-Smtp-Source: AGHT+IFRCMTqAtnx1lJOXQDX29nDI4+CCN6NWkAMX5fYC2ARvI22ZU8xADTmQZTKYwHDsc5BMUJKvlSQCWBnX+lMDls= X-Received: by 2002:a17:907:2d8c:b0:a7a:8a38:9d99 with SMTP id a640c23a62f3a-a7d3fb8340emr30974266b.35.1722018180811; Fri, 26 Jul 2024 11:23:00 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 From: Bryce <678yym@gmail.com> Date: Fri, 26 Jul 2024 14:22:43 -0400 Message-ID: Subject: Kernel boot process and root fs in minimal systems To: freebsd-fs@freebsd.org Content-Type: multipart/alternative; boundary="000000000000f6d146061e2a99fc" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.81 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.81)[-0.809]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62a:from] X-Rspamd-Queue-Id: 4WVx2H0zwjz4TBW --000000000000f6d146061e2a99fc Content-Type: text/plain; charset="UTF-8" Hello list, Ive been using FreeBSD for a few months now, and have been using Linux for a few years. I've read some man pages and relevant sections of the manual. I'm not opposed to RTFM, but please point to relevant sections. So what I've gathered: BSD has a 3 stage bootloader, stage 0 is obviously just for getting past the one sector limit, stage 1 passes kernel configuration options(?) to stage 3, which finds the kernel on the rootfs (which may be the network), and passes stage 2 config onto the kernel (ie, what modules to load etc?). Then, what I assume happens is that the kernel takes the config options from stage 2 and mounts rootfs and then executes /init. Is this correct, list? If so, is it possible to use a tmpfs-like filesystem to mount rootfs in memory alone? I know about md(4), and how it bakes the md image into the kernel. This is what I'm looking for, but what about the bootloaders? do they need to be configured to not look for rootfs on disk? sorry if my questions are uninformed, I'm quite new. If somebody wants to point me to the relevant sources in the source tree I'd be happy to read them. also, if this is the wrong list to be writing to, I apologize, I couldn't find a more appropriate list. thanks list. --000000000000f6d146061e2a99fc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello list,

= Ive been using FreeBSD for a few months now, and have been using Linux for = a few years. I've read some man pages and relevant sections of the manu= al. I'm not opposed to RTFM, but please point to relevant sections.

So what I've gathered:<= /div>

BSD has a 3 stage bootlo= ader, stage 0 is obviously just for getting past the one sector limit, stag= e 1 passes kernel configuration options(?) to stage 3, which finds the kern= el on the rootfs (which may be the network), and passes stage 2 config onto= the kernel (ie, what modules to load etc?).

Then, what I assume happens is that the kernel takes t= he config options from stage 2 and mounts rootfs and then executes /init.

Is this correct, list? If= so, is it possible to use a tmpfs-like filesystem to mount rootfs in memor= y alone?

I know about md= (4), and how it bakes the md image into the kernel. This is what I'm lo= oking for, but what about the bootloaders? do they need to be configured to= not look for rootfs on disk?

sorry if my questions are uninformed, I'm quite new. If somebody = wants to point me to the relevant sources in the source tree I'd be hap= py to read them.

also, i= f this is the wrong list to be writing to, I apologize, I couldn't find= a more appropriate list.

thanks list.

--000000000000f6d146061e2a99fc--