From: Georg Potthast 2 <nospam@georgpotthast.de>
To: ELKS <linux-8086@vger.kernel.org>,
Derek Johansen <djohanse678@gmail.com>
Subject: Re: Errors in nano-x add_to_full3.sh script
Date: Sun, 19 Mar 2017 18:46:49 +0100 (CET) [thread overview]
Message-ID: <1493615259.71217.1489945609581@webmail.strato.com> (raw)
In-Reply-To: <CAOv0vdk=ewzn3LtG=3--crdLErp2QUU7g4guCGKV1Lco_-kfmA@mail.gmail.com>
I am not at my development PC for several days now. However, on my distro I did not need "#!/bin/bash" but I can add it. The other messages appear since the script tries to unmount first to be on the save side. Also I did add a "df" command to see how much space is left on the floppy image after adding the demo file.
I usually disable the network drivers and the dj compression for slip to get enough space. I think nterm will then work for you all the time.
Georg
> Derek Johansen <djohanse678@gmail.com> hat am 19. März 2017 um 05:17 geschrieben:
>
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-03-19 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 4:17 Errors in nano-x add_to_full3.sh script Derek Johansen
2017-03-19 4:19 ` Jody Bruchon
2017-03-19 17:46 ` Georg Potthast 2 [this message]
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=1493615259.71217.1489945609581@webmail.strato.com \
--to=nospam@georgpotthast.de \
--cc=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).