From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 0EDBB30BA2 for ; Fri, 1 Nov 2024 22:46:27 +0100 (CET) Received: from wopr.sciops.net ([216.126.196.60]) by 9front; Fri Nov 1 17:45:27 -0400 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1730497518; 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: in-reply-to:in-reply-to; bh=EVyC5XKuTF8fL6zZspuXtXyv17PAffFRjbx7EV9CGVU=; b=m79DI7wHBTc9L3g/ae5/1/vW67qvo4G+H+NhW9zLI2aKF/DOdK1m464xQQT7IJ3R7scPyR EDxiK5yraO/PV9q9KmoUOK4CInXeert+uX+vfx3ezNl4sMvI6/RRXQNAPu3KLVaPVl2GVz 6nD8BivRK3FuWQ/DtRyQawZAJ4xvfCw= Received: by wopr.sciops.net (OpenSMTPD) with ESMTPSA id c7dca935 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO) for <9front@9front.org>; Fri, 1 Nov 2024 14:45:17 -0700 (PDT) Message-ID: <29790B4B8F4496B039C4AD89CDC64077@wopr.sciops.net> Date: Fri, 01 Nov 2024 22:45:22 +0100 From: qwx@sciops.net To: 9front@9front.org In-Reply-To: <2EAE56A49E96CD45AC9B9DED47A695A6@thinktankworkspaces.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extended extensible DOM WEB2.0 over WEB2.0 blockchain DOM frontend Subject: Re: [9front] hjfs type mismatch Reply-To: 9front@9front.org Precedence: bulk On Fri Nov 1 18:42:31 +0100 2024, william@thinktankworkspaces.com wrote: > Does it matter which image I use? I can use both regardless of architecture and I often do although > I do notice a performance issue if it doesn't match the host OS. Of course it matters. I'm assuming you're only running 386 and amd64 vm's, and to oversimply to the extreme, one is 32-bit, the other is 64-bit. There's no multilib or whatever on 9front. Another more important difference is that amd64 is de facto the standard (followed by arm64), and 386 is used very rarely -- meaning that there probably are more bugs in 386 just because fewer people test and use it. Furthermore I am very doubtful that aws or other providers are running 32-bit systems limited to less than 4gb of RAM etc., hence the "performance hit" you're probably referring to when you're running a 386 vm on there. In any case, now we don't know if it's problems specific to amd64 or 386, or anything. Cheers, qwx