Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FUSE for macOS is no longer open source

colatkinson.site

Post reply on HN
Print view View original

401–407 of 407 posts

Re: FUSE for macOS is no longer open source

#401

Post by ivebeenthere »

II2II wrote: post #137
pjmlp wrote: post #69

Earlier quoted context omitted.

This will keep going on, until FOSS community accepts that beyond university projects, someone pumping up their CVs, having a company sponsorship, or being able to pimp it up with some kind of subscription/consulting, there is little to no money to be made and everyone has bills to pay.

If the end goal is earning an income, sure. Yet there are other reasons to adopt an open source model. It is useful as a collaborative model. For that to happen, people have to be willing to submit code and the maintainer has to be willing to accept code. It sounds like that was not happening here.

He is not getting any contributions. It would need a Mac kernel expert to fix most bugs anyway.

Re: FUSE for macOS is no longer open source

#402

Post by mechanical_jane »

mr__y wrote: post #328
progval wrote: post #207

Earlier quoted context omitted.

> with a clause that forbids removing/disabling that message This sounds similar to the "invariant sections" clause of the GNU Free Documentation License; except you're talking about software instead of documentation. > I assume that many developers or end-users[1] at home are perfectly fine with a messagebox popping up once a month with a "f## off" message Some people are really angry about GNU Parallel's citation "…

>Some people are really angry about GNU Parallel's citation "nag the way I understand this, is that by requiring to interactively enter "will cite" the ability to run it as part of a larger script is broken. This would break a cron-job as well. The non-interactive nag in output would not cause such probles. The non-interactive message in output of course could create problems on its own - especially if the nag would…

> This would break a cron-job as well.

How so? GNU Parallel only outputs the notice if stderr is a terminal. I think you did not try this. Am I right about that?

It is litteraly the 3rd point in https://git.savannah.gnu.org/cgit/parallel.git/tree/doc/cita...

Did you try any of the other situations? Or are you simply speculating that this might cause problems without actually testing?

Re: FUSE for macOS is no longer open source

#403

Post by trasz »

chinesempire wrote: post #400
trasz wrote: post #392

Earlier quoted context omitted.

And how’s that relevant? Another example would be the closed source VMWare ESX, which is definitely not GPL-compatible.

It is relevant because you can't legally distribute GPL code linked to non-gpl compatible code. In fact VMWare and FSF/SFC have been fighting over it for the past 10 years. Even though the court dismissed the claim, VMWare announced that will remove the code in question ( https://www.vmware.com/company/news/updates/march-2019-hellw... ) You can read more about it here https://linux.slashdot.org/story/19/03/09/0423243…

Erm, from the links you've pasted it clearly follows that you can - that's what the court decided, twice, isn't it?

Re: FUSE for macOS is no longer open source

#404

Post by pilif »

saagarjha wrote: post #371
pilif wrote: post #349

Earlier quoted context omitted.

Macs do have such a toggle. You can boot from the recovery partition, launch the terminal and issue the `csrutil disable` command. This will turn off all the security features that have been added over the years, including the “Catalina Vista” prompts people were complaining about in September. The reason this requires booting from the recovery partition is to make it impossible for malware to flip the switch and to…

> This will turn off all the security features that have been added over the years, including the “Catalina Vista” prompts people were complaining about in September. I installed it back in June, so my memory might be a bit hazy, but as far as I’m aware SIP doesn’t control TCC.

You are right. That's controlled by gatekeeper which you disable with `spctl --master-disable`

Re: FUSE for macOS is no longer open source

#405

Post by saagarjha »

pilif wrote: post #404
saagarjha wrote: post #371

Earlier quoted context omitted.

> This will turn off all the security features that have been added over the years, including the “Catalina Vista” prompts people were complaining about in September. I installed it back in June, so my memory might be a bit hazy, but as far as I’m aware SIP doesn’t control TCC.

You are right. That's controlled by gatekeeper which you disable with `spctl --master-disable`

You sure turning off Gatekeeper turns off TCC too?

Re: FUSE for macOS is no longer open source

#406

Post by eropple »

gdfasfklshg4 wrote: post #393
eropple wrote: post #390

Earlier quoted context omitted.

I agree that that's part of it!

Basically it comes down to companies having systems for paying invoices. It's hard to get small and medium sized companies to make charitable donations - especially to open source which doesn't even help their corporate social responsibility goals.

Yes, exactly. The hard part is how, and that's what I think can be done. ;)

Re: FUSE for macOS is no longer open source

#407

Post by chinesempire »

trasz wrote: post #403
chinesempire wrote: post #400

Earlier quoted context omitted.

It is relevant because you can't legally distribute GPL code linked to non-gpl compatible code. In fact VMWare and FSF/SFC have been fighting over it for the past 10 years. Even though the court dismissed the claim, VMWare announced that will remove the code in question ( https://www.vmware.com/company/news/updates/march-2019-hellw... ) You can read more about it here https://linux.slashdot.org/story/19/03/09/0423243…

Erm, from the links you've pasted it clearly follows that you can - that's what the court decided, twice, isn't it?

Actually the court did not decide that.

They disagreed that vmkernel is a driver, they did not rule that GPLv2 software can be combined with incompatible licenses.

The source code for vmklinux, The actual kernel module, is released by VMWare for this exact reason.

Post reply on HN