From: Derek Johansen <djohanse678@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Errors in nano-x add_to_full3.sh script
Date: Sat, 18 Mar 2017 22:17:56 -0600 [thread overview]
Message-ID: <CAOv0vdk=ewzn3LtG=3--crdLErp2QUU7g4guCGKV1Lco_-kfmA@mail.gmail.com> (raw)
1) I get the following errors when I run sudo ./add_to_full3.sh nterm:
djohanse@djohanse-VirtualBox:~/elk2/elks/nano-X/src$ sudo
./add_to_full3.sh nterm
Adding nano-X demos to ELKS full3 image
Enter demo file in bin directory to copy to full3 image as script parameter
./add_to_full3.sh: 9: ./add_to_full3.sh: shopt: not found
./add_to_full3.sh: 17: [: !=: unexpected operator
umount: full3: not mounted
umount: /mnt/elks: not mounted
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop0 1424 1286 138 91% /mnt/elks
-e
Run nterm in full3 with
qemu.sh
2) When I run .sudo ./qemu.sh to bring up ELKS, then try to run nterm,
about 50% of the time I get a "not enough memory" error. The other
times I get an xterm which is very cool.
Thanks,
Derek
next reply other threads:[~2017-03-19 4:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 4:17 Derek Johansen [this message]
2017-03-19 4:19 ` Errors in nano-x add_to_full3.sh script Jody Bruchon
2017-03-19 17:46 ` Georg Potthast 2
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='CAOv0vdk=ewzn3LtG=3--crdLErp2QUU7g4guCGKV1Lco_-kfmA@mail.gmail.com' \
--to=djohanse678@gmail.com \
--cc=linux-8086@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).