pgp trash troll delete

Why all the pgp trash for a not-funny one-liner?

cordially, as always,

rm

Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Nobody from there has asked me to killfile you yet.


> - --keith

> - --
> kkeller-usenet@wombat.san-francisco.ca.us
> (try just my userid to email me)
> AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)

> iD8DBQE/qSemhVcNCxZ5ID8RAkv6AJ9cJfZ8edZs+B7LvMpNUNbpVnQ07w CeN23O
> mf01rWJ6UYkKoNR67sFQEZY=
> =z2sq
> -----END PGP SIGNATURE-----

What mailing lists are you talking about? In any case, he figured
the problem out without going elsewhere. Ain't that a bitch?

Which causes your panties to knot tighter? Asking an "off-topic"
question or answering one?

cordially, as always,

rm

Joost Kremers <joostkremers@yahoo.com> wrote:
> Adams-Blake Co. wrote:
> >> you should ask this on a kde forum: they have mailing lists and there is
> >> also a newsgroup, comp.windows.x.kde or something like that. aols is not
> >> the best place for help with kde-related questions.
> >
> > I don't know Joost. I've posted some problems over there and never get
> > answers. In fact, I see way more questions then I *ever* see responses in
> > that NG.

> and what about the mailing lists? it's been a while since i last used KDE,
> but i remember the mailing lists being good sources of information.

> > I still can't figure out why with Slack 9.1 and KDE ... many times a menu
> > icon (both at top of screen or in task bar) does NOT hear the first click
> > and I have to click again. Maybe a mouse problem? Very annoying... but no
> > one on x.kde seems to know either (but I doubt any of them run Slack, if
> > indeed it is a Slack issue... which I rather doubt.)

> it could have to do with focus. perhaps try setting the focus policy to
> 'focus follows mouse' and see if that changes things.

> IMHO this is exactly the sort of thing you should ask on a KDE forum. if
> you don't get any answers on comp.windows.x.kde, then maybe the people that
> know about kde do not hang out there. IME they do subscribe to the mailing
> lists.

Joost Kremers <joostkremers@yahoo.com> wrote:
> James Telfer wrote:
> > Joost Kremers wrote:
> >
> >> you should ask this on a kde forum: they have mailing lists and there is
> >> also a newsgroup, comp.windows.x.kde or something like that. aols is not
> >> the best place for help with kde-related questions.
> >>
> > Ok, I'll hold my hands up to this one, I simply couldn't be bothered to
> > subscibe to another NG, so I posted it here, apologies:-)

> oh no, don't get me wrong. you can post anything here you like. what i was
> trying to say is that on a kde forum you're likely to find more people who
> know and use kde, so they can help you. it's not an issue of good or bad
> behaviour, it's an issue of maximising your chance of finding the answer.

No, it's not. It's an issue of anal retention. KDE questions must
go in the KDE box.

cordially, as always,

rm

Ori <oridean@rogers-dot.com> wrote:
> Randy Myers wrote:

> >
> > Maybe he did ask, moron. In any case, there most certainly will be
> > konqueror users reading this group that can help him with some real
> > information. KDE sounds right up your alley. You could probably
> > help him but you won't because you feel he is in the wrong group,
> > right doofus?
> >
> > cordially, even to anals,
> >
> > rm
> Maybe he was pointing him to somewhere where he would be more likely to
> get a good answer??

But he wasn't. He was directing traffic. He had on his gun and
his whistle and his uniform in his fantasy world and everybody was
doing as he told them.

cordially, as always,

rm

Joost Kremers wrote:

> oh no, don't get me wrong. you can post anything here you like. what i was
> trying to say is that on a kde forum you're likely to find more people who
> know and use kde, so they can help you. it's not an issue of good or bad
> behaviour, it's an issue of maximising your chance of finding the answer.
>
True, I just thought that this was simply me being dense/blind (it was!) and
hence posted here for convenience.
--
James: jwt102@york.ac.uk
http://www-users.york.ac.uk

Al writes:

>
>> I still can't figure out why with Slack 9.1 and KDE ... many times a menu
>> icon (both at top of screen or in task bar) does NOT hear the first click
>> and I have to click again. Maybe a mouse problem? Very annoying... but no
>> one on x.kde seems to know either (but I doubt any of them run Slack, if
>> indeed it is a Slack issue... which I rather doubt.)
>

Joost writes:

> it could have to do with focus. perhaps try setting the focus policy to
> 'focus follows mouse' and see if that changes things.
>
> IMHO this is exactly the sort of thing you should ask on a KDE forum. if
> you don't get any answers on comp.windows.x.kde, then maybe the people
> that know about kde do not hang out there. IME they do subscribe to the
> mailing lists.
>

Oh yes. I DID post this exact question over there, as well as the one about
Kview (which got me in such hot H20 here!) as well as the one about the
Kpilot daemon. I don't think anyone over there knows any of the answers to
anything... but maybe I just hit topics that are too esoteric.

