AndrewDavis

Hi,there's a lot to unpack here.

> They could always move to a compatible license? > No, it was always designed to be hostile to Linux from the outset. It's a project that doesn't want to interoperability with Linux

I'm not sure why you've jumped here. I didn't mention a specific project or licence.

But, nonetheless I'm going to assume you mean OpenZFS.

1. No they can't change the license. Much like Linux contributors retain their own copyright, OpenZFS can't just change the license. The only group that could hypothetically change it is Oracle given the clause the steward of the license can release a new version, but that's unlikely and Oracle has absolute nothing to do with the existing project.

2. Staying on the license and compatibility. It's really quite confusing on what's compatible in the eyes of Linux. The very fact they have separate export and export GPL symbols suggest Linux as a project sanctions non GPL modules, and considers them compatible if they only use those symbols, perhaps in the same vein as they consider the syscall boundary to be the compatible with non GPL? If someone who is actually in the know about why there are two sets of exports if love to be know.

3. Always designed to be hostile to Linux. Whether that's true or not is the debateable, there are conflicting opinions from those who worked at Sun at the time. Also the comment criticises a community that had no hand in whether or not it was intended to be hostile to Linux or not. In the end is copyleft software, very similar in spirit to the Mozilla public license. And by definition copyleft licenses are inherently incompatible without specific get out of the jail clauses to combine them (see MPLv2 for example).

4. Re interoperability. Strongly disagree. OpenZFS takes great strides to be compatible with Linux. Each release a developer sends hours pouring over Linux changes and updating a compat layer, and the module remains compatible to compile against multiple Linux versions at any one time, there are even compat patches to detect distro specific backports that while the version hasn't changed the distro have back ported things that change behaviour. That's a serious commitment to interoperability. And a large number of openzfs devs do their work against Linux as their primary platform, hence why the FreeBSD rebased their ZFS upstream on ZFS on Linux, leading it to become the official upstream OpenZFS. I can't see how anyone could say in good faith they don't care about Linux compatibility unless they haven't looked over at the openzfs project for over a decade.

4. Re why do I think Linux folks should maintain APIs for them.

The way you worded this strongly implies I was saying Linux should maintain an API for them. In no way did I say that. I was replying to a post that was adament that Linux doesn't remove things. I provided a perspective that Linux does in fact remove things. I wasn't arguing for maintaining any API, Linux doesn't even guarantee internal APIs for themselves. I was pointing out changing a symbol export from export to everyone to export GPL only isn't changing it, given it's the exact same API they've just simply removed it for some groups.

None the less I think it'd be great if Linux could maintain some APIs for out of tree modules. But they don't and that's fine. I just find changing exports from open for everyone tomorrow GPL only to be rather hostile.

Really, no one in either of these communities had any say in their license (sans Torvalds). Both creating great stuff for we as users to run. And it'd be great if people working on free software could get along, and those in the peanut gallery didn't prescribe malcontent between them because of a difference in license they didn't pick.

That's all a matter of perspective.

Is moving a symbol from EXPORT_SYMBOL(some_fun) to EXPORT_SYMBOL_GPL(some_func) actually changing the API? Nope, the API is exactly the same as it was before, it's just changed who is allowed to use it.

From the perspective of an out of tree module that isn't GPL you have removed stuff.

I'm honestly not sure how one outside the kernel community could construe that as not removing something.

I can only speculate, but maybe they're referring to the same thing Andrew Morton meant when he described ZFS as a rampant layering violation.

ie ZFS isn't just a file system. It's a volume manager, raid and file system rolled into one holistic system vs for example LVM + MD + ext4.

