From nobody Wed Sep 25 03:40:37 2024 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 4XD2Z26QjNz5WW89 for ; Wed, 25 Sep 2024 03:40:42 +0000 (UTC) (envelope-from gadcode@earthlink.net) Received: from mta-202a.earthlink-vadesecure.net (mta-202a.earthlink-vadesecure.net [51.81.232.240]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XD2Z15gxQz4fq0 for ; Wed, 25 Sep 2024 03:40:41 +0000 (UTC) (envelope-from gadcode@earthlink.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=earthlink.net header.s=dk12062016 header.b="GHB3M/FB"; dmarc=pass (policy=none) header.from=earthlink.net; spf=pass (mx1.freebsd.org: domain of gadcode@earthlink.net designates 51.81.232.240 as permitted sender) smtp.mailfrom=gadcode@earthlink.net DKIM-Signature: v=1; a=rsa-sha256; bh=tfqaPl5fzGuSTR75RZSyWbprxfqR77TLuBziJ0 Kb7ok=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1727235640; x=1727840440; b=GHB3M/FBf6EQT7FI9xD3IN9KkoV myRbmyhIbCc0NRUX7mpAUa7xopqyNgee0iccrCwaFDwdJlhbHHeUxyQLJOndE8hqxl+kjZJ 1j1Flv8QMXIBs/7Ka8VMmbFf2L/ceNYmoo08GLauW/UTZiSRVMEadfMqicB9Vx1/slBdAuF dxHxNrDmweiXgZwhs7OZO5krUA7ccxqvT3O5tT4t8S6YrG7U+UbPbcE8YFYgxUHUWK2lFh2 nTdbaFhNZJii7ZOV2dvjAVT6gxw8COrAHlCy0TMkqmD/wTUuwu00t/TeBcBfSrKkcxITLg3 USIKBHS0Wax4+iVpQyniX5z05YNf23w== Received: from [128.113.125.59] ([74.70.87.37]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id 4faf5564-17f85fa9c213c837; Wed, 25 Sep 2024 03:40:40 +0000 From: Garance ELC Drosehn To: Kevin Oberman Cc: current Subject: Re: New console output at boot? Date: Tue, 24 Sep 2024 23:40:37 -0400 X-Mailer: MailMate (1.14r5937) Message-ID: <2BB545B2-9A98-4D2E-A450-6839E59FEEAA@earthlink.net> In-Reply-To: References: 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 Content-Type: multipart/alternative; boundary="=_MailMate_79402FAC-AFCB-4B27-9B78-FC5740B7B667_=" X-Spamd-Result: default: False [-2.82 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.918]; DMARC_POLICY_ALLOW(-0.50)[earthlink.net,none]; R_DKIM_ALLOW(-0.20)[earthlink.net:s=dk12062016]; R_SPF_ALLOW(-0.20)[+ip4:51.81.232.240]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ONCE_RECEIVED(0.10)[]; FREEMAIL_ENVFROM(0.00)[earthlink.net]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[earthlink.net]; ASN(0.00)[asn:16276, ipnet:51.81.128.0/17, country:FR]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; DKIM_TRACE(0.00)[earthlink.net:+] X-Rspamd-Queue-Id: 4XD2Z15gxQz4fq0 X-Spamd-Bar: -- --=_MailMate_79402FAC-AFCB-4B27-9B78-FC5740B7B667_= Content-Type: text/plain; format=flowed On 22 Sep 2024, at 20:20, Kevin Oberman wrote: > Since an update to current a couple of weeks ago, I now see several > lines > (6 or 7) early in the boot. I'm not sure whether it is from one of the > boots or the loader, but it comes out so quickly (and so briefly) but > it > vanishes on my display before I can read it. Just a minor aside: At various times on various OS's I've hit situations where messages go by too fast at boot-up. It finally occurred to me that I could use some of the alternate video-recording modes on my iPhone to record the screen during the entire boot-up process, and then rewatch the boot-up process in slow motion. This trick has helped me solve a few problems that none of us at work were able to fix, because none of our eyes are fast enough to read all of those boot-up messages as they fly by. And before this, none of us had thought to take out our modern-technology cell phones to record messages on the very ancient-technology of "serial console" messages written to a the screen of a monitor. -- garance --=_MailMate_79402FAC-AFCB-4B27-9B78-FC5740B7B667_= Content-Type: text/html Content-Transfer-Encoding: quoted-printable

On 22 Sep 2024, at 20:20, Kevin Oberman wrote:

Since an update to current a couple= of weeks ago, I now see several lines
(6 or 7) early in the boot. I'm not sure whether it is from one of the
boots or the loader, but it comes out so quickly (and so briefly) but it
vanishes on my display before I can read it.

Just a minor aside: At various times on various OS's I'v= e hit situations where messages go by too fast at boot-up. It finally oc= curred to me that I could use some of the alternate video-recording modes= on my iPhone to record the screen during the entire boot-up process, and= then rewatch the boot-up process in slow motion. This trick has helped = me solve a few problems that none of us at work were able to fix, because= none of our eyes are fast enough to read all of those boot-up messages a= s they fly by.

And before this, none of us had thought to take out our m= odern-technology cell phones to record messages on the very ancient-techn= ology of "serial console" messages written to a the screen of a= monitor.

		-- garance
--=_MailMate_79402FAC-AFCB-4B27-9B78-FC5740B7B667_=--