Re: Errors in nano-x add_to_full3.sh script

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 sin=
ce 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 add=
ing the demo file.

I usually disable the network drivers and the dj compression for slip to ge=
t enough space. I think nterm will then work for you all the time.

Georg

> Derek Johansen <[email protected]> hat am 19. M=C3=A4rz 2017 um 05:17=
 geschrieben:
>=20
>=20
> 1) I get the following errors when I run sudo ./add_to_full3.sh nterm:
>=20
> djohanse@djohanse-VirtualBox:~/elk2/elks/nano-X/src$ sudo
> ./add_to_full3.sh nterm
> Adding nano-X demos to ELKS full3 image
>=20
> Enter demo file in bin directory to copy to full3 image as script paramet=
er
>=20
> ./add_to_full3.sh: 9: ./add_to_full3.sh: shopt: not found
> ./add_to_full3.sh: 17: [: !=3D: 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
>=20
> 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.
>=20
> Thanks,
> Derek
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html