Slashdot Mirror


X.Org Server 1.16 Brings XWayland, GLAMOR, Systemd Integration

An anonymous reader writes The much anticipated Xorg Server 1.16 release is now available. The X.Org "Marionberry Pie" release features XWayland integration, GLAMOR support, systemd support, and many other features. XWayland support allows for legacy X11 support in Wayland environments via GL acceleration, GLAMOR provides generic 2D acceleration, non-PCI GPU device improvements, and countless other changes. The systemd integration finally allows the X server to run without root privileges, something in the works for a very long time. The non-PCI device improvements mean System-on-a-Chip graphics will work more smoothly, auto-enumerating just like PCI graphics devices do. As covered previously, GLAMOR (the pure OpenGL acceleration backend) has seen quite a bit of improvement, and now works with Xephyr and XWayland.

226 comments

  1. Soon... by Anonymous Coward · · Score: 3, Insightful

    there will be no usable X, at least not from X.org, outside of poetterix.

    1. Re:Soon... by Anonymous Coward · · Score: 0, Troll

      I'm sure all 10 desktop BSD users will figure something out.

    2. Re:Soon... by rujasu · · Score: 5, Funny

      Why are you writing numbers in binary?

    3. Re:Soon... by Anonymous Coward · · Score: 0

      Why are you writing numbers in binary?

      Come on, that was pretty damn funny.

    4. Re:Soon... by Anonymous Coward · · Score: 0

      Generosity.

    5. Re:Soon... by Anonymous Coward · · Score: 0

      Funny until you consider the amount of OSX users running XQuartz.

      Next to none? So few people use X11 on OS X that it has only been an optional install since 2005.

    6. Re:Soon... by Anonymous Coward · · Score: 0

      And to add, Mountain Lion even uninstalled it if you had X11 installed. That must have been because of the huge user base, right?

    7. Re:Soon... by Desler · · Score: 1

      And how many users is that?

    8. Re:Soon... by kuzb · · Score: 3, Funny

      It's actually at least 15. They always walk single file in order to hide their numbers.

      --
      BeauHD. Worst editor since kdawson.
    9. Re:Soon... by ogdenk · · Score: 3, Interesting

      ML removed the old stale obsolete Apple-branded X11.app. It did not uninstall XQuartz. And XQuartz is quite actively maintained. Does the average kid running GarageBand need it? No.

      It's been an optional install from the beginning because most folks don't need X11 apps. Native mac ports of apps are much nicer most of the time and pretty easy to find. Running legacy X11 apps is not something most people need. But if the need arises, you can, and it works REALLY well. LOTS of people run command-line FOSS tools under OSX though.

      Apple solved the crappy UNIX desktop environment problem. They just didn't give away the source. I don't care if software is FOSS or not however. If it's good, I'll use it. If the price is too high, there's plenty of ways around that issue that any 14-yr-old kid with a web browser can find.

    10. Re:Soon... by ogdenk · · Score: 2

      Oh, and in fact, if you try to run an X11 app without XQuartz installed on 10.9, it will ask you if you want some help installing XQuartz and will direct you to a site to download it.

    11. Re:Soon... by Anonymous Coward · · Score: 0

      It's been an optional install from the beginning because most folks don't need X11 apps.

      So as I said, the user base is next to no one.

    12. Re:Soon... by ogdenk · · Score: 1

      And how many desktop Linux users do you know outside of the IT department besides a simple web-browsing box some guy set up for his Grandma?

      Because pre-installed Linux desktops just fly off the shelves. Please. The only widely successful end-user Linux environment for daily use has been Android.

      Both Linux and FreeBSD desktop users are a minority that few care about. Though if you count the Sony PS4 as desktop FreeBSD usage then it will soon trump Linux. Market share is a lame argument, FreeBSD is a great OS that is better documented than Linux and has several advantages as well as Linux binary compatibility with native performance.

    13. Re:Soon... by ogdenk · · Score: 1

      It's enough that it sees active development and a lot of use where old RISC-based UNIX boxes were once king.

      In terms of installed base, there's FAR more headless Linux servers than desktops, so X11 users in general are "next to no one" right?

      Generally it gets used when some "gotta-have-it" FOSS app lacks a proper mac port. X11 apps are less desirable because generally they suck compared to proper mac applications. And it's not XQuartz that's the problem, it's X in general. X11 on the mac is a last resort even if it works well because Apple's windowing system is THAT MUCH BETTER.

    14. Re:Soon... by Anonymous Coward · · Score: 1

      I have an X11R5 app here that still works, no sweat.

    15. Re:Soon... by Desler · · Score: 1

      What does any of that have to do with my post? I was simply asking you how many users there were of XQuartz since you were implying it was some large number.

    16. Re:Soon... by ogdenk · · Score: 1

      Maybe I'm tired.... thought you trying to bash XQuartz for some reason.

      I don't think anyone has compiled real statistics but I wouldn't be surprised if the number exceeds the number of FreeBSD desktop users by a large margin. It's certainly not an insignificant number but probably a fairly small percentage of OSX users. Most Mac users I know have Fink or Macports installed along with XQuartz but my numbers are likely skewed because I'm an IT monkey. Most of the "average" mac users I know only ended up using it to play with older versions of GIMP or OpenOffice.

    17. Re:Soon... by armanox · · Score: 2

      BSD/Linux X11 has breakneck feature obsolescence because nobody wants to actually standardize. I can run a 20 year old Windows app on Windows 8.1, but I can't run a 8 month old Linux application because it may depend on some obscure UI/UX feature that someone didn't like and quit maintaining.

      Actually, I thought the whole impetus behind moving to Wayland was being able to delete legacy X11 features. Anything that uses X standards seems to compile and run on any X11 platform (XSun, Xorg, XSgi, XQuartz) without too much hassle (take GTK 2.x, for example. Or Qt4).

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    18. Re:Soon... by Dishevel · · Score: 1

      There is no standard working-out-of-the-box desktop linux.

      /quote>

      There is no standard working-out-of-the-box desktop Windows.

      To use pre installed windows. ...

      Boot the machine. Activate it. Spend 4 hours updating and rebooting while uninstalling the shitloads of crapware and Norton that come pre installed just so I can finally install the stuff I need from 8 different sites.

      Or

      I can put in a burned DVD 2 min later I am in a live Linux environment. Install Linux ... 20 min later it is installed, updated and has the stuff I want on it.

      Linux actually goes from zero to a workable system really quickly.

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    19. Re:Soon... by Rob+Y. · · Score: 2

      WINE on the Mac uses XQuartz too. It works well, except when it doesn't. I've had it freeze up my display completely - happens when I exit my WIN32 app and then restart it. If I wait a while before restarting, it's okay. But if I restart it too soon, X launches and the screen goes all white. That's when you find out that the Mac's equivalent of Windows task manager is pretty crappy. It won't come up either, so you need to reboot...

      --
      Posted from my Android phone. Oh, I can change this? There, that's better...
    20. Re:Soon... by Anonymous Coward · · Score: 0

      OSX is nice, too bad you can only use it via a hardware vendor that grossly overcharges for said hardware.

    21. Re: Soon... by BitwizeGHC · · Score: 1

      systemd dependency is optional in Xorg 1.16.

      It's likely that the major desktops will have switched to Wayland and deprecated X support before systemd is made a hard dependency for Xorg.

      --
      N4st0r, trixx0r h0bb1tz0rz! Th3y st0l3 0ur pr3c10uzz!
    22. Re:Soon... by Anonymous Coward · · Score: 0

      Sure and you can dock most android phone to a monitor/keyboard, therefore it is as much a desktop as the PS4 is.

      FreeBSD is a joke, get over it.

    23. Re:Soon... by ogdenk · · Score: 1

      Mac hardware isn't really overpriced. Just stick to the base config and add your own RAM and bigger drive. The thing is that Apple doesn't have crappy budget machines aside from the Mac Mini and even the Mini is no slouch. Look at similar PC's with the same config, in the same form factor with nice sturdy all-metal chassis. You'll find the Mac is often cheaper.

      Where Apple is unappealing to a lot of "enthusiasts" is the lack of low-end or mid-range expandable machines with slots. People shouldn't have to spend $3,000 for expandability. But most of that crowd knows how to build a hackintosh if they want one anyway. I run it on cheap non-Apple hardware very successfully for home use with full hardware support. I let my employer buy the newer Apple-branded hardware except maybe my little used 2009 MacBook at home which runs 10.9 quite well also.

      Even if the mythical "Apple Tax" were true, I'd pay it to get a nice stable UNIX workstation with support from major commercial desktop software vendors and no Linux dependency hell. It's worth it to me to NOT be stuck running Windows. Linux and BSD on the desktop are fun if you like being an isolated leper.

    24. Re:Soon... by ogdenk · · Score: 1

      That's a WINE issue, not really an XQuartz issue. Really only an issue with full-screen stuff. To be fair, I've had this happen a lot on Linux/BSD machines as well.

      I never use the old "Cmd-Opt-Esc" Force Quit method. Easier to hold opt and rightclick dock icon and hit force quit there. If that's not an option I usually have a terminal window open and I can just kill it from the CLI. TotalTerminal is awesome and should be part of the base OS. I haven't had a situation where it didn't pop up over whatever was running. X apps included.

    25. Re:Soon... by Anonymous Coward · · Score: 0

      FreeBSD is a joke, get over it.

      Yep, so much of a joke that folks as big as Netflix swear by it and a lot of code/userland stuff in Linux distros was lifted straight from it. And in many situations runs Linux binaries faster than Linux, is much easier to keep up to date, has far better documentation and a much cleaner, more understandable layout. Yep. It's a joke.

      I guess pfSense, JunOS and FreeNAS are jokes too, right?

    26. Re:Soon... by Anonymous Coward · · Score: 0

      The C library used by Android is from FreeBSD. I guess Android is a joke.

    27. Re:Soon... by Anonymous Coward · · Score: 0

      It's to get rid of unused legacy features and provide a compatibility layer for everything else.

    28. Re:Soon... by Desler · · Score: 1

      And it will run on Wayland using XWayland.

    29. Re:Soon... by retchdog · · Score: 1

      I agree; Apple sucks.

      The best (and maybe only) competition so far, though, is Ubuntu and its derivatives. Fucking christ, that's depressing.

      --
      "They were pure niggers." – Noam Chomsky
    30. Re:Soon... by mccoma · · Score: 1

      I thought is was from OpenBSD

    31. Re:Soon... by Blaskowicz · · Score: 1

      Even the $3000 model is not internally expandable these days.
      Have fun with your mismatched enclosures, USB hubs and dongles cluttering your desk next to your sleek and "sturdy" well made all-metal piece of computer.

      The only problem with Macs is that people hoard them instead of throwing them in the trash where they belong. Else I would have picked up a Mac Mini on the ground, install BootCramp on it and then it would be about good enough as a DHCP server and porn storage unit.

    32. Re:Soon... by Mr0bvious · · Score: 1

      Really?

      OSX has some very annoying 'features'

      Finder - that's the worlds worst GUI ever, must it really be so difficult to go up a folder, can't afford a button for that?

      Keybindings - why the hack did they swap ctrl for option - I use 3 machines every day Linux, Windows and OSX and every time I use that damn mac I need to reset my muscle memory for my keyboard. Don't bother mentioning changing the key bindings as I've tried every trick in the book and while it works to some degree it is not applied consistently across all apps so then you have a 'what key do I use in this app' dilemma (which is even worse).

      Default dock behaviour is awful. Can't easily see what apps are open, clicking on an icon (terminal for instance) will wizz me to a different workspace and focus all my open terminal instances when I wanted a new instance (yes I know I can right click and select 'New Window', but that's just awkward).

      Sure some of these annoyances could be worked around but regardless - by default OSX is a PITA to use in a mixed machine environment. /rant

      --
      Never happened. True story.
    33. Re:Soon... by goarilla · · Score: 1

      The only problem with Macs is that people hoard them instead of throwing them in the trash where they belong. Else I would have picked up a Mac Mini on the ground, install BootCamp on it and then it would be about good enough as a DHCP server and porn storage unit.

      So you want one but can't get one through "dumpster diving". Oh, poor you.

  2. So... by Agares · · Score: 1

    Why are there going to be all of these changes? I am genuinely curious since I have only heard a little about this in the past.

    1. Re:So... by XanC · · Score: 1

      Well, you see:

      The systemd integration finally allows the X server to run without root privileges, something in the works for a very long time. The non-PCI device improvements mean System-on-a-Chip graphics will work more smoothly, auto-enumerating just like PCI graphics devices do. As covered previously, GLAMOR (the pure OpenGL acceleration backend) has seen quite a bit of improvement, and now works with Xephyr and XWayland.

    2. Re:So... by ustolemyname · · Score: 3, Insightful

      Totally agree. When I read his analogy it initially made sense to me, but only because I implicitly switched the order of Systemd and SysV init because that makes sense. "abomination that does "everything" complexly and half-assed" perfectly describes the hell that was init scripts.

    3. Re:So... by UnknowingFool · · Score: 1

      Well init in my opinion is as the poster stated init is an excellent chef's knife. The problem is in the modern age, sometimes you need a screwdriver and sometimes you need scissors. Systemd can do all those things but it's not great at doing so. It's enough to get by.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    4. Re:So... by allquixotic · · Score: 3, Insightful

      I don't think SysVinit is particularly good at anything, especially considering it's SysV's complete lack of functionality that caused the emergence of 9 different ways to do network config (Debian way, RHEL way, Gentoo way, and many others); 9 different ways to do logging (syslog, rsyslog, syslog-ng, etc.); and so on with starting daemons, yada yada.

      That said, I'm really somewhat disappointed that, as powerful of a unifying force within the Linux distro world Poettering's contributions have been, they completely neglect non-Linux FOSS operating systems. I've been a RHEL/Debian hand for years and years, but recently I've started falling in love with SmartOS, which is based on Illumos/OpenIndiana/OpenSolaris. It actually has a REALLY good built-in init system called SMF, which, like all init systems, sucks at some things but is really really nifty at others. One thing I can say for certain about SMF is it kicks SysVinit's ass from one side of the world to the other. It's always disappointing when a project team for something other than systemd, which previously compiled fine on SmartOS, decides to add a hard dependency on Systemd. It basically guarantees that your project will be forked for all the people out there who aren't using Systemd.

      Looks like Xorg doesn't strictly require systemd, which is the CORRECT way to integrate Systemd into a project: make it an OPTIONAL dependency. I have absolutely no qualms with a project ADDING support for Systemd while maintaining support for non-Systemd systems, such as non-Linux OSes. I have a problem when something I need on SmartOS is basically hard-locked to the Linux kernel by indirection to hard-depending on Systemd.

    5. Re:So... by drinkypoo · · Score: 4, Insightful

      It's crappy at managing services,

      init doesn't manage services. Services are either managed by inetd or by themselves. init only has to start the services.

      it's crappy at running shell scripts (as witness by the non-standardness of init.d scripts),

      That's proof of how good it is at running shell scripts. It just runs the script.

      it's shit at managing running services with interdependencies (inittab)

      Init doesn't need to be good at that. You can use a tool to create your runlevels which can figure it out. The only problem I see is the lack of parallelism. I suspect that this could have been fixed without replacing init.

      it's shit at dynamically reconfiguring systems (e.g. network reconfiguration for Wifi.),

      Why in the love of all that is Unix would you expect init to handle network configuration? Its job is to start and stop things, not to reconfigure your NIC. This mindset is exactly how we got systemd when we didn't really need it. We should have been able to use selinux to run X without root.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:So... by gweihir · · Score: 1

      Well, there are people with different opinions about that. SysV init works very well for me and in particular lets me customize everything, which I routinely do. Now, is some people want systemd, I am completely fine with that. What I am decidedly not fine with is having systemd forced on me.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    7. Re:So... by gweihir · · Score: 1

      Can the propaganda. What you claim is so obviously wrong, it is not funny anymore.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    8. Re:So... by Anonymous Coward · · Score: 0

      Why is it that "sysv" keeps on being trotted out as our only hope against poetterbloat?

    9. Re: So... by Anonymous Coward · · Score: 0

      It happens to all systems. Things are changing, and the people who learned Linux early are now seeing their knowledge being phased out. Same thing happens with any OS - compare windows 3.1 to windows 8. Linux needs to have modern features that are difficult with the old UNIX-from-1970s philosophy.

    10. Re:So... by Anonymous Coward · · Score: 0

      I see school is out for the summer.

    11. Re: So... by Anonymous Coward · · Score: 0

      I love it when the newbies come and try to tell us veterans what we should use. They are probably the same assholes that criticized us for creating and using an out-of-date operating system to compete with their more modern Microsoft Windows. Now that Linux has gained traction, they still have the nerve to tell us that we are doing it wrong.

    12. Re:So... by gweihir · · Score: 2

      Bullshit propaganda from an AC, no less. Either you are lying or you have no clue what is going on. In any case you are being dishonest and follow just the usual patterns of lying, cheating, and ad Hominem that is so prevalent in systemd circles whenever anybody dares to say something negative.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    13. Re:So... by Agares · · Score: 1

      Well I was looking for more specifics but ok.

    14. Re:So... by Darinbob · · Score: 1

      One service should do one job. The problem is that in the past people tried to lump everything onto one tool or small set of tools, and so started thinking along the lines of "what if we had just one system daemon to rule them all?" Ie, init should do init and not network configuration.

      Another problem people point to which I don't see as a problem, is a complaint that different distributions have different methods of doing the same thing. I don't see a problem with 10 different solutions to the same problem, especially if they come from 10 different distributions. It helps distributions be distinct from each other (I hope people still see this as a good thing), and it helps competition between solutions as the users decide which works best for themselves. If someone likes systemd then they can use it, if someone likes sysvinit they can use that, if someone comes up with something better then we can try it out.

    15. Re:So... by Anonymous Coward · · Score: 0

      Types deserve attention just like cookies do.

    16. Re:So... by Anonymous Coward · · Score: 0

      There's a reason alternatives were created, y'know.

      Alternatives, plural, but if the systemd people get their way all the others will be exterminated.

    17. Re:So... by drinkypoo · · Score: 1

      Why is it that "sysv" keeps on being trotted out as our only hope against poetterbloat?

      sysvinit became dominant over the bsd-style init in Linux-land, where most of us live these days if we're even still running Unix. It's pretty obvious why it would be the topic of conversation.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    18. Re:So... by retchdog · · Score: 1

      nah, most slashdot comments are really just versions of what the AC said, especially when they have anything to do with politics, where nerds are especially unclueful.

      i thought it was a pretty solid troll. it has nothing to do with systemd in particular. that you thought it did is just more evidence of the troll's success.

      --
      "They were pure niggers." – Noam Chomsky
    19. Re:So... by Aighearach · · Score: 2

      He's accurately describing the reasons for systemd and the reasons so many of us use it.

      He's giving the main, standard party line. It is not "propaganda," it is how people with a different view than you really feel about it.

      Compare that to your hyperbole that misrepresents the choice, and ask yourself who is producing propaganda!

    20. Re:So... by Aighearach · · Score: 1

      IMO you have it exactly backwards on all the factual parts. I can agree that people will have different preferences, and if somebody enjoys using SysV init, great!

      But on a more factual level, it is somewhat... absurd to claim that systemd does what it does poorly. To get that view, instead of listening to SysV fans, you'd need to listen to people who wanted the systemd features, but found they didn't achieve what they claimed. And if you look around, that is not the nature of the dispute at all. The dispute is entirely over 2 things: who wrote systemd and is he too uncool to use his software, and what features are actually desired in an init system?

      The rational, technology-based arguments against systemd are all related to the desired features. The code itself is being heavily used by people who consistently report that it does indeed work as advertised; it does well what it does. Rational opponents who dislike the featureset of course don't see that as a good thing.

      But if you can't get passed the hyperbole to find the real dispute, how can your position make sense?

      systemd is better at every specific thing than SysV init. People who understand both and like SysV like that it doesn't do much, and that is fine. But that is not the same as what you're claiming.

    21. Re:So... by Aighearach · · Score: 1

      Because everybody else other than [that guy who is not cool enough for our clique] failed at writing a SysV init replacement that actually functions well and doesn't introduce new problems.

      I guess name-calling doesn't translate directly to code.

    22. Re: So... by Aighearach · · Score: 1

      Sorry newbie, without a UID you're clearly in disguise. Busted!

      Anyways, it was the old guard who was against linux back then. Linux was the new OS, trying new things. You try to place it as having been in opposition to windoze, but it really in opposition to commercial *nix. That end users who use it would otherwise have been stuck on windows was related to the high price of commercial *nix, that's it. Everybody I knew in the 90s that hated windows also at some point wished OS/2 had had available software, that Amiga hadn't crashed and burned, and that an unknown rich uncle would send them a fancy *nix workstation for Christmas.

      The funny thing is to see somebody now claiming that those linux rebels were the old guard all along, and that therefore 20 years later they should be against anything new.

      I remember in 2001 Linus said in an interview that he hoped people weren't still using Linux 10 years later, because he hoped something newer and better would come along.

      The real solution of course to these disputes would be to have better distros and to have distros that make choices like SysV init and then commit to not changing any philosophical decisions or base technologies... ever. So then when new stuff comes out, people who use front-edge-following distros will have that new stuff thrown right at them, but people who use Stable distros would only ever see the new stuff by changing distros. As it is now, you can never choose a distro and be sure it will still meet your (unchanged!) needs in the future.

    23. Re: So... by Blaskowicz · · Score: 1

      Poor OS/2.. if only IBM had made it incompatible with Windows 3.1 applications, maybe it would have succeeded.
      As for Amiga, I disheartenedly learned not long ago that a XOR patent killed the AmigaCD 32 which is totally despicable. It would have become the first successful CD-based console, probably. A couple years headstart on the Playstation. Commodore/Amiga could have transformed into a console manufacturer, selling tens of millions units.. Junk their computer division : the DOS PC had won already back then.

    24. Re:So... by bingoUV · · Score: 1

      You are right. I haven't looked into it in great detail, but the solution I see is to create a dummy systemd which need not have all the functionality of systemd but just translates simple systemd calls into shell scripts. Then it would fit into SysV init as well as other initialization systems.

      Do you think it would work?

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    25. Re:So... by gweihir · · Score: 1

      I have heard exactly the same argument on mailing lists, may not have been a clueless troll after all. But you are right, this scum lives of their sadism, as is well-known by now.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    26. Re:So... by retchdog · · Score: 1

      "sadism"? really? it's just some asshole on the internet.

      what's with you, anyway? i know barely anything about this issue, but can you explain how systemd is being forced onto linux in general? if other apps are building it in as a dependency, maybe that's because it offers useful functionality despite the drawbacks. no one's even made a very clear list of the drawbacks, though i get the general idea of sprawling monolithic monstrosity. but then maybe that's just a side effect of the same development process offering useful functionality.

      can you explain how it's being forced onto people?

      --
      "They were pure niggers." – Noam Chomsky
    27. Re:So... by gweihir · · Score: 1

      As to trolls being sadists, are you living under a rock?
      http://www.independent.co.uk/l...

      As to your obvious trolling, go away. A 15 second Google search on systemd and 2 minutes of reading are enough to find out.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    28. Re:So... by retchdog · · Score: 1

      whether all trolls are psychopaths is another issue. pop psychology isn't that impressive to me.

      i'm not trolling, i honestly don't understand. you seem heavily invested in this issue, and since you've already spent a lot of time on this topic (judging from your posts here), i thought you could explain it to me briefly. i can only conclude that you just don't like systemd, and are upset because something you don't like has become popular. maybe i've already read those articles and simply disagree with them. i just wanted your opinion. disagreement isn't trolling.

      --
      "They were pure niggers." – Noam Chomsky
    29. Re:So... by gweihir · · Score: 1

      This is not "pop psychology", but hard science. The original article costs money though: http://www.sciencedirect.com/s...

      You are trolling, and you continue to troll. A 15 second google("systemd sucks") would gives you a good overview. And stop fishing for something necessarily abbreviated from me the that you can then attack.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    30. Re:So... by goarilla · · Score: 1

      init doesn't manage services. Services are either managed by inetd or by themselves. init only has to start the services.

      That's not completely true: init (re)spawns (a|min)getties on the ttys. So it does some monitoring of its "special" children.
      Wether this is feature creep and/or an exception I don't know.

  3. Systemd? Not on my system... by gweihir · · Score: 5, Insightful

    I really hope it is not a requirement and will never be on for X.org. Otherwise, I will end up having to make my Linux-servers X-less and probably use Windows as terminal. After all, with systemd, windows-like levels of intransparency, insecurity, complexity and developer arrogance have already been reached. One system with that is quite enough, I do not need to deal with that crap on Linux as well.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 1

      ...not on mine either.

      Not sure yet if systemd is a virus or malware infection.
      Regardless, do they have to pedal this crapware so ubiquitously?

    2. Re:Systemd? Not on my system... by UnknowingFool · · Score: 1

      Systemd vs init: It's the new emacs vs vi debate for the 21st century. :P

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    3. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      "...I will end up having to make my Linux-servers X-less and probably use Windows as terminal."

      Say what? Welcome to the internet my friend. We usually don't run any type of Unix server with a Graphical User Interface (GUI). It's unneccssary, as most things can be done through bash (the command line interface or CLI) without the overhead and security risks with running unneeded software. Running a GUI is what you would normally do when running a Windows based operating system for a server, though there are exceptions here.

    4. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 5, Interesting

      Anyone thinking about defending systemd should read this.

      Mod parent up.

    5. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Yeah, emacs vs vi, or a user of one of those pesky OS that that don't have it...

    6. Re:Systemd? Not on my system... by Warbothong · · Score: 2

      I use systemd on GobiLinux to launch Gnome3 in Wayland so I can tab-indent, via my Dvorak keyboard, the UTF-16-encoded, dynamically-typed code of my GPLed program in Emacs. While playing Oggs in Amarok2 through PulseAudio on OSS4. /nerd-troll

    7. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Systemd vs init: It's the new emacs vs vi debate for the 21st century. :P

      Vote third party!

    8. Re:Systemd? Not on my system... by NoNonAlphaCharsHere · · Score: 5, Insightful

      Systemd vs init: It's a Swiss Army knife vs a chef's knife. A shiny abomination that does "everything" complexly and half-assed, vs a simple tool that does one thing very very well.

    9. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 2, Interesting

      Anyone thinking about defending systemd should read this.

      Interesting read, but my "defense" of systemd is usually an "systemd could be the devil himself and you'd still sound like a paranoid asshat." I don't care if people don't want to use systemd. but shouldn't they be putting effort into collaborating on a set of remove-systemd-dependancy patches instead of bitching on the internet about the inevitable?

    10. Re:Systemd? Not on my system... by arth1 · · Score: 2

      No, generally emacs users are happy with systems that have both emacs and vi, and emacs won't prevent vi (and all the tools depending on ex/ed) from working.
      This is more like replacing ISC bind with samba domain controller. It's incomplete, broken by design, and has so many levels of abstractions that no sane person can admin it without specialized tools.

      I'm already boycotting Red Hat 7 because of the poetterification that changes simple things that work to complex things that don't. Now Xorg will have to go too.

    11. Re:Systemd? Not on my system... by UnknowingFool · · Score: 1

      Well there are advantages to systemd whether you personally like it or not. Like automatic dependency handling, parallel service starts, monitoring built-in. And there are disadvantages too.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    12. Re:Systemd? Not on my system... by ogdenk · · Score: 2

      I'm still a little confused as to why the Linux crowd didn't just adopt launchd from Apple. It's open-source as well and while "different" it's launch scripts are readable and it does its job quite well. Personally, I prefer the old BSD rc scripts but I can tolerate launchd. Systemd looks like a far bigger mess and will end up fragmenting quite a few projects. I imagine GNOME functionality under FreeBSD will take a nosedive. systemd seems very "Un-UNIXy".

      As long as systemd support remains OPTIONAL in X.Org I'll be a happy man. It's times like these I'm glad I'm a BSD guy.

    13. Re:Systemd? Not on my system... by TheRaven64 · · Score: 5, Insightful

      Systemd definitely solves a problem that exists. Unfortunately, it solves it in the same way that a nuclear warhead solves the problem of rat infestation.

      --
      I am TheRaven on Soylent News
    14. Re:Systemd? Not on my system... by rahvin112 · · Score: 1

      And why should I give a rats ass what some random blogger thinks about software? Pappp's opinion about SystemD is as relevant as the homeless person down the street.

      There will always be a Linux distribution that doesn't use systemD, if you are so adamant about not using it, don't use it instead of trying to convince everyone else it's evil because CLEARLY everyone else doesn't agree with you. You people that hate systemd are worse than "born-again's" and mormons and just like them you don't have the answer and I don't care what you think about it.

    15. Re:Systemd? Not on my system... by NoNonAlphaCharsHere · · Score: 4, Insightful

      The juxtaposition of your post and sig "Well, there's spam egg sausage and spam, that's not got much spam in it." has me ROFLing. Systemd is, indeed, just like the spam skit - it's in EVERYTHING, and everybody gets stuck with it, even though nobody wants it. In the same way that spam isn't really FOOD, it's just on your plate, systemd isn't UNIX, it's just on your system.

    16. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      If systemd were about 100 separate packages that were drop in replacements for existing functionality, I'd insult them and quickly move on. It's not. It's an all or nothing option that replaces most of userspace with things which are demonstrably worse, bloatier, more binary, and generally as anti-unix as you can get. I will never run it on my systems. I would probably go to openBSD right now but I've got too much stuff running ext4 soft RAID on linux, so it would be a huge pain. As it is, I'll stick with Crux and Slackware, who do not have systemd.

      -DX

    17. Re:Systemd? Not on my system... by NoNonAlphaCharsHere · · Score: 3, Insightful

      You've got that exactly backwards. The systemd lovers are more like the people who say "I don't care WHAT the Mormons believe, as long as they accept Jesus Christ as their Lord and Savior".

    18. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 1

      It's a different story here, we are all dreading the change.

    19. Re:Systemd? Not on my system... by bill_mcgonigle · · Score: 1

      Systemd vs init: It's a Swiss Army knife vs a chef's knife. A shiny abomination that does "everything" complexly and half-assed,

      systemd needs improvements in many areas - I can't argue with that.

      However, it's worth noting that in my past few days of playing with CentOS 7, it's been tremendously faster than CentOS 6 on every workload I've been able to throw at it.

      I haven't done a deep dive to figure out why exactly, but I have noticed 'tuned' running, doing some dynamic system optimizations, it seems via systemd's control of cgroups.

      Lennart's handling of bug reports makes my blood boil as much as the next guy, but there may very well be some baby in that dirty bathwater.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    20. Re:Systemd? Not on my system... by gweihir · · Score: 4, Insightful

      Emacs never tried to crush vi. Systemd is trying to crowd out all other init-systems and to remove choice from the user. That is a bit different.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    21. Re:Systemd? Not on my system... by gweihir · · Score: 4, Insightful

      I like this analogy! The reason I use Linux is that I like excellent, simple and clear tools which are decidedly "user serviceable parts inside". I do mess with the init-system in occasion, and some of my hacks have been reliable with the traditional init for more than a decade now. The systemd answer to that is "submit a patch", in C no less and if they do not like it (which is standard), have it rejected. How that can be viewed as an improvement is beyond me.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    22. Re:Systemd? Not on my system... by gweihir · · Score: 4, Insightful

      The main beef I have with it is the "embrace-and-extend" cancer-like model that is used to push it on people by. If it were just a cultured, friendly alternative, but anybody not wanting to use it could easily be without it, I would have no problem with it at all. Instead it is a clear, uncultivated power-grab in the Linux-sphere and that is not good at all.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    23. Re:Systemd? Not on my system... by gweihir · · Score: 2

      For the reasons you describe, it is not on my system. Currently, long-term support for Debian without it looks like a temporary solution, but eventually, I think, I will have to go to Gentoo. (Unless by that time a few more distros have woken up. There may be some reason Debian now has long-term support for the last version that does not make systemd mandatory...) I need security and reliability, not "faster boot times".

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    24. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 1

      What kind of self-respecting nerd would encode his source in UTF-16?

    25. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      daemontools supported all of that about ... ten years ago now?

    26. Re:Systemd? Not on my system... by UnknowingFool · · Score: 1, Insightful

      I would have to disagree with the analogy of embrace and extend as systemd is open source whereas MS products were not. And you can use alternatives but it may be more work to maintain them.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    27. Re:Systemd? Not on my system... by UnknowingFool · · Score: 1

      And it hasn't been maintained in 12 years or so.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    28. Re:Systemd? Not on my system... by gweihir · · Score: 1

      The main improvement systemd needs is that is has to stop forcing itself on people and raping their systems. It has to be an option among many, not the "one true way". And forcing itself on people at this crappy, early stage is beyond anything I have ever seen, and can only be attributed to total disrespect for all Linux users. If systemd were stable, secure and well-documented, I would say these people were just severely misguided. This way I can only call what they are doing outright malicious.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    29. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      ...not on mine either.

      Not sure yet if systemd is a virus or malware infection.
      Regardless, do they have to pedal this crapware so ubiquitously?

      Damn right! Keep those bicycles off my system (and my lawn!)

      (I think you meant "peddle") ;P

    30. Re:Systemd? Not on my system... by fahrbot-bot · · Score: 2

      Systemd definitely solves a problem that exists. Unfortunately, it solves it in the same way that a nuclear warhead solves the problem of rat infestation.

      To be fair, systemd have never irradiated anyone, like Godzilla - yet.
      (Though, we should all fear the day it does...)

      --
      It must have been something you assimilated. . . .
    31. Re:Systemd? Not on my system... by gweihir · · Score: 1

      Well said.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    32. Re:Systemd? Not on my system... by gweihir · · Score: 2

      I completely agree to that. I do not object to systemd's existence. I disagree with the way it is forced on people. Next, it will probably try to invade libc. It already tried to mess with the kernel, but fortunately was stopped. At this time, it seems only Gentoo and Slackware have long time plans to do without it or leave it optional. Gentoo had to fork udev to make that possible. All other major distros seem to have caved to pressure and, as far as I can see, without any arguments that are based on any real merit systemd has.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    33. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      And why should I give a rats ass what some random blogger thinks about software? Pappp's opinion about SystemD is as relevant as the homeless person down the street.

      So he's made some reasonable observations, tied them together, and you have nothing to say about them? You're really just going to dismiss them offhand like that? That's funny, because I always figured /. to be healthily skeptical. What happened to weighing arguments on their merits and not the titles attached to their speaker's name?

      There will always be a Linux distribution that doesn't use systemD, if you are so adamant about not using it, don't use it instead of trying to convince everyone else it's evil because CLEARLY everyone else doesn't agree with you. You people that hate systemd are worse than "born-again's" and mormons and just like them you don't have the answer and I don't care what you think about it.

      The problem is, at some unspecified point in the future it may become impossible to have a working system without systemd. It's more obvious in the case of a "graphical system" since we already have desktop environments adopting systemd, and now we've got X doing it. This is a conversation that needs to be had. A small cadre of developers is making choices which will likely impact the *nix community for a long, long time and the proposed solution has unmet criticism.

      I never claimed to have the answer. I don't need to have a valid solution to criticize an existing one; the criticism remains just as valid.

    34. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Systemd needlessly adds complexity. Maybe for sysadmins it's worth it, but I'd take the simplicity of init scripts over the mess that is systemd any day. Mind you, I use systemd due to it being the standard on Archlinux. It's nice that it's parallel but it's a pain to use when compared with SysV.

    35. Re:Systemd? Not on my system... by armanox · · Score: 1

      Not really, because the systemd group is creating the issue.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    36. Re:Systemd? Not on my system... by DeHackEd · · Score: 5, Interesting

      Here's a true story. I was in a CentOS 7 system via chroot and trying to troubleshoot some problems. If it were CentOS 6 I would just run "service rsyslog start" and have syslog running in the chroot so I can get the diagnostics I was expecting, but since systemd wasn't actually running I couldn't do that. I had to launch rsyslog directly by command-line, but then it didn't listen on /dev/log like it's supposed to and I had no logging. After all, it's systemd integrated now and gets its listen socket a different way. And this is just the most recent incident.

      Systemd may be technically better than sysvinit but the latter is just shell scripts which are sufficiently independent of anything else and just work. Systemd takes over your machine and wants to get its hands into everything to the point that you can't even use it anymore without systemd. This is what we're worried about what will happen to X.Org and other software.

    37. Re:Systemd? Not on my system... by armanox · · Score: 1

      Not the story here. We are not moving to RHEL 7 because of systemD (and I don't make that decision, although I support avoiding systemD. It doesn't offer me anything but headache).

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    38. Re: Systemd? Not on my system... by Anonymous Coward · · Score: 1

      Why couldn't you just use journalctl?

    39. Re:Systemd? Not on my system... by Maltheus · · Score: 1

      I've just made it back from RTFA and Phoronix is calling it "Optional systemd Support".

    40. Re:Systemd? Not on my system... by dbc · · Score: 1

      Great link. Very well stated.

    41. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      And why should I give a rats ass what some random blogger thinks about software? Pappp's opinion about SystemD is as relevant as the homeless person down the street.

      Pappp gave a rational criticism of Systemd. You resorted to ad hominem attacks.

    42. Re:Systemd? Not on my system... by gweihir · · Score: 4, Informative

      I think the analogy is completely valid. Sure, closed source is even more effective at embrace & extend and at forcing technology on users they do not want, but the same principle applies here.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    43. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Well there are advantages to systemd whether you personally like it or not. Like automatic dependency handling, parallel service starts, monitoring built-in. [...]

      I've been IT for over ten years now, and I have never found that I actually needed these things on the servers I've run over the years. Not on FreeBSD 4-10, not on Solaris 2.6/7/8/9/10, and not on the various Linux incarnations (RH, Fedora, Debian, Ubuntu).

    44. Re:Systemd? Not on my system... by marcello_dl · · Score: 1

      Indeed debian has extended support for debian 6, we are on debian 7, but systemd-logind is the only thing installed.

      On the other hand it is entrenched like the monster in Alien.

      # aptitude purge libsystemd-login0

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    45. Re:Systemd? Not on my system... by Darinbob · · Score: 1

      He's suit in disguise!

    46. Re:Systemd? Not on my system... by Darinbob · · Score: 2

      However, systemd is not the only way to solve those problems. Overall it seems to have more politics than technical advantages that surround it.

      The real problem is that so many systems "require" it so that you can't escape it. If you want newer alternatives then you stick out as a subversive. The idea of simple tools that do simple things well falls by the wayside as the distros attempt to be the fastest booting things out there, or by mimicking other systems.

    47. Re:Systemd? Not on my system... by Darinbob · · Score: 1

      Yes, there is too much political smog that surrounds it. The fights for and against it very often devolve into political squabbles. Many egos jockeying for position. So in that sense it very much has an open source culture behind it.

    48. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      No, because choosing the wrong editor only causes pain for yourself. Rather, systemd is being painfully forced on everyone.

    49. Re:Systemd? Not on my system... by nabsltd · · Score: 1

      systemd makes system administration a joy.

      Please explain, in detail, what was so difficult before that is now much better because of systemd.

    50. Re: Systemd? Not on my system... by Anonymous Coward · · Score: 0

      cgroups, kernel capabilities, boilerplate code when writing own system services, cgroups, cgroups, cgroups, did I mention cgroups?

    51. Re:Systemd? Not on my system... by Darinbob · · Score: 2

      Agreed. I never saw a distribution release that said "we're replacing vi with emacs", or "X finally did the work necessary to interoperate with emacs", and no flame wars that people who still use vi are luddites holding back the advancement of Linux.

    52. Re:Systemd? Not on my system... by goarilla · · Score: 1

      You run X on servers ? Nevermind, ... what was your (inital) opinion of Apple creating launchd to replace
      init, cron, at, ... ?

    53. Re:Systemd? Not on my system... by Darinbob · · Score: 1

      True, it hits the key point that systemd is not a unix-like way of doing things. That isn't to say that it's a bad thing in itself (if you subtract out all the politics). So the question is whether you want Linux to remain a unix-like system or not.

      I haven't seriously used Linux in awhile, but it just doesn't seem much like Unix anymore, and it's not just systemd doing this.

    54. Re:Systemd? Not on my system... by NoNonAlphaCharsHere · · Score: 2

      I'll even push the analogy a little further. Once you use (or, more likely are forced to by some other project) the tweezers from the Swiss Army knife, it FORCES you to use it as your ONLY tweezers. And your ONLY knife. And your ONLY screwdriver. And your ONLY corkscrew. And your ONLY toothpick. And your ONLY scissors. And your ONLY saw...

    55. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Hey dumbass, the D in systemd is not capitalized. Just like its httpd and dhcpd not httpD and dhcpD.

    56. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Indeed debian has extended support for debian 6, we are on debian 7, but systemd-logind is the only thing installed.

      On the other hand it is entrenched like the monster in Alien.

      You're going to love when jessie goes from testing to stable! Systemd is now a dependency of udev, which is a dependency of xserver-xorg-core. In other words, remove systemd, remove the entire desktop...

      I tolerated it because systemd was only forcing the logind part on me, but updating from 204-8 to 204-14 (which is current in testing) will make the conversion complete by obliterating init. I've been putting it off because I expect difficulties in the switch -- it's an old install that's been upgraded through multiple releases -- and would rather not deal with an unbootable system right now.

    57. Re:Systemd? Not on my system... by gweihir · · Score: 1

      I think even of my Linux Laptop as a "server". But you are right, headless servers of course do not get X, unless there is some stupid distro dependency, like a gnuplot installation suddenly pulling in a full X server...

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    58. Re:Systemd? Not on my system... by rahvin112 · · Score: 2

      I get your intent but you really messed up the delivery. The Mormons do believe Jesus is their lord and savior, so arguing that someone doesn't care whatever wacky thing they believe if they support that statement would be exactly the opposite of your intended meaning because it's in fact true.

      My point is that the anti-systemD propaganda out there runs from it's all a redhat conspiracy to personal attacks on the author. Some talk about systemD violating Unix philosophy, very few talk about implementation and I've seen almost no comment what it actually does. Most of the attackers have never actually used it, only read blog posts about philosophy and redhat conspiracies.

      Which is all relatively silly because no one is forcing you to use it. (of course other than the conspiracy theorists who claim this is a redhat plot to force everyone to do everything the redhat way). Let me say that again, even if your favorite distribution uses it and it become popular in the Linux community such that it's support is incorporated into numerous packages you are never going to be forced to use it. There is ALWAYS going to be a distribution that doesn't use it. And even if there isn't and it takes over Linux completely there is always one of the BSD's.

      That is what is so bloody stupid about this whole I hate pottering and systemD BS. Pottering and RedHat are not trying to destroy Linux, they aren't going to hold you down and force you to use SystemD. You don't like it? Don't use it. If it gets so popular other packages depend on it, stop using those too. This is argument is beyond stupid. It's free software for gods sake, if you hate it that much you can always pay someone else to make software that works around it.

    59. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      vs a simple tool that does one thing very very well.

      You're an idiot.

    60. Re:Systemd? Not on my system... by suutar · · Score: 1

      We don't like thinking it's inevitable yet. We like thinking that maybe the distros that we used to use and love can be convinced to stay the way we love them instead of growing apart.

    61. Re:Systemd? Not on my system... by Aighearach · · Score: 0

      Yeah, system admins and developers just loved the only SysV init and writing init scripts! They hate it when they have to switch to systemd and instead of writing a giant obtuse bash script, they just have to create a symlink. Especially since every has the simple syntax and semantics of bash memorized, and they might have to look up what to symlink to since they're new to systemd.

    62. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      I don't think you even know what "embrace and extend" means. Odd, given your user ID. Alzheimer's? Oh, wait, I get it, it was just "flamebait."

    63. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      systemd is the solution that exists though, and is being standardized on.

      All of the other SysV replacements either lack the features, or have significant problems.

    64. Re:Systemd? Not on my system... by Aighearach · · Score: 0

      This is actually ignorant lies. It is modular, but nobody is writing alternatives because the actual individuals parts are actually well enough written that they're hard to replace, so no distros do. And users don't make these choices, they just choose between distros.

      It isn't "demonstrably" worse at anything, it is "subjectively" worse to people who don't like it. Most objective metrics, it is better at everything. Maybe you still don't like it for other reasons. Maybe those are great reasons. But no need to be dishonest about what type of choices are being made.

    65. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      yeah systemd showed up at my door with a baseball bat and demanded that I switch to a distro that uses it!

      Sorry, false alarm, it was just the pizza guy.

    66. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      So now your real complaint comes out. They rejected your contributions because your contributions were using the old system it replaced. No, they aren't going to want to roll in your SysV init scripts. But there is compatibility with them for the users. You can still use your init scripts, and write new ones.

      You're just butthurt that they didn't accept your patch, that didn't even attempt to use the same technologies and languages that they're using. Fail.

    67. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      I use both every day. Emacs is the best code editor, and vim is the best system config editor. I've been using both for 15+ years.

      And BTW, I'm running systemd and it didn't eat my cat or whatever when I use an old SysV initscript. Actually, it has backwards compatibility for that! While I do really like systemd, I haven't converted any of my own initscripts. Mostly because I'm the only one using them. If they were in released software, well, it is normal that SysV get replaced eventually and it is a small burden to write a dozen lines of code every 20-30 years when there is a large scale shift to a new startup system. Especially when most software doesn't need startup support!

      No hatred is stronger than ignorant hatred.

    68. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      It is not up to you to decide if it is inevitable that others will choose systemd.

      Who is trying to force who? People who hate systemd seem to hate it so much they want to destroy it, wipe it from the face of the Earth! systemd supporters don't really care what other people use, they want a better, modernized init running on their own systems. It is normal to have distros that would adopt a new init, and others that don't. There is no reason to be against systemd just because you don't want to choose it.

    69. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      Homeless people value rapid startup time more than almost anybody, because the library limits that number of hours patrons can use the free wi-fi per day. And homeless linux users usually have ancient, dilapidated laptops that are considered by others to be past end-of-life.

      So I think the homeless guy has a legit use case for systemd, and people who want to choose something else should just leave him alone and let him have his systemd. Nobody is trying to force them to use it.

    70. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Why do you have X on your servers? Honestly, what purpose does it serve?

    71. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      I don't know why these anti-systemd posts get upvoted so much.

      Because these days most slashdot users don't even know a sysadmin.

    72. Re:Systemd? Not on my system... by nctritech · · Score: 2

      Open source is irrelevant when a significant number of critical projects required to build a functioning graphical desktop are tied to the undesirable project. It's hard to maintain a fork as it is, but 10 forks? 20 forks? At some point the hard dependency on systemd eventually boxes in everyone.

    73. Re:Systemd? Not on my system... by Blaskowicz · · Score: 1

      I've been thinking that my next computer ugprade (which is otherwise not really needed) will allow me IOMMU/Vt-d and VGA passthrough, so maybe I can get back to Windows for gaming. But having two graphics card, and a KVM or two sets of keyboard/mouse etc. and a way to deal with the monitor(s) would be a pain so why not just use the Windows desktop and use linux via ssh, X11, RDP etc.

      If debian 8 can be used without systemd if you don't use a desktop, it could be done that way! lol.
      Anyway there's a udev fork and debian/KfreeBSD, debian/Hurd will go on, certainly with low priority but there's a possiblity that a debian/linux/without-systemd is unofficially made building on the work for those?

      Now what about Ubuntu, which is what I actually use.. (because it's just debian with more packages and more stuff just working, and linux Mint is awesome). Well we're fucked. Mint 17 is an LTS with versions based on Ubuntu 14.10, 15.04 skipped, perhaps that's good enough but what happens in 2016/2017.. I don't fucking know! I guess I'll use systemd anyway. Or go back to Windows 98, install an old Cygwin and browse the web with Internet Explorer 5.

    74. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      And keeping the discussion on topic, what exactly were you doing with an X server on those servers?

    75. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      You seem to be emotionally attached to systemd and your trolling is quite transparent.

    76. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      I get it now--you're astroturfing support for systemd. It all makes sense now!

    77. Re:Systemd? Not on my system... by suutar · · Score: 1

      I'm not against systemd. I'm just bummed that I have to leave Ubuntu to avoid it.

    78. Re:Systemd? Not on my system... by nctritech · · Score: 2

      Except the people who control systemd (Red Hat) and the people who control everything on freedesktop.org (Red Hat) are the same, and that power is being used to crowbar systemd dependency into absolutely critical components on freedesktop.org that every significant Linux graphical desktop environment relies on. The real problem here is that Red Hat controls critical Linux ecosystem components and has used that control to force people to do what they want. Shout about "open source" and "choice" and "forks" all you want but the fact remains that the manpower required to maintain "no systemd dependency" forks is increasing exponentially, and even a user who can maintain one or two forks could simply never hope to maintain them all.

      What will end up happening is people who don't want it and can't find working forks that don't force it down their throats will stick with old versions. That means less security, unfixed bugs, and no more enhancements. Eventually that will crowd out anyone who buys new hardware because old software doesn't recognize and/or work with the new hardware.

      If systemd had not absorbed all the important freedesktop.org projects and was not a hard dependency for GNOME and other important things, the vitriol would not happen. As long as Red Hat continues trying to box people into their vision of how things should work and use tactics befitting late-90's Microsoft to slowly choke out alternatives, the hatred of systemd and the vocal backlash against it will continue and the backlash is completely justified and proper.

    79. Re:Systemd? Not on my system... by Blaskowicz · · Score: 1

      Ever heard of a multi-user machine? By definition it's both a desktop and a server. Or right-clicked on a folder in Windows 98 to share it? Your Windows 98 desktop is now a server.

      We have the freedom to do whatever the hell we want. Had a network with an Ubuntu 8.04 machine that was extremely powerful (four cores, four gigabyte of RAM, a multi-hundred-gigabyte HDD) : it acted as an LTSP server for thin clients (one, two or three), served storage with Samba, proxy and wad even the local DHCP and DNS for that network segment. Single point of failure, but it was always on and worked, so who gives a shit.

    80. Re:Systemd? Not on my system... by arth1 · · Score: 1

      If they were in released software, well, it is normal that SysV get replaced eventually

      I guess that depends on your definition of eventually. Good working designs don't have to be replaced any time soon.

      We still have steering wheels on cars, despite some people in the 70s thought that joysticks and hand controlled throttles would be much better. Most of my clothes have buttons, despite Velcro and Ziploc. Heck, even zippers did not replace buttons.
      Change for the change of change is seldom a recipe for success. The number of admins who complained about sysv init and not having an octopus program with hooks into everything were not really high. In fact, most admins have praised the toolbox approach where mounting is a completely separate thing from starting a daemon, and where nothing is truly integrated but everything is as separate as possible. The Unix mantra is "do just one thing but do it well".
      I don't really care whether systemd shaves twenty seconds off the boot. My systems run for years, and take ten or more minutes from power-up doing hardware checks and RAID enumerations until they even start booting. That the boot process isn't abstracted and can be troubleshot by a human is far more important. So is the ability to easily have different systems with the same installation base do different things. Or make changes that you know won't take effect immediately. Or replace one thing without replacing ten more. Or use config files that you can do a simple search/replace on, unlike MSDOS .ini files where you have to be aware of the "section" abstraction.
      K.I.S.S., and avoid abstractions like the plague it is.

    81. Re: Systemd? Not on my system... by armanox · · Score: 1

      And does anyone actually care about or use these features?

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    82. Re:Systemd? Not on my system... by Barsteward · · Score: 1

      you'll have to explain that to me. how does systemd force you to use it? Doesn't init force you to use it if its the system that drives your machine. Is it not because of the distro you chose to install uses systemd? Or are you expecting a choice (like the menu in Grub) to choose between the two systems on how to start your machine?

      i'm personally on the fence as i don't know enough about either but as long as my system runs i'm happy but i would like to know more about the real advantages/disadvantages of both before i fall off the fence. All is sounds too personal rather than technical at the moment.

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    83. Re:Systemd? Not on my system... by bingoUV · · Score: 1

      You do realize that X is used by non-linux UNIXes?

      And you do realize that systemd does not support non-linux?

      Why do you think these two together make a good idea?

      Look - systemd is fine. But hard dependency of software on systemd is not fine. "Hard" dependency of software on init never created an issue - because it just meant that a shell script was shipped along with the software to start|stop|restart|status the software. Systems using systemd/upstart/SysVInit could use that shell script, or maybe not use that and roll something of their own.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    84. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      (Same AC checking back in here)

      I've been thinking that my next computer ugprade (which is otherwise not really needed) will allow me IOMMU/Vt-d and VGA passthrough, so maybe I can get back to Windows for gaming. But having two graphics card, and a KVM or two sets of keyboard/mouse etc. and a way to deal with the monitor(s) would be a pain so why not just use the Windows desktop and use linux via ssh, X11, RDP etc.

      I've considered the same thing to replace dual booting. Even if I decide not to do it I'm going to be sure I get a motherboard and cpu combination that supports it so I have the option. Maybe test it out, see how it works, and decide from there.

      Going off topic a bit, but if you do try it, be wary of nvidia for the guest OS: I've seen reports that gtx cards past the 400 series don't work with VGA passthrough unless you do some fairly invasive card modification. Nvidia started artificially restricting it in the consumer-grade cards, probably to push sales of their $2000 GPUs for virt users. People have reported successfully bypassing this by performing physical modification of their cards, but I don't think that's a very attractive solution. If they don't want the business, fuck 'em, I'll go with an AMD GPU next time.

      (TL;DR: use AMD GPUs for VGA passthrough, it hurts less.)

      As for running a Win desktop, I happen to like my KDE setup enough that I'd rather deal with virt, wine, dual-booting, etc. I'll even learn to live with systemd when I have to, I suppose, though I'll be dragged into it kicking and screaming the whole way. ;)

      If debian 8 can be used without systemd if you don't use a desktop, it could be done that way! lol.
      Anyway there's a udev fork and debian/KfreeBSD, debian/Hurd will go on, certainly with low priority but there's a possiblity that a debian/linux/without-systemd is unofficially made building on the work for those?

      You're supposed to still be able to use other init systems if you want instead of systemd, even with jessie, so I'm not sure what the brain damage is right now that's making it try to auto-remove everything. Hopefully it's some sort of packaging/dependency error that will get resolved.

      To better explain, certain desktop bits (and udev) started needing parts of systemd within the past couple months. Systemd itself didn't replace my init, just did some other non-init things like login management. Insidiously putting its tentacles in things, but not the part I object to, the init. The sysvinit package accepts upstart, systemd, or sysvinit-core as init systems, so everything was happy up until recently, when part of the update process started needing systemd-sysv.

      (update)
      While writing this I did some more digging and I found the problem, and a bit of hope. The update to 204-14 also updates the libs, right? libpam-systemd apparently gains a dependency on systemd-sysv or systemd-shim, which, according to the package description, "emulates the systemd function[sic] that are required to run the systemd helpers without using the init service."

      So, installing systemd-shim manually first fixes the dependency problem and everything is happy. The problem is that the dependency is buried inside a random required lib package instead of systemd itself, so it's rather obtuse and looks like systemd-as-init is being forced on you. Looks like Debian's still trying to keep systemd as optional as possible, at least for now. Though the solution is so non-obvious that it almost seems deliberate. I'm going to bookmark this comment in case I forget about the systemd-shim bullshit later.

      I should probably feel dumb for not noticing the systemd-shim bit before, but I was just checking the udev and systemd dependency chain while diagnosing. Didn't expect the answer to be in a lib instead of the main packages.

      Now what about Ubuntu, which is what I actually use.. (because it's just debian with mo

    85. Re:Systemd? Not on my system... by bingoUV · · Score: 1

      Yes. And that is why a dummy / fake systemd seems to me to be the only realistic solution. It need not have all the features of systemd, but it should be able to call scripts on simple systemd calls. That should be able to fit in with SysV init, or other initialization systems.

      The software packages that contain this fake systemd will declare to provide systemd to the software package manager.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    86. Re:Systemd? Not on my system... by nctritech · · Score: 1

      Critical components on freedesktop.org now have mandatory systemd dependencies. To continue receiving bug and security fixes, those "mandatory systemd" versions must be adopted by distros, that is unless they don't want things like udev, evdev, GNOME, etc. Distros are adopting systemd because they really do have no choice. Red Hat crowbarred it into so many important things (or absorbed those things into systemd entirely) that the effort required to dump it is growing faster than people can fork away.

      Your distro of choice shoves it down your throat because Red Hat tainted things with it that are MANDATORY for supporting fundamental features of an interactive graphical desktop system. Red Hat is essentially the late-90's Microsoft of the Linux world. People love to blame Poettering but the truth is that Red Hat is his employer and Red Hat is the driving force that's jamming this unwanted garbage down everyone's craw. It's classic "embrace, extend, extinguish."

    87. Re: Systemd? Not on my system... by nctritech · · Score: 1

      No.

    88. Re:Systemd? Not on my system... by Kiwikwi · · Score: 1

      Systemd vs init: [...] complexly and half-assed, vs [doing] one thing very very well.

      SysV init doing anything "very very well"?

      HAHAHAHAHAHAHAHAHAHAHAHAHAHAHA!

      (phew) Thanks, that brightened my day!

    89. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      You do understand that optional support for systemd doesn't have anything to do with requiring it, so it wouldn't impact OSes that don't use it... right?

      Talk about d' oh! lolol

    90. Re:Systemd? Not on my system... by pthisis · · Score: 1

      No, generally emacs users are happy with systems that have both emacs and vi, and emacs won't prevent vi (and all the tools depending on ex/ed) from working.

      Except when distributions screw up their dependencies, which they almost all did for about the first 10 years.

      Emacs' crappy legacy ctags was part of the emacs package rather than a separate ctags package (despite the fact that emacs itself prefers etags). Hence it was impossible to install emacs and have modern functional code navigation in vi (vim/elvis/nvi) without overriding the rpm/dpkg dependencies or some other hack.

      (This is not emacs' fault, it's the distributors who screwed it up for years).

      --
      rage, rage against the dying of the light
    91. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      Go look up how old SysV init scripts are, and then ask yourself if those decades count as "any time soon" from when it was adopted. It is silly to start the measurement now, after decades of sysadmins complaining about the poor feature set. You spend decades being told, "we'll have something better someday" and then when it finally arrives and works and does all the stuff that sysadmins wanted (cgroups, better logging, etc) then people are worrying if it is too "soon." Well geeeeeeeeeee, why wouldnn't it be late? Seems like a fake complaint to me. Not sure how you can compare it to cars with joysticks, which drivers haven't been asking for.

      Also, it is very telling about your attitude that instead of addressing what sysadmins say is good about systemd, you just call it names like "octopus." Yes, I'll agree they didn't request any of the features using pejoratives. People who value a feature set usually discuss it using real terms. So the feature requests are not "octopus" but "modular centralized logging" and "better process groups" and "parallel service startup" and "effective service dependencies." All of these things are directly related to what SysV init does too. Just because it is less effective at them, you count it as doing one thing. Except there is more than one thing that has to happen right there, and SysV init does more than one thing too.

      The KISS argument is especially daft. How is a mishmash pile of init and scripts and logging somehow more simple? Every part is complicated because it is a giant "pile." And process management is complicated with SysV by the complete lack of needed security and management features. cgroups reduces overall system complexity by providing a means of managing process groups. cgroups are a new feature in the linux kernel. It exists for real reasons. I guess you think it would reduce complexity and keep it simple to just tack on cgroups to what SysV init already did, right? Oh, wait, you only want it to do strictly one thing. Except it already does more than one. So just, no cgroups, right?

      None of your complaints are actual problems with systemd. It is just repeated propaganda. And nobody using a software package cares if you don't need all the features, like faster boot time. Isn't it rather freakin' obvious that that is a feature that is going to be valuable for many use cases? You don't have that use case, fine. And if you did, would you still be against software that provides it?

      You really think systemd makes it so humans can't troubleshoot? Wow, those sysadmins celebrating it must be alien superheros. Oh, wait, no. We're humaans after all. Trust me, humans without an irrational hatred of systemd have no trouble at all troubleshooting it. There are even cheat sheets that map the old commands, to the new equivalent ones. It would be a funny set of arguments to listen to if somebody claimed that youngsters who learn on systemd would have an easy time troubleshooting an old SysV box, based on this claim that SysV is more amenable to human troubleshooting. I guess you'd have to resort to comparisons that claim that SysV is even easier than DOS, because learning bash scripting and the standard SysV sh libraries is so much easier than learning that an .ini file has sections.

    92. Re:Systemd? Not on my system... by bingoUV · · Score: 1

      For many software in many situations, it is not optional , see http://sporkbox.us/blog/?r=pag... for just one small example.
      Not sure how X will turn out.

      Whereas support for SysV init is naturally optional as I explained earlier.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    93. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      For many software in many situations, it is not optional , see http://sporkbox.us/blog/?r=pag... for just one small example.
      Not sure how X will turn out.

      Whereas support for SysV init is naturally optional as I explained earlier.

      One optional is not different than the other optional. I can assure you, as somebody who read the story, that it is "optional" as in "optional" and there is nothing about any of it that would create a technical reason for it to not be optional. It is like saying that if X is ported to OSX, then Linux users will have to switch to macs. It is complete nonsense. Conspiracy-theory level nonsense. In fact, an optional feature being accused of having some plot to become mandatory... that is a conspiracy theory! lolol

      If you read your own link you'll find there is no conspiracy at all, arch is just a sucky distro that doesn't have the dependency tree mapped out well enough for users to choose the combination of packages they want. It then goes into a bunch of personal attack against the author. Who wrote the software does not matter; the software runs the same either way. So as soon as you see those types of attacks, you should really be able to recognize that you're being offered a clique-attack, and not a real technical objection.

      You link seems to suggest that a software developer should not be allowed opinions; should not be allowed to push for distros to standardize on their ideas. You'd be out of developers if you enforced that consistently. But as is fitting of a clique-attack, they only set this standard for the one person they're circling around.

      If you think Arch Linux discourages choice, my advice is to use Fedora. It is funny too, since the guy you hate so much works for RedHat. But RedHat's distros have the time (and money) to build out the dependency trees so that you DO have choice. And as a RedHat employee, why would you blame Arch sucking on him???

    94. Re:Systemd? Not on my system... by arth1 · · Score: 1

      cgroups reduces overall system complexity by providing a means of managing process groups. cgroups are a new feature in the linux kernel. It exists for real reasons. I guess you think it would reduce complexity and keep it simple to just tack on cgroups to what SysV init already did, right?

      What does cgroup have to do with anything? I run several systems with cgroup and sysv init. The two are separate, and there is no need for systemd for that.

      None of your complaints are actual problems with systemd. It is just repeated propaganda.

      Actually, they're all mine - no repeat at all. I have been a system administrator since the early 90s, and know what problems Unix like systems have. sysv init has not been anywhere near the top of that list. It was a great improvement over starting apps directly from inittab, and is something that has been working and has kept on working, precisely because it's so simple.

      I guess you'd have to resort to comparisons that claim that SysV is even easier than DOS, because learning bash scripting and the standard SysV sh libraries is so much easier than learning that an .ini file has sections.

      I say this with feeling: You are an idiot.
      The problem is obviously not "learning that an .ini file has sections", but that you cannot easily use standard Unix tools on an .ini file because of the sections. sed -e 's/port=.*/port=587/' works great on standard config files, but not .ini files where more than one section may have a port. .ini files are inherently automation unfriendly, because the lines depend on a context you can't derive from the line itself.

    95. Re:Systemd? Not on my system... by goarilla · · Score: 1

      Are you insulting the samba project ?

    96. Re:Systemd? Not on my system... by Blaskowicz · · Score: 1

      Wow, thanks for answering my rant and especially the bit about hardware modding an nvidia card. How silly.
      On another note, H264 streaming of a game from Windows VM to display on the linux desktop would be a way to do the reverse. So you keep the linux desktop. The encoding is done real time by a dedicated unit on the GPU.. and that feature is especially supported on Geforce 600 and 700 series!, i.e. the generation past 400 series. So that's why it's disabled (though there's some level fo consumer support for this if you use a separate computer)

      As a side rant, years ago I thought the port of KDE to Windows meant we'd be able to run the KDE desktop on Windows but no it was more about the infrastructure and libs to run apps. There may be some hacky way to barely run KDE desktop components (run an X11 server, do some ugly hacks..) but I suppose it would be a total waste of time.

    97. Re: Systemd? Not on my system... by goarilla · · Score: 1

      Cgroups are used by VPS resellers IIRC.

    98. Re:Systemd? Not on my system... by arth1 · · Score: 1

      Are you insulting the samba project ?

      No, not at all. They produce the very finest shit eating utensils in the world. It's not the utensil that is the problem.

    99. Re:Systemd? Not on my system... by bingoUV · · Score: 1

      RedHat/Fedora is not better as I personally know. Removing systemd removes an enormous amount of "unrelated" software.

      And no, Fedora doesn't have time to create correct dependency mapping. For last three releases, installing vim-enhanced "conflicts" with vim-minimal. Easy solution is to remove vim-minimal. Which also removes "sudo". Those who don't set root password and depend on sudo, now cannot install any thing as root.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    100. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Wow, thanks for answering my rant and especially the bit about hardware modding an nvidia card. How silly.

      No problem, I always try to follow up on posts in case there are questions or anything else, even when I post anonymously here. Not much point with logging in since I comment rarely; usually everyone else covers any useful input I'd make before it even hits my RSS reader, so I just lurk and anon-post here. On SoylentNews I actually comment enough to bother being logged in (as Marand), because there aren't as many people contributing already, so I'm more likely to have something to say that won't be redundant.

      This page on the Xen wiki has info about hardware that works, as well as some information on what cards need modification. It also has some references such as this one detailing the sort of work required. The actual modification doesn't seem too bad, but the fact that it's needed at all is bullshit. Hell, I'm not even sure what will happen if you try to use the cards for dom-0 (host) while using an AMD or older nvidia card on a guest.

      Something else I learned while researching this is that nvidia seems to be deliberately crippling the hardware at the driver level if it thinks you're not using a quadro. I found where this guy went from a 200 series to a 400 series gtx and noticed a massive performance drop on certain operations. He even re-implemented the operations with shaders and the performance difference evaporated, which makes it sound like deliberately gimping of certain GL calls that are used more in non-gaming apps, to sell Quadros.

      Also, it seems I was mistaken about the 400 series. I thought I saw before that the 400s would work fine, but the Xen page says they need modding as well. I know my gtx 260 should work on a guest OS, but that's a hell of a downgrade. If/when I try I'll just have to pick up an AMD card I guess.

      I've been using nvidia GPUs since the '90s because their drvers always worked well, especially in Linux, but lately I've been finding a lot of reasons to look elsewhere. I hate that, but I'm not going to tie myself to a brand if they're going to go out of their way to make it harder for me to use. Same reason I tend to use AMD processors; it's far easier to find an AMD cpu+mobo that works with all the virt stuff you want.

      On another note, H264 streaming of a game from Windows VM to display on the linux desktop would be a way to do the reverse. So you keep the linux desktop. The encoding is done real time by a dedicated unit on the GPU.. and that feature is especially supported on Geforce 600 and 700 series!, i.e. the generation past 400 series. So that's why it's disabled (though there's some level fo consumer support for this if you use a separate computer)

      Good point; wasn't that supposed to be a selling point of that SHIELD thing nvidia was pushing? Plus Steam does something similar now and has a Linux client. It might actually be easier to run a second Windows machine with a kvm switch and then stream it to Steam running on Linux, now that the Linux client got support for it.

      The pro is that it's likely easier to set up, the con is that you have to duplicate your hardware unless you don't do anything cpu/gpu intensive on the Linux side, in which case you could just have a trash-box for the regular desktop.

      Thinking about it, I believe I'm still inclined to go for passthrough instead. I could set up a kvm switch and hook one monitor up to both displays, and just switch that monitor over when I want to play a game, or something like that.

      As a side rant, years ago I thought the port of KDE to Windows meant we'd be able to run the KDE desktop on Windows but no it was

    101. Re:Systemd? Not on my system... by goarilla · · Score: 1

      NFS is crap too and in my testing also slower.

    102. Re:Systemd? Not on my system... by Blaskowicz · · Score: 1

      Oh, I didn't check KDE-on-win for a long time. And anyway I feel at home in the GTK2 environments.

      I solved the problem of dual booting by leaving Windows for good. Part is I wouldn't ever reboot anyway (who wants to, and lose everything that's going on?), part is I was fed up with Windows 7 for petty reasons. Disk/memory intensive for my own taste, but foremost after ten years of using Windows 98 then XP with basically the same GUI, there were more than one thing that pissed me off. I had a hilariously ugly desktop at some point, with my attempts to make it more traditional.

      I made my life worse, had some ugly quirky desktops (ugly gnome2/mate layout, random combinations of mate/nautilus 3.x/xtce/lxde iwith duplicate tools and a broken icon there and the wrong file manager coming up.. CLI-only debian squeeze NAS that was semi fucked up.. lol!
      But in the end, Mint 16 Mate and Mint 17 Mate saved the day. I can install the latter on any buddy's laptop or desktop in 20 minutes, install or tweak just one thing or three and it's done!

      Now, what were we talking about..
      Yeah I will probably try KDE 5.1 (if it is to have such a versioning scheme) down the road. For psychological reason (let it double-extra mature) and because I now see a philosophical similarity with Mate. Provide a GUI that's still about the same a decade later, but really maintained and with ever so slight improvements here and there that I can't pinpoint but the thing feels ever more polished.
      I'm waiting on LXQt 0.8, too (more than KDE). When it's out I'll jump on it to try it first time. High hopes there. I think the main dev has good taste.

    103. Re:Systemd? Not on my system... by arth1 · · Score: 1

      NFS is crap too and in my testing also slower.

      But nfs does not take over and cripple your dns server.
      It's the hooks into and taking over parts that work fine on their own that's the problem with domain controllers and systemd. It goes directly against the Unix toolbox approach, and stifles innovation because now you have to do everything within the context of the super-program.

      (As for your testing, did you try with jumbo packets? NFS supports it, and CIFS doesn't. It makes a tremendous difference, especially for writes to remote RAIDs or disks with a 4k block size. Also, avoid distros that set up NFS to use tcp instead of the default udp. That's a huge performance killer, and not needed unless you use hubs instead of switches or need to tunnel the traffic.)

    104. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      XP's actually what pushed me to use Linux as my primary OS, with a bit of help from Vista. Did a system upgrade, went to reinstall XP, and it seemed like everything was great until I tried to boot. It managed to completely obliterate everything on the drive, partitions, everything, because it couldn't handle SATA but didn't bother warning me about it. No problem, just put the disc with the drivers in, right? nope, drivers were on a cd-rom and I haven't had a flopppy drive since around the time XP came out.

      I didn't want to use Vista (I'd tried it and hated it) and didn't want to deal with trying to fix XP's idiocy, so after about a decade of either dual-booting or running dedicated machines with each OS, I went 100% Linux-only, no dual-boot safety net. Eventually, after Windows 7 came out, I set it up as a dual boot for a handful of games, but the damage was done: I go months at a time between booting that partition, because I just don't need it. Windows had been little more than a front-end for launching PC games for me for years any way, so that time I spent without it at all just pushed me to get most of the stuff working in wine or a VM.

      7 is just tolerable enough that I'm okay with having it around for rare use, and I dare say it's actually better than XP in most ways, but I just like KDE more than either for actual desktop use. I've always liked trying different OSes, so learning new ones doesn't bother me. I adapt quickly enough that I don't get stuck in "I dislike this because it's different".

      That said, I'm not a fan of gnome3 from what I've encountered. I can live with razor-qt, lxde, gnome2, etc., though usually if I can't use KDE I tend toward windowmaker first, xfce second.

      Waiting a bit on KDE5 sounds like a good call. It's not going to be as painful as the 3.5->4 transition, but it's still going to take some time to iron out the problems and get enough things migrated over. Still, KDE4 is actually really good right now. I skipped the whole KDE4 migration pain by waiting until Debian transitioned away from 3.5, which meant I missed those early releases that everyone complained about :)

      LXQt, that's the one where lxde and razor-qt have a baby, right? Judging from what I've seen of razor-qt and lxde separately, that has potential.

    105. Re:Systemd? Not on my system... by goarilla · · Score: 1

      Also, avoid distros that set up NFS to use tcp instead of the default udp. That's a huge performance killer, and not needed unless you use hubs instead of switches or need to tunnel the traffic.)

      I'm not avoiding a distro if it chooses tcp over udp.
      Isn't using UDP instead of TCP removing that last bit of pseudo-security NFS has ?
      Aren't you now vulnerable to all sort of spoofing mayhem now ?

    106. Re:Systemd? Not on my system... by arth1 · · Score: 1

      TCP isn't noticably more secure than UDP - the extra fields in TCP are unsigned and can be spoofed too. There are even a couple of attacks that only works with TCP, like source congestion. The only "security" TCP buys you is if you have a dynamic real-time alerting system for tcp sequence errors and similar likely to be seen in spoof attacks. You don't have such an alerting system.
      Thus, security is implemented on top of the transport layer, where it works just as well for udp as tcp. The advantage of udp then is that you get more payload per encrypted or signed unit, thus higher speed.

      That said, the main use of nfs is within secure perimeters, where speed and transparency is the main goal. In which case all you need is a honor system access control, designed to prevent users and apps from doing bad things no matter who they (say they) are. I.e. the focus is on what is shared, and what's allowed, not who you share it to.

      Where Windows is very user focused in its trust based security model, Unix is very data focused.
      A typical Windows share will allow any user to write and execute whatever they like. The users don't understand the "Advanced Security" properties anyhow, so implementing it will just lead to complaints. If a client is compromised, so is the share..
      A typical Unix share will only allow users write and execute access to specific directories, no matter who they say they are. Remote root users typically get even less access, not for security but to prevent accidents. If a client is compromised, the shares should be safe.

    107. Re:Systemd? Not on my system... by goarilla · · Score: 1

      TCP isn't noticably more secure than UDP - the extra fields in TCP are unsigned and can be spoofed too.

      But it's a lot harder since you need to have the server believe you've established a connection and can't just dump spoofded data on the wire like with UDP.

      Thus, security is implemented on top of the transport layer, where it works just as well for udp as tcp. The advantage of udp then is that you get more payload per encrypted or signed unit, thus higher speed.

      What are you talking about: NFSv4 ?, ipsec ? What is this security you speak of.

    108. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      It is just lies and handwaving, "an enormous amount" of "unrelated" software... except, not.

      Your best example is that different vim meta-packages conflict? Yeah, generally with meta-packages, you choose one. And then you can also install an extra version from source in your home dir. That is the normal way to install 2. Sounds like user error. You set it up so you have to use sudo, with no backup access, and then removed sudo, and blamed systemd? Exactly.

    109. Re:Systemd? Not on my system... by Aighearach · · Score: 1

      I say this with feeling: You are an idiot.

      That feeling you're feeling is fanboiyitis.

      You just claimed your SysV init scripts are helping your software take advantage of cgroups. Then you called me names. Derrrrrrrrrr!

    110. Re:Systemd? Not on my system... by Blaskowicz · · Score: 1

      The Windows 7 partition is very useful : it allows to chkdsk a NTFS partition, and so it's good to keep it around.

    111. Re:Systemd? Not on my system... by arth1 · · Score: 1

      You just claimed your SysV init scripts are helping your software take advantage of cgroups.

      If that's what you read, you need to practice your reading skills, cause they suck.
      What I pointed out is that cgroups are separate from the init process, and can and do indeed run on sysv init systems too. cgroups has nothing to do with init, and runs separate from init no matter what you use for init.

      When you brought up cgroups as an argument, it appeared to be from a false belief that systemd was needed for cgroups to work - in fact, it's the other way around!
      And when systemd uses cgroups, it takes them over for its own purpose, which lessens the value of cgroups compared to systems where you are free to use cgroups from scratch. Freedom to choose - that's what makes Unix great. Poetterware takes away that freedom.

    112. Re:Systemd? Not on my system... by bingoUV · · Score: 1

      It is just lies and handwaving, "an enormous amount" of "unrelated" software... except, not.

      In a relatively small installation of total 2.9
      yum remove systemd | grep 'will be erased' | sort | uniq
      ---> Package ConsoleKit-libs.x86_64 0:0.4.5-7.fc20 will be erased
      ---> Package ConsoleKit.x86_64 0:0.4.5-7.fc20 will be erased
      ---> Package GConf2.x86_64 0:3.2.6-7.fc20 will be erased
      ---> Package ModemManager.x86_64 0:1.1.0-2.git20130913.fc20 will be erased
      ---> Package NetworkManager-glib.x86_64 1:0.9.9.0-20.git20131003.fc20 will be erased
      ---> Package NetworkManager-openconnect.x86_64 0:0.9.8.0-2.fc20 will be erased
      ---> Package NetworkManager-openvpn-gnome.x86_64 1:0.9.9.0-0.1.git20140128.fc20 will be erased
      ---> Package NetworkManager-openvpn.x86_64 1:0.9.9.0-0.1.git20140128.fc20 will be erased
      ---> Package NetworkManager.x86_64 1:0.9.9.0-20.git20131003.fc20 will be erased
      ---> Package PackageKit-glib.x86_64 0:0.8.13-1.fc20 will be erased
      ---> Package adwaita-gtk2-theme.x86_64 0:3.10.0-2.fc20 will be erased
      ---> Package adwaita-gtk3-theme.x86_64 0:3.10.0-2.fc20 will be erased
      ---> Package aic94xx-firmware.noarch 0:30-6.fc20 will be erased
      ---> Package alsa-firmware.noarch 0:1.0.27-2.fc20 will be erased
      ---> Package alsa-plugins-pulseaudio.x86_64 0:1.0.27-2.fc20 will be erased
      ---> Package alsa-tools-firmware.x86_64 0:1.0.27-3.fc20 will be erased
      ---> Package alsa-utils.x86_64 0:1.0.27.2-3.fc20 will be erased
      ---> Package anaconda-widgets.x86_64 0:20.25.15-1.fc20 will be erased
      ---> Package anaconda.x86_64 0:20.25.15-1.fc20 will be erased
      ---> Package asunder.x86_64 0:2.3-3.fc20 will be erased
      ---> Package at-spi2-atk.x86_64 0:2.10.2-1.fc20 will be erased
      ---> Package at-spi2-core.x86_64 0:2.10.2-1.fc20 will be erased
      ---> Package at.x86_64 0:3.1.13-13.fc20 will be erased
      ---> Package audit.x86_64 0:2.3.2-1.fc20 will be erased
      ---> Package avahi.x86_64 0:0.6.31-21.fc20 will be erased
      ---> Package b43-openfwwf.noarch 0:5.2-10.fc20 will be erased
      ---> Package biosdevname.x86_64 0:0.5.0-2.fc20 will be erased
      ---> Package bluez-cups.x86_64 0:5.12-1.fc20 will be erased
      ---> Package bluez.x86_64 0:5.12-1.fc20 will be erased
      ---> Package cairo-gobject.x86_64 0:1.13.1-0.1.git337ab1f.fc20 will be erased
      ---> Package cairo.x86_64 0:1.13.1-0.1.git337ab1f.fc20 will be erased
      ---> Package cairomm.x86_64 0:1.10.0-7.fc20 will be erased
      ---> Package chrony.x86_64 0:1.29-1.fc20 will be erased
      ---> Package clipit.x86_64 0:1.4.2-5.fc20 will be erased
      ---> Package colord-libs.x86_64 0:1.1.4-1.fc20 will be erased
      ---> Package colord.x86_64 0:1.1.4-1.fc20 will be erased
      ---> Package crda.x86_64 0:1.1.3_2013.02.13-4.fc20 will be erased
      ---> Package cronie-anacron.x86_64 0:1.4.11-4.fc20 will be erased
      ---> Package cronie.x86_64 0:1.4.11-4.fc20 will be erased
      ---> Package crontabs.noarch 0:1.11-6.20121102git.fc20 will be erased
      ---> Package cryptsetup-libs.x86_64 0:1.6.2-1.fc20 will be erased
      ---> Package cryptsetup-python.x86_64 0:1.6.2-1.fc20 will be erased
      ---> Package cryptsetup.x86_64 0:1.6.2-1.fc20 will be erased
      ---> Package cups-filters.x86_64 0:1.0.41-4.fc20 will be erased
      ---> Package cups-pk-helper.x86_64 0:0.2.5-2.fc20 will be erased
      ---> Package cups.x86_64 1:1.7.0-4.fc20 will be erased
      ---> Package dbus-x11.x86_64 1:1.6.12-1.fc20 will be erased
      ---> Package dbus.x86_64 1:1.6.12-1.fc20 will be erased
      ---> Package dconf.x86_64 0:0.18.0-2.fc20 will be erased
      ---> Package device-mapper-event-libs.x86_64 0:1.02.82-3.fc20 will be erased
      ---> Package device-mapper-event.x86_64 0:1.02.82-3.fc20 will be erased
      ---> Package device-mapper-libs.x86_64 0:1.02.82-3.fc20 will be erased
      ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-55.fc20 will be erased
      ---> Package device-mapper-

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    113. Re: Systemd? Not on my system... by nabsltd · · Score: 1

      cgroups, kernel capabilities, boilerplate code when writing own system services, cgroups, cgroups, cgroups, did I mention cgroups?

      So, one feature of systemd that is used only by a very small percentage of users and could have been broken out into its own code is worth making debugging startup issues almost impossible?

      Since the poster who originally said "systemd makes system administration a joy" never replied, I'm gonna assume he was either being sarcastic or a troll.

    114. Re:Systemd? Not on my system... by Anonymous Coward · · Score: 0

      Launchd is not more cross platform than systemd. Launchd do not support linux...

    115. Re:Systemd? Not on my system... by ogdenk · · Score: 1

      It supports MacOS X and a couple BSD variants. I'm sure with a little effort it could have been ported fairly easily rather than reinventing several wheels.

      That means it supports more platforms than systemd..... which supports one. And properly dealing with it in software means broken fragmented apps and desktop environments.

  4. systemd? by Anonymous Coward · · Score: 0

    I am excited about XWayland support, I would like to give wayland a try and maybe even write a dead simple compositor for building simple WMs on. I am not excited about systemd though (also not surprised), does anyone know if systemd is a dependency of X now?

    -DX

    1. Re:systemd? by Desler · · Score: 1

      It's not. It's only a dependency to run X as non-root.

  5. X, systemd, and priveleges? by Anonymous Coward · · Score: 1

    Is this configuration, currently the only way to run X with non-root priveleges? Is there no way to use OpenRC to run X as non-root? Or is that statement in the headline such that, with systemd, you can finally run X as non-root?

    1. Re:X, systemd, and priveleges? by ustolemyname · · Score: 1

      The latter. Prior to this change it was impossible to run X as non-root, it took significant work (and a more capable init system) to support non-root X.

    2. Re:X, systemd, and priveleges? by dpilot · · Score: 2

      Are you able to explain more?

      My impression is that there were 2 issues with non-root X - mode setup and input device management. KMS and DRI2/DRI3 take care of the former, and I'm under the impression that systemd-logind takes care of the latter. But ultimately these are all just kernel interfaces - if systemd-logind has a root-helper and makes a series of kernel calls to manage the input devices, then that same job could be done by some other piece of software.

      Again, do you understand the base mechanism at work here?

      --
      The living have better things to do than to continue hating the dead.
    3. Re: X, systemd, and priveleges? by BitwizeGHC · · Score: 1

      Running X as non-root requires systemd-logind. Currently the only way for the X server to do the device management it needs to run is to either be root or delegate it to systemd-logind. You don't like it? Code up another way, and convince the Xorg, GNOME, and KDE developers to adopt your way.

      Systemd is widely adopted because the systemd developers solved real problems with working code.

      --
      N4st0r, trixx0r h0bb1tz0rz! Th3y st0l3 0ur pr3c10uzz!
    4. Re:X, systemd, and priveleges? by Anonymous Coward · · Score: 0

      You are wrong. You've been able to run X as non-root for Intel and Radeon drivers for months now.

    5. Re:X, systemd, and priveleges? by ustolemyname · · Score: 1

      Sure, if you were building dev releases. And as per patches like http://lists.x.org/archives/xo..., you needed systemd-logind.

      The point is 1.15 couldn't, and 1.16 can with systemd components. I think calling development builds of the 1.16 branch "previously" is quite disingenuous.

    6. Re:X, systemd, and priveleges? by ustolemyname · · Score: 1

      It also manages access to the display driver and the actual session. And yes, the same job could be done by another piece of software, but none have been written that I am aware of. That is also true of any piece of software, so I'm not sure what your point is.

      Nice summary of requirements for non-root X: ehttp://hansdegoede.lvejournal.com/14268.html

  6. What about non-Linux users? by armanox · · Score: 5, Insightful

    So, to me it sounds like they are moving to being Linux only. As someone who supports multiple UNIX flavors (AIX, Solaris, HP UX, IRIX, and FreeBSD), all of which are running some form of X (and several of them running X.Org), I am displeased with the trend towards all of the primarily Linux dependencies for a lot of software - GNOME 3, Wayland, and now features of X11.

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
    1. Re:What about non-Linux users? by serviscope_minor · · Score: 3, Interesting

      I am displeased with the trend towards all of the primarily Linux dependencies for a lot of software - GNOME 3, Wayland, X11

      We had a GNOME 3 dev on here a while ago. Apparently they've been working hard to get the features of GNOME3 working without systemd.

      As for X11, it also has this feature to run rootless in Windows. However, that doesn't affect me as a Linux user. I think adding integration with more systems is generally done well on Xorg.

      --
      SJW n. One who posts facts.
    2. Re:What about non-Linux users? by acoopersmith · · Score: 1

      Xorg continues to run fine on Solaris, since Oracle pays developers (including myself) to make sure Xorg continues to work and to contribute fixes upstream. Xorg continues to run fine on most BSD's, since BSD developers continue to contribute fixes upstream to make that happen. Of course, neither of those platforms get all the features, such as those requiring systemd/udev, because no one has stepped forward to write the code for them. The Xorg server has never run on AIX, HPUX, or IRIX, since no one who used those platforms ever cared enough to port it. (Isn't IRIX EOL'ed by SGI now anyway?)

    3. Re:What about non-Linux users? by armanox · · Score: 2

      I know it never ran on IRIX - IRIX uses XSgi. The HP-UX box I currently have access to (which is horribly outdated) is running XFree86. AIX, however, does use X.Org. (BTW, IRIX wasn't EOL until the beginning of this year)

      bash-4.2$ /usr/X11R7/bin/Xorg -version

      X Window System Version 7.1.1
      Release Date: 12 May 2006
      X Protocol Version 11, Revision 0, Release 7.1.1
      Build Operating System: AIX IBM
      Current Operating System: AIX aix71 1 7 00036A2AD300
      Build Date: 07 July 2006
                      Before reporting problems, check http://wiki.x.org/
                      to make sure that you have the latest version.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    4. Re:What about non-Linux users? by Anonymous Coward · · Score: 0

      As someone who supports multiple UNIX flavors (AIX, Solaris, HP UX, IRIX, and FreeBSD)

      You must be a sucker for pain. It would be a great day if AIX, Solaris, and HP-UX would just die already.

  7. As a primarily linux user: by Anonymous Coward · · Score: 5, Interesting

    I can tell you I feel similiarly.

    But until and unless a large percentage of the community starts coughing up money to directly pay devs otherwise, they're going to do what their corporate masters (primarily redhat, but also other tech incumbents) choose to do.

    It's the same reason lots of other tech has made it into the linux kernel but taken years to a decade to make it into BSD. If the community isn't ponying up the cash to keep the development in a direction they desire, then some corporation will coopt it and pervert it into something we hate.

    It's not the first nor last piece of software we'll see this happening with.

  8. XFree86 Passed Away in 2008 At Version 4.8.0 by Anonymous Coward · · Score: 0

    Good software despite it's flaws, it will be missed.

  9. Linux kernel? Not on my system... by Anonymous Coward · · Score: 0

    I really hope it is not a requirement and will never be on for kernel.org. Otherwise, I will end up having to make my Linux-servers Linux kernel-less and probably use Windows as an OS. After all, with the linux kernel, windows-like levels of intransparency, insecurity, complexity and developer arrogance have already been reached. One system with that is quite enough, I do not need to deal with that crap on Linux as well.

    Same goes for glibc!

    1. Re:Linux kernel? Not on my system... by gweihir · · Score: 0

      You should start taking your meds again.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    2. Re:Linux kernel? Not on my system... by armanox · · Score: 1

      You could always run a non-GNU Linux setup if you don't like glibc. I'm all in favor of that!

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
  10. So... by warrax_666 · · Score: 4, Insightful

    So what particular one thing does SysV init do well in your opinion? I honestly can't think of a single thing. It's crappy at managing services, it's crappy at running shell scripts (as witness by the non-standardness of init.d scripts), it's shit at managing running services with interdependencies (inittab), it's shit at dynamically reconfiguring systems (e.g. network reconfiguration for Wifi.), etc. etc.

    There's a reason alternatives were created, y'know.

    --
    HAND.
  11. "An anonymous reader writes" by Anonymous Coward · · Score: 0, Interesting

    FUCK OFF MICHAEL LARABEL

  12. And the dirfference is? by Anonymous Coward · · Score: 0

    Let's see, not run X as root... this is different than startx from runlevel 3 exactly how?

    Oh, and for the ignorant idiot, most distros of Linux work just fine out of the box for desktops. Certainly CentOS/RHEL, and Ubuntu, and SuSE do. Why, what were you thinking of... or is it that you've never *used* Linux?

                    mark

    1. Re:And the dirfference is? by dpilot · · Score: 1

      OK, I'll feed the troll. Either X or an X wrapper is suid root. Find the right hole in X, and you've got root. I presume that X or an X wrapper tries to do the best it can, drops capabilities, etc. But it would still be better to not be root at all.

      --
      The living have better things to do than to continue hating the dead.
    2. Re:And the dirfference is? by goarilla · · Score: 1

      So the solution is to hand the critical stuff to systemd-logind which I assume has root privileges.
      Why didn't the Xorg folks split their root sections from the server themselves ?

    3. Re:And the dirfference is? by dpilot · · Score: 1

      There's the snarky answer, and what I suspect is the real answer.

      First, systemd and everything associated with is just so kewl and shiny that's it's a privilege to even use any of it, which makes it all the more amazing that they're actually welcoming us to do so, instead of making us fight for a place in line.

      Second, X11 goes way back before anyone was really concerned with security. I suspect from a core competence point of view, the X11 coders are far more comfortable and far more engaged with the graphical display code than the input side. I get the impression that a lot of effort was spent in properly cleaning and separating the root-requiring functionality. I know I've read of KMS and DRI work for years now. It's been a long road, and I believe it may have only been in the past year that the display side has gotten to the point where they could think about going rootless.

      I also suspect that the input device part is not their core competence - they'd like events coming in from "elsewhere" and get back to their graphics work. So along comes systemd, saying, "We'll handle the gnarly details of console access and security for you," and X said OK, if only in the spirit of modularity and going back to their graphics work. (Graphics work includes processing the inputs, not just drawing outputs - I think they'd just like the inputs to be clean and handed to them.)

      --
      The living have better things to do than to continue hating the dead.
  13. Re:Well, time to switch to __OTHER_OS__! by Anonymous Coward · · Score: 0

    Best post of the thread.

  14. um... not to be gross, but... by UncHellMatt · · Score: 1

    Did this dude get so excited over the release that he peed his pants? http://www.phoronix.com/image-...

    1. Re:um... not to be gross, but... by drinkypoo · · Score: 1

      My ass used to sweat like that when I was a teenager. Horribly embarrassing all around but there you have it. Since this image is not presented in smellovision we have no way to know for sure.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:um... not to be gross, but... by UncHellMatt · · Score: 1

      This is one of those situations where, you know, I'd rather NOT have a technology at hand to validate an assumption.

  15. Re:Well, time to switch to __OTHER_OS__! by armanox · · Score: 3

    Actually, a lot of us, including Linus Torvalds, do submit bug reports and patches to various groups (such as GNOME) that get promptly ignored or rejected because of politics.

    And in my case, it's "I was using Linux happily until I tried other operating systems, and realized how horrible the GNU/Linux setup really is"

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  16. me, for one by raymorris · · Score: 1

    I use it. Sometimes to run something like Wireshark, sometimes I do:
    ray@mymac$ ssh -X -C me@linux.myhouse
     

    1. Re:me, for one by Anonymous Coward · · Score: 0

      Next to no one != no one.

      Oh and these days Wireshark no longer needs X11 if you use the Qt version.

  17. Embrace, extend.... by hazeii · · Score: 1

    I think we've seen this strategy before.

    Basically, it's job security; make it so complex you need to pay for 'support' to make it work.

    --
    All your ghosts are just false positives.
  18. How many people do you think read your post by raymorris · · Score: 1

    For a rough guesstimate, let's say 25 people read your post. At least one of those people (4%) use XQuartz. Is 4% of people "next to no one"?

    1. Re:How many people do you think read your post by Anonymous Coward · · Score: 0

      Yes.

  19. Um... by Anonymous Coward · · Score: 0

    Why is it named after Washington DC's crack smoking mayor-for-life?

  20. GNU/Linu-x not GNOME/Lenna-x by knorthern+knight · · Score: 4, Funny

    Is Lennart paid by Redhat or by Microsoft?

    --

    I'm not repeating myself
    I'm an X window user; I'm an ex-Windows user
  21. Why do they have to fuckup X. by Anonymous Coward · · Score: 0

    Isn't there other software they can bloat the shit out of that isn't used as much?

  22. I can only repeat my question by warrax_666 · · Score: 1

    You've just said what "init" doesn't do -- which btw, I'm well aware of -- I was merely preempting some responses I've seen in the past. Tell us which single thing it does do well.

    --
    HAND.