![]() In fact many companies are looking for developers who are commiters in a successful open source project since that's a very good sign for useful competence. due to canceling the project because of some kind of pressure from another big software company.ītw, are you sure it's not unlawful in your country if a company wants to supervise its employee's free time? At least it is in most European countries. Otherwise NTFS write support on OS X may have never happened, e.g. Luckly several people dealing with Apple and having negative experiences in the past have warned us about their unethical practices, so we didn't rely on them and kept working openly. Perhaps you know that one of our developers was hired by Apple to work on NTFS write support in 2005 and we all agreed to dual licence our past contributions (GPL and BSD or an Apple specific one) in exchange getting the newly developed Apple code back. If it weren't done this way then there wouldn't be open source, freely available read/write NTFS driver for Mac OS X, Linux, FreeBSD, NetBSD, DOS, and Haiku today. Many people contributed over the last 7 years and this can't be changed. The source is GPL because of historical reasons. ![]() But since you were doing mostly Mac OS X specific distinct work (scripts, etc) and the changes to NTFS-3G source code are publicly available elsewhere (Csaba Henk's performance enhancing ublio, compilation fixes) thus it weren't a real issue. ![]() If you linked with or made modifications to it then you must have released the source code. What you were doing was a violation of the NTFS-3G licensing. You can do the later more freely but not with the former. Szaka, if you want to discuss this further, just send me an email.įor one, I don't quite know the effect of linking to a GPL library versus an LGPL library. For one, I don't quite know the effect of linking to a GPL library versus an LGPL library. Licensing is a complicated issue that I don't fully understand (I'm an engineer, not a lawyer). Mostly, I want to make it easy for a company like Apple or Parallels to use the bundle if it suits their needs. However, once WWDC is over, it shouldn't be long before I have an answer from them.Īlso, I haven't decided how to license the code I've written, but I've been leaning towards a BSD-style license. Unfortunately, the people that need to "sign off" on it (essentially, just see what I'm doing and say "OK") are extremely busy this week and next. My new tools actually link to ntfs-3g, but I can't release them because I haven't yet gotten clearance from my employer. The previous iterations were based around a shell script, but it was woefully inaccurate in some cases. I've still been working on it in my spare time, and the result is several scripts for Xcode and a slew of C code. I will if/when my employer gives me the go-ahead in fact, distributing it from the NTFS-3G site would probably be good. Recently we also created a new forum for Mac OS X users: See "Adding a user to a group.Why don't you publish your contribution open source, distribution unrestricted just like the NTFS-3G project and its Fink and MacPorts ports do? -) would happily integrate and publish your contribution and give write access to the development source repository. If mount succeeds but no share appears in the FinderĮnsure the user belongs to the group that may use the share. Server: Įxtra Options (Advanced): -oallow_other -oumask=7002 -odefer_permissions ssh has a chmod of 700 and authorized_keys has a chmod of 600.Īdd shares as "Favorites" with the following properties: Option C (all users): Run in terminal: sudo defaults write /Library/Preferences/.GlobalPreferences NSUmask 2Ĭreate a user: sudo useradd Ĭreate /home//.ssh/authorized_keys and paste the earlier copied outputĮnsure. Option B (current user only): Run in terminal: defaults write -g NSUmask -int 2 ![]() Ignore the warning it only applies to restricting permissions further. Option A (current user only): Install and use TinkerTool to enable group writable permissions (Octal 002) by default. Generate public/private keys: ssh-keygen -tdsa Give the group read/write access and force new items to be part of the directory's group: sudo -R chmod 2770 įorce all new files in the directory to be group writable: sudo setfacl -d -m 'g::rwx' Ĭonfiguring a client and the corresponding server user Have a group own the directory: sudo chown : ![]()
0 Comments
Leave a Reply. |