If you want to try modifying the launchd sources, you might want to
have a look at the openlaunchd fork of it, as it seems to be more
up-to-date than the version on opensource.apple.com at least:
https://github.com/rtyler/openlaunchd
On 5/5/14, Brandon Allbery wrote:
> On Mon, May 5, 2014 at 9:0
On Mon, 2014-05-05 at 11:54 -0400, Gus Heck wrote:
> I'm having more or less exactly this
> issue: https://www.mail-archive.com/meld-list@gnome.org/msg02071.html
> on OSX 10.9.2...
>
>
> I had never found need to use any of homebrew/fink/macports but
> apparently fink or macports is the recommend
> I'm having more or less exactly this issue:
> https://www.mail-archive.com/meld-list@gnome.org/msg02071.html on OSX
> 10.9.2...
>
> I had never found need to use any of homebrew/fink/macports but apparently
> fink or macports is the recommended way to get meld and I wanted to get
> meld... a
I'm having more or less exactly this issue:
https://www.mail-archive.com/meld-list@gnome.org/msg02071.html on OSX
10.9.2...
I had never found need to use any of homebrew/fink/macports but apparently
fink or macports is the recommended way to get meld and I wanted to get
meld... after many many min
On Mon, May 5, 2014 at 9:03 AM, "René J.V. Bertin" wrote:
> Maybe it'd be possible to trigger the mounting of local partitions through
> launchd ... assuming one can control the order in which launchd scripts are
> executed?
Well, there's this bit where launchd does stuff via the plists, so this
On May 05, 2014, at 14:52, Brandon Allbery wrote:
> On Mon, May 5, 2014 at 7:17 AM, Julien T wrote:
> If it's really the case, it means launchd is starting before other volumes
> are mounted, even for the local one ... :(
>
> launchd is the process that starts the system; the only mounted volu
On Mon, May 5, 2014 at 7:17 AM, Julien T wrote:
> If it's really the case, it means launchd is starting before other volumes
> are mounted, even for the local one ... :(
launchd is the process that starts the system; the only mounted volume is /
when it starts. That said, perhaps it should dist
I search a bit the web to know when non-system partition are mounted but
it seems unclear. Many people seems to do a mount script+plist to mount
various network partition.
As a launchd option, PathState could be a solution to try
http://stackoverflow.com/questions/19449288/how-to-instruct-launchd
2014-05-05 6:18 GMT-04:00 "René J.V. Bertin" :
> Of course all permissions/ownerships are correct on both the Launch*
> directories and the plist, and the directories are on a volume that's
> mounted when the system tries to launch tasks at boot (which in my
> experience requires that they reside
On May 5, 2014, at 05:18, René J.V. Bertin wrote:
> Of course all permissions/ownerships are correct on both the Launch*
> directories and the plist, and the directories are on a volume that's mounted
> when the system tries to launch tasks at boot (which in my experience
> requires that they r
Of course all permissions/ownerships are correct on both the Launch*
directories and the plist, and the directories are on a volume that's mounted
when the system tries to launch tasks at boot (which in my experience requires
that they reside on the boot volume)?
R.
On May 05, 2014, at 06:28
11 matches
Mail list logo
