Re: sharing memory map between processes (same parent)

On Apr 28, 2:44 pm, phil-news-nos...@xxxxxxxx wrote:

I do purposely try to avoid answering questions that go off track of what I
an seeking answers for. I used to not do that, and that would almost always
result in a pointless drawn out thread with someone else trying to suggest
ways to do things that would not really work because of many issues in the
program, that I didn't post in the first place because they were not relevant
to

You can't use USENET that way. It's just not fair.

If you ask a really unusual question without any discussion of why
it's unusual, and you get (maybe even by luck) exactly the right
answer, the exchange will help nobody but you. Worse, other people
looking at the exchange may think the answer is the normal or
appropriate way, though it's only right because of all your "many
issues in the program", which they don't even know exists.

If you want help from USENET, you have to explain your situation such
that it's, at a minimum, not misleading to people in the future who
hunt around for useful information.

| Any time you ask a question, expect the response "why don't you do it
| the usual way?" and give the answer in the question. Why not just have
| each process map it itself? That's more efficient, because it doesn't
| require extra coordination.

When I ask, expect that I have checked out the "usual" way, and that either
that way doesn't work for some reason, or that I am already doing it that way
and am exploring to find another way.

Unfortunately, that doesn't work for two reasons. First, the time when
you haven't checked out the usual way, it will lead you further
astray. Second, people who need the more typical answer will be lead
astray by the exchange.

These are real, common, problems whose consequences have been learned
by hard and painful experience. You are asking for things that just
don't work on USENET.

If I describe some particular way to do something and ask if it is available
in some system, then I'm not interested in other ways, even though one of the
other ways might be the usual. If I describe what end result I want and ask
how to accomplish it, then any method to accomplish it is fair game.

But you don't describe what end result you want. You describe how you
think you could accomplish that end result.

For example, in this thread, was the end result the mapping at the
same address in both processes or not?

The only way to know what result you wanted was to understand what you
were trying to accomplish. Otherwise, we'd have to tease through every
tedious permutation of how two processes could wind up with the "same
mapping".

If what I want to do cannot be done, then just say "no" or don't say. But do
not make assumptions about what other stuff I may or may not have explored.
If you are curious what I have explored, you can always ask. I may or may not
be interested in pursing that subthread.

That's not a fair attitude on USENET. USENET is a give and take, and
you cannot refuse to give. Spend the extra ten minutes explaining your
problem. Not only will that help novices to better understand whether
the answers you get apply to them or not, you will get better answers.
Plus, you will spend less time explaining why the answers you get
aren't helpful or saying "I already tried X, that was obvious" because
you didn't make clear why X wasn't what you wanted.

And this post is not just for you. It's more for anyone reading this
thread who might think that your post serves as a good example of how
to ask a question.

This is probably the most frequently posted link on USENET:
http://catb.org/~esr/faqs/smart-questions.html
See especially the section no describing the ultimate goal and the
section on being specific.

DS
.

Relevant Pages

  • Re: sharing memory map between processes (same parent)
    ... |> I do purposely try to avoid answering questions that go off track of what I ... | You can't use USENET that way. ... Until such time as I have completed the exploration of it, ... |> how to accomplish it, then any method to accomplish it is fair game. ...
    (comp.unix.programmer)
  • Re: Weathering the troll storm
    ... It won't accomplish much. ... Google is just an archiving service and to my ... As for complaining to those who do administer usenet, ... usenet groups for reporting such abuses, but ordinary trolls do not ...
    (alt.gathering.rainbow)
  • Re: My Work Is Done
    ... left this little area of Usenet for awhile and told everyone I would ... I think I have accomplished every thing that I wanted to accomplish ... Altimer McDaniel of Clan Donald ...
    (soc.culture.scottish)
  • Re: How to change decimal point , to decimal comma ,
    ... PERO wrote: ... a suitable suggestion would be to post it on Usenet ... ... What exactly are you trying to accomplish, what code have you written so far and where does your code not meet your expectations? ...
    (comp.lang.perl.misc)
  • Re: New Years Open Apology to Gellman
    ... >>> I've always wondered, though, why Usenet seems so stuck in 1990. ... >>> connections...any current node doing that deserves to die!), and storage space ... >>centralized server. ... > Is this something new in Exchange 2003? ...
    (alt.smokers.cigars)