Page 46 of 46 FirstFirst ... 36444546
Results 451 to 456 of 456

Thread: New Group Calls For Boycotting Systemd

  1. #451
    Join Date
    Feb 2011
    Posts
    1,127

    Default

    Quote Originally Posted by Luke View Post
    I suspect even an iPhone could be unlocked if the source code for the firmware was leaked.
    It would still need to be properly signed once compiled in order to get it past the existing bootloader and/or firmware checks.

    Quote Originally Posted by Luke View Post
    Speaking of that, I just thought of a way to prevent use of the kernel by the makers of tivoised devices without relicensing it: move some key functionality needed to start it to GRUB and copy it into all other Linux bootloaders willing to be licensed under the GPL3. Only that code would have to be relicensed. Make enough changes that cutting and pasting GPL 2 code from an older version won't work.
    Has Linus ever personally spoke out against tivoization? From what I gather, preventing such things has never been one of his goals, but I can't speak to that with any confidence.

  2. #452
    Join Date
    Sep 2014
    Posts
    2

    Default

    Quote Originally Posted by TheBlackCat View Post
    It would still need to be properly signed once compiled in order to get it past the existing bootloader and/or firmware checks.


    Has Linus ever personally spoke out against tivoization? From what I gather, preventing such things has never been one of his goals, but I can't speak to that with any confidence.
    Linus says in debconf 2014 that he personaly does not like tivoization. But the social contract he pretends for the kernel is giving and receiving the source code. The trivoization clause seams to prevent that.

    https://www.youtube.com/watch?v=1Mg5_gxNXTo#t=2841

  3. #453
    Join Date
    May 2013
    Posts
    538

    Default I was talking about the FIRMWARE source code

    Quote Originally Posted by TheBlackCat View Post
    It would still need to be properly signed once compiled in order to get it past the existing bootloader and/or firmware checks.
    If it was iPhone firmware being hacked, recompiled from leaked source, and force-flashed by an external "bus pirate" device, the firmware checks would be what was removed, allowing any bootloader to be used that supported the processor in question, thus any operating system compiled to that architecture. Actually, the compiler might be a bigger problem: does anyone know exactly what architecture (presumably some kind of ARM) Apple is using?

  4. #454
    Join Date
    May 2014
    Posts
    3

    Default

    Um... No one is trying to force you to do anything. If anything, those "boycotting" are the ones attempting to force it out!

    Am I the only one who thinks "organizing" a boycott is a little... unnecessary? I mean, anyone who cares that much will likely switch distros anyway, correct? That, or implement something else themselves...

    It seems like a sad waste of time and energy that could be better spent on developing a viable, modern alternative. If we don't like it, then we make something better. Crying doesn't solve anything.


    Quote Originally Posted by phred14 View Post
    I don't mind that. Feel free to use systemd, I really don't mind that either.

    But I don't want to use systemd, and it need go no farther than that. You need not know or understand my reasons - they may matter to me, but they don't have to do you. When someone comes out and says, "systemd has won" as was posted earlier in this thread, it's not far to imagine some glee in the idea that I too will be forced to run systemd soon.

    Why do you care! Is your life that boring that you have to try to control my computer, too? Get a life!

    (The next thing someone else on this thread will do, besides schooling me on how stupid, backward, and retarded I am, will be to tell me to "get a life" and just go ahead and use systemd, already.)
    Last edited by bmourit; 09-20-2014 at 05:16 AM.

  5. #455
    Join Date
    Nov 2011
    Posts
    278

    Default

    So someone (apparently affiliated with the group that inspired this) went ahead and forked systemd 208 as "uselessd" (they suggest parsing it as "use less" or "useless", whichever you prefer).
    http://uselessd.darknedgy.net/

    It can compile and run on musl, uClibc, and FreeBSD systems; the last-mentioned is as a service manager started by init, requires a bit of mucking around to use, and is missing a lot of functionality/barely partly working.

    Most of the systemd features other than the process supervisor have been removed.
    I found out about this when I updated aports.

    Still not interested.
    The init I'm really interested in weighs 492 lines right now, and may be less by the time it's done.
    And if you say "But gnome depends on systemd", I'll say "Good riddance!" I've hated it since I first tried it (Dapper Drake, on a Thinkpad 600x with 64 megs of RAM and a 500 MHz CPU ). And I'm barely more interested in KDE and Xfce. The only desktop a computer should have is the one it sits on.

    Well, OK, I use CDE sometimes; but it's the only DE I'd consider.

    I've written sysv-style init scripts several times, including a networking service because there aren't enough of them already (or at least enough that work right ). I've hacked together a couple rc scripts to start built-from-scratch systems.
    And guess what? I liked it, and I want to do it again.

    But I might try writing a dependency-based init in make first, just because make is a dependency-based language.

  6. #456
    Join Date
    May 2014
    Location
    Germany
    Posts
    68

    Default

    Quote Originally Posted by Ibidem View Post
    ... I'm barely more interested in KDE and Xfce. ...
    LXDE/LXQt?
    Enlightenment?
    Étoilé?

Posting Permissions

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