[haiku-commits] Re: BRANCH axeld-github.launch_daemon [6cadc777073e] src/servers/launch src/kits/app headers/private/app data/launch headers/os/app

  • From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Thu, 02 Apr 2015 16:23:02 +0200

On 04/02/2015 02:52 PM, Augustin Cavalier wrote:

On Thu, Apr 2, 2015 at 8:48 AM, Stefano Ceccherini
<stefano.ceccherini@xxxxxxxxx <mailto:stefano.ceccherini@xxxxxxxxx>>
Nice idea! Also the fact that you're taking inspiration from

It was less an idea than a need: since PM the Bootscript is read-only which makes the whole thing pretty static. Since I'd like to use DriveEncryption's Login application to automatically mount my encrypted drives on login, I need a more flexible solution.
And why not aim for the full solution? :-)

systemd, no need to reinvent the wheel completely...

It won't be as "vast" as systemd, but will somewhat more similar to
launchd. I haven't looked at the user session part of this yet, though, and how this all will work out.

Well, some parts of systemd are nice -- but hopefully he'll not
follow the more braindead patterns, like the binary logs or the need
to use a

I won't change the current logging mechanism at all.

SSD to get any sort of substantial boot performance... :p

That's only somewhat true. The way the launch daemon works, it will
launch pretty much all servers at once -- an SSD will benefit from this
the most, obviously, but an HD will, too.

Also, some servers like the print server, midi server, most probably the
media server, etc. can all be launched by demand only which will shave
off a few milliseconds, plus some memory.


Other related posts: