Opened 8 weeks ago
Last modified 8 weeks ago
#19269 new enhancement
Allow more system components to be "overridden" by non-packaged counterparts.
| Reported by: | bipolar | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Servers/launch_daemon | Version: | R1/beta5 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
While trying to test a custom version of mount_server, I've noticed that it wasn't possible to just black-list the system provided one, and just place the custom server under non-packaged locations.
I think the issue (or at least part of the problem) is that launch_daemon uses absolute paths pointing to things under /system/ in both system and user files.
Given that we generally can override system libs/addons/etc by placing them under non-packaged, I think it would make sense if launch_daemon tried those locations first (except on safe-mode) to see if the user wants them to be overridden.
Change History (3)
follow-up: 3 comment:1 by , 8 weeks ago
comment:2 by , 8 weeks ago
| Component: | - General → Servers/launch_daemon |
|---|---|
| Owner: | changed from to |
comment:3 by , 8 weeks ago
Replying to bipolar:
Now I wonder if I can just "override" those data/{system,user} files instead?
Seems like launch_daemon does reads files from [...]/non-packaged/data/launch/, but my attempts at changing the binary used for mount_server:
service x-vnd.Haiku-mount_server {
launch /system/non-packaged/servers/mount_server
}
only resulted on getting the system stuck at the last boot icon.
Now I wonder if I can just "override" those data/{system,user} files instead?