OK, so I do a google on "kde focus policy?" I've been using KDE for a year
with Mandrake and never heard of this one. I also never had this problem
with KDE 2.x.

Am I the only one that thinks that maybe KDE 2.x was more stable than the
3.0 version? The 3.0 is prettier and has more "stuff" but there seem to be
several rough edges.

But one thing about Slack. It is really stable. I've been trying to take it
down but it runs and runs and runs. I blow out an app everyone once in a
while, but Slack just keeps cranking. Mandrake was never this solid. I'm
glad I'm here.... even if some of you aren't :-) Ok, Ok, I'm trying to be
good and keep out of trouble. I sure has hell don't want Guy to use any of
this on me!!!

http://www.guymacon.com/FUN/INSULT/INDEX.HTM

Al

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Thu, 06 Nov 2003 02:02:14 GMT, Adams-Blake Co. <atakeoutcanton@adams-blaketakeout.com> wrote:
> I don't think anyone over there knows any of the answers to
> anything... but maybe I just hit topics that are too esoteric.

This should put their attempt to blame it on "the slackware
developers" in context, I think.

> OK, so I do a google on "kde focus policy?"

Precisely. :-) This is actually a window manager issue. KDE has its
default window manager, but you are not limited to it. There are a
few others that are more or less KDE-compliant.

> Am I the only one that thinks that maybe KDE 2.x was more stable than the
> 3.0 version? The 3.0 is prettier and has more "stuff" but there seem to be
> several rough edges.

Are you wedded to KDE? I use Ratpoison on my desktop (which you
probably wouldn't like), but I just compiled xfce4 for my laptop and I
really like it. I had sworn off desktop environments after my last
fling with KDE, but xfce is nice. You might like it. I guess,
though, with that screaming new computer, you don't really need
"light." It's a philosophical issue for me, though. :-)

> But one thing about Slack. It is really stable. I've been trying to take it
> down but it runs and runs and runs.

How exactly are your trying to "take it down"? Anybody have a sure
fire way to crash a slackware box?

> Ok, Ok, I'm trying to be good and keep out of trouble.

I'm not sure if this is a sarcastic comment or not, but don't obsess
over what people think of you on Usenet. As a successful writer, are
you this sensitive to bad reviews?

> I sure has hell don't want Guy to use any of this on me!!!
> http://www.guymacon.com/FUN/INSULT/INDEX.HTM Al

I would consider it a complement, in an odd sort of way.

Bryan

--
Give a man a fish, he owes you one fish.
Teach a man to fish, and you give up your monopoly on fisheries.
- Proprietary Software 101
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/qbZZZHkU/XQom+8RAhTAAKCRkVR4CV20XcYJnrt8wJtgL6k5zwCePxMC
mVk+7V+9VWNKYp66rA2nsJ4=
=p0ce
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Wed, 05 Nov 2003 20:47:59 -0600, Bryan Bibb <bryanREALNAME@REALHOSThevel.org> wrote:
> How exactly are your trying to "take it down"? Anybody have a sure
> fire way to crash a slackware box?

IIRC, as root:

dd if=/dev/urandom of=/dev/mem

does it... but I don't think I ever tried that one myself.

dd if=/dev/urandom of=/dev/hda

Would probably kill a running system pretty dead, as well.

I heard somebody post a while back about doing a recursive grepping of
/proc for something crashed their system.

But, if you aren't root, I really don't know how you'd crash or kill
Slackware.

Well, if you have physical access, you could pop open the side of the
case and pull out the RAM chips, or pop off the HSF... but you don't
want to do that, and I think we want to rule out hardware crashes.

I'd say trying to exploit something in X would probably be your best bet
to crash the system. Other than that... I dunno.

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/qbzHhm6KEoOOAe0RAqpwAJ0VYmbUoJ+7umPbo4oEC4984HQY3w CfaGDt
7HuZGJ7TLzkg+uzPNh0TQZM=
=kNNq
-----END PGP SIGNATURE-----

On Wed, 05 Nov 2003 20:47:59 -0600, Bryan Bibb
<bryanREALNAME@REALHOSThevel.org> wrote:
> Anybody have a sure fire way to crash a slackware box?

I once ran 'dd if=/dev/zero of=/dev/mem' as root (for no better reason
than curiosity) and the machine rebooted. Does that count as crashing?


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams

Bryan Bibb wrote:

>
> How exactly are your trying to "take it down"?**Anybody*have*a*sure
> fire way to crash a slackware box?
>

The only sure-fire way I knew with my old box (MDK 8.2/KDE 2.2) was to do
(in Konqueror) a right-click copy of a file and paste it to the floppy disk
window. That would always freeze the entire box and require a re-boot. Just
for kicks, I put in the old floppy to the new box and tried it. Won't
crash with Slack and KDE 3.1.4. Writes just fine.

Al