nrc

Yes, corporate funding and organization have enabled systemd to get where it is. But did the corporate entities drive that for their own benefit or are they simply supporting wrong-headed people with bad ideas? I tend to believe the latter but I certainly wouldn't argue strongly against the former.

systemd supporters use "modern init system" as a synonym for systemd. To them, systemd is a modern init system and a modern init system must be systemd. This presumes that a "modern init system" is one that takes over a whole host of functions that have been accomplished effectively for decades by independent utilities interacting with one another. Of course this bit of nonsense is a product of Poettering's thinking. One might surmise that the idea comes from the fact that he doesn't play well with others so he would rather just control everything his project touches. It's simply not true that all of that is necessary for a "modern init system". The need for a "modern init system" in the Poettering style presumes that he is correct in his belief that there are all sorts of things that simply can't be accomplished without a "modern init system." There were other init systems in development prior to systemd, they just didn't work on the premise that it was within their purview to replace anything but the actual init system. The political aspect of this is clear. Redhat and Novell are the largest contributers to key pieces of the stack. In many cases they empoy the maintainers of those pieces. So when RedHat employee Poettering decides that udev should be absorbed into systemd RedHat employee Sievers says "Why yes, of course it should." Thus leaving any distro that isn't inclined to adopt systemd in a quandary. Repeat that process with multiple pieces of GNOME and pretty soon you leave distro maintainers with few options. For the community to replace the effort of these paid developers takes time. Even if they don't agree with the choices that Poettering and company are making, they're not willing to cede their position as "major distros" to wait for alternatives to arrive - particularly with Poettering making it clear that he intended to do everything he could to make alternatives impractical, if not impossible. The decision for Debian was also political but came from an entirely different perspective. systemd advocates used simmering resentment toward Canonical's use of Debian for commercial purposes to lead free software advocates down the garden path of dependence on a RedHat controlled stack. Fortunately dissension continues and there's now a move to call for a general resolution to forbid Debian packages from depending on a specific init system. Hopefully that will move forward and succeed. This isn't an "evil corporate conspiracy." I think most of these people believe that they're doing good for the community. They just have well funded bad ideas.

RedHat has paid Poettering to develop a lot of code and then given it away for free. So what? That doesn't exempt him from criticism for his bad ideas and behavior. Poettering hasn't developed as much code as Linus but Poettering doesn't seem to feel that puts Torvalds beyond criticism. Most people haven't chosen systemd. They chose a distro. Poettering, his funders, and supporters were successful at coercing most major distros into adopting systemd through a combination of political manoeuvring and threats that anyone who didn't fall in line would be rendered "irrelevant" as systemd consumed every project it touched and became a dependency for everything. The average user doesn't understand UNIX programming principles or how much of what is good about Linux stems from them. So of course they're not going to immediately dump their favorite distro just on principle. It's true that efforts to create alternatives to systemd have been slow to organize. Until the coup in the Debian technical committee there were certain to be alternatives to systemd and there was no threat that Poettering could continue to force dependencies beyond projects driven by RedHat. That safety net is now gone. If people want any alternative to systemd they're going to have to do something about it. I don't think Poettering's little sob story was as random and pointless as it seems. I believe that he was trying to provoke one of Torvald's patented "piss off" rants so that the can play the victim and court sympathy in his future dealings with the kernel community. His accusations of racism and sexism in the kernel community are designed to start lining up sympathetic victims. Expect more bad ideas from Poettering soon.

Lennart Poettering has posted a whine to G+ about how mean everyone's being to him. https://plus.google.com/app/basic/stream/z13rdjryqyn1xlt3522sxpugoz3gujbhh04 He blames this on the open source community and calls out Linus Torvalds specifically for setting a bad example. Of course Poettering fails to attribute any blame to his own history of being rude, obnoxious, and dismissive of anyone that disagrees with him. I don't condone threats of harm or violence but welcome to the Internet, Lennart. Yes, there are stupid and immature people in nearly every community, the Open Source community included. But it's pathetic to suggest that these behaviors are somehow specific to the Open Source community or that Linus Torvalds bears some responsibility. Yes, Torvalds can be blunt but in all the cases where I've seen him lambaste someone, it's been a judgement on the quality of their work. Don't develop software for public consumption if you don't want criticism of your work. I think that's really the root of this rant. Poettering believes that his work should be above criticism. He feels like the adoption of systemd is proof of that when it's largely the result of funding and political machinations. Thank drobbins we have an alternative. Hopefully the rest of the Linux world will wake up eventually.

When you're looking for your first "real" job they'll have three things to judge you on: your personality, what you have accomplished while in school, and how you did in school (your GPA). Some people can accomplish so much that maybe they don't need to care a lot about their GPA. Create a project that shows that you've got initiative, good ideas, and the ability to execute them and maybe a B or C average is good enough. In the absence of that you will need a strong GPA to get serious consideration from the better companies. My advice is to complete your BS and work a while before deciding whether to pursue an advanced degree.

I wish I had the graphic talent to provide you with something worthy. I did a search for appropriate symbols for systemd but this is all I could find... Credit: http://www.codekid.net/index.php?itemid=2026

I dug up your thread. It's certainly an odd reaction to people doing what open source is supposed to be all about. There's this vicious circle in the reasoning around systemd. On one hand if you complain that systemd is too monolithic or has consumed too many other projects they will explain that systemd is modular and you can replace those pieces if you don't want to use theirs. But then if you propose to replace one of those components or just work around it they will explain that it's really not practical to do so because everything is so interdependent and everything is going to start depending on their pieces anyway. I suppose a rolling release source based distribution is never going to be hugely popular, but I'm surprised that we're not seeing more growth here given how much some people like to complain about systemd.

So they're deliberately cleaned up. Is that necessary or were they just viewed as chaff? Am I wrong in thinking that if they weren't cleaned up they would be pulled down in the git pull and available for equery?

Is 'equery changes portage' expected to show a changelog as documented in the equery man page? I get the same error no matter what package I specify: !!! Fatal error: /usr/portage/sys-apps/portage/ChangeLog does not exist or is unreadable I don't see ChangeLog files for anything under /usr/portage/sys-apps/.

Previous responses contain good information about identifying the correct driver. But the comment that he has only the loopback interface suggests that he needs to run Kubuntu to have the network connection he needs to get the driver. Yes, when you chroot your network connection will remain active. On your chroot command, try using the full path to your chroot executable, possibly '/bin/chroot'.

Starting to sound like a drobbins cheerleader here but what the heck. This is fantastic. Exactly what the Linux world needs - choices, not forced homogenization through unnecessary dependencies.

If you can find a live CD that supports your wireless it might be helpful to boot that and confirm that it's a software rather than hardware problem.

That's a great attitude. Being new to the distro I'm reluctant to report because I'm not sure what might be a bug versus just something I've messed up. I'll be quicker to SPAM Jira from now. :)

That would be a good problem to have.

The user map on funtoo.org main page seems to be missing some users relative to the one on the user map page.

Works for me.

Yeah, skulls don't really say "Funtoo" to me. Not even screaming satanic ones.

I'm just happy to feel like I'm running Linux again instead of something that seems to be trying very hard to become Windows.

Glad to help.

I notice that some Jira sites have additional menus in the navigation. Looks like it may be possible to do a basic plugin to create this. Seems like a lot of trouble for a link. https://developer.atlassian.com/display/JIRADEV/Adding+Menu+Items+to+JIRA

Google says that the USB controller on your MB is a VIA VL805 chip. The advice to get that chip working appears to be to add the kernel parameter "iommu=soft".

On the main Funtoo site there is a box at the top right with links to the various key pieces of the Funtooverse. It would be nice if the other pieces had some similar place for links to simplify navigation. For me this is a question of laziness, but for new people who find one bit or the other through a search, there should be links to the other parts.

Any chance that Funtoo "proper" could follow the lead of BSD dists and work to create modules that replace the systemd GNOME dependencies? I see that they've got 3.10.2 running in OpenBSD with plans to eventually replace timedated, localed, hostnamed and logind. http://undeadly.org/cgi?action=article&sid=20140219085851

My reference to systemd was because systemd's consumption of more and more user space ultimately led to the changes in udev and upower that are now creating problems. I was able to suss out a lot of the dependencies you talk about. At least I'm learning a few things about portage in the process. I don't mind that I can't update my home system but unfortunately this is also stopping me from completing the build on my new work system which is a bit more painful. I tried switching the build profile to stable (after I'd already emerged quite a few packages under "current") but it still hits the problem packages. Would starting the build from scratch with the stable build profile fare any better? It seems like with these issues lurking out there it would be desirable to make sure that "stable" always builds even if it doesn't get updated for a long time. I understand what a sticky problem some of this is and I can't emphasize enough how appreciative I am that there are some developers who are willing to tackle these problems. As much as some people want to push the need for uniformity in the Linux ecosystem I really believe that the ability to try different solutions and the "UNIX way" are much more important than just going along with the latest edict from the big contributors.

Thanks. Do you expect that clearing up the upower issue in FL-1261 will eliminate whatever dependancy is attempting to drag systemd into the mix? Based on the news item in the latest update it's clear that systemd is once again the root of all evil. Or at least this issue. I wish I could be more helpful in isolating the issue but I'm new here and still learning portage.