Sponsored link
Vyatta –
Linux & Open Source
Alternative to Cisco –
Advanced Routing,
Firewall, VPN, QoS..
Free Download ->
| |||||||||||
Novell's IRC session on the Microsoft dealNovell's IRC session on the Microsoft dealPosted Nov 28, 2006 9:53 UTC (Tue) by nix (subscriber, #2304)In reply to: Novell's IRC session on the Microsoft deal by khim Parent article: Novell's IRC session on the Microsoft deal
What `more intimate access' does udev use? netlink sockets use the socket API: normal system calls. inotify is a normal system call. Digging through /sys uses open()/read()/close(), normal system calls.
Sorry, I don't think that merely *reading /sys* binds you by the requirements of the GPL (if it does, then reading /proc does too, and I can think of a good few proprietary apps that do that, and nobody complains.)
(Log in to post comments)
Novell's IRC session on the Microsoft deal Posted Nov 28, 2006 11:47 UTC (Tue) by khim (subscriber, #9252) [Link] Sorry, I don't think that merely *reading /sys* binds you by the requirements of the GPL (if it does, then reading /proc does too, and I can think of a good few proprietary apps that do that, and nobody complains.) /proc and /sys are quite different: /proc is decoupled from kernel internals, /sys is 1-to-1 mapping for kernel structures. Yuo can as well claim that your program is not bound by GPL if it uses just /dev/kmem to change the kernel and install 10Mb of code there: you are just using open()/read()/close(), right ?
Novell's IRC session on the Microsoft deal Posted Nov 28, 2006 23:58 UTC (Tue) by nix (subscriber, #2304) [Link] This is where the law leaves me behind, I'm afraid. If using syscallsalone is considered not to impose tight enough coupling to contaminate with the GPL, I can't see how using syscalls alone to read a particular filesystem can be considered tight enough either.
(But then this is all completely academic for me anyway as everything I've
|
|||||||||||