Announcement

Collapse
No announcement yet.

Systemd 198 Brings "Many Big Changes"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Calinou
    replied
    Originally posted by funkSTAR View Post
    HEALTY COMPANIES
    Intel's commercial practices are fair, very fair (eg. pay more for overclocking).

    Leave a comment:


  • 89c51
    replied
    Originally posted by funkSTAR View Post
    Intel showing further commitment to systemd by buying sysyemd service provider ProFUSION.
    Aren't they the same people that are behind enlightenment? They contribute a lot to it i think. Hope this doesn't change.




    The only think i hope with 198 is that they fixed the journal size bug.

    Leave a comment:


  • newwen
    replied
    Originally posted by funkSTAR View Post
    Stuff not mentioned in the changelog:

    LOTS of new community hacking.

    More paid developers working at systemd on a regular basis.

    Intel showing further commitment to systemd by buying sysyemd service provider ProFUSION.




    This is SANE software, developed in the OPEN, by a DIVERSE group of TALENTED hackers, supported by HEALTY COMPANIES, working on EQUAL AND FAIR TERMS without contributor licenses derailing freedom. Why wait for a space cowboy to deorbit and serve you crappy CLAed skunkwork?
    Very much my thoughts

    Leave a comment:


  • funkSTAR
    replied
    Stuff not mentioned in the changelog:

    LOTS of new community hacking.

    More paid developers working at systemd on a regular basis.

    Intel showing further commitment to systemd by buying sysyemd service provider ProFUSION.




    This is SANE software, developed in the OPEN, by a DIVERSE group of TALENTED hackers, supported by HEALTY COMPANIES, working on EQUAL AND FAIR TERMS without contributor licenses derailing freedom. Why wait for a space cowboy to deorbit and serve you crappy CLAed skunkwork?

    Leave a comment:


  • GreatEmerald
    replied
    Those are really nice additions. Integration with the bootloader makes a lot of sense, it's an integral part of the booting process, and that's exactly what systemd is handling. And no longer needing to install Python for boot time analysis is definitely an added bonus.

    Originally posted by Ericg View Post
    Everything is a compile time flag, and nothing conflicts with existing solutions other than systemd vs sysv vs openrc and thats because only 1 program can register as 'init' and can claim to be PID 1.
    Not even that conflicts. Systemd has compatibility with OpenRC, uses some of its configuration and could even execute its script files. As for registering as init, it's directly controlled by the kernel "init" option. The user has to explicitly add it there, one way or another. So it's not a conflict, but a configuration option.

    Leave a comment:


  • Ericg
    replied
    Originally posted by duby229 View Post
    I guess the real question is, What is it that systemd is -not- trying to be?

    It tries to be everything and yet it isnt good at anything.... I hate it.... It's ruining Linux....

    I wish LP would disappear. All he manages to write is buggy bloatware.
    Yeah duby you really dont have a leg to stand on....

    1) What is systemd trying to be? CoreOS. Thats been the expressed intent for a long time. Systemd is trying to remove all the fragmentation and random BS that exists at the lowest levels of the linux stack, so that the important work can keep going without worrying about random distro differences for things that shouldnt matter. (Such as where the hostname gets set, just as an example)

    2) "buggy bloatware" uh huh.... PulseAudio was buggy when it came out, sure...if you used ubuntu who packaged a pre-alpha version and called it stable. Pulse has been working just fine, gradually getting better and better since about 3years ago.

    Bloatware? Systemd is about as modular as you can get... Everything is a compile time flag, and nothing conflicts with existing solutions other than systemd vs sysv vs openrc and thats because only 1 program can register as 'init' and can claim to be PID 1. Even the journal doesn't conflict with syslog. Systemd has 2 mandatory components: systemd, journald, and udev-- and the last one you probably have on your system already.

    3) Ruining Linux? By what? Removing the fragmentation and inconsistencies? By getting rid of shell scripts and replacing them with flat ini files? If you want to argue against systemd, then bring specific technical faults with specific examples. Otherwise shutup, sit down, and let the people who actually UNDERSTAND whats going on do what they've set out to do.

    Leave a comment:


  • bwat47
    replied
    Originally posted by duby229 View Post
    I guess the real question is, What is it that systemd is -not- trying to be?

    It tries to be everything and yet it isnt good at anything.... I hate it.... It's ruining Linux....

    I wish LP would disappear. All he manages to write is buggy bloatware.
    I couldn't disagree more, systemd is far superior to the shitty hacked together bash scripts of previous init systems. Both sytemd and pulseaudio have significantly improved my linux experience.

    Leave a comment:


  • schmidtbag
    replied
    Ive been using systemd for a while now and havent been getting any issues at all, I think it works quite nicely. I do prefer the old fashioned comfig method but at least systemd has GUI tools to make the transition easier. IMO it makes booting noticably faster.

    Leave a comment:


  • Hamish Wilson
    replied
    Originally posted by duby229 View Post
    I wish LP would disappear. All he manages to write is buggy bloatware.
    PulseAudio and systemd running here, running fine.

    Leave a comment:


  • Marc Driftmeyer
    replied
    In short, systemd/systemctl are working to match up with launchd/launchctl capabilities from OS X. Good. It's been needed for a long time.

    Leave a comment:

Working...
X