Can ext2 kernel run ext3 binaries.

["Followup-To:" header set to alt.os.linux.slackware.]

On 2007-06-05, Sylvain Robitaille wrote:
>>
>> How many messages use pgp ...?
>
> Slightly under 10%:
>
> : newsflash[syl] ~; grep -rl "^-----BEGIN PGP SIGNATURE-----" \
> /news/spool/alt/os/linux/slackware |wc -l
> 26

You may also wish to include posts with the PGP signature in the
headers. I don't recall the exact headers used by my signer, tinews.pl,
but it should be relatively obvious from the headers on this post.
(These numbers don't have a bearing on the current PGPinline/MIME flame
war, though, so maybe your numbers are more appropriate.)

--keith


--
kkeller-usenet-at-wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

On 2007-06-05, Sylvain Robitaille wrote:
> Robert M. Riches Jr. wrote:
>
>> I use slrn, and it is apparently not in sync with your idea of how to
>> use MIME and your signatures.
>
> Another SLRN user here, and I'm afraid I may not be seeing the same
> thing as others: I see the "MIME" disclaimer at the top of Sam's
> ...
>
> Each group has a slightly different culture, and I think it can be
> argued to be bad form to impose a new form on a newsgroup just because
> you insist on using it. Consider that contrary to the argument you
> posted in followup to Alan Hicks' request, your posts (at least those
> that have made it to AOLS on the news server I use) don't, in fact,
> include any characters not available in the standard ACSII character set.
> If your only intention for using MIME is to make it possible to use
> other character sets, that appears to be lost on the rest of us who are
> reading your posts in plain English ...

Just for the record, I believe it was Sam who responded to
Alan's request and who posts with the MIME signature stuff.

--
Robert Riches
spamtrap42-at-verizon.net
(Yes, that is one of my email addresses.)

On 2007-06-05, Sam wrote:
> This is a MIME GnuPG-signed message. If you see this text, it means that
> your E-mail or Usenet software does not support MIME signed messages.
> The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
> To open this message correctly you will need to install E-mail or Usenet
> software that supports modern Internet standards.
>
> --=_mimegpg-commodore.email-scan.com-19228-1181041770-0002
> Content-Type: text/plain; format=flowed; charset="US-ASCII"
> Content-Disposition: inline
> Content-Transfer-Encoding: 7bit
>
> Robert M. Riches Jr. writes:
>
>> Sam, FWIW, in case you are listening, I'll second Alan's
>> request. I use slrn, and it is apparently not in sync with
>> your idea of how to use MIME and your signatures.
>
> It's not "my idea", it's a ten-year old Internet standard.
>
>> Whenever
>> you post, I see the full text of all your MIME wrapper
>
> So, go get slrn fixed. Why is it that everyone else, who's not using slrn,
> are required to work around ancient slrn bugs?
>
>> stuff, and it makes it difficult to see what you're actually
>> saying. There are very few postings in comp.os.linux.misc
>> that have the problem, so I would venture to say it looks to
>> me like your use of MIME stuff is in the minority.
>
> You don't know what you're talking about. Go read RFC 2015, then we can
> have an intelligent discussion here, but not before then.
>
> As I've shown, around here 70% of messages are MIME messages, which is very
> much a majority. Now, different messages may use different aspects of MIME
> formatting, but it is still MIME, and all properly-written MIME parsers will
> handle it correctly.

I will admit my lack of familiarity with the many RFCs out
there. However, elsewhere in this thread, multiple other
posters have quite convincingly argued against your position
and your statistics. Based on their arguments, if I find
your MIME signature stuff too annoying, I can solve that by
adding a few lines to my ~/News/Score file.

--
Robert Riches
spamtrap42-at-verizon.net
(Yes, that is one of my email addresses.)

On 2007-06-05, rm-at-biteme.org wrote:
> In alt.os.linux.slackware Robert M. Riches Jr. wrote:
>
>> Sam, FWIW, in case you are listening, I'll second Alan's request.
>> I use slrn, and it is apparently not in sync with your idea of how
>> to use MIME and your signatures. Whenever
>
> And what do you have to say about our request that The Coward Hicks
> bury his pgp trash trolling in his headers?

I'm not acquainted with anyone who calls himself "The Coward
Hicks" or with the definition of "pgp trash trolling". I
believe it was someone who calls himself "Sam" who decorates
his postings with a bunch of MIME signature stuff, and
someone who calls himself "Alan Hicks" asked Sam to get rid
of the MIME signature stuff.

>> you post, I see the full text of all your MIME wrapper stuff, and
>> it makes it difficult to see what you're actually saying. There
>> are very few postings in comp.os.linux.misc that have the problem,
>> so I would venture to say it looks to me like your use of MIME
>> stuff is in the minority.
>
> And The Coward Hicks' use of pgp trash trolling is also in the
> minority. Could you please advise The Coward Hicks to bury his pgp
> trash trolling in his headers?

Ditto from above.

> cordially, as always,

My sarcasm detector just started beeping. Hmmm... I wonder
why it's doing that.

--
Robert Riches
spamtrap42-at-verizon.net
(Yes, that is one of my email addresses.)

In alt.os.linux.slackware Robert M. Riches Jr. wrote:
> On 2007-06-05, rm-at-biteme.org wrote:

>> And what do you have to say about our request that The Coward
>> Hicks bury his pgp trash trolling in his headers?

> I'm not acquainted with anyone who calls himself "The Coward
> Hicks" or with the definition of "pgp trash trolling". I
> believe it was someone who calls himself "Sam" who decorates
> his postings with a bunch of MIME signature stuff, and
> someone who calls himself "Alan Hicks" asked Sam to get rid
> of the MIME signature stuff.

And which of "Alan Hicks" and "Sam" do you think is referred to by
the name, The Coward Hicks?

>> And The Coward Hicks' use of pgp trash trolling is also in the
>> minority. Could you please advise The Coward Hicks to bury his
>> pgp trash trolling in his headers?

> Ditto from above.

And why does it matter whether you know who we mean by The Coward
Hicks? He is a pgp trash troll, by whatever name you wish to call
him. That's a fact. And the issue is not his name - the issue is
the fact that he uses pgp trash trolling. Pgp trash should be
buried in headers. Why don't you ask The Coward to bury his trash
in headers?

cordially, as always,

rm

Thomas Overgaard writes:

>
> sam-at-email-scan.com wrote :
>
>> You don't know what you're talking about. Go read RFC 2015, then we
>> can have an intelligent discussion here, but not before then.
>
> Wrong RFC, check out RFC 3977 instead. Here you'll see that at Usenet
> MIME is restricted to be used to specify the character set of the body.

Section 10.2, from the above document, quote:

Firstly, the use of MIME for article headers and bodies is strongly
recommended.

Get that? "Strongly recommended".

Looks like that if you're using slrn, then, as the saying goes: "sucks to be
you."

Have a nice day.



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

iD8DBQBGZeOsx9p3GYHlUOIRAo3hAJ4qY4mMJf0zvo/uJ2kjy36YlmB8AwCfVG3Z
QuT+mRCp+Rfff/fLhrBSdYY=
=yCzw
-----END PGP SIGNATURE-----

Floyd L. Davidson writes:

> Sam wrote:
>>
>>You don't know what you're talking about. Go read RFC
>>2015, then we can have an intelligent discussion here,
>>but not before then.
>
> Your arguments would carry more weight if they cited the
> correct RFC's and other documents. RFC-2015 does not
> pertain to Usenet, and indeed does not even mention it.
>
> Please read RFC-3977 "Network News Transfer Protocol
> (NNTP)".

Okee-dokee. How about this part:

Firstly, the use of MIME for article headers and bodies is strongly
recommended.

?

> "NOTE: This corresponds to the range of octets
> permitted in MIME 8bit data [RFC2045]. Transports

HELLO?????? McFLY!!!!! ANYBODY HOME???

Do you know what "MIME 8 bit data" means?


> ...
>
> "While a charset parameter is defined for this media
> type, most existing software does not understand MIME
> header fields or correctly handle descriptions in a
> variety of charsets. Using a charset of US- ASCII
> where possible is therefore RECOMMENDED; if not
> possible, UTF-8 [RFC3629] SHOULD be used. Regardless
> of the charset used, the constraints of the above
> grammar MUST be met ..."

Uh-huh. Guess what character set I use? Can you say "UTF-8"? I know you
could!


> Currently the only acceptable MIME format is ASCII text
> or UTF-8 or "and ecnoding based on it, such as RFC 2047"
> which must be used for all parts of the article
> generated by the client.

I agree 100%. Now, where's your beef?

>
>>As I've shown, around here 70% of messages are MIME
>>messages, which is very much a majority.
>
> Your figures are meaningless. My messages for example
> show up as MIME in your analysis.
>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii

And they are.

> You've only looked for a MIME version header, but have
> ignored the all telling Content-Type header.

Look! Up there! Up in the sky! Way above your head, it's the contents of
this thread!

The original complaint is that that MIME does not belong on Usenet,
according to the first genius who whined about his buggy newsreader choking
on certain MIME messages. His claim was that "MIME" does not belong
on Usenet, period.

He clearly had no clear understanding of what MIME (without any further
qualifiers) is. Your message meets the 100% definition of a MIME messages,
notwithstanding what actual bits of MIME it carries, so does a crushing
majority of Usenet traffic; and the proportion keeps increasing every year.

>>Now, different
>>messages may use different aspects of MIME formatting,
>>but it is still MIME, and all properly-written MIME
>>parsers will handle it correctly.
>
> A "properly-written MIME parser" for Usenet messages
> distributed via NNTP protocols can, and will, quite
> correctly toss any message that contains a message body
> with other than UTF-8 or US-ASCII.

Ummm, yeah. Now, go find some message of mine with content anything else
encoded NOT in UTF-8, or US-ASCII, and then maybe you'll have a point.


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

iD8DBQBGZeWnx9p3GYHlUOIRAvfVAKCAoKUyiektEjnAvO1lN5/aFKoQ+ACeJLUO
l7t8eNQ//HSKlDqBkm1mcXI=
=Dhmg
-----END PGP SIGNATURE-----

Robert M. Riches Jr. writes:

> I will admit my lack of familiarity with the many RFCs out
> there. However, elsewhere in this thread, multiple other
> posters have quite convincingly argued against your position
> and your statistics. Based on their arguments, if I find
> your MIME signature stuff too annoying, I can solve that by
> adding a few lines to my ~/News/Score file.

Right, spanky. Please don't let your delusions of self-grandeur hit your
ass, on the way out.



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

iD8DBQBGZeXjx9p3GYHlUOIRAk5QAJ4tS/WmMQWUvENtDyfTylciN1SAZgCeM4/m
BLtDmG01nx6Up8Z/GpE8+kU=
=sWZC
-----END PGP SIGNATURE-----

On Tue, 05 Jun 2007 17:38:28 -0500, Sam wrote:

> Right, spanky. Please don't let your delusions of self-grandeur hit your
> ass, on the way out.

I would recommend that all A.O.L.S. regulars killfile this n00b punk
immediately. Nothing worse than a whiny little chump who thinks he knows
something, when in fact he's a complete moron and a fool, and wrong.

Bugger off, dimwit.

--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

Dan C writes:

> On Tue, 05 Jun 2007 17:38:28 -0500, Sam wrote:
>
>> Right, spanky. Please don't let your delusions of self-grandeur hit your
>> ass, on the way out.
>
> I would recommend that all A.O.L.S. regulars killfile this n00b punk
> immediately. Nothing worse than a whiny little chump who thinks he knows
> something, when in fact he's a complete moron and a fool, and wrong.
>
> Bugger off, dimwit.

My deepest apologies, sir. I wasn't aware that someone died, and made you
king.

Honest mistake.




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

iD8DBQBGZfacx9p3GYHlUOIRAn/JAJ0SC+iHnbwZy2D9cVusi98KaZPQAwCcDev5
uSjm4E3Zoty4WlRJfHWRwW4=
=uVEl
-----END PGP SIGNATURE-----