From: Al <oss.elmar@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: oder of files opened by a process
Date: Sat, 2 Oct 2010 00:06:51 +0200 [thread overview]
Message-ID: <AANLkTin1Bsz5Xq256q7CD4n0hmBkzWSaxdQLNFvDPHFZ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinomYVny+RRxEyfPzByryUcHS-NPYh3_XYopwxd@mail.gmail.com>
> Hey, that's cool man...I'm certainly not telling you not to post here,
> I just think it would have been a good idea to post details of your
> esoteric setup in the original post. As you've found, the cygwin and
You are right in that to enough degree. In this case it would have
been of advantage.
> gnu/linux environment(s) are not exactly compatible, and a solution in
> one may not work in the other. I'm not even saying it's the way it
> should be, but rather that it's the de facto way it is: A very large
> majority of people on this list run whitebread 'Gentoo Linux' and as
> such, without further clarification in your post, that's what they
From my experience it is also a reason to strip down my questions to
something as simple as possible. Then I get useful answers. The strace
program, Dale suggests, is a good answer for me. I am not only using
Vista after all. I still can boot Gentoo/Linux to find the answer by
that program.
If I explain the esoteric context, to ask a simple newby question
thereafter, people often give crazy comments and you go without an
answer. Everything out of their horizon is evil for some stubborns.
That is also a real live experience. It is tiresome, if that happens
to often.
I guess you knows this, you ask: How to do this and that ... people
start a political discussion ... why do you want to do this and that?
Time is lost, no answer yet. That is often simply counter productive.
Hence, I became a little conservative with explaining esotric
contexts. But, in this case it was the other way round. I got the
comments, because I didn't explain the context. There isn't a perfect
world. :-)
> think you are running as well....so I don't know, you may have better
> results on the specialized gentoo-alt list, but if you want to post
> here go ahead...just give us some details :)
Have a nice WE
Al
next prev parent reply other threads:[~2010-10-01 22:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 15:29 [gentoo-user] oder of files opened by a process Al
2010-10-01 16:29 ` Dale
2010-10-01 17:00 ` Darren Kirby
2010-10-02 15:41 ` David Relson
2010-10-01 17:25 ` Al
2010-10-01 17:51 ` [gentoo-user] " walt
2010-10-01 19:05 ` Paul Hartman
2010-10-01 18:14 ` [gentoo-user] " Dale
2010-10-01 18:38 ` Al
2010-10-01 19:07 ` Dale
2010-10-01 19:19 ` Al
2010-10-01 20:37 ` Volker Armin Hemmann
2010-10-01 20:48 ` Al
2010-10-01 18:36 ` [gentoo-user] " Grant Edwards
2010-10-01 18:47 ` Al
2010-10-01 18:56 ` Grant Edwards
2010-10-01 19:01 ` Al
2010-10-01 19:16 ` Dale
2010-10-01 19:23 ` Al
2010-10-01 19:38 ` Grant Edwards
2010-10-01 20:37 ` Al
2010-10-01 19:26 ` Grant Edwards
2010-10-01 19:33 ` Florian CROUZAT
2010-10-01 19:45 ` Al
2010-10-01 19:59 ` Grant Edwards
2010-10-01 20:39 ` Volker Armin Hemmann
2010-10-01 21:07 ` Grant Edwards
2010-10-01 19:35 ` Darren Kirby
2010-10-01 19:41 ` Al
2010-10-01 19:52 ` Darren Kirby
2010-10-01 20:07 ` Al
2010-10-01 20:36 ` Darren Kirby
2010-10-01 22:06 ` Al [this message]
2010-10-01 21:01 ` Grant Edwards
2010-10-01 21:13 ` Al
2010-10-01 18:35 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin1Bsz5Xq256q7CD4n0hmBkzWSaxdQLNFvDPHFZ@mail.gmail.com \
--to=oss.elmar@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox