Answer Best answer as chosen by user franco265
One option would be to just create a simple shell script. You'd want to test this with OS X, but it should be as simple as:
sudo sysctl -w net.smb.fs.kern_deprecatePreXPServers=0
Save the bolded part and name it something like nas_enable.sh or some such. Then you'll need to run chmod +x on the full path of the file. So say you saved it to your desktop, and your username is "joe", then it would be something like: chmod +x /Users/joe/Desktop/nas_enable.sh
Once you do that, then you can just add nas_enable.sh to the login items in system preferences.
That only causes the file to trigger when you login, which is probably a better option for now, especially if you have little to no idea what you're doing at the Unix command line. Seems a pretty safe bet given your clumsy terminology (no offense intended BTW, just pointing out an observation) to try and describe the situation. You probably don't want to go messing with the lower level Unix layer too much, because Apple may change something on a whim and just not bother to tell anyone because now that OS X is pretty well established they want people to forget that all Apple did was modify FreeBSD a little and slap on their own spiffy GUI. It's not like the old OS 6-9 days when Apple was doing the full OS stack top to bottom, now they're standing on the shoulders of the FreeBSD developers to a large extent. There's nothing wrong with that, and it's all perfectly legal, I'm just a big proponent of giving proper attribution. I base some of my work on the work of others, I think it's only proper that I give them credit for their part laying the groundwork.
Anyway, since Apple tries to hide the Unix layer from everyone as much as possible, they could argue that they're free to change anything and everything about it, as long as the Aqua GUI and Cocoa API based apps keep working. That's really about all the more Apple ever guarantees will remain the same, and indeed the lower level parts of Mac OS X have undergone a number of fairly major changes since 10.0. So even if you added your program to a lower level configuration file, it might be when 10.7.5 comes out, they just completely blow away the file you're using and replace it with a fresh copy. All because they never guaranteed that file would remain the same. BTW, this is just a small taste of what app developers have to deal with on a daily basis. So while my solution might have a few drawbacks, it also avoids a few major pitfalls. Kind of a balancing act that you have to play.
Was this reply helpful? (0) (0)