Slashdot Mirror
Linux 4.5 Adds Raspberry Pi 2 Support, AMD GPU Re-Clocking, Intel Kaby Lake (phoronix.com)
The Linux 4.5 merge window has been open for the last two weeks; that means that the 4.5-rc1 kernel is expected to emerge, with the official kernel following in about eight weeks. An anonymous reader writes with this top-level list of changes to look for, from Phoronix: Linux 4.5 is set to bring many new features across the kernel's 20 million line code-base. Among the new/improved features are Raspberry Pi 2 support, open-source Raspberry Pi 3D support, NVIDIA Tegra X1 / Jetson TX1 support, an open-source Vivante graphics driver, AMDGPU PowerPlay/re-clocking support, Intel Kaby Lake enablement, a Logitech racing wheel driver, improvements for handling suspended USB devices, new F2FS file-system features, and better Xbox One controller handling.
Offtopic fud! Maybe you should big fix the old init sys of your choice
The solution is for all the systemd haters to band together into one distro and move on. I'm not a particular fan of the idea of systemd either but it's time to get over it.. To continue to fight something with that kind of momentum is ridiculous. It's as bad as expecting microsoft to go away and die.
Still using the old init sys on RHEL6 and it works great, there is nothing to be fixed.
Would your or I be here today if we simply let the Nazis walk over us?
So happy to see the Raspberry Pi 3D support. Thanks for the goodies!
Why is the "Logitech racing wheel driver" part of the kernel, even if it is optional, rather than a user space driver?
Jumpstart the tartan drive.
If you're seriously comparing systemd with nazis then I don't even know where to begin. If you want to discuss systemd then use factual arguments.
I was totally agnostic about it, not really caring either way. Well, I was, up until one of my three systems that has been running Linux fine since forever no longer boots under systemd, and the command it gives me to produce a log output gives no hints whatsoever about what is wrong.
This system still boots fine under older OSs.
I have no idea whether systemd will be fine once it's ready, but currently it is NOT ready for prime time release.
This. I had a CentOS 7 box start failing to boot giving a udev failure message. This is with a KDE desktop install with no extra packages installed.
I ran hardware diags on the machine and when they all passed, I installed OpenBSD on it.
You systemd folks can keep singing kumbaya until you're all using Lennux distros built on systemd/kerneld where literally everything can crash the system without any rhyme of reason.
Nazis never harmed me directly. I wish I could say that about SystemD.
Without full desktop OpenGL support on the Raspberry PI, you can't run the good Linux games like BZflag, Supertux and Tux Racer. I'm hoping this moves the dream forward. It'll be interesting to see if this just opens some new 3d options or if we can actually start to build and run games that use full OpenGL in the near future.
You should be using RHEL 5 if you want a real veteran UNIX sysadmin approved init. RHEL 6 uses upstart which is a modern replacement and it is not particularly old. It could easily have been Upstart that took of and won over systemd, but systemd has the developer support.
My RPi2 already runs an older Linux kernel. Can someone explain what's new in 4.5 that makes it "support RPi2"?
How come there was never so much controversy over Upstart when it was introduced? Because it was worse than SystemD?
The fact that all of the major Linux distros now use systemd is a huge problem.
Why?
Many Linux users just cannot use systemd.
It has a manual.
They can't risk the problems it brings.
What?
I dislike issues such as initd (that is, systemd) ceasing to respond if it's busy doing something (such as a poorly written unit file allowing a service to pull in dodgy non-working dependencies, or an application rapidly consuming all the RAM at startup, being killed, and being launched again), leaving the system difficult to reboot or recover without pulling the plug. That being said, I enjoyed these problems under Raspbian. Haven't seen them on a real computer.
It would be best to concentrate on actual problems like those above, rather than the benefits, like journald (which you suggest is a problem), configurability and flexibility, service containment and security/delegation model. Having dealt with nearly every UNIX(-like) init system, IMO, systemd isn't actually that bad. I'd put it in #2 place, after OpenRC.
For perspective, if you want to try something with the rock-solid stability of systemd and the ease of use of BSD init, go back to Upstart to refresh your memory.
Where is there any other concise change-log at the moment?
The summary says Raspberry Pi 2 support is included in this release, but I've been running Linux on my Raspberry Pi 2 for over six months. This can't be a new feature. The RPi2 support might have improved somehow, but it's not a new feature.
It should be a simple patch to a distro like Ubuntu, and easy enough to maintain. I'm surprised that no one has stepped up and packaged something like: "Slow booting Ubuntu for systemd haters." I understand that you can tweak around and get most of that lost boot time back, so do that in the distro and make it worthwhile.
This has already happened. The most talented and experienced Linux users have already moved to FreeBSD. Maybe you don't realize it, but this is the worst thing that could have happened to Linux. Now Linux and its community will no longer benefit from the decades of experience these users each tend to have. They're the unsung heroes who kept the Linux community going. Now their contributions benefit the FreeBSD community instead.
The exact same thing is happening to Linux that has happened to the Firefox web browser. In the case of Firefox, it was the awful and unwanted UI changes (especially Australis) which drove away Firefox's most important users. Without their support, Firefox's overall share of the market has dropped to only around 7% today. Systemd is the equivalent when it comes to Linux. It's an unwanted and awful change for many users, and it has forced them to abandon Linux completely.
Systemd has harmed Linux and its community way more than Microsoft, SCO, Apple, or any other company could have. Linux's collapse has come from within. It has come from people like you, who tell the best Linux users to basically "fuck off and die". Well, those users have listened, and now they're happy, productive, proud and helpful FreeBSD users, and they make absolutely no contributions to the Linux community any longer.
While I do not keep up with every changelog, it seams that gaming and video related improvements are all the rage now for the kernel. I have to say I like this and it has been needed for some time. The kernel is here to stay in both handheld devices, embedded set top devices and now consolish and home brew steamboxen. Seeing the OS improve as it pushes into these spaces is a great development.
Silence is a state of mime.
The National Socialist Party? The Nazi party? Are you fucking serious? That's your idea of an analogy?
Even when it becomes ready, it should still be optional.
What I love best about open source is that it's free and you can take it or leave it. There are choices available that don't use systemd. Pick one.
Yes. SystemD is a terrible thing and the outrage it generates is reasonable.
And isn't that how it's supposed to work? The survival of the fittest?
I assume he refers to the fact that the jews and whatnot were victimized by the nazis.
At first, they refused to take their own responsibility, and whined to everyone that the nazis and others should change the state of affairs in their favor.
But, as we all learnt in school, that didn't work, so they took their ever present freedom to fork the entire planet and patch it, replacing the nazis with something they were comfortable with.
So actually, the analogy is quite fitting.
How come there was never so much controversy over Upstart when it was introduced? Because it was worse than SystemD?
Because it turns out replacing sysvinit was necessary and is something that the GNU/Linux community has gained from doing. Now what happened with systemd is a very sad story where a small but non-trivial amount of Linux users had some historically bad experience with another project called pulseaudio which happened to have been developed by the same person that was initially responsible for systemd. The problem was that these people really don't know how to behave civilized. They spend all night trolling /. and not really doing anything useful. They are not deeply involved in any larger open source project. They don't actually know what it takes to make an independent large-scale GNU/Linux distro. And when they saw that systemd was coming up and also happened to be led by this person that they were not exactly on the same page with since before they decided to fire up on all cylinders and obstruct the adoption of systemd by to be fair simply bullying its developers and supporters. A large part of the commenters that you see here repeating the same arguments are into that; stories about systems that no longer boots, that systemd drops stderr, that you are forced to use a binary logging format etc. It's just lousy arguments that are simply not true because they are missing the necessary context to put them into perspective. The problem is that when we are fed these arguments all the time then people that don't know enough about it starts repeating it without fully understanding the big picture, and the cycle repeats. It's not that upstart was necessarily better or worse, it's that we never really had a ground zero-like situation like we had with systemd where some people already from the start decided that this was not just something that they just didn't like but something that they would take upon themselves to make their mission in life to stop at any cost.
What I love best about open source is that it's free and you can take it or leave it. There are choices available that don't use systemd. Pick one.
I like watching pro-systemd people get their jimmies rustled. It makes me smile. I like what Linux Mint did, they've decided to wait until the next stable release in 2019 before they switch to systemd. By then, most of the issues should be ironed out for systemd on Debian based systems. I'm loving Mint 17.3 but it is FAR from being bug-free. No need to introduce more bugginess by shoving systemd in there right now. It seems Mint is where the sanity is.
Nobody objects to sysvinit being replaced.
They're objecting to it being replaced with something that's far more broken and architecturally-flawed (systemd).
The solution is for all the systemd haters to band together into one distro and move on.
Most of us did. My distro of choice is now FreeBSD and I regret not making the jump sooner.
I found out about the connection with Pulseaudio months after I started using (and being pissed off about) SystemD. I wasn't surprised.
And Linux used to be at the top and we were all fine with it.
They destroyed Gnome, Firefox, and now Linux itself.
Of course, people have already moved on, but we can still let some outrage be shown. You should learn to accept this, it will be quicker than us accepting systemd.
Does RPI 3D support means that we can see full futured android running on it?
No, it's never time to "get over it" for any fixable problem. Humanity gathers the resources to accomplish things in its own time, and plying social pressure to present a false choice (to accept a substandard solution (from their POV) or perform an unnecessarily increasingly monumental task) leads in the wrong direction. Everything must always be up for review.
Decoupling is a virtue. SystemD like any other component is better "a choice" and not "The Way". Killing choice where there always was choice but now is not because of pressure from certain parties is not good. The virtue of decoupling is lost to many who haven't experienced how difficult it is to change unnecessarily dependent things.
So, what we have here, is a guy who likes to watch jimmies being rustled. It makes him smile. I believe the term is "meatgazer".
yOU arE A fUCKinG iDIoT!
Show us your wound and then read above: "The solution is for all the systemd haters to band together into one distro and move on."
Netcraft confirms it, Linux is dying.
God, that felt good to say. Now I need to find my way back to reality.
Why "The most talented and experienced Linux users have already moved to FreeBSD" and didn't create one working non systemd Linux distro?
Because they are that most talentet and experienced?
You misunderstood, my point was that it makes no sense to compare SystemD with the Nazis.
Sorry for that.
Your spelling of systemd makes it hard to find the sarcasm in your post.
Talent's one thing but numbers count too. RedHat has the numbers, and they're under Lennart's spell for some unfathomable reason.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Exactly, stop moaning, if you don't want a certain init system, use a distro that does, or move to *BSD life really is that simple, and if you have a separate /home just make sure you set up your user with the same user / pass combination and same GID/UID. It's not like you don't have a choice in the matter
http://chimpbox.us
Oh, I use that spelling only because it looks like the huge cock systemd is, being jammed down users' throats.
But you misunderstood about the nazis.
Bah.
Linux vs BSD? Nope. We need both. Some competition is good, it prevents stagnation. As for systemd - it is not part of the kernel. You can run linux with or without systemd. You can run bsd with or without systemd. Ther kernel, and the sw to go on top if it is nearly orthogonal.
What I love about systemd is that it shows Linux users for what they really are: Real fucking assholes who will even shit on their own kind. Really pathetic but simultaneously entertaining!
> rock-solid stability of systemd
Bwahahaha!
systemd doesn't even have usable logs. Binary logs are nice... but something happens, they are absolutely useless.
This has already happened.
No only part of that has happened. They may have banded together in one distro, but what the parent described as "move on" implied not bitching and moaning about it on every bloody off topic post that mentions the word Linux.
Many Linux users just cannot use systemd. ... Systemd's use of binary logging is one of the most obvious problems with it.
Found the guy who can't read the fucking manual.
And if this is what we are doing to ourselves, imagine what we're capable of doing to your kind. Pretty scary eh?
so, I see Lennart still hasn't finnished his assignment yet.
cruel world.
neo@matrix:~$ sudo apt-get install vagina
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package vagina
neo@matrix:~$
Couldn't you have just wiped Debian 8, reinstalled Debian 7, restored your system and picked up where you left off?
systemd doesn't even have usable logs. Binary logs are nice... but something happens, they are absolutely useless.
it lets you forward logs to syslog-ng
systemd doesn't even have usable logs. Binary logs are nice... but something happens, they are absolutely useless.
it lets you forward logs to syslog-ng
I don't like binary logs either though. they get corrupted on incorrect shutdowns.
Ehm, socket activation is not exactly new; we've used it for years except back then it was called xinetd and was used by pretty much everyone. It was old, stagnated and received almost no new development. Now when that functionality is integrated into systemd it's actually has more people working on it.
Without getting into an argument about systemd...
To continue to fight something with that kind of momentum is ridiculous. It's as bad as expecting microsoft to go away and die.
You've just described the first decade of the Linux community. Is people's knowledge of history really that short? Microsoft was massive had far, far more momentum than systemd and had an utter stranglehold on the PC market, and would stoop at more or less nothing to maintain the dominance. The solution was to fight and keep fighting and it worked.
SJW n. One who posts facts.
xinetd.org isn't even responding for me right now, maybe a sign that the project was pretty much dead.
And of course you can opt not to use it with systemd. Nothing is listening if you don't have any sockets activated.
Would you care to name some of these talented users whose move to FreeBSD is causing Linux to collapse from within?
-- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz
A slashdot troll with a good backup and a plan? What the fuck are you smoking?!
Only retarded idiots were "fighting" MS while using Linux. Those who actually create (instead of bitch and moan on slashdot) were doing so because they wanted to improve Linux. Jokes aside, no one but whiny crybabies care about toppling MS.
Which is more moving parts and more things to go wrong.
You Poettering ass lickers are really fucking pathetic.
News Flash: Having over a dozen executables that are all dependent on each other is no different than one massive executable.
Binary logs are the best. You can read them in every situation under which you don't need to read logs, and none of the situations under which you do.
If systemd "doesn't even have usable logs", then neither does sysvinit. Because systemd can log to exactly the same places sysvinit does, in exactly the same way! And on my system it does. Systemd also has other options, which I may explore later at my leisure. But for now, nothing about my logs has changed with systemd!
Of course, I'm using Debian, and this whole thing is reminding me very much of the glibc transition, back in the day. Lots of people were screaming about how glibc was breaking everything, because certain vendors (no names will be mentioned...rdht) rushed the transition out the door. Debian took their time and did it right, and Debian users barely even noticed the transition.
Would you care to name some of these talented users whose move to FreeBSD is causing Linux to collapse from within?
If people grossly insulted by a relatively small change say they will make a much bigger change they're usually bluffing or a very vocal minority. Like Windows 8 sucks, I'm moving to Mac/Linux. The new ribbon sucks, I'm moving to Open/LibreOffice. So systemd sucks, allegedly. And because of that you're not switching to/making a non-systemd Linux distro but a non-Linux distro? And it doesn't solve the compatibility issues, if Linux-oriented software starts depending on systemd you either have to implement systemd, port all the software or do without. Which is a rather phyrric victory.
Live today, because you never know what tomorrow brings
So happy to see the Raspberry Pi 3D support. Thanks for the goodies!
Goes double.
Is anything similar planned for BeagleBones - especially BeagleBone Black, which is the current cutting edge?
I have to deal with them, and the last time I looked their kernels were coming out of a separate project - which distributes an archive of script to be applied to the corresponding version of the packages, to be overlaid on and applied to the corresponding kernel sources, to hack them into shape for the Bones. It would be far easier to keep up with kernel fixes if the Bones (or at least the Black) were supported directly by the official kernel distributions.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
Isn't he a Red Hat employee?
I'm starting to think GNU is the problem with "GNU/Linux" these days.
He was modded '5 Informative'. Why shouldn't I assume that he had a good backup and a plan?
So when you encounter your first boot problem with OpenBSD, what OS are you going to install over top of it in order to solve your problem?
Of course he can't read the manual. How the hell is he supposed to when systemd prevented his computer from booting? One can't read man pages or access web sites when one's computer halts mid-way through the boot process thanks to systemd failing in some way!
Whined? I don't like the tone or sentiments of your post.
Lots of arguing, but I do not see where anybody has answered the question.
Can I use Linux 4.5 without systemd? Will it work without systemd on Gentoo? Will it work, without systemd, on RasPi?
One thing that (AFAIK) can cause this is the fstab file listing filesystems as required to boot which are not present. Other init systems may incorrectly ignore their absence, but systemd believes that if a required filesystem is missing manyal intervention should be required.
Although this shoukd be pretty obvious from tge 'journalctl -xb' output.
If you use the DVB subsystem (using a tv tuner for example), then the 4.5-rc1 kernel is borked here. Either a patch broke it, or part of a build was added, but not the whole thing, etc. In any event, DVB wasn't "changed but still working", it was "changed and left in a broken state". These things happen with early RC kernels though, so if you already build one, just boot into an older kernel.
Wooosh.
Watch this Heartland Institute video
The most talented and experienced Linux users have already moved to FreeBSD.
You say that but it doesn't appear to be true. Notice, of course, that Linus still uses Linux. Notice that Linux is still being actively developed. I think you're just saying what you want to be true.
I, for example, still use Linux and I typically use Lubuntu which has systemd. I should also add that I should not be counted as "talented and experienced." I do have a lot of Unix experience, then Windows, then Linux, but Linux only stayed on a partition and hardly got any use. I've since switched to using Linux exclusively and spent a couple of years making the switch.
I'd like to hate systemd but, so far, it's done me no harm and I've learned a few new commands (like blame and analyze) and have even found it useful. I've yet to find a lot that I can't read. I've yet to find a problem I couldn't make worse by fucking something important up - except systemd. For all the things I break, that's yet to be the cause of a single problem. Trust me, I break a lot of things.
I did mention that I'm not in the talented group for a reason, after all.
I'd love to hate it. I love me a good hate fest and I like to rant and rage. I love to find something that pisses me off and tell the world about it. I break my computer in new and interesting ways. I don't just break one - I break a lot of them. I've got real server hardware, I've got colocated hardware, I've got countless desktops and laptops. I mean, a truly obscene amount of hardware. At my home in Maine, there is not one room without at least one computer in it. Every single room has at least one computer. Down here in Florida, a house I've used a total of six times, I'm refreshing the hardware that will remain here - there are three desktops, four laptops, and one server. Oh, there are three desktops, complete with all their hardware, that are ready to go to a good home. They were a few years old (I bought them in 2013) so they're being replaced but the new ones have not been set up yet. They are physically here, however. The laptops will leave when we leave to go back to Maine and the server will remain, it doesn't need refreshing and I'm too lazy to reconfigure a new one. Anyone need a few fairly recent desktops and is local to Panama City Beach?
At any rate, for all the poking and breaking that I do, I don't have a problem with systemd. I can't speak for you, for Tom, for Dick, or for Harry - but I can say that, as much as I'd like to be outraged, the damned thing hasn't caused me one iota of trouble. It has even been, dare I say it, helpful more than once.
Anyhow, I don't think the best and brightest have moved to FreeBSD. I imagine some have but they probably weren't the best and brightest. I don't see Linus switching and I'm gonna go out on a limb and say that he's probably among the best and most experienced. Besides, they'd go to GhostBSD anyhow. It's the same damned thing, pretty much, but much nicer by default. Even I can figure out how to use it.
"So long and thanks for all the fish."
Nobody here has just one computer. None of us... Every single one of us has at least two, many of us have far more than that. Personally, I have no fucking clue how many computers I own but it's a damned sight more than two. Err... It's probably in the... No, I'm not gonna admit that in public. :( Erf... Yeah, if I count my 'collection' of old hardware, I'm easily in the 100 computer range. No, I'm not even kidding. In my defense, I own several houses and have my own servers as well as desktops, laptops, tablets, phones, SoCs, etc... Yeah, umm... Err... It's probably actually over 100. I have a whole "lab" in my basement, a sever room, and a networking closet in my home in Maine.
Not counting phones, there are six desktops, four laptops, a backup server, and a couple of tablets in this house (PCB, FL) right now. In my defense, again, three of the desktops are a few years old and I'm hoping to send them to a good home. They're not bad, they've all got 16 gigs of RAM or more, SSDs with HDD backups, and recent CPUs - they were bought a few years ago when I was down here last and I'm in the process of refreshing them. If I don't find anyone local to take them, I'll just donate them - I did find a maker club that was fairly local so I can contact them - they'd probably want them. They still have Windows on them but they're MSDN licenses so I can't transfer those and will need to wipe them before they go. I don't suppose you, fine AC, are in the area and in need of some computers? I'm even giving away the peripherals as I've purchased new monitors, mice, and keyboards. Hell, I might even have more than that. I've not looked in the attic and there are boxes that I've not peeked into out in the garage. There's also a storage shed attached to the boathouse. So, yeah, I might have more than that here.
Yes, yes I have an addiction problem. I can stop any time I want to!!!
But, seriously, they can read the manual - it's online and NOBODY here has just one computer or even just one computer with internet access. I suspect that not only do we all have more than one computer WITH internet access, we've a "parts closet" (I can't be the only one) that can be hit up to make several other computers in a matter of a few minutes. I mean, literally, a few minutes. If I'm careful then I can put a box together in like a half hour. Hell, I probably can do that here and I don't even technically live here - I just visit and vacation here. So, on the off-chance that six computers, a server, four laptops, and a couple of tablets AND the phones all died - I could probably rummage around and get something going, online, and read the fucking manual.
For the record, yes, yes I have read the manual for systemd. All of it. Why? It was new and I wanted to see what the hell it did. I've actually used some of the features and they've come in handy. Specifically analyze and blame have been the most handy for my last use but I regularly use journalctl and using journalctl with grep comes in pretty handy too.
"So long and thanks for all the fish."
That's easy. The complaint here is about binary logging, implying that if he'd be able to read text logs if text logging was switched on. But if he has the means to read text logs then he also has the means to look up how to switch text logging on.
It exists. It's called Debian. Just install sysvinit in place of systemd.
(If you're allergic to the letters "d", "e", "m", "s", "t" and "y" you may want to check out Devuan, which wants to be Debian with all packages containing those letters removed).
Watch this Heartland Institute video
systemd doesn't even have usable logs. Binary logs are nice... but something happens, they are absolutely useless.
Why are they useless?
Watch this Heartland Institute video
When I do this in Ubuntu 15.10, it works, but it also slows down boot times pretty badly. All the systemd haters say that there are ways to fix that, I'd really like to see one of them put up (a convenient, and sensible, patch for Debian that addresses the boot time issue), or all of them shut up.
Not really. By the time you encounter any other kind you've already emptied your bowels over your own, so by the time you face us you're already shitless. Then you just get to be scared shitless like the little nerds you are. You can't smell what the Rock is cooking because your pants are too full of shit. (not the same AC)
No Sir, not at all and it's a serious question.
When I do this in Ubuntu 15.10, it works, but it also slows down boot times pretty badly. All the systemd haters say that there are ways to fix that, I'd really like to see one of them put up (a convenient, and sensible, patch for Debian that addresses the boot time issue), or all of them shut up.
Oh, that's easy to fix. Just install systemd.
Watch this Heartland Institute video
That's what I do in Raspbian ;-P
Every single one of us has at least two, many of us have far more than that.
While that's true, I don't know if "separate computer required" is a great bullet point on the feature list. Is there some sort of benefit to moving to binary logs by default?
I suppose there's probably some benefit. It's not like they still can't be read with a whole host of other tools. It's probably speedier, less space, and while binary they're not actually hard to read at all - in my experience. I've yet to have a problem with them, have you? I'm also pretty sure that you can change the logging and forward it or do almost anything you want with it - though I have no idea how to do so, I'm sure I could Google it if I needed.
Don't get me wrong - I'd love to hate systemd like the rest of you. I just haven't had a problem with it - at all, ever, on a whole variety of systems. Other than a few Android tablets, a Windows phone, and an iPad or iPod or two - I've got systemd on pretty much everything I own and use on a regular basis. Not only do I regularly end up messing stuff up but that's the whole reason I use Linux - to keep learning new things. Yet, even though everyone tells me it's terrible, I've had a whole whopping zero problems with it.
That's not because of some great skill or some arcane knowledge. I don't consider myself adept with Linux at all. I've always, well since the mid-90s, had one distro or another installed somewhere or on a partition in a dual boot, I hardly ever used it until a couple of years ago when I started using it more. Then, I decided my brain was turning to mush from not learning anything new, so I switched to using Linux almost exclusively. (I don't use the tablets very often, I sometimes use GhostBSD in a VM, and I recently decided to start using a Windows phone so I've had the phone for about four months.)
I've a convoluted setup, I won't bother to describe it all right now, but I'm on the road (stalled in Florida for the winter - I think) but was living in various hotels and wanted to ensure I was able to have a reasonably secure connection so I was often connected to my home computer, via VNC, while using a VPN, and often with a VM or just using a Live USB with, sometimes, persistent memory. And, no, it actually gets worse than that - but it's a long story. Suffice to say, it's probably the least likely system to work at all - yet, I left home in September. I can still connect and do all of that same stuff today - but I'm actually just connected normally at the moment because I'm not at a hotel, I'm at my house in Florida.
Hell, I even upgraded that home box to Lubuntu 15.10 when the time came - by remote, it rebooted and there I was. I regularly even reboot it, via remote, to apply kernel updates. (I then, often, use a VM which I can play with, trash, and learn with - while still keeping functionality.) On top of that, there's a whole network that I can use remotely. I don't really even save anything locally any more. I haven't in a long time. It's all saved to a server, backed up regularly with on-site and remote backups.
It just works. At least for me. I can not make any claims for you or for anyone else but has this binary logging been a problem? I've not yet been unable to access a log when I needed to - that even includes accessing boot logs when I had trouble. I'm not much more than a bumbling fool with Linux, I've been awarded as a Microsoft MVP multiple times but have long-since given up on that and I have a long history with Unix, specifically Solaris from back in the day. I've used a little BSD, GhostBSD as mentioned - though I've tried the others, and am largely still very much learning new things with Linux. That's why I use it - specifically why I use it. I use it because I suck at it and want to not have my brain turn to mush. I'm getting older, was getting to be a rather passive computer user, so I switched to using Linux pretty much to the exclusion of everything else.
In other words, by every measure, I should hate systemd and should be having all sorts of problems. I haven't. I can still use init scripts if needed. I can still read the logs - I love journalctl and grep when there are problems. I've read a bunch about it. At one point, I had a handy link where someone had done a complete teardown of
"So long and thanks for all the fish."
I'm no Linux expert myself (my hotrodding days are behind me; I just need stuff to *work*, please and thank-you), and I can't say I have particularly strong opinion of systemd yet, beyond wondering what the benefit is. And I mean that in the simple sense of - OK, we're breaking some of the old cardinal rules of *nix (multiple small programs that each do one thing well, use plain text because then everything can talk to everything else), so what are we getting in trade for it?
My problems with Linux boxes over the years have almost never been boot-related (OK, the one time when I didn't realize that *nix "are you sure" prompts are waay more serious than the Windows versions), so I likely will never have a particular problem with it. But in the same way I don't jump to buy the newest thing, I'm not sure why we're all jumping here. What does it get us that the old way didn't?
I'm sure it's possible to opt out from using it with SystemD, but the point was to be able to opt out of using SystemD in the first place.
Or even better, those who want to use SystemD should be able to opt in.
Take your pills
Dude that's offtopic
Linux is far from dying, but it used to be a joy to work with and now due to systemd it no longer is.
Yes there's journalctl and machinectl and all the other non-intuitive commands which are not in compliance with the Unix way of doing stuff.
But why should I memorize them during their beta-testing stage?
RTFM! ;-) (I've always wanted to say that. I don't think I've ever actually said it - in referencing the actual man pages.
http://www.freedesktop.org/sof...
Fedora's got a good bit of documentation on it that goes beyond just the man pages:
https://fedoraproject.org/wiki...
I'm generally a Lubuntu user so:
https://wiki.ubuntu.com/system...
https://wiki.ubuntu.com/System...
That last link is really pretty good - it doesn't look like it, judging by the URL, but it's pretty good at giving some info. From the second link, the one to the Fedora site, there's a link on that page that's actually pretty good. It's worth a read and it's explaining why they, the Fedora project, are going (went) with systemd. I'll save you the time and add a direct link to that as well.
http://0pointer.de/blog/projec...
I paid for my copy, it's paper, but this site claims that is Creative Commons and has a link to both the book and the web code examples, it appears to be legit so I'm going to go ahead and link it. It's the 2015 (9th Edition) Linux Bible. I own a copy, as mentioned, in dead tree format and have been happy with it as both a browse/read and reference book. It has some information about systemd in it as well. You can download the copy and code examples, free of charge, at this site:
http://appnee.com/linux-bible-...
A quick look says that it's the same as my paper book so I'm assuming that the content is the same.
Keep in mind, I'm not a systemd aficionado or anything. I've just never had cause to hate it like everyone says I should. So, I did a bunch of reading and I've done a bunch of thinking, some poking and testing, and haven't had a problem with it. I learned a few new commands, they've come in handy, and I'm pretty happy with it - so far.
User phantomfive (here on this site) has been doing a code review of it. I believe he's at section 12 now. That might be worth a read. You can get to his account easily enough by simply changing the URL. This should work: http://slashdot.org/~phantomfi... and you can get to his journal from there. The navigation will be on the left but I suspect you know that.
If you need stuff to "just work please and thank you" then, well, my experience has been that it just works. I, too, am no expert and have been learning more and more as I go - that's exactly why I switched to using Linux exclusively. I simply wasn't learning anything any more. I was stagnant and, well, there wasn't much more to learn about Windows. I'd already done the MVP thing, I'd been awarded the award multiple years in a row in several categories. I gave up my participation, burned out really, and just paid for my own damned MSDN subscription. So, it's been serving that purpose nicely for a while now. I'm getting older, to the point where it's time for me to legitimately worry about maintaining cognitive functions. I'd become lethargic, a passive consumer, and was not happy with that state of affairs. Thus, the switch and the ensuing switch to using it exclusively because I found that, even dual booting, I'd still just boot to Linux and I rebooted so seldom that I was often in the middle of something and needing to return to Windows to finish it. So, Linux it is... I had managed Unix just fine, so off I went... It's been a fun ride.
As an interesting (to me) aside: It's amazing how quickly things become normal. I had the opportunity to sit in front of a Windows 10 system for a brief spell. I was lost for a while. I've also had one occasion to sit in front of a more familiar Windows 7 system and, still, I was lost. I'd actually f
"So long and thanks for all the fish."
You got it wrong (intentionally).
SystemD is the thing that makes users move to FreeBSD and the thing causing Linux to collapse from within.
Maybe they're the only ones that cared about it, but we did it all together.
If the log is not written completely, the systemd decides they are corrupt and refuses to read and/or view them. Which is not so nice, if the whole system crashes and burns during the bootup.
That's easy, I'll just go with windows 10 and get this over with. I mean what's the point of living
He ain't?
This is, of course, nonsense. If part of the log is corrupted systemd will show you all but the corrupt part. Just like with text logs.
Watch this Heartland Institute video
yeah the systemd boot time is nice, but frankly it is not worth it unless you reboot your computer constantly. If you do not, you are letting a ever growing shoggoth in the door for no reason.
Some of us just stuck with Gentoo, which is still OpenRC.