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.0 required=5.0 tests=RCVD_IN_DNSWL_NONE
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 13501 invoked from network); 2 Dec 2020 04:41:49 -0000
Received: from ewsd.inri.net (107.191.116.128)
  by inbox.vuxu.org with ESMTPUTF8; 2 Dec 2020 04:41:49 -0000
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Tue Dec  1 23:40:44 -0500 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id d7fceb80 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Tue, 1 Dec 2020 20:40:35 -0800 (PST)
Message-ID: <2CBE3EA1DC65A1D691F7EAEB82F90D0A@eigenstate.org>
To: lockywolf@gmail.com
To: 9front@9front.org
Date: Tue, 01 Dec 2020 20:40:34 -0800
From: ori@eigenstate.org
In-Reply-To: <871rg8dfnz.fsf@delllaptop.lockywolf.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: content-driven SSL over ActivityPub extension blockchain-based extension hosting database 
Subject: Re: [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues
Reply-To: 9front@9front.org
Precedence: bulk

Quoth Vladimir Nikishkin <lockywolf@gmail.com>:
> 
> Sure, it may be irrelevant to the network at all. I have to idea, to be
> honest, this is my first time doing anything with 9front.
> 
> But the `nbdsetup` task is otherwise called "setup network
> configuration", so I thought it might be relevant.
> 
> `/n/newfs` is indeed empty.
> 

I strongly suggest qemu or vmware instead of virtualbox; there's
a history of emulation bugs on vbox, so it's very much a "you're
on your own" platform. I've been told it's better now, but I don't
think anyone tests it regularly.

And, yeah -- what josuah said, this is definitely an issue with
mounting the install disk, and not the network. Make sure that
there weren't any errors reaming it or anything.