From nobody Sun Sep 22 17:15:04 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 4XBXnC2Z6Cz5WPPZ for ; Sun, 22 Sep 2024 17:15:11 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XBXnB00Lkz4JFq for ; Sun, 22 Sep 2024 17:15:09 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b="qmrGP6/n"; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 48MHF5tw056447 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Sun, 22 Sep 2024 13:15:06 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1727025306; bh=oqmTWitLgOd2KyDaBQOGLP1KvYZYrJ50hV03drCTDF4=; h=Date:To:From:Subject; b=qmrGP6/nq9emjp0yRcbue+ACBJAMzc/cpdsG5xoOze8QfQRZotR6bISBoo8lIWHKo rdNjW0vrIb1F3TC/ceky9U39vdpu80eIG0xrJpW7JuIkcjdGTTNak3teqNt9vsCM5x b4Y3GXuBJk0jjxMbyEwARvdcCv4Hk0s29eb1z9aRa0AGCXbGdVfZqkzh7Ln8+1vPBC JjxudfF+pR2jkqbW4Jx8QuodQLNaG+EDIXU1XgwikSdyQp5PCi2rsKSQdjbnpcyY7f b2Df5xAybcePd0Oqfpyiw5zGvonj/7sfnh4Vk9x9p0OUc2MNuRg5i8DkqJpw38lBP3 zoCIajxjluWlA== Message-ID: <2661b46d-b1bb-4731-acbd-75a7fb3c6233@blastwave.org> Date: Sun, 22 Sep 2024 13:15:04 -0400 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 User-Agent: Mozilla Thunderbird To: FreeBSD Current Content-Language: en-CA From: Dennis Clarke Subject: regarding that stack of newline chars expressed at boot Organization: GENUNIX Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 48MHF5tw056447 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Result: default: False [-4.69 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; TO_DN_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XBXnB00Lkz4JFq X-Spamd-Bar: ---- This is from the "better late than never" file. So yes, any machine I had with a serial console was kicking out a newline char on every one of the "autoboot_delay" countdown. Seems to be a default of 10 secs and so therefore I was seeing ten lines of stuff. Seems to be related to : https://cgit.freebsd.org/src/commit/?id=101afbc6ee2f06f77e6886f1f3ffe115c579967c The trivial solution is to NOT use and old fashioned 80x24 DEC VT100 type XTerm size for the session that connects to serial. The behavior vanishes at 80x25 now. I see that as the old DOS PC-Term size that some folks at Microsoft loved. Many years ago. Maybe it would be more elegant to just output the countdown secs number and then utter 010 BS chars and keep kicking out numbers that overwrite whatever was there before? Or do nothing. Hardly an issue really. Just seemed weird when I saw it. Thanks for letting me paint the bikeshed. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken