[haiku] Re: Network transfer, one Haiku machine to another ?

Ingo Weinhold wrote:
On 2009-05-26 at 16:32:07 [+0200], Raymond C. Rodgers <sinful622@xxxxxxxxx> wrote: 
André Braga wrote:

Now, we all know how this story ends: a hundred thousand hacks to handle
dependencies and conflicts between services.

Why exactly would that happen? In the case of sshd, just a link for its
executable in this dir would suffice.

How exactly do you think the rc.d/init.d kludge was born?

See if this rings familiar: a quick hack, to serve a specific purpose;
never meant to be a permanent solution. But which sort of works well
enough and is also deemed simple enough so that it will be trivial to
replace by the eventual successor. But that suddenly gets used by more
and more people -- despite the clear hackish nature of it. And then
becomes sort of a de-facto way of doing similar stuff on the system
(here, starting services). Which then gets the committee treatment and
gets ratified into a standard.


On the other hand, there's no need to over-engineer something either. I
love the advantages of node monitoring and attributes, but they have
their limitations as well. Some thing I came across in developing the
plug-in support for Themis years ago was that the node monitoring system
(in BeOS R5 at least) doesn't always send the notifications you'd
expect. This was particularly true for deleting files, sometimes the
notifications weren't sent because the file wasn't technically deleted,
it was just moved to the trash directory, and the notification wasn't
sent until the trash was emptied or some other similar events.
You should at least get an B_ENTRY_MOVED notification when an entry is moved to the trash. BeOS did indeed suffer from dropping a notification message when the message port to which it should be delivered was full at that time. Haiku solves this problem by sending messages via the registrar, which periodically tries to resend messages that couldn't be delivered yet. It allows for a serious backlog before actually starting to drop messages. 

CU, Ingo
I might be wrong on exactly what the circumstances were, but I do remember pulling out hair over missing notification messages while doing node-monitoring auto loading/unloading of plug-ins. :-) 

Raymond

Other related posts: