Page 1 of 8 123 ... LastLast
Results 1 to 10 of 75

Thread: Systemd's Plan For Stateless Systems, Factory Resets

  1. #1
    Join Date
    Jan 2007
    Posts
    15,100

    Default Systemd's Plan For Stateless Systems, Factory Resets

    Phoronix: Systemd's Plan For Stateless Systems, Factory Resets

    Following the exciting systemd 214 release that worked on new sandboxing features and other improvements toward a stateless Linux system, Lennart Poettering has blogged about the latest features and their plans going forward...

    http://www.phoronix.com/vr.php?view=MTcyMjQ

  2. #2
    Join Date
    Sep 2011
    Posts
    122

    Default

    This sounds amazing! Still, where do systemd guys expect applications to be installed (like in years from now if their ideas catch on). Still in /usr? It would be cool to reinstall the OS without losing apps and data (like if the system is unusable because it shutdown in the middle of an update).

    I ask because this is the most I can find on the subject from the blog post:

    For end-user machines like desktops, tablets or mobile phones, we want a generic way to implement factory reset, which the user can make use of when the system is broken (saves you support costs), or when he wants to sell it and get rid of his private data, and renew that "fresh car smell".
    But this sounds like the opposite of what I am asking about.
    Last edited by CTown; 06-17-2014 at 02:56 PM.

  3. #3
    Join Date
    Oct 2013
    Posts
    416

    Default

    anyone else went for popcorn when seeing title? systemd topics are so amusing on phoronix. but, trolls are so late... c'mon it's been minutes already

  4. #4
    Join Date
    Oct 2013
    Posts
    416

    Default

    Quote Originally Posted by CTown View Post
    This sounds amazing! Still, where do systemd guys expect applications to be installed (like in years from now if their ideas catch on). Still in /usr? It would be cool to reinstall the OS without losing apps and data (like if the system is unusable because it shutdown in the middle of an update).

    I ask because this is the most I can find on the subject from the blog post:

    But this sounds like the opposite of what I am asking about.
    if i would have to guess, the applications will probably reside in both usr and home as part of http://www.superlectures.com/guadec2...ions-for-gnome

  5. #5
    Join Date
    Jan 2013
    Posts
    141

    Default

    See, this is why having a consistent base system is useful!

    People keep moaning about systemd 'breaking' their bizarre single-case hacks that had strange edge-cases anyway, and then ignore the fact that we get consistent, reliable, cross-distro features that are useful to everyone.

  6. #6
    Join Date
    Dec 2007
    Posts
    188

    Default

    Quote Originally Posted by CTown View Post
    This sounds amazing! Still, where do systemd guys expect applications to be installed (like in years from now if their ideas catch on). Still in /usr? It would be cool to reinstall the OS without losing apps and data (like if the system is unusable because it shutdown in the middle of an update).

    I ask because this is the most I can find on the subject from the blog post:
    Looking into the crystal ball, the future seems to be that will be two kinds of "apps": the normal ones as we know it, in form of a rpm or deb package, and "sand boxed" apps that are developed via a special SDK, and runs in an environment that are totally independent of the underlying OS.

    Such SB apps can in theory run unmodified on any Linux distribution that support the sand boxing environment. Such apps could in theory be carried over to a new OS (either OS upgrade or another brand) without modification and without loss of data and configuration.
    There still needs a lot of work to make this happens, like kdbus in the kernel etc, so this is mostly theoretical at this point.

    AFAIK, you can just install normal apps either system wide in the "golden master" image (persistent) or in a running OS container if you got the right user permissions (might not be persistent across boots, depending of model.)


    I especially like the "Verifiable System". Security is so damn hard to get right on the Internet and every system exposed is under a constant attack. It would be nice if only a sand boxed container OS was exposed to the net, that could be verified as not-compromised (AV-scanners etc. aren't much help against this these days, and Tripwire and similar also have its problems).

  7. #7
    Join Date
    Mar 2013
    Posts
    268

    Default

    I acknowledge that I was wrong. They don't want to turn Linux into Windows. They want to turn it into iOS.

  8. #8
    Join Date
    Feb 2014
    Posts
    48

    Default

    * Systemd's plan for hijacking your system...

  9. #9
    Join Date
    Mar 2013
    Posts
    268

    Default

    Quote Originally Posted by FLHerne View Post
    useful to everyone.
    You're not everyone, my friend. This crap isn't useful to me in the slightest. The only thing that systemd would change for me is that I would have to run twice as fast just to stay where I am now with sysvinit.

  10. #10
    Join Date
    May 2011
    Posts
    1,558

    Default

    Quote Originally Posted by prodigy_ View Post
    I acknowledge that I was wrong. They don't want to turn Linux into Windows. They want to turn it into iOS.
    It's amazing how awful Linux has become. It's like Linus has totally phoned it in and is off on perpetual scuba diving vacations.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •