From: Vladimir Nikishkin <lockywolf@gmail.com>
To: ori@eigenstate.org
Cc: 9front@9front.org
Subject: Re: [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues
Date: Wed, 02 Dec 2020 13:45:28 +0800 [thread overview]
Message-ID: <87y2igbx06.fsf@delllaptop.lockywolf.net> (raw)
In-Reply-To: <2CBE3EA1DC65A1D691F7EAEB82F90D0A@eigenstate.org>
I should have read the log output better.
The `copydist` task actually fails with the `bucket 9 is full` error.
I expected the installer to fail too at failed tasks. No wonder it can't
find what does not exist.
I didn't notice that such a large drive would be needed, as the FQA
says, 30Gb. I just took the .iso size, multiplied its size by 10, and
expected that to be enough.
Anyway, thank you everyone.
ori@eigenstate.org writes:
> 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.
--
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
next prev parent reply other threads:[~2020-12-02 5:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:19 Vladimir Nikishkin
2020-12-02 0:03 ` Josuah Demangeon
2020-12-02 4:03 ` Vladimir Nikishkin
2020-12-02 4:40 ` ori
2020-12-02 5:45 ` Vladimir Nikishkin [this message]
2020-12-02 16:46 ` ori
2020-12-02 17:12 ` Stanley Lieber
2020-12-02 18:07 ` ori
2020-12-02 19:03 ` Stanley Lieber
2020-12-03 0:35 ` kvik
2020-12-03 0:52 ` Stanley Lieber
2020-12-03 1:02 ` [9front] Cannot ori
2020-12-03 1:28 ` Stanley Lieber
2020-12-03 1:53 ` ori
2020-12-03 2:54 ` Xiao-Yong Jin
2020-12-03 3:11 ` Stanley Lieber
2020-12-03 3:22 ` Alex Musolino
2020-12-03 3:35 ` kvik
2020-12-03 16:07 ` kvik
2020-12-03 16:36 ` Stuart Morrow
2020-12-04 0:39 ` Alex Musolino
2020-12-02 7:15 ` [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues Iruatã Souza
2020-12-02 16:44 ` ori
2020-12-03 18:02 ` Stuart Morrow
2020-12-03 18:18 ` hiro
2020-12-03 18:32 ` Stuart Morrow
2020-12-03 18:46 ` hiro
2020-12-03 18:53 ` Stuart Morrow
2020-12-03 19:37 ` hiro
2020-12-06 3:52 ` sl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2igbx06.fsf@delllaptop.lockywolf.net \
--to=lockywolf@gmail.com \
--cc=9front@9front.org \
--cc=ori@eigenstate.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).