Introduction
I've just installed a networking simulator Called Netkit. On Debian stretch stable. Using the official installation guide here.
Installation
After setting the correct paths and installing. I then run the check_configuration.sh script.
Everything is checked OK, and it has found the terminal emulator xterm which is needed for netkit. And recieve the complete message.
[ READY ] Congratulations! Your Netkit setup is now complete!
Enjoy Netkit!
The Problem
Running netkit using the command:
vstart pc1
The xterm netkit-kernel emulator starts running. However I'm getting an infinite loop of the same error message:
ubda: can't open "home/foo/netkit/pc1.disk" failed, errno= 13
So im guessing it's because the file is missing? if so how do i obtain it? and if not, what is causing this error. I've followed the install guide completely.
I'm assuming your system is not a 32bit system. Netkit is only supported on the 32-bit architecture(unless the compatibility libraries are installed). Hence I would suggest you download a 32-bit VM(instead of installing the libraries) and run Netkit on the same(worked fine for me).
Check position of your lab-folder..
Related
Hey I changed my System from Linux to Windows and I would like to install Node.js via .exe. The problem I have is, that I get an Error Pop-up. How could I fix it?
What I tried:
I checked already the permissions and I got also the confirm-box for the admin and everything seems to be normal.
Install Windows 10 ISO via bootable stick and Rufus in MBR and GPT and also by creating an usb via MediaCreationTool.
Thanking you in anticipation
Yeah, I got in this issue too. There is already an approved bug on the maintainers GitHub: https://github.com/nodejs/node/issues/39224. So assume that a fix will be available in the next days.
Short term solution: Install the version before the latest (e.g. 14.17.1): https://github.com/nodejs/node/issues/39224#issuecomment-872702653. This worked for me
System - Win 7 64 bit.
Nodejs - node-v6.9.4-x64.msi
Installation error - Another installation is in progress. You must complete that installation before continuing this one.
Solutions that did NOT work - Run as admin, Run via commandline as admin, log had same error i saw in installer, don't install online docs option,
Please help me to fix this. Thank you !
This will not be an issue with your NodeJs installation, it might be because of your previous installation (might be any other software) which might be still in progress or not exit properly.
To solve your issue, please try restarting your machine once and install. This will indirectly kill your previous unstable installation and allow you to install NodeJs
I had this issue with '2017-03-21, Version 6.10.1 'Boron' (LTS)'. Restarting my PC solved the issue.
P.S. However, this issue seems to be specific to the NodeJs installer. I tried installing other programs after the NodeJs installation threw up this error and they installed fine (even before the restart).
I'm trying to compile a Go app for linux/arm and keep running into problems on my Ubuntu machine. When I run GOOS=linux GOARCH=arm go build in my source directory, I get tons of erorrs that are variations of:
# github.com/huin/mqtt
gccgo: error: unrecognized command line option `-marm`
Running gccgo --help informs me that options starting with -g, -f -m (and others) will be passed on to any sub-processes started by gccgo, so I don't know which process it's sending -marm to.
Any clues? Ubuntu 14.10 LTS, 64bit
So thanks to a clue by Dean, I've worked out the issue and solved it.
The issue was caused by me installing Go via apt-get, then removing it (via apt-get), then installing Go from the golang website. There were still files left over from the first install, which were probably older versions and therefore didn't have support for the -marm flag.
I was going to wipe my dev machine anyway, so I did, installed Ubuntu again, installed Go from the website (not via apt-get) and everything worked first time. If you don't want to wipe your machine, then just make sure to look around to see if there are version conflicts.
I've been stung by this sort of thing before (when installing node.js via apt-get, realising it was many versions out of date, then removing, and installing node.js via source), so if anyone is reading this, be careful when installing software via apt-get, then upgrading, as you might have similar version issues like I did!
I am trying to follow this tutorial for building and running an MPI application on an ARM based Ubuntu 11.10 system.
When installing open-mpi environment on my PC machine, the sample program runs well. However, trying the same on the ARM machine, the terminal hangs up and I need to kill the MPI process from a second terminal in order to release it.
The MPI packages I installed using apt-get, on both machines, were mpi-default-dev and mpi-default-bin, so I assume that the packages are as updated as they can be.
The first sample program in the tutorial makes every process prints a "hello" message with some info. On the PC I get messages from all 8 processes (although running on a single core) and then the program ends. On the ARM, I get no output at all. The program is just stuck immediately after launch.
Any idea on what's wrong? I am not sure even where to start to debug this?
Update: I tried removing the OpenMPI package and install the alternative MPICH2 package - but the result is just the same.
Ubuntu 11.10 did not ship with a functional Open MPI implementation for ARM (although it may have shipped with a nonfunctional one). Ubuntu 12.04 did.
I would recommend building your own Open MPI from source - available at http://www.open-mpi.org/software/ompi/v1.6/, unless you can update to a more recent version of Ubuntu.
Alternatively, you could rebuild the 11.10 package using the fixes pointed out in https://bugs.launchpad.net/ubuntu/+source/openmpi/+bug/949044.
I am completely new to both Macs and Node.js, so sorry if this one is a bit basic.
I am running Mac OS X 10.5 (Leopard) and have just installed the last version of Node.js (released version, not built from source).
Whenever I attempt to run Node or do an NPM install, I get the following error message:
FATAL ERROR: CodeRange::GetNextAllocationBlock Allocation failed - process out of memory
Does anyone know what the problem is? If not, what would be the next steps to figure this out?
Edit: It turns out that if I run these commands a few times then they eventually work. So my work-around is to keep repeating the command until I get success. This is better than nothing but still not acceptable. Software like WebStorm, which needs to execute these tools, doesn't know about this workaround and fails all the time.
The issue seems to show up when running the distributed build of Node on anything pre OSX 10.6.
You can manually build the binary yourself if you don't have the option to upgrade your OS.
http://therobotsbrain.blogspot.com.au/2012/03/installing-nodejs-on-os-x-105.html
I'm running X.5.8, and node 0.10.13 was giving me this error message. I tried some earlier versions of node, and 0.10.3 works while 0.10.4 gets the error message. This is the x86 version, x64 seems to crash at .3 but works at .0. Oh wait, it's more complicated than that. Seems to make a difference when I make a symlink to the app in /usr/local/bin, it crashes. more often. Try a few different ones see which work for you.
I really need to get a new laptop.
download here: http://nodejs.org/dist/