From nobody Mon Jan 15 19:54:54 2024 X-Original-To: freebsd-arch@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 4TDNCP3qXdz57RpT for ; Mon, 15 Jan 2024 19:54:57 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDNCP3Jtsz4fJj for ; Mon, 15 Jan 2024 19:54:57 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705348497; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=3jSaCpDYGzBUe+TQxyciFU56G3Vt1fkWbHfKZr0My9Q=; b=VvoMVshEiY3VGKcuQWfY4XFCcQEY/eNQMQ3Gb2RuVGS3XGHmqgnnr6KJFxTNUTbYsdWob3 HJgd4j6T8lwFGQ3d0UqnVXfa+XuaoUSG8Y+ie2rvA2j+8bk7dxNg3QRWsdzGgauPhy8MwN 8MtIIh3K3fCqnA2/R8+80+Fd8B3n8kMS17gfCE8fv5J+H78UOdT79bMY3wfgmcSy7t9uFM i5TEOEIPaPFp05uKg3PfkyRAYk4ebrIbPNZxv+yo1ZCkm5Fml9NStgUZ4QhdrIsSLm/TbK C6XcOWUZqZGwtxnHlxsCgqk4qQ6V2HpbmNhaOtslWcsPuOsjpzvafgWTAo/qhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705348497; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=3jSaCpDYGzBUe+TQxyciFU56G3Vt1fkWbHfKZr0My9Q=; b=JhC5fxLm+7SlZXpWb36WFWeWaL8NhWKxEk2BG79IK4xmCk/gf46md4vxA8LKsS69oTMhgq 4CyWTpqsKBbxZ/3mN4R3d+Z0agsL/jUZDsSxl3hBrJEniSclh8MAUf5eoAiAfU8x3BnA+/ 7NYEy6S7cd+P15IwGYUEj56sCAKYYCyI1F9jMFBgeEwmtpXwSP94La304Ri7WXMao/53wL dBlHJOxFk0N/OdzjHmSj+4xj5oJZSnuRUK5RKd7lMj1qjaiUtPDe5fXqwaPQ8U9/THut1r efAHSYRZEU7drZtZv8ahYqhYtq63pkbuf00Tw6vcYCetvPETjAPiVOPltYY7aQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705348497; a=rsa-sha256; cv=none; b=ZnOFMk9YACovSjtbztdiyEnGQCJzlyPL8twkXTyXCnIVhunL+6lPQTLGcb4hRhtD5oqy2G hrqY57FRZP3HUFAIwAD5EPAjJkm2N698rlV3j2gx8Ne1PTu8IOUzvVccaMWa7ik1JDSI9r xIsWG4XXbvM2F75TKYmRv7qiBQk1e478wmeJYd3hA5irJOCmL1vc1Sji+5iBfXPpc99vC8 RtQUm/oY5ffyyTYbj5RQRYLWKqytA+rFDVRbyB1Uq0rqwZNknJ/b2GNcAOaS07XksQu8jT C49RgiZC1SaxJPn11V5zsugnyYa9bXm3KPOjfXTCWMynSx+7jf2RHttkz3+04Q== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4TDNCP19V7zNTY for ; Mon, 15 Jan 2024 19:54:57 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> Date: Mon, 15 Jan 2024 13:54:54 -0600 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: freebsd-arch@freebsd.org From: Kyle Evans Subject: orch(1) for tty testing Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, I wrote a tool for tty testing w/ lua scripts, inspired by expect(1) and with some similarities, but explicitly without the goal of trying to be compatible: https://git.kevans.dev/kevans/orch An example of its use is here: https://git.kevans.dev/kevans/tty-tests/src/branch/main/test_canon.orch Each spawn() creates a new pts(4) and allows us to drive I/O to the process with write/match statements. I have one or two tests written with it so far and the end result is, IMO, much less painful looking and less error prone than the equivalent in C. It still needs a bit of polish (e.g., improved diagnostics when a match fails), but I'd like to consider importing this somewhere for use in the near future for tty testing given how much it simplifies. I can push it to ports, but we have a private liblua in base so it could be built and banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life just a tad easier re: getting these to run in CI. It's pretty lightweight; the orch binary on my amd64 system clocks in at ~27K, and orch.lua at 13K. Any objections to importing this new tool into /usr/tests or maybe even /usr/libexec? Thanks, Kyle Evans From nobody Tue Jan 16 18:56:55 2024 X-Original-To: freebsd-arch@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 4TDytC4KwWz57q61 for ; Tue, 16 Jan 2024 18:57:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDytC2XD3z53Lv for ; Tue, 16 Jan 2024 18:57:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a2c67be31edso637065266b.0 for ; Tue, 16 Jan 2024 10:57:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1705431426; x=1706036226; 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=mFvIgEnw1hsi9yK48E0n66xc3OjLp1UJc9buD7GwPek=; b=UYUh952pndvx4IcUoV4W/4dlhxHPWZjAYBF0lXgrsh3EjdqryValmo5znAqcTuBdLG Hy1nK59vXqTfXe4ALq8bCYI1IvxSXCJMpaZEJguA6lVVNwzkcg0RKRmG1Yo8gzA2TQp1 dtpLdzzA2dPYyvKy375Fq4WxQzyjg5NaUVuon94RApK6CBe1A23c0bl38dio9Birlmvv s4YeHTb0Wzu/ih6S4O79DbRiqVC9L9OpKZwar308klcuTB1tsX+l3NoBwxkjqMUzSCIq m4YGM1VEV8mO+dy+HtyJM+ranjAK11tO/6bMF5nSDaOkJGzviVT9cUkmQ8wnOVPy/uhW y0aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705431426; x=1706036226; 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=mFvIgEnw1hsi9yK48E0n66xc3OjLp1UJc9buD7GwPek=; b=KRh6+2Tlafe39EuY7UhJbFxmsoKopWlfAkB7V88X+VG1vroA7XaujvJ0880dQhyu98 4r+uoJS4UJun6ltd9ER3l9Rp3c3NeKUsiwHHJmSw0bMMS+/OItS8isi3xSHmoDCk+Csd 6BYDpgAOhyz+8k8D2Nr5rWLNaJIt8jan7usXxPRCd7scSgY3HPVCZbwfaW06v9EYzAGj jkT9Qed2dMTDDbOapLGl5a+G8QKENCxOQhgH3RX3G+XvQS0F+gT1rByQGAwaUQF6vAwa 8bYIVaheCdTAY2kFB08okLhRqu7Ihjre1ufzQP3FxXC6ArDSnj92NvnqY1PtEOm0Evtn gd8Q== X-Gm-Message-State: AOJu0Yx2CyaSVdo9INC99wZ47iIIHwI8qD+WNLxkKx3GG0VIkRxuIZWS wx2nBJ9StKvDJb+nm/Hmk1TGMH8Avhjn+o9kJVaFtw/g2ZT9MA== X-Google-Smtp-Source: AGHT+IEwcD/4MKMKQJu37LcpnuG9K+qMWp5RkNfRV740ItTg9S9LjuAaltFzaayvFcqs4nApKFe++nrdLkZWg7D0CB0= X-Received: by 2002:a17:906:c41:b0:a2a:18ab:6387 with SMTP id t1-20020a1709060c4100b00a2a18ab6387mr2137392ejf.215.1705431426120; Tue, 16 Jan 2024 10:57:06 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> In-Reply-To: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> From: Warner Losh Date: Tue, 16 Jan 2024 11:56:55 -0700 Message-ID: Subject: Re: orch(1) for tty testing To: Kyle Evans Cc: freebsd-arch@freebsd.org Content-Type: multipart/alternative; boundary="00000000000057cd63060f14b2e8" X-Rspamd-Queue-Id: 4TDytC2XD3z53Lv X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --00000000000057cd63060f14b2e8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jan 15, 2024 at 12:55=E2=80=AFPM Kyle Evans wr= ote: > Hi, > > I wrote a tool for tty testing w/ lua scripts, inspired by expect(1) and > with some similarities, but explicitly without the goal of trying to be > compatible: > > https://git.kevans.dev/kevans/orch > > An example of its use is here: > > https://git.kevans.dev/kevans/tty-tests/src/branch/main/test_canon.orch > > Each spawn() creates a new pts(4) and allows us to drive I/O to the > process with write/match statements. I have one or two tests written > with it so far and the end result is, IMO, much less painful looking and > less error prone than the equivalent in C. > > It still needs a bit of polish (e.g., improved diagnostics when a match > fails), but I'd like to consider importing this somewhere for use in the > near future for tty testing given how much it simplifies. I can push it > to ports, but we have a private liblua in base so it could be built and > banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life just > a tad easier re: getting these to run in CI. It's pretty lightweight; > the orch binary on my amd64 system clocks in at ~27K, and orch.lua at 13K= . > > Any objections to importing this new tool into /usr/tests or maybe even > /usr/libexec? > Seems useful enough to include. For more than just testing... Warner --00000000000057cd63060f14b2e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jan 15, 2024 at 12:55=E2=80= =AFPM Kyle Evans <kevans@freebsd.o= rg> wrote:
https://git.kevans.dev/kevans/orch

An example of its use is here:

https://git.kevans.dev/kevans= /tty-tests/src/branch/main/test_canon.orch

Each spawn() creates a new pts(4) and allows us to drive I/O to the
process with write/match statements.=C2=A0 I have one or two tests written =
with it so far and the end result is, IMO, much less painful looking and less error prone than the equivalent in C.

It still needs a bit of polish (e.g., improved diagnostics when a match fails), but I'd like to consider importing this somewhere for use in th= e
near future for tty testing given how much it simplifies.=C2=A0 I can push = it
to ports, but we have a private liblua in base so it could be built and banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life just a tad easier re: getting these to run in CI.=C2=A0 It's pretty lightwei= ght;
the orch binary on my amd64 system clocks in at ~27K, and orch.lua at 13K.<= br>
Any objections to importing this new tool into /usr/tests or maybe even /usr/libexec?

Seems useful enough to in= clude.=C2=A0 For more than just testing...

Warner= =C2=A0
--00000000000057cd63060f14b2e8-- From nobody Tue Jan 16 19:22:42 2024 X-Original-To: freebsd-arch@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 4TDzRr04H4z57s5d for ; Tue, 16 Jan 2024 19:22:48 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDzRq4XhKz3xfC; Tue, 16 Jan 2024 19:22:47 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x731.google.com with SMTP id af79cd13be357-7831ed13d39so819954485a.0; Tue, 16 Jan 2024 11:22:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705432965; x=1706037765; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=g9iq+XbeD3soB6t0CPh6QnYDcJ/JkN9GdyVm6PkZMm4=; b=bap69O/2Aftl97Rd2WoHmsddjvJ0pxNvdA8wfO6oOWsbOHj3R9V3pqvCBqlDArApaM E+yVODnUW8iyR9+7pps+zp/osK2Wx93Hv2RylW3RUl9qOWgt68l9wJT3V4SawTdN4sSd LOgTZ0lcocY/MwV7qmZLHRCaTqaJ+ikfa3xJxO+Lpq16+aipmRnnLA3vk/JQc4PaTpRR HMND/cdiLECDi1iaBp0uYhy8ZwFKejziOYz8O13IPYjtbUQeCBKzFejNpiDS9qNwnkl1 5PO+XgK4Hui2q6OB7cgSJSP1FYO5nwgYGYNuGj6MgNPgp8JnTFCfJafq0kF9okalJKYx VubQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705432965; x=1706037765; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=g9iq+XbeD3soB6t0CPh6QnYDcJ/JkN9GdyVm6PkZMm4=; b=O3+RufAQAdztxV4peiCG6pI/Q2Ib8SIzqPOfen5bmM0uegpbOxub07aiSVbh5Wu5z3 0CKECckkde1t8Artm5hT1FOqmsnb6RMS/DUZ/Pxlux9EyLdr/iM82/iMIp1PgKMzWC7/ FZpNjYgTR+3QtztLnVjPy3qmWwVBrkLLWcI3Orqz6uH/9HaElDBr8jUIKvMilQvj8IwG aUOsuMCvRRxMJ/LQgdCKKZnwxj0Pz1AOK5u4i8YN7RL12dHpXH/vZPmTq0nMXyww4Z5W pZOt6b4birgery9SVJ4WAnTJ98Df/r+IKlSFHGHxg9XuNFlVGKYIM6CQJpmLsnLOjCMk AmTA== X-Gm-Message-State: AOJu0YzYlz+OHXf88bFhfuC+9aJzCiNKO/WlqACqwNG7MkoGT9SV3bpr +A77tsg+d0nss0cOnbnnM1rUihLgskQs9Q== X-Google-Smtp-Source: AGHT+IH1KSg08NBHZYmcH5Rcn3b7MAs85njba7sjX5dc5SlZYv0xefnVMp5UQQ9dfwIVcNZarimEYw== X-Received: by 2002:ae9:c10a:0:b0:781:5efd:403b with SMTP id z10-20020ae9c10a000000b007815efd403bmr8769985qki.13.1705432965012; Tue, 16 Jan 2024 11:22:45 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id z25-20020a05620a261900b00781ae860c31sm3943151qko.70.2024.01.16.11.22.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jan 2024 11:22:44 -0800 (PST) Date: Tue, 16 Jan 2024 14:22:42 -0500 From: Mark Johnston To: Kyle Evans Cc: freebsd-arch@freebsd.org Subject: Re: orch(1) for tty testing Message-ID: References: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> X-Rspamd-Queue-Id: 4TDzRq4XhKz3xfC X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Mon, Jan 15, 2024 at 01:54:54PM -0600, Kyle Evans wrote: > Hi, > > I wrote a tool for tty testing w/ lua scripts, inspired by expect(1) and > with some similarities, but explicitly without the goal of trying to be > compatible: > > https://git.kevans.dev/kevans/orch > > An example of its use is here: > > https://git.kevans.dev/kevans/tty-tests/src/branch/main/test_canon.orch > > Each spawn() creates a new pts(4) and allows us to drive I/O to the process > with write/match statements. I have one or two tests written with it so far > and the end result is, IMO, much less painful looking and less error prone > than the equivalent in C. > > It still needs a bit of polish (e.g., improved diagnostics when a match > fails), but I'd like to consider importing this somewhere for use in the > near future for tty testing given how much it simplifies. I can push it to > ports, but we have a private liblua in base so it could be built and > banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life just a > tad easier re: getting these to run in CI. It's pretty lightweight; the > orch binary on my amd64 system clocks in at ~27K, and orch.lua at 13K. > > Any objections to importing this new tool into /usr/tests or maybe even > /usr/libexec? This looks quite handy. I have some lua scripts which I use to checkout a src tree, build a VM image, boot the image and run tests, then download the resulting kyua DB, all with a single CLI command. I currently run the hypervisor under expect(1) and send commands over a pipe, but that was an expedient hack and I'd rather use something implemented natively. There are some existing lua expect ports, but orch looks simpler and I'll try it out to see if it's missing anything for my use-case. More generally, we lack a test framework which lets one boot and interact with VMs, and orch might be a useful component of that. From nobody Wed Jan 17 01:27:23 2024 X-Original-To: freebsd-arch@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 4TF7XY3bQvz56Wd8 for ; Wed, 17 Jan 2024 01:27:25 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TF7XY3981z4cBf; Wed, 17 Jan 2024 01:27:25 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705454845; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WU3/CQ05UTL8asxuoccjEUqVdvN6+1Fd/lVxyPq7IqY=; b=QCE2+X5evee0jA0T12yWEg5TmyjgZgwJ0ikhvbVSqn0j3f89SszXG0sNzvUG63UrWBrfbf avN3+cTnedJsuusjh3xJtyJ7K4uUTPZNBa6+H3ktPw25r6Xv2c2QAXeMOMWBOQsjPBIFBn 4GqVa3yNn9tseRUpeMgiV/zs8LQHG3JBESv2SnQS7NISBaoRieCxmG8fPhfqh49oKm55d2 B5tn0eFwC5EnQYEu3tq0QswriJZvby53gH1Z4dv3NvfAERbmdiDMe3iyF8yjf54vNYQepo Sq/qmoALak7jW4wiLLZ27/8ADoYz8KDpwf07TzvG6ib5gH9fI7kpuenkC73jkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705454845; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WU3/CQ05UTL8asxuoccjEUqVdvN6+1Fd/lVxyPq7IqY=; b=YDUtX1hl82MK4AZu9IJ+D2LBp29kEMJPR1xzFvxsWOBrdm7Cxm4ylI/ezzCWqVH1l2voQN ARsLg7P8UbKvBhZyOWFzXXQG914hCFhwLWPethl9GqhakyLrD/2IACFvvAsErWMQp/rBLG zepMh18oMXAi5rwgoRvd08VKfbbqBanLRPq6TAYsm/E5ltpZrjD7M+YYSG3M9mlrQ5JMe6 GYDXxvevyr0/EaHRx/nF/Kts8uvpm8WizyKdSM/hSub3XhmO9aK+H8I8793AjTNZpk1Ruz rhdUYkSHTZbXk+tWa6btEyvjMXiNVH5ums7/p6cJPz9ZrRoDDahJABgGzheF4A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705454845; a=rsa-sha256; cv=none; b=nrqXrPVnuSJYiN9Uj2XK7qHvLX5QvupOl0xBV2xmtyRwZn32y1CGUXC/+jEssQRGOk9O9P GlUuGXhtG0Vm6Rg3Ry346gZsncGDN95SYujtQiiVfeR+QqnYRNpn6Rd5Yb2O99CstknbXx Uq6rloBkq1602VijeQxro9V7NtvgSdHEvTu7/n71BNKqiUUPFs/GlMzwaYkcda48HMVSMK dXoQJ7dZIcV28Vn1IRAt/wrgz1VKzAPWBpxHSQA0LXsUkHhX0vhg/7MnW+HYLFLAAPtmtC eqsL2FdHpeg0FezXlc/0sBYBOA8O4dX0sN7PsQTEhQLND1UMEQhAfKgQujWJ/w== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4TF7XY0STLz1CyH; Wed, 17 Jan 2024 01:27:24 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: Date: Tue, 16 Jan 2024 19:27:23 -0600 List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: orch(1) for tty testing Content-Language: en-US To: Mark Johnston Cc: freebsd-arch@freebsd.org References: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 1/16/24 13:22, Mark Johnston wrote: > On Mon, Jan 15, 2024 at 01:54:54PM -0600, Kyle Evans wrote: >> Hi, >> >> I wrote a tool for tty testing w/ lua scripts, inspired by expect(1) and >> with some similarities, but explicitly without the goal of trying to be >> compatible: >> >> https://git.kevans.dev/kevans/orch >> >> An example of its use is here: >> >> https://git.kevans.dev/kevans/tty-tests/src/branch/main/test_canon.orch >> >> Each spawn() creates a new pts(4) and allows us to drive I/O to the process >> with write/match statements. I have one or two tests written with it so far >> and the end result is, IMO, much less painful looking and less error prone >> than the equivalent in C. >> >> It still needs a bit of polish (e.g., improved diagnostics when a match >> fails), but I'd like to consider importing this somewhere for use in the >> near future for tty testing given how much it simplifies. I can push it to >> ports, but we have a private liblua in base so it could be built and >> banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life just a >> tad easier re: getting these to run in CI. It's pretty lightweight; the >> orch binary on my amd64 system clocks in at ~27K, and orch.lua at 13K. >> >> Any objections to importing this new tool into /usr/tests or maybe even >> /usr/libexec? > > This looks quite handy. I have some lua scripts which I use to checkout > a src tree, build a VM image, boot the image and run tests, then > download the resulting kyua DB, all with a single CLI command. I > currently run the hypervisor under expect(1) and send commands over a > pipe, but that was an expedient hack and I'd rather use something > implemented natively. There are some existing lua expect ports, but > orch looks simpler and I'll try it out to see if it's missing anything > for my use-case. More generally, we lack a test framework which lets > one boot and interact with VMs, and orch might be a useful component of > that. That seems like a good exercise for it- feel free to get in touch. I wouldn't mind porting whatever you've written in expect(1) over and take the opportunity to fill in the feature gaps, regardless of whether you use the end result or not. From nobody Wed Jan 17 01:55:51 2024 X-Original-To: freebsd-arch@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 4TF89c2jcqz56ZYB for ; Wed, 17 Jan 2024 01:56:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TF89c16DVz4gdm for ; Wed, 17 Jan 2024 01:56:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-55818b733f7so9680459a12.3 for ; Tue, 16 Jan 2024 17:56:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1705456562; x=1706061362; 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=gobZftMiidsJ9Gtgrm8smILs1nV5hjMAK2ZPwvYYfE0=; b=t+AZbmc3gsaq9kDIxbJiJkNOtvLMqGk+3LVhYbUgeTfXRr3CpptABKJo/33EpOkvUj vtRg8kUdXKiI9a46wMF/fPIVFF7lFw2LPkTVRS2B4rHuVPdqZl63Bwe/IdB1lgjsSXdK ExTLxw1KXKTEGwM6tl4XuAzVPs6UxMe15OlHiVC/SW16dhsEGGO9Kwldp4QNHHzghiLF /u/cIIhwuPzbwwznLzkyeFVFcU8HnBF8GF9P51h2FO2QxvQ8eFoEiK15387sfAGRyILB SmIUU8hJd4SAjAVOBN8OzXKqwufCuTIIud1DZV0sMIZIBs4WUnQfBuYDfXTtEWT5rbsH o3yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705456562; x=1706061362; 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=gobZftMiidsJ9Gtgrm8smILs1nV5hjMAK2ZPwvYYfE0=; b=jTWbTqeDrXSOkMDc6bpFgidh+iKAzTr/MwEMECMmyj31U1PXAAsJdJiKgG9KCgZVS3 ZYlNs0ZZ45c3yJSO1O4T6equIAuOodG+LFX33/cz5TDrO7gZ8go4vscvaLUXnMLM7r03 5bZYhXqzaNbvhAX2w/H7Omihwr6RViSSVfXIEBqpWBF9h8NauXohoTTBJLjTi/FOWVUl c2e08ZxhxCVXuldKoWRURknQw6AMnfwqvlp4ZTG2a/HoipJiQcON4bc4UwFtmfkrqlJb LJ2vIdCwcnzzCJfn3vvScRnT8IDNHxtNRx3wUlIfEVto2KSO2Ekhyqdp2Iui3NcevNUI 5ywQ== X-Gm-Message-State: AOJu0Yxo/Snn9wcUlh9wzZ3aIYm04uJUIeYJ0qDGxzRCETfvmirSj1Ad lqH8i1ls9gvMJXMXn6Kot2UGIT20Y3C7xFGg2j7iFpHEik+1Er1RoL4eaitJCBg= X-Google-Smtp-Source: AGHT+IERJpw4TYmcRh7L8I33CPQZ3z5Aq6xz61OE84/AFe/XVxRid9JMWrztFtVMVl2Dz8bvOMJsdaQco4EO2rjSDD8= X-Received: by 2002:aa7:c2c6:0:b0:558:df3e:9eb7 with SMTP id m6-20020aa7c2c6000000b00558df3e9eb7mr3853714edp.6.1705456562504; Tue, 16 Jan 2024 17:56:02 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <478cf238-ab2e-4185-a5eb-4230b5efe735@FreeBSD.org> In-Reply-To: From: Warner Losh Date: Tue, 16 Jan 2024 18:55:51 -0700 Message-ID: Subject: Re: orch(1) for tty testing To: Kyle Evans Cc: Mark Johnston , freebsd-arch@freebsd.org Content-Type: multipart/alternative; boundary="00000000000096979e060f1a8cc2" X-Rspamd-Queue-Id: 4TF89c16DVz4gdm X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --00000000000096979e060f1a8cc2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jan 16, 2024 at 6:27=E2=80=AFPM Kyle Evans wro= te: > On 1/16/24 13:22, Mark Johnston wrote: > > On Mon, Jan 15, 2024 at 01:54:54PM -0600, Kyle Evans wrote: > >> Hi, > >> > >> I wrote a tool for tty testing w/ lua scripts, inspired by expect(1) a= nd > >> with some similarities, but explicitly without the goal of trying to b= e > >> compatible: > >> > >> https://git.kevans.dev/kevans/orch > >> > >> An example of its use is here: > >> > >> https://git.kevans.dev/kevans/tty-tests/src/branch/main/test_canon.orc= h > >> > >> Each spawn() creates a new pts(4) and allows us to drive I/O to the > process > >> with write/match statements. I have one or two tests written with it > so far > >> and the end result is, IMO, much less painful looking and less error > prone > >> than the equivalent in C. > >> > >> It still needs a bit of polish (e.g., improved diagnostics when a matc= h > >> fails), but I'd like to consider importing this somewhere for use in t= he > >> near future for tty testing given how much it simplifies. I can push > it to > >> ports, but we have a private liblua in base so it could be built and > >> banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life jus= t > a > >> tad easier re: getting these to run in CI. It's pretty lightweight; t= he > >> orch binary on my amd64 system clocks in at ~27K, and orch.lua at 13K. > >> > >> Any objections to importing this new tool into /usr/tests or maybe eve= n > >> /usr/libexec? > > > > This looks quite handy. I have some lua scripts which I use to checkou= t > > a src tree, build a VM image, boot the image and run tests, then > > download the resulting kyua DB, all with a single CLI command. I > > currently run the hypervisor under expect(1) and send commands over a > > pipe, but that was an expedient hack and I'd rather use something > > implemented natively. There are some existing lua expect ports, but > > orch looks simpler and I'll try it out to see if it's missing anything > > for my use-case. More generally, we lack a test framework which lets > > one boot and interact with VMs, and orch might be a useful component of > > that. > > That seems like a good exercise for it- feel free to get in touch. I > wouldn't mind porting whatever you've written in expect(1) over and take > the opportunity to fill in the feature gaps, regardless of whether you > use the end result or not. > Last summer's gsoc student wrote a bunch of Lua to do similar things with testing boot loaders against a kernel and minimal userland... Would be nice to have those in-tree and maybe using this. Warner --00000000000096979e060f1a8cc2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Jan 16, 2024 at 6:27=E2=80=AF= PM Kyle Evans <kevans@freebsd.org<= /a>> wrote:
O= n 1/16/24 13:22, Mark Johnston wrote:
> On Mon, Jan 15, 2024 at 01:54:54PM -0600, Kyle Evans wrote:
>> Hi,
>>
>> I wrote a tool for tty testing w/ lua scripts, inspired by expect(= 1) and
>> with some similarities, but explicitly without the goal of trying = to be
>> compatible:
>>
>> https://git.kevans.dev/kevans/orch
>>
>> An example of its use is here:
>>
>> https://git.kevans.d= ev/kevans/tty-tests/src/branch/main/test_canon.orch
>>
>> Each spawn() creates a new pts(4) and allows us to drive I/O to th= e process
>> with write/match statements.=C2=A0 I have one or two tests written= with it so far
>> and the end result is, IMO, much less painful looking and less err= or prone
>> than the equivalent in C.
>>
>> It still needs a bit of polish (e.g., improved diagnostics when a = match
>> fails), but I'd like to consider importing this somewhere for = use in the
>> near future for tty testing given how much it simplifies.=C2=A0 I = can push it to
>> ports, but we have a private liblua in base so it could be built a= nd
>> banished off into, e.g., /usr/tests/sys/kern/tty/, to make my life= just a
>> tad easier re: getting these to run in CI.=C2=A0 It's pretty l= ightweight; the
>> orch binary on my amd64 system clocks in at ~27K, and orch.lua at = 13K.
>>
>> Any objections to importing this new tool into /usr/tests or maybe= even
>> /usr/libexec?
>
> This looks quite handy.=C2=A0 I have some lua scripts which I use to c= heckout
> a src tree, build a VM image, boot the image and run tests, then
> download the resulting kyua DB, all with a single CLI command.=C2=A0 I=
> currently run the hypervisor under expect(1) and send commands over a<= br> > pipe, but that was an expedient hack and I'd rather use something<= br> > implemented natively.=C2=A0 There are some existing lua expect ports, = but
> orch looks simpler and I'll try it out to see if it's missing = anything
> for my use-case.=C2=A0 More generally, we lack a test framework which = lets
> one boot and interact with VMs, and orch might be a useful component o= f
> that.

