From: raingloom@protonmail.com (Raingloom)
Subject: [9fans] Raspberry Pi 3 B+ image of 9front
Date: Sat, 5 Jan 2019 22:44:10 +0000 [thread overview]
Message-ID: <G-63q-6ybS4eclnVqthd6j5asR7AyErEJYqGY-n0p_TxRZJsDEa9io3m7WY-0FgvleWEs4v-CJLwexyTgDy7BA2jcLahxQGgcRvKu3IIG6c=@protonmail.com> (raw)
In-Reply-To: <2ECD349844717870DA8862A351DA2ED6@felloff.net>
> build bootable hjfs sdcard image
>
> =================================
>
> cd /sys/lib/dist
> mk /tmp/mysdcard.pi.img
This last step fails with:
mk: don?t know how to make '/n/src9/sys/lib/sysconf g/proto/cmpdistproto? in directory /sys/lib/dist
next parent reply other threads:[~2019-01-05 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ECD349844717870DA8862A351DA2ED6@felloff.net>
2019-01-05 22:44 ` Raingloom [this message]
2019-01-05 23:37 cinap_lenrek
2019-01-06 0:48 ` Raingloom
-- strict thread matches above, loose matches on Subject: below --
2019-01-05 19:13 cinap_lenrek
2019-01-05 17:08 Raingloom
2019-01-05 21:49 ` Chris McGee
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='G-63q-6ybS4eclnVqthd6j5asR7AyErEJYqGY-n0p_TxRZJsDEa9io3m7WY-0FgvleWEs4v-CJLwexyTgDy7BA2jcLahxQGgcRvKu3IIG6c=@protonmail.com' \
--to=raingloom@protonmail.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).