Re: 'Reverse' ldd ??

Bombadil wrote:

Nathan Keel <nat.k@xxxxx> wrote:
Bombadil wrote:

Nathan Keel <nat.k@xxxxx> wrote:
Bombadil wrote:

<snippity>

Nathan said, referring to scripting languages:
There's a lot out there, not a lot of people know it all.

I wouldn't post scripts them as
solutions to problems on the usenet, because I know that other
people don't use them and that bash is what everyone does use,
more or less.

Bombadil

I don't agree, people either are willing to run a solution in
script
form or not (either taking time to figure if it's safe or not). I
don't see the problem, but it would take only a minute to recode
that in bash if you prefer, so maybe do that?

In order recode scripts you have to know BOTH languages.

Right, at least to the point where you know what it's doing and how
to
do that in the different language. So, you don't have to know the
other any better than to understand what it's doing.

I am not
learning a new language in order to recode a snippet. Are you nuts?

Okay, relax. I never suggested you learn a new language and what I
said
wasn't crazy. I said, if you know bash (which is what you
apparently), then you will quickly recognize what the tclshell script
is doing and be able to make a few small and quick changes for valid,
working bash code.

Wrong. I don't understand the code there. This should be quite obvious
to you.

Yes, it is obvious you don't know the code, which is why you said what
you did. But, the thing I was saying, is how is bash any better for
you? If you knew any bash at all, you'd be able to understand the
tclsh code immediately (it's very close). I'm not upset that you don't
know it (or want to), I just was confused that you were complaining
that it wasn't in bash (since the fact you don't understand the posted
code, shows you don't know bash either). I don't mean that as
offensive, I just am saying that's what I found confusing.

Assuming that because a person knows one scripting language that they
can use another is quite erroneous.

Not when they are almost the same in the example.

You are far too relaxed. Get some exercise and some oxygen to your
brain.

Don't be an *** because you are so picky and choosy about the help
people give you (for free). I wasn't insulting you, I was genuinely
confused. Also, the last thing anyone would accuse me of, is being too
relaxed.

In response to your other article, bash is _by_far_ the most
commonly
used scripting language in linux. People who post solutions in
(relatively) obscure scripting languages on general linux forums
are being elistist jerks.

Bombadil

You've got a pretty strange attitude here about what you insist upon,
when you don't seem to know a lot.

You've got a strange attitude for someone who doesn't seem to know a
lot.

That's the best you can do? You're upset at yourself, not me.

After all, you ripped into someone
that replied and offered code to help you.

No. I ripped into someone who was trying to impress everyone with
his technical superiority by posting an alleged solution in a
scripting language that only a tiny percentage of linux users use.

You're being ridiculous and petty. The person didn't post what they did
to try and impress anyone, it was to help you. They posted what they
knew, and maybe they didn't have the script in bash? As for technical
superiority, the script was very basic and simple, I don't think the
guy posted it to show off or boast. Is that the reaction people get if
their helpful replies don't meet your very specific and limited
knowledge or comprehension and demanding attitude? If you're going to
be so offended when someone offers help, don't ask for help. Now
you're just being weird. As for the percentage of Linux users, you
clearly don't know much about this field, and you are comfortable
proclaiming things you feel (based on you personally not knowing) as
fact. That's taking it a little too far. It's used enough, even if
it's not as common as bash. It's the solution they knew, in the
language they knew and they offered their code and time to you for
free, not showing off, not asking for anything, and instead of thanking
them, you rip into them, and then rip into me when I said how it's
confusing you insist on bash when if you knew bash well enough to
matter which script you ran (bash or tlcsh) that you'd see if it was
safe or familiar.

And the jerk didn't even commment the code.

Consider that you might be the jerk in this situation. Maybe let it go?

You complained, said you
were joking and then complained in every post following it. No one
is insisting you use the code.

Nor did I ever imagine that I had to. Nor say so.

Then what's the problem? Why are you still complaining and insulting
people about it? Move on.

Who are you talking to?

To you, obviously.

If you don't want to, I don't think anyone
is going to be upset. Also, korn shell and Perl are not obscure in
any manner,

I never mentioned korn. Once again I ask: Who are you talking to?

I mentioned korn shell and Perl are also very common in response to you
claiming almost everyone used bash for almost everything on Linux. I
outlined this wasn't the case. You replied to that and went on about
obscure languages. I said those aren't. I was talking to you.

nor is tcl scripting.

For every person who knows tcl, there are a thousand who know bash.

Maybe, maybe not. Where do you get your figures?

What language would you use to post a solution on a general linux
forum?

That depends on the question, what I know and what's more appropriate.
It's not always bash. I could post bash and Perl and korn shell
scripts you'd be just as confused about and offer a script in each
language and that would just just as unhelpful to you.

Apparently, any language that popped into your head.

Not really, as explained above. You can assume the poster intentionally
tried to confuse you by posting a solution in a language that
apparently they somehow knew you didn't know if you like, but I think
your attitude sucks.

Remind me to be very careful about taking any technical advice from
you in the future.

Bombadil

Remind me (and everyone else) not to bother to try and offer any help to
your ungrateful, clueless ass in the future.
.

Quantcast