Caldera, Yellow Dog & Turbolinux were also significant names from history. And is Gentoo really the first source based distro or just the "last of the first" since others like Sorcerer disappeared the way Yggdrasil did leaving us with Slackware?
Slackware will always be special to me as my first Linux distribution and I still consider switching back to Gentoo on occasion, but I have no delusion that these distro's role in history make them major distributions now.
That's why the emacs is a great OS... joke isn't just a joke. Emacs is a platform with a bunch of tools I'd hate to lose, like ediff, hexl-mode, org-mode and even simpler things like isearch, flyspell-mode and rectangle editing.
Emacs is a contain for lot of tools and you can switch between. It can even shell out. You can write one-lines on the fly. Getting back to Inception, a good bit of emacs is written in emacs
/me waits for a low 4 digit UID guy to extoll the virtues of "ed".
You've got me boxed in a corner here.
If it were under GPL3 it would be safe. There are probably a few other licenses with similar patent protection explicitly built in.
Their patent pledges are useless. They have been written in the past such that they could sell the patents to a 3rd party who would be free to sue. They grant a non-revocable license or it does not count.
Don't worry. I'm sure Windows 12 can access your microphone too. I haven't heard Microsoft deny using it, but I'm sure they would if you'd only ask.
Linux has plenty of good games. You just have to decide if you love the Windows exclusive games more than you hate the way Microsoft treats you. Then accept your decision. If you stick with Microsoft, it's your fault, not theirs. Several people have moved on. More will. The market is reacting.
I guess I've always assumed the bar for maintaining interface stability for users space was much higher. The interface line has always been between kernel and users space. I'm not ready to give that line up to the systemd team. But we have to support our users so we don't get to choose. So I try to make sure lapses don't go unnoticed in the hopes that systemd culture might change with enough "gentle nudging" from the community.
And I've never been what I would call a Stallmanite either, but seeing where all the concerns are with mobile and IoT devices not getting updates, I can see that we are about to find Richard was right, yet again.
Most recent on slashdot was breaking the backgrounding of processes.
Which is disabled by a simple option in the config file. Which Debian has done, btw.
Yes, but I won't how long until this non-default config breaks something else. I don't trust them.
My product had our (once) portable init script broken in RHEL7.2 by a systemd change that now declares that the init.d script cannot be a symlink to the product installation area
Really? Are you sure? I just tried that and it works.
Yes. From https://bugzilla.redhat.com/sh...
"Note that the real location of the init script must be on the partition that is mounted in the initial ramdisk (initrd)"
I could agree with this, but my problem is upstream. The systemd folks keep breaking or changing things that were once standard, documented and could be counted on. Most recent on slashdot was breaking the backgrounding of processes. Given the creation of an 'su' function I'm waiting for su, sudo and the like to be declared broken and for the accompanying posix calls to be superseded by function in libsystemd.
My product had our (once) portable init script broken in RHEL7.2 by a systemd change that now declares that the init.d script cannot be a symlink to the product installation area. This worked in RHEL 7.1 with systemd and with prior releases and other (pre-systemd) distributions. Yet another gentle nudge to doing things the systemd way, or else.
If I trusted upstream to maintain a interface that could be made portable I'd be less resistive to systemd. It provides some good features, even if the architecture is awful. A sane, portable re-implementation for be made once the current architecture shows its problems. But a re-implementation won't be possible with an upstream that breaks compatibility without a second thought.
The fact that the community has accepted this so willingly makes me dread the day that Linus gives up the reigns of the kernel. It's not unlikely that we'll wind up with the kernel being led by a twit, a push over or a committee.
Never call a man a fool. Borrow from him.