Originally Posted by juiceme

Only some OS'es have the bloody abomination that is systemd

Originally Posted by alfmar

Sorry to redpill you, but SailfishOS has always been built on systemd and some non-trivial benefits (like a faster boot time when compared to Android) depend on it.

Jolla developers wisely chose Wayland protocol instead of the 30-year-old X11, systemd init manager over initscripts, Qt over Gtk/Gnome, because they were building a modern Linux phone, not a desktop PC, even less a server, even less a *BSD machine. And that happened even if Wayland and systemd were not yet considered - back in 2012/2013 - well-tested and feature-complete.

The systemd hate, FUD and criticism come from luddites' worst nightmares, from ancient bug-reports (especially from misconfigured/mispatched systems), and from the wrong assumption that previous methods (like the boot script files approach) give the same level of performance, safety, manageability, speed. Basically the same kind of argument when back in 1992 Linux kernel was criticized for being monolithic by the author of Minix.

Booting a system is a non-trivial task (dependencies, ordering, parallelization, logging...) and not only systemd takes care of everything in a fast, safe and sound way, it also keeps compatibility with oldschool SysV/LSB scripts and adds in quite a number of security features based on Linux kernel features (for example capabilities restrictions) without the need to patch libraries and services. The latest systemd release adds in IP traffic accounting and dynamic users, two features found in Android, also in the Android layer on your old Jolla1) that Jolla guys may apply to native apps without modifying them.

Disclaimer: I use systemd in my job. Since 2014 it saved me countless hours debugging coworkers issues (did he use a wrong userid? early start? forgot to release permissions? wrong pidfile directory? accidentally wiped /tmp? logged to a different stream? started before the network was ready?...) A number of bizarre and hard-to-catch bugs disappeared overnight as soon as I switched to systemd; we now use systemd in production on all of our servers). I bet Jolla guys just felt the same way.

Originally Posted by DrYak

Just to make a check list :

• The Jolla phone is updated to the latest 34.3.A.0.228 or .238 firmware (Important to do first because after unlocking the boot loader, OTA won't work as easily)
• Developer menu is activated
• USB debugging is on
• 3rd party application are authorizsed
• OEM unlocking is authorized
• You have registered your IMEI on Sony's website
• You've obtained a long hexadecimal code in return from Sony
• Your phone was first shutdown
• Afterwards (wait 10 seconds at least), your phone was turned on in Fastboot mode (hold "volume up" while plugging the USB cable)
• the Xperia is in Fastboot mode (no message on the screen, the LED is blue instead of green

At that moment you should run the fastboot command in your command shell (in cmd.exe) :
fastboot.exe oem unlock 0x<hexadecimal code>

Note that depending on how windows works, this might require admin rights (I have no idea, I use Linux. Maybe you'll get a UAC security prompt ? Or you need to "Run as..." cmd.exe to start the shell in admin mode ?)

Originally Posted by clovis86

Sorry, too easy xD
But anyway, all they gotta do is to rtfm, nop ?
( especially with windows procedure )

Originally Posted by alfmar

Jolla developers wisely chose Wayland protocol instead of the 30-year-old X11, systemd init manager over initscripts, Qt over Gtk/Gnome, because they were building a modern Linux phone, not a desktop PC, even less a server, even less a *BSD machine. And that happened even if Wayland and systemd were not yet considered - back in 2012/2013 - well-tested and feature-complete.

Originally Posted by mrsellout

To be fair, even highly skilled users had difficulties getting Windows 10 to play nicely.
I'd wager he's got some UAC notice lingering in the background, but I'm not in a position to help, as I've not done the process myself.