From: ori@eigenstate.org
To: skhds1@gmail.com, 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Thu, 6 Jun 2019 22:00:46 -0700 [thread overview]
Message-ID: <AD7C2E3B67E706ABADE446CBF2F1D048@eigenstate.org> (raw)
In-Reply-To: CAHZWWqr2Prp4_yJDGCUrmioR80YQ_iK0mUYJu9oYe9BDAHJG8g@mail.gmail.com
> Hello, newbie here.
>
> I've installed 9front for 64bit (I did the cross-compiling too), but
> there was some failure during "confignet", so the internet overall is
> not working (cat /net/ndb returns nothing).
>
> I thought at that time that I can just run that later, but I am having
> trouble doing so. Also, since I just bypassed that part, I can't
> recall the message for it.
>
> So my question boils down to :
>
> 1. Can I run confignet again AFTER installation? If there is, can you
> point me to the right methods?
I've never done re-run the installer after installation, but it's still
around:
ls /bin/inst/
Note that inst/confignet only sets some environment variables for
future steps to run, but doesn't actually save them. That appears to
be done in
inst/ndbsetup
Inst/ndbsetup appends a line to /lib/ndb/local. On my system, that line
looks somewhat like:
sys=meathoook ether=560001dbcf68
> 2. I am unsure of how I can diagnosis the network problem when the
> installation itself failed, so a direction of where to look might be
> nice.
Take a look at 'man ipconfig', which is used for configuring your
network cards. Running it manually should give you either a working
network or some errors that can be debugged.
> Re-installing won't really be a problem right now, as I haven't done
> anything that extensive in my current system. So I am considering that
> as an option, although I'm feeling a little bit too lazy for it.
You also learn more from fixing a broken system.
> Also, I'm new to mailing lists in general (I am not an expert
> programmer and my current job is to write Javascripts for a web
> page...), and this is basically my first mail to any mailing lists, so
> please understand if I'm doing something wrong.
Nope. Nothing wrong.
> Anyways, thanks in advance! I'm looking forward to tinkering with my
> new 9front system :)
>
> Thank you,
> Joonhyeok Yeom.
next reply other threads:[~2019-06-07 5:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 5:00 ori [this message]
2019-06-10 4:46 ` 염준혁
2019-06-10 5:30 ` 염준혁
-- strict thread matches above, loose matches on Subject: below --
2019-06-17 7:24 cinap_lenrek
2019-06-17 8:59 ` 염준혁
2019-06-17 6:58 cinap_lenrek
2019-06-17 7:21 ` 염준혁
2019-06-17 4:19 cinap_lenrek
2019-06-17 5:01 ` 염준혁
2019-06-17 6:45 ` 염준혁
2019-06-14 1:16 cinap_lenrek
2019-06-17 3:56 ` 염준혁
2019-06-13 8:48 ori
2019-06-14 0:52 ` 염준혁
2019-06-14 13:35 ` hiro
2019-06-11 16:15 ori
2019-06-12 1:14 ` 염준혁
2019-06-12 9:25 ` hiro
2019-06-11 9:49 vp
2019-06-11 13:26 ` 염준혁
2019-06-10 15:51 ori
2019-06-11 11:10 ` 염준혁
2019-06-10 6:59 ori
2019-06-10 8:44 ` 염준혁
2019-06-10 10:58 ` 염준혁
2019-06-10 6:54 ori
2019-06-10 6:43 vp
2019-06-10 12:47 ` Ethan Gardener
2019-06-07 4:46 염준혁
2019-06-07 5:34 ` [9front] " Stanley Lieber
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=AD7C2E3B67E706ABADE446CBF2F1D048@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=skhds1@gmail.com \
/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).