From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11002 invoked from network); 21 Jul 2023 20:35:58 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 21 Jul 2023 20:35:58 -0000 Received: from naffnet.org.uk ([62.30.227.12]) by 9front; Fri Jul 21 16:32:58 -0400 2023 Received: from site.naffnet.org.uk (localhost [127.0.0.1]) by naffnet.org.uk (Postfix) with ESMTPS id E56405FAB6 for <9front@9front.org>; Fri, 21 Jul 2023 21:32:55 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=naffnet.org.uk; h= Message-ID:From:Subject:To:MIME-Version:Content-Type; s=adsp; bh=Vml6ZPznsN4dOe1dgOqp6uH9udo=; b=PSt7giZ1STBLv87Q1w3Gd4+mzJ1i UAbdqiQhjiwASXmNwOfJAQEvsIERQpopKw4BF+w3r4uJ06BJz7dZ+AVrM4FtgR4o cwCCD+FNWfwfEwsvvikkRh2zmYF22kXr3jgzAge6i/wppKllYslXEtSuOVADOSxb Jy2USF4IgWSVkfw= ARC-Seal: i=1; a=rsa-sha256; cv=none; d=naffnet.org.uk; s=adsp; t= 1689971576; b=abIUpQTHRJ3uJHejwAC9U6bYRLVkfbUJuvzpCo5VadwMPdiIai 39v/B+EJDw1pPWas/0fFBSfT7TNXUx1TteBgLscQlSga5j6jaUFkzfuFnf+hHxYI /TGvitxav2O1hEHCDorfKwxxv8lx9EfiaPby2sy71eDE2aX4qgI4vw3w0= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= naffnet.org.uk; h=from:to:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding; s=adsp; bh=IRLpVOpqe11s+wi4w9+FULqYx/Mioi0du88c2LRidC4=; b=TdL5 8VU6LgttjuITsYKIp9dOyefLIx2syUHWBhI+4J5qHq8wD5suNBBK87oM8LtLPoz0 rEme3Tt3tN3a49cINfo4a3rt366bl1mknLFDbjQenPUXju0zkqngGbW0gETIkUCW PyQv0PpUvbwD8b8zO1qf11Iz291uRl2twBwG5xk= ARC-Authentication-Results: i=1; naffnet.org.uk; dkim=pass; spf=pass smtp.mailfrom=naffnet.org.uk (connected ip 192.168.0.7); dmarc=none X-Assp-Version: 2.8.1(23131) on naffnet.org.uk X-Assp-ID: naffnet.org.uk m1-71575-01489 X-Assp-Session: 7F8A22B0F4B0 (mail 1) X-Assp-Envelope-From: dave@naffnet.org.uk X-Assp-Intended-For: 9front@9front.org X-Assp-Client-TLS: yes X-Assp-Server-TLS: yes Received: from unknown ([192.168.0.7] helo=site.naffnet.org.uk) by naffnet.org.uk with SMTPS(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.8.1); 21 Jul 2023 21:32:55 +0100 Received: from DaveLaptop (Dave-Laptop.naffnet.org.uk [192.168.250.208]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by site.naffnet.org.uk (Postfix) with ESMTPSA id 5AD63C1288 for <9front@9front.org>; Fri, 21 Jul 2023 21:32:55 +0100 (BST) From: "Dave Woodman" To: <9front@9front.org> References: <16899707650.65CeDaC8.6255@lsd.chicago.il.us> In-Reply-To: <16899707650.65CeDaC8.6255@lsd.chicago.il.us> Date: Fri, 21 Jul 2023 21:32:54 +0100 Message-ID: <003501d9bc12$87328ad0$9597a070$@naffnet.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQItgLPyzW9jJITqdtn5yC8r6wIIvq8dIV0Q Content-Language: en-gb List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: flexible component out-scaling frontend Subject: RE: [9front] 9front Successfully Installed; USB Weirdness Reply-To: 9front@9front.org Precedence: bulk Hi, Progress indeed! I would guess that the hub in the keyboard might be the root of this evil. Dave. -----Original Message----- From: Jay F. Shachter Sent: Friday, July 21, 2023 9:19 PM To: 9front@9front.org Subject: [9front] 9front Successfully Installed; USB Weirdness Esteemed Colleagues: I have successfully re-installed 9front, and it boots. In a few paragraphs, I will speculate why the previous installations (with only one exception), did not complete. Prior to the re-installation, I destroyed the 5-Gigabyte slice of disk onto which 9front had been previously installed, and recreated it with a size of 20 Gigabytes. I also had to zero out the beginning of the slice, because until I did that, the 9front installation program skipped the repartitioning phase. I am now able to boot into a working 9front system, except for some USB weirdness that I shall describe in a moment. So it seems that the first time I installed 9front, the 5-Gigabyte slice of disk was not large enough to contain it (which surprises me), but the installation program did not detect, and report, that the slice of disk was not large enough to contain the system that was being installed onto it (which also surprises me). Now, as for why so many of my other installation attempts failed, I have a theory. I have not thoroughly investigated whether the theory is true, because life is too short to thoroughly investigate everything in the world that puzzles you, but maybe it will interest you. I have a USB keyboard, which itself has 2 USB ports on it. I normally stick my USB mouse into one of those ports, and then I stick the keyboard into whatever computer I am currently working with. I think the successful installation, among all the unsuccessful attempts, took place when my USB keyboard was not stuck in to the computer onto which I was install 9front, but, rather, into another computer, where I was scrolling thru https://lunduke.locals.com/post/4184409/how-to-install-9front-a-plan-9-fork. When I attempted to install 9front when the USB keyboard was not connected to the computer, then the installation worked. I know this explanation sounds preposterous, but it is the only theory, as of this moment, that I have. Now for some additional, thoroughly perplexing, complexity. I have two operating systems on my computer that can generate GRUB menus: a Linux system, and a Solaris system. The Linux GRUB menu is installed onto (if I may use the Linux terminology) /dev/sda and /dev/sda10; the Solaris GRUB menu is installed onto /dev/sda13. Each GRUB menu has a menuitem that invokes the other one. Thus: menuitem 'Solaris GRUB Menu' { set root=(hd0,13) chainloader +1 } and menuitem 'Linux GRUB Menu' { set root=(hd0,10) chainloader +1 } This is necessary to be able to access all the operating systems on the computer, because the Linux GRUB menu cannot boot Solaris (or it can but I haven't figured out how), and the Solaris GRUB menu cannot boot OpenBSD (Solaris has a bad version of relocator.mod, the bug was reported and fixed years ago, but Oracle has never upgraded its GRUB). Now for the USB weirdness. Each of these two GRUB menus has been furnished with the following menuitem: menuitem '9front' { set root=(hd0,14) chainloader +1 } When I boot 9front from the Linux menu, I cannot use the USB keyboard. I can use the USB mouse only if I take it out of the keyboard port and stick it in directly to the computer. But when I boot 9front from the Solaris menu, I can use both the USB keyboard, and the USB mouse when it is connected to the USB keyboard. This is completely bewildering. Apparently something is happening in the Solaris GRUB menu that renders the USB keyboard visible to the 9front system. I have no idea what. If anyone reading this has any notion why 9front is unable to see the USB keyboard when it is booted one way, but is able to see the USB keyboard when it is booted another way, I would welcome hearing it. Jay F. Shachter 6424 North Whipple Street Chicago IL 60645-4111 (1-773)7613784 landline (1-410)9964737 GoogleVoice http://m5.chicago.il.us jay@m5.chicago.il.us "But when she traced the killer's IP address ... it was in the 192.168/16 block!"