Choice is not a matter of just pressing a button and have it magically appear. Someone has to actually maintain it. The Devuan developers think that they can do that. If so then that's great. It's sad that they don't think that they can do the same thing within Debian though I understand their reasoning. It takes a lot of time and effort to get into Debian and they want to be more pragmatic.
Modern NetworkManager releases also include a handy tool called nmtui which is basically the GUI implemented in curses. Nmcli can sometimes be a bit unintuitive so it's a good thing to have around.
Keep in mind that Mac OS X supports case-sensitive HFS+ filesystems, and has done so from Mac OS X 10.3 on (2003). All you have to do is create a partition with that particular flavour of HFS+.
Stepping back from HFS+ they've even supported case-sensitive file systems long before that since you could use UFS on OS X. Even OS 9 supported it but I don't remember if you could boot that from it.
However, Adobe refuses to support case-sensitive filesystems. The Photoshop installer refuses to install on a case-sensitive filesystem, and Lightroom geolocation support is broken on case-sensitive filesystems, and always has been. Of course this limitation is not documented in their sales documentation, and the official fix is to reformat the partition...
Yep. The Adobe suite won't even open files over NFS.
The GPL has never had a problem with bundling programs with different licensing or linking LGPL into non-GPL, or GPL into non-GPL for that matter; it's only if you distribute that mix that GPL has a problem with it. What you do on your own computer is up to you.
The GPL is not bypassed becaused that's not what it was designed for. The GPL was not designed to prevent you from doing useful things on your own computer. You just can't give the software to someone else and not at the same time give them the same freedom that you got. Downloading GPL software and linking it locally is tottally OK, because it does not restrict someone else's freedom.
...but experience slowness when using GNOME 3/Cinnamon.
At least for Gnome 3 if you used one of the earlier versions and felt that it was slow then you should really try the latest version, preferrably 3.14. It's night and day difference between them. It's still not going to be great if your hardware is too old or too slow, but it's going to be better than before.
Some people dislike systemd because they can see where it is headed. Here is your sign.
Skimming that pdf is insightful. It promises magic unicorns from systemd, and raves on about using it to "build products" (what f*ing products and for whom?) and "the next generation OS". Such rhetoric is typical of GNOME-world megalomaniacs, those that force-fed us that new UI of early Gnome3. I distrust it immensely.
Tablets, phones, and quite a lot of embedded systems runs Linux.
Well, I'm a current Debian user, and I switched from testing to stable because of problems with systemd. OTOH, there's a good reason that it's called testing.
I have not tried Jessie recently, but I have used systemd for a long time now on production versions of both Fedora and CentOS. It's fine, I'm totally OK with it.
Still, any init system that marks problems with its logging system as "won't fix" is dubious. That the main logging system is binary just makes things much worse.
You didn't say what the problem was, but if it was that it uses a custom logging format then of course that's not going to be fixed. It's a feature, old-style text files is not suitable if you want to store the metadata that the journal supports.
So does expansions like having the "init system" include things like terminal manager, etc. It even makes me tempted to go back to Etch (yah, that's a rediculuous thing to suggest, as the current stable works fine without systemd).
Systemd is not an init system. To quote the systemd home page, "systemd is a suite of basic building blocks for a Linux system." That includes an init system.
"for variety of reasons". Who are we kidding? It's the fucking systemd by Redhat's Poettering.
Ah yes, systemd. Everything was all fine and well until it came around and screwed everything up. Oh, and it's just a conspiracy anyway to let Red Hat take control over Linux.
I give you 2.11BSD.
1980s Unix, fully up to date. Patches are still actively maintained, one once every year or so. Completely systemd free, guaranteed!
All you need is a PDP-11, or a PDP-11 emulator. Go ahead, install it. I dare you to install it!
All you need. No bloaty modern unnessessary cruft that replaces stuff _THAT WORKED_ just fine!
Why do you want to remove it? Seriously, what will you loose by using systemd? Is it performance? Is it stability? In what way will your systems run worse with systemd than without it?
According to the story you just commented on they apparently care quite a lot about cross-platform support since they want people to help them with it.
An API is not removed just because it's deprecated. It just means that you are discouraged to use that function in new code, and that it *might* be removed in a later version. This is not uncommon in minor versions and you typically wait for a major version until you actually remove them, to preserve ABI compaitibility.
Slashdot Mirror
And GNU/Linux is not UNIX.
Choice is not a matter of just pressing a button and have it magically appear. Someone has to actually maintain it. The Devuan developers think that they can do that. If so then that's great. It's sad that they don't think that they can do the same thing within Debian though I understand their reasoning. It takes a lot of time and effort to get into Debian and they want to be more pragmatic.
NetworkManager has a command line interface. Two actually, a cli tool and one based on curses.
You wouldn't want it on a server, but you wouldn't want to be without it on pretty much any other use case.
NetworkManager should be fine on most servers. While the project used to be focused on desktops and laptops there's nothing non-serverish about it.
Modern NetworkManager releases also include a handy tool called nmtui which is basically the GUI implemented in curses. Nmcli can sometimes be a bit unintuitive so it's a good thing to have around.
Keep in mind that Mac OS X supports case-sensitive HFS+ filesystems, and has done so from Mac OS X 10.3 on (2003). All you have to do is create a partition with that particular flavour of HFS+.
Stepping back from HFS+ they've even supported case-sensitive file systems long before that since you could use UFS on OS X. Even OS 9 supported it but I don't remember if you could boot that from it.
However, Adobe refuses to support case-sensitive filesystems. The Photoshop installer refuses to install on a case-sensitive filesystem, and Lightroom geolocation support is broken on case-sensitive filesystems, and always has been. Of course this limitation is not documented in their sales documentation, and the official fix is to reformat the partition...
Yep. The Adobe suite won't even open files over NFS.
The GPL has never had a problem with bundling programs with different licensing or linking LGPL into non-GPL, or GPL into non-GPL for that matter; it's only if you distribute that mix that GPL has a problem with it. What you do on your own computer is up to you.
The GPL is not bypassed becaused that's not what it was designed for. The GPL was not designed to prevent you from doing useful things on your own computer. You just can't give the software to someone else and not at the same time give them the same freedom that you got. Downloading GPL software and linking it locally is tottally OK, because it does not restrict someone else's freedom.
...but experience slowness when using GNOME 3/Cinnamon.
At least for Gnome 3 if you used one of the earlier versions and felt that it was slow then you should really try the latest version, preferrably 3.14. It's night and day difference between them. It's still not going to be great if your hardware is too old or too slow, but it's going to be better than before.
Depends on the type of server. If it's for remote desktop then sure, then it's absolutely necessary. On a web server, probably not.
Some people dislike systemd because they can see where it is headed. Here is your sign.
Skimming that pdf is insightful. It promises magic unicorns from systemd, and raves on about using it to "build products" (what f*ing products and for whom?) and "the next generation OS". Such rhetoric is typical of GNOME-world megalomaniacs, those that force-fed us that new UI of early Gnome3. I distrust it immensely.
Tablets, phones, and quite a lot of embedded systems runs Linux.
Except OS X lacks half of the feature set. No containers for example.
Well, I'm a current Debian user, and I switched from testing to stable because of problems with systemd. OTOH, there's a good reason that it's called testing.
I have not tried Jessie recently, but I have used systemd for a long time now on production versions of both Fedora and CentOS. It's fine, I'm totally OK with it.
Still, any init system that marks problems with its logging system as "won't fix" is dubious. That the main logging system is binary just makes things much worse.
You didn't say what the problem was, but if it was that it uses a custom logging format then of course that's not going to be fixed. It's a feature, old-style text files is not suitable if you want to store the metadata that the journal supports.
So does expansions like having the "init system" include things like terminal manager, etc. It even makes me tempted to go back to Etch (yah, that's a rediculuous thing to suggest, as the current stable works fine without systemd).
Systemd is not an init system. To quote the systemd home page, "systemd is a suite of basic building blocks for a Linux system." That includes an init system.
They also tend to be more unmaintained, like with owncloud.
You know how much bandwidth each Firefox update require?
But still not great.
"for variety of reasons". Who are we kidding? It's the fucking systemd by Redhat's Poettering.
Ah yes, systemd. Everything was all fine and well until it came around and screwed everything up. Oh, and it's just a conspiracy anyway to let Red Hat take control over Linux.
I give you 2.11BSD.
1980s Unix, fully up to date. Patches are still actively maintained, one once every year or so.
Completely systemd free, guaranteed!
All you need is a PDP-11, or a PDP-11 emulator.
Go ahead, install it. I dare you to install it!
All you need. No bloaty modern unnessessary cruft that replaces stuff _THAT WORKED_ just fine!
2.11BSD!
Halle freakin lujah!
There is no support for Flash...
There is no need for Flash anymore.
Why do you want to remove it? Seriously, what will you loose by using systemd? Is it performance? Is it stability? In what way will your systems run worse with systemd than without it?
I've used their "self-support" subscriptions at times when all I wanted was the bits.
According to the story you just commented on they apparently care quite a lot about cross-platform support since they want people to help them with it.
Well, except that in this case the entire story is that they want help making it work great on non-Gnome platforms.
An API is not removed just because it's deprecated. It just means that you are discouraged to use that function in new code, and that it *might* be removed in a later version. This is not uncommon in minor versions and you typically wait for a major version until you actually remove them, to preserve ABI compaitibility.
Torvalds has said he might rewrite the kernel in VB one day. With .NET going open source (one bit at the time) this might not be too far away.
Didn't they fixed most of the nuisances with 8.1 and 8.1 Update?