That seems like a good exercise for it- feel free to get in touch. I
wouldn't mind porting whatever you've written in expect(1) over and= take
the opportunity to fill in the feature gaps, regardless of whether you
use the end result or not.

Last summer&= #39;s gsoc student wrote a bunch of Lua to do similar things with
testing boot loaders against a kernel and minimal userland... Would be nic= e
to have those in-tree and maybe using this.

<= /div>
Warner
--00000000000096979e060f1a8cc2-- From nobody Fri Jan 19 18:03:54 2024 X-Original-To: freebsd-arch@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 4TGnYg6Gn5z573MG for ; Fri, 19 Jan 2024 18:04:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TGnYg1SJVz4XyZ for ; Fri, 19 Jan 2024 18:04:07 +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=yMSp4UoA; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::530) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-55790581457so1345724a12.3 for ; Fri, 19 Jan 2024 10:04:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1705687445; x=1706292245; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=1tB1oOMrfyq9+nxq6i1xZMQa0y0dTX0j4e6ycYcAYlw=; b=yMSp4UoA27jbyB1cyebt/GoW81aRD+JeeYXOygmjLholeVCnQcbrAShn8rA3DBwzSr eOkFbAhyWz5fjrKhqgcrC5gFUI/kCqoOnCJeJWi9t7rhBrnxIRgIhsSwKaly3AowMCpF 28FECaPX/kknaG60cmEXCx7iNYKU5IF3uGjuFBLmqsUdymswoM3wBa0j1XaYBrsH+emj wouVGLExNfWDdUxQkaqZPkARUUOMaAV11WUzXQ0aXLVGWjbMMmYTrWdSj1o7NGWQ9E83 ePKfeQ86WXnX3/QPQjSmNtDrYbcsSH6l0/n0YSUX7jkWmsA4Aznljp3LXUl6WD3NAutv OgVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705687445; x=1706292245; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=1tB1oOMrfyq9+nxq6i1xZMQa0y0dTX0j4e6ycYcAYlw=; b=B56sZg71EHfiY2WpUxBzzyLYo1O3PgbdwlngC3duOdAxprFCS6Xvbz/Zfkhf+hVXa/ wN5M1epyWmvfG+HATcru1NRdvnhD8Nuj47oSvSpzq5PWI+RsK6wVnfFNBrqXpTdPT+QG Iva1StvqtkS4LfVPeoZW3WiNNjAdUGL4BahVAmAXbde1n9pfrK8AscLGj1HENcpLeemG 5SKqe16nGQmxMP7HQfbElYkVKfzjV8T++8wtXV5ue+3PKSuMXxWxfnh0yi9PhWmcBKro 3BB3PssXpAfYv5w09ndG4I+ymBVbKmbgvFmJ4Tu6zswvKiEsqZU3+Aa8Hfmr+eu31NwQ WgKw== X-Gm-Message-State: AOJu0YwgCO50LdcoVAFRt3FLHfi+RXZlJ7AKcA5cy7Vx5ZXRy/Bb0RA6 jRqFZd1egXZb1LDLG//YC3p/ZhNZ3YP7naVXIG73D16EhtXpJk6Fc6QC45+uf6NArIrfvXkMw7z GJEuRho7BEQaYadugoUC+RS67hwqXelYT0dzIp7tV3gWkS4R92Nw= X-Google-Smtp-Source: AGHT+IFgUOWh/HKkRbCAHFRNSEd/sViGVpRRCAPoPiJhPDR0688P6bFv/WCvxMSw56Dcua/fh06prKqUZjrT+AmC6kU= X-Received: by 2002:a05:6402:373:b0:55a:63b0:57f5 with SMTP id s19-20020a056402037300b0055a63b057f5mr86110edw.32.1705687445549; Fri, 19 Jan 2024 10:04:05 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 From: Warner Losh Date: Fri, 19 Jan 2024 11:03:54 -0700 Message-ID: Subject: PS3 Support Query To: "freebsd-arch@freebsd.org" , powerpc@freebsd.org Content-Type: multipart/alternative; boundary="0000000000004a44dd060f504e23" X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; 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]; TO_DN_EQ_ADDR_SOME(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::530:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4TGnYg1SJVz4XyZ --0000000000004a44dd060f504e23 Content-Type: text/plain; charset="UTF-8" Greetings, I'm wondering who is using FreeBSD/powerpc64 on a PS3 still? I tried to bring a PS3 off ebay up and was unsuccessful. Seems like hardware mods are required? Anyway, it got me thinking: Are there any other PS3 users out there? If not, then I think sadly we should consider retiring support for PS3. Comments? Warner --0000000000004a44dd060f504e23 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Greetings,

I'm wondering who is usi= ng FreeBSD/powerpc64 on a PS3 still? I tried to bring a PS3 off ebay up and= was unsuccessful. Seems like hardware mods are required?

Anyway, it got me thinking: Are there any other PS3 users out there= ? If not, then I think sadly we should consider retiring support for PS3.

Comments?

Warner

--0000000000004a44dd060f504e23-- From nobody Sat Jan 20 09:31:39 2024 X-Original-To: freebsd-arch@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 4THB8f3kGRz56gV9 for ; Sat, 20 Jan 2024 09:32:18 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4THB8d73TLz4Lx2; Sat, 20 Jan 2024 09:32:17 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1705743123; h=from:from: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; bh=Ev92jWJvH3DseIdCzgRG4Ecqf+DBOCIXwO+9O4W6SV4=; b=RMWB1C3/EW0NuqtNzYywEbPRLPjBzmE86UfJup7mmYzd1VcaVtZxFJgigvgcFrHxaMObvS 7xWu+d6gxy2mIla8glFgpfKZaJF80peRrEbThp0hZMAJQakS0JleHh/mZGFCgyUlYPA3Fu 6a3UsSNEsRew5w6ok57ZcqU9It/910rABsI9kwqslDJrmWZdpYqc9mXPq2LLsqoejGFovj ykRegRw7o0si4CzsvGUdHBV1L3hkRyabfPIL0SH4oIrWIWv6qL2S/ms2vTzkjaJOuHvpIO BKIX/BuPm53qhErUrR4NVahNXpbnL/u699h4RXU9Myknlz8qcNjYYXTAjjd5Pw== Date: Sat, 20 Jan 2024 10:31:39 +0100 From: Alexander Leidinger To: Warner Losh Cc: freebsd-arch@freebsd.org, powerpc@freebsd.org Subject: Re: PS3 Support Query In-Reply-To: References: Message-ID: <249e0f16411602946fd84bac1adbb5d1@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_0a3e46e68a4c9138fa5f17e14516a7a1"; micalg=pgp-sha256 X-Rspamd-Queue-Id: 4THB8d73TLz4Lx2 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_0a3e46e68a4c9138fa5f17e14516a7a1 Content-Type: multipart/alternative; boundary="=_a21a35cbce9a66445bf2d6c38eb7b4b4" --=_a21a35cbce9a66445bf2d6c38eb7b4b4 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-01-19 19:03, schrieb Warner Losh: > Greetings, > > I'm wondering who is using FreeBSD/powerpc64 on a PS3 still? I tried to > bring a PS3 off ebay up and was unsuccessful. Seems like hardware mods > are required? IIRC it depends on an old PS3 OS version which still allows to run linux (at some point Sony removed that support). AFAIR it was not intended to take over the complete control of the PS3. So you would not only have to get the reare luck of getting a PS3, you would need to get one with an very outdated OS. This are just memories just from a bystanders view, I never had a PS3. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_a21a35cbce9a66445bf2d6c38eb7b4b4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Am 2024-01-19 19:03, schrieb Warner Losh:

Greetings,
 
I'm wondering who is using FreeBSD/powerpc64 on a PS3 still? I tried t= o bring a PS3 off ebay up and was unsuccessful. Seems like hardware mods ar= e required?

IIRC it depends on an old PS3 OS version which still allows to run linux= (at some point Sony removed that support).  AFAIR it was not intended= to take over the complete control of the PS3.

So you would not only have to get the reare luck of getting a PS3, you w= ould need to get one with an very outdated OS.

This are just memories just from a bystanders view, I never had a PS3.

Bye,
Alexander.

--
= http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http:/= /www.FreeBSD.org    n= etchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF
--=_a21a35cbce9a66445bf2d6c38eb7b4b4-- --=_0a3e46e68a4c9138fa5f17e14516a7a1 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmWrkwsACgkQEg2wmwP4 2IYuGQ/9Hhxlrlzt91hlnLDbFqKYG7/0NuAeeDc204Cu6MDWLWJgP3Pek5p6Rw1G m+mKenAlkRlkFiISTRduxva7pNCO4Frq+J97ecrDsc4nthZ/sp4RQCPgEhdDj40O NxqyjJ7enF/ztjNRUwxPqT3zKuGqoDQBG1mx1Yf3yKup2UGSXKTzh6iwWEcLkd82 +NugyLKMUZtEQ22LgqWBWp9G/KJKAfvkIYlR3sfy+zEXCS+iYz0/0meuREpS5JP5 htgf8wmOfxZGyp6kKnoXF8U5t1gRdM+xmxY7wGTR/YSezfVxunagTQcV4NtUYE86 9gw3yqon/+5S0zgNUk56eHwtjq6zqzCCxdHmxk361XLq0zZbjVY4kaHdd/3V2eKQ HQEIc4zVh4ASmWF7PHpZs7Hq5b9blzDd1xRXj2FG9FGewe84cQe+ij3pxbYRCAe2 PC/tQ+XgUeDE/EcE3zJ3xGlWJJMkBkCb97HraeBoUbE5DTqW5l6QBtbxF6pt9nlq 0xEVrzjNcIihTymvC5/0xbH7qyHfU/fKl8TmE4QXSrAY8A4YdtydrwCX8iCbhUrm axKdHANDOBWFozE8Cvcw2AC7R6HtPlffl86XTOLsWmYtItsPOGfg09GzljXjfsh3 yYiRvxz5Jb5yOC1yGv9O7NPOfEp0L8h80YzOkuUzBFgyDOGgpbo= =WrO+ -----END PGP SIGNATURE----- --=_0a3e46e68a4c9138fa5f17e14516a7a1--