And (again I'm only speculating) in their micro kernel design want to have individual components running separately to layer together a complete solution.

> If it didn't actually work, it would've been discarded by companies long ago

That makes the assumption that company hiring practices are evidence based.

How many companies continue to use pseudo-science Myers Briggs style tests?

Microsoft had a POSIX personality on NT since its release in 1993.

https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem

Then with the release of XP it was replaced with: https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

> WSL 1 was relatively innovative, integrating Linux application compatibility into the Windows operating system itself

Both FreeBSD and Illumos were running Linux applications (at various levels of compatibility) many years prior to wsl v1. Joyent even went as far as re-implementing the Docker api to allow running OCI images natively in LX zones. Hence, it wasn't even that novel of an idea.

If I remember correctly you need both. Program the cells to be X organ cells, and provide a scaffold for them to grow on.

I just restarted using RSS recently. And I discovered I can also use it to track software releases (on github). The url is the release page with .atom appended. Eg

https://github.com/openzfs/zfs/releases.atom

Two? I envy you.

I really wish I had the space for another CRT. One day I hope to have a second for two player time crisis.

I've decided that titles are mostly meaningless in software. What X title means in one org means another in a different one with near zero overlap, and another title might have considerable overlap with a differently named one but viewed lowly, borderline pejoratively at another org. Eg system admin vs devops vs sre. In one org sysadmins are deploying desktop machines with no expectations they can cut code, in my old role as one I was working with Linux systems, building glue and orchestration, and when things go wrong debugging backend code written by a development team. Something far closer to the work of "devops" or "sre".

As a aside, I find your example of doctor as amusing because it's overloaded with many considering the term a synonym of physician, and the confusion that can cause with other types of doctors.

Perl has subroutine signatures now. You can write

sub foo ($x, $y, $x) { ...}

It's just syntactic sugar, so you still can't pass in multiple lists, and the list must be the final parameter.

Not sure if you've deliberately put in two bugs there haha

1. shift only shifts off the first element.

2. (if classify this as a bug) using $a and $b are frowned upon because they're the default variables when using sort.

I visited Denmark a few years ago and went to the Hans Christian Anderson museum in his home town of Odense.

It's absolutely fantastic, the museum is presented like a story you walk through his life.

Highly recommend!

I gave up and started buying $4 rshirts. Why? Because each year the clothes I'd buy were were on quality than my previous clothes.

When buying a $4 shirt I know the price:quality ratio, it's cheap:crap. Whereas majority of the time buying more expensive it might be slightly better, but it's still expensive:crap.

I really enjoy the TV show Escape to the Chateau. A lot of couple buy an old run down French chateau and move in with their two kids. Each episode is roughly them doing up a part of it. Often with ideas for making money out of it.

Very much light entertainment, but it's eye opening how significant of a restoration and maintenance burden it is.

`dir` was also in CP/M. Though it didn't have a concept of a file hierarchy, so it listed all files on the disk (but did support supplying a pattern to filter against).

It'd be interesting to see open data about this.

My understanding is games with microtransactions optimise for "whales", people who spend inordinate amounts of money. While the majority of users don't pay anything, or at most very little.

Yes! It's reusable, but not duplicated.

They definitely aren't unique even without reboots. Postfix uses the inode number as a queue id. At $dayjob we've seen reuse surprisingly quickly, even within a few hours. Which is a little annoying when we're log spelunking and we get two sets of results because of the repeating id!

(there is now a long queue id option which adds a time component)

Similar to you it is incredible at bringing down fever in my kid. I've seen my kid go from whimpering looking like death, to be crawling about playing happily again in half an hour. With the behaviour change tracking with her temperature coming down.

As an adult using it as a pain killer it has been ineffective.

Even that sounds easy compared to my country. In Australia a constitutional change requires a referendum, with a double majority condition to pass. Specifically it requires the vote in over half the states to be in favour, in addition to the overall national vote in favour.

Classic Mitchell and Webb skit https://www.youtube.com/watch?v=CS9ptA3Ya9E

The difficulty I find with the wayback machine is it's great when you find a dead link, put it in wayback and voila you can go to it.

But if you're searching for now defunct pages it's hard unless you know the url already. eg if I wanted the page to the q6600 for example, how do I even get that?

> Usually this is because of the Modern Standby/S0 crap and in many cases there isn't a solution because the BIOS removed support for S3.

Also, modern windows won't let you select S3 sleep if it detects support for S0. There used to be a simple registry edits you could do but Microsoft seem to have closed that loophole.

I chose my current laptop because in the BIOS it has a sleep setting, and if you pick the oddly named "Linux sleep" it disables S0 sleep. Thereby allowing S3 sleep in Windows.

This is after having a previous laptop act like a heater to my lunch in my bag, or being dead despite being full charged after waking up overnight and running hard till the battery ran out. Or perhaps the most obnoxious, my wife closing her laptop with a video running and at 3am her laptop bringing itself to life waking us up.

> Supporting ZFS in a UNIX kernel requires excessively extensive modifications to the design and implementation of the VMM, namely:

FYI: Apple did a bunch of that work. They ported ZFS to OSX shortly after it was open sourced. With with only support landing in 10.5. With it being listed as an upcoming feature in 10.6.

But something happened and they abandoned it. The rumour is a sun exec let the cat out of the bag about it being the next main filesystem for osx (ie not just support for non root drives) and this annoyed Jobs so much he canned the whole project.

Redraw facilities are available in most countries? Refinancing etc? Genuinely curious.

For example (in Australia), my mate recently spent $40k, drawn out of his mortgage on solar panels, battery, double glaze windows, heat pump heating and cooling, gas stove to induction, gas hot water to heat pump and is currently investigating drawing more to upgrade roof insulation.

Yep that was it.

Or phrased another way, if local first software is so difficult why are we doing it at all when these devices worked BEFORE they had software.

The worst washing machine I've ever had is my current one, and it isn't even a "smart" appliance. It has just enough software to be worse than my one with dials for everything.

Similarly I went on an XP odyssey late last year. I acquired a retired workstation from $dayjob that I decided to turn into a retro XP game machine. It was very late for XP but within a generation or two before Intel, Nvidia and the motherboard provided drivers (Ivy bridge and GTX 660 GPU).

But that didn't get you through the installer... I discovered a plethora of alternative install media with built in community drivers providing support for nvme drives, modern ACPI extensions etc.

It's so complete you can install it on today's current hardware.

It is a shame that Orion is Mac and iOS only. I found this statement[1] in response to a request for it on other platforms

> We are getting a lot of repeat questions about windows/linux/android version and sometimes it appears that users think that the team is choosing not to work on these platforms. The situation is quite different and simpler - we do not have the resources to hire a new team to do any of these platforms yet.

> And since Orion is funded by its users only, it is entirely up to the number of subscribers and Orion+ sales we have that will enable funding a new team to make Orion for any new platform. And building a browser is not cheap, especially one on top of WebKit.

> Ways you can help accelerate this is: > Contribute to Orion development with your time > Help spread the word about Orion to attract more users > Get Orion+ and financially support developmet

This is a tricky situation to be in. A lack of resources to support multiple platforms, but the solution being more subscribers. But the incentive structure is perplexing. Those supporting development going to be those already using Orion. And those not on Mac/iOS are unlikely to financially support a browser they can't use in the hopes it might one day come to a platform I use.

[1] https://orionfeedback.org/d/2321-orion-for-windows-android-l...