3 ms·
If I'm not mistaken, the author recommends saving the file to /opt/local/etc/oui.txt but the plist runs bash /opt/local/bin/macrandomize.sh I think
by jarin 12y ago
If I'm not mistaken, the author recommends saving the file to
/opt/local/etc/oui.txt
but the plist runs
bash /opt/local/bin/macrandomize.sh
I think one or the other probably needs to be changed, unless I'm missing something here.
- webXL 12y agoThe file that you download is oui.txt. The shell script visible on that page is what you're supposed to save as macrandomize.sh. My guess is that he leaves a few steps out so that only people who know what they're doing actually attempt this.
- LeoPanthera 12y agoSaving stuff into /opt/local is a terrible idea anyway, it's the default path for MacPorts.
- aroch 12y agoHonestly using MacPorts is a terrible idea. If you need non-standard packages uses homebrew -- which goes out of its way not to break system components, unlike MacPorts.
- LeoPanthera 12y agoHuh? The whole point of MacPorts is that it builds its own dependencies, thereby not touching the "system components" at all. It's entirely self-contained in /opt/local, or /Applications/MacPorts for GUI apps. I've been using it for many years and it's never broken anything. (Except occasionally itself.) I would argue that you're far more likely to have stuff already installed in /usr/local than in /opt/local. Homebrew is currently trendy but there was nothing wrong with MacPorts. Declaring the entire project to be "a terrible idea" is simply ignorant.
- aroch 12y agoI've been using MacPorts for the better part of decade and some ports in it clobber system files without warning. I've been bitten one too many times by that