I had updated some node stuff on my system one day (macOS 10.13.6). Later, when I went to work on a Laravel project, I discovered somewhere along the line I had broken something. Laravel would not run.
I thought perhaps my packages for this project were messed up so I tried reinstall them via
npm install , but that was erroring. After a lot of frustration and research, I narrowed it down to the node-gyp package causing the problems. It appears it doesn’t support spaces in paths (that’s what this conversation was saying at least). The space in question here is the space in my main macOS user home directory path. I have my home directory on a separate drive from my system. That drive is named “User Drive”. node-gyp was trying to write some temp files inside my home dir and the error message was saying something along the lines of can’t find “Drive/myusername/yadayada”. Well, that’s because it’s not “
Drive/myusername/yadayada“, it’s “
User Drive/myusername/yadayada“! I find it very odd that a mature software in 2019 would have such an issue ????
On the main node-gyp page, I found that I can set the temp directory to something other than my space-having home path. I just did this:
I was then able to run
npm install which fixed my laravel project. All was good again.
When using Google Chrome’s DevTools,
Ctrl-Shift-C) will toggle inspector functionality. So much nicer than hunting and pecking for the little magnifying glass icon!
For those of you wondering, “websitewelcome.com” is HostGator.
I downloaded CentOS 5.2 Minimal Installation v1.3 pre-made VMWare virtual machine. After I upgraded CentOS from 5.2 to 5.4 (
yum upgrade), my network connection stopped working because it wasn’t getting a dhcp address. Turns out my ifcfg-eth0 file had the wrong “HDADDR”.
Luckily the solution was easy:
- Make note of the “HWaddr” from it’s output. You’re looking for a hex value that looks something like: 00:0c:29:72:46:d6
/etc/sysconfig/network-scripts/ifcfg-eth0 and make sure the HWADDR in that file is the same as the HWaddr from the ifconfig command
That solved the problem for me
I have two clients that I’ve grandfathered in working on their PCs. Everyone else I told — in much prettier language — to get a Mac or go to hell. One of those clients experienced a nice little BSOD stating: “UNMOUNTABLE_BOOT_DEVICE … Stop: 0x000000ED (89d28900, c000009c, 00000000, 00000000)”.
Ugh, with windows crap like this, I could care less about what caused it and why. Let’s just cut to the part where I found the solution to this problem. I found the answer on how to fix this at MSGOODIES. I wanted to dupe their info here in case that page goes away. All credit goes to this post on MSGOODIES!
- Boot off of a XP CD
- Type “r” to go into recovery console
- Run these commands:
chkdsk c: /r /p
That fixed the issue for me. Hope it does for some other poor windows souls. Thanks guys!
I’ll just preemptively ask that you don’t post comments asking for assistance. The above information is all I know or care to know. Like I said before … Windows can go to hell! 😉