From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
Subject: Re: [9fans] tarfs & 2GB limit
Date: Sun, 15 Jan 2006 20:57:35 -0600 [thread overview]
Message-ID: <20060116025735.6F47332554@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0601141022g720dd846q6e1148d6100c95b6@mail.gmail.com>
you're right, of course.
Russ Cox <rsc@swtch.com> writes
|
| > one question, with tpfs, there's a cast to vlong:
| > seek(tapefile, 512*(vlong)r->data+off, 0);
| > i cast to (int) because the size is only 3 bytes.
| > is there anything drasticlly wrong with this?
|
| the cast is there not because r->data is big,
| but so that multiplying by 512 and adding
| off doesn't overflow.
sendmail 9fans@cse.psu.edu rsc@swtch.com
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu,
Russ Cox <rsc@swtch.com>
References: <ACCF003CBA3D09458207DB0CB86AD17D20153F@XMAIL.asuch.cas.cz>
<20060113164151.ED27C35076@dexter-peak.quanstro.net>
<20060114121550.4FD0134FFB@dexter-peak.quanstro.net>
<ee9e417a0601141022g720dd846q6e1148d6100c95b6@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <ee9e417a0601141022g720dd846q6e1148d6100c95b6@mail.gmail.com>
Subject: Re: [9fans] tarfs & 2GB limit
you're right, of course.
Russ Cox <rsc@swtch.com> writes
|
| > one question, with tpfs, there's a cast to vlong:
| > seek(tapefile, 512*(vlong)r->data+off, 0);
| > i cast to (int) because the size is only 3 bytes.
| > is there anything drasticlly wrong with this?
|
| the cast is there not because r->data is big,
| but so that multiplying by 512 and adding
| off doesn't overflow.
sendmail anna@annabradshaw.com quanstro@quanstro.net
From: erik quanstrom <quanstro@quanstro.net>
To: Anna Bradshaw <anna@annabradshaw.com>,
erik quanstrom <quanstro@quanstro.net>
References: <BFED25BA.3B5B%timothy-barrett@uiowa.edu>
<2872A7CE-AE8D-4B03-A3F5-A2D291CF6B1A@annabradshaw.com>
<20060113173158.EF72835076@dexter-peak.quanstro.net>
<B0445687-0DC1-4B1B-B8E3-C9A914223558@annabradshaw.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <B0445687-0DC1-4B1B-B8E3-C9A914223558@annabradshaw.com>
Subject: Re: bug steals the show
i'm sure it's a bug in the mailer. computers. you can't live with 'em, you ....
- erik
Anna Bradshaw <anna@annabradshaw.com> writes
|
| I just sent them like I always do. The comment was the subject
| line. Not sure what happened exactly.
|
|
sendmail anna@annabradshaw.com quanstro@quanstro.net
From: erik quanstrom <quanstro@quanstro.net>
To: Anna Bradshaw <anna@annabradshaw.com>,
erik quanstrom <quanstro@quanstro.net>
References: <BFED25BA.3B5B%timothy-barrett@uiowa.edu>
<2872A7CE-AE8D-4B03-A3F5-A2D291CF6B1A@annabradshaw.com>
<20060113173158.EF72835076@dexter-peak.quanstro.net>
<B0445687-0DC1-4B1B-B8E3-C9A914223558@annabradshaw.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <B0445687-0DC1-4B1B-B8E3-C9A914223558@annabradshaw.com>
Subject: Re: bug steals the show
i'm sure it's a bug in the mailer. computers. you can't live with 'em, you ....
- erik
Anna Bradshaw <anna@annabradshaw.com> writes
|
| I just sent them like I always do. The comment was the subject
| line. Not sure what happened exactly.
|
|
sendmail lucio@proxima.alt.za quanstro@quanstro.net
From: erik quanstrom <quanstro@quanstro.net>
To: lucio@proxima.alt.za,
quanstro@quanstro.net
References: <a75cdbce8f12d43125d85da97b6aa622@proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <a75cdbce8f12d43125d85da97b6aa622@proxima.alt.za>
Subject: Re: [9fans] warning of putchar
it's a good stop-gap. i'm pretty sure the hueristics like this do
not work, in general.
the most consistant indicator of spam is the structure of the
Recieved lines. unfortunately, i have yet to figure out how to
write a set of rules for recieved lines that's 85% effective.
maybe the real problem is that spam is like porn. "i know it when
i see it." ;-)
- erik
lucio@proxima.alt.za writes
|
| > there is recourse. run your own mailserver. i blew some power
| > supplies, i've been using the third-in-line server, which i don't
| > control.
|
| Ah, that explains it. My approach to spam curbing consists of dumping
| unknowns to a folder in Cape Town and forwarding to my home only
| summary headers. Occasionally, I spot mail from a desired source,
| otherwise I check the folder on a whim.
|
| It's not ideal, but it does diminish my frustration level without
| depriving me of important mail. Now to figure out how to use the
| notification as a remote mechanism to prompt forwarding or discrding.
|
| ++L
sendmail lucio@proxima.alt.za quanstro@quanstro.net
From: erik quanstrom <quanstro@quanstro.net>
To: lucio@proxima.alt.za,
quanstro@quanstro.net
References: <a75cdbce8f12d43125d85da97b6aa622@proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <a75cdbce8f12d43125d85da97b6aa622@proxima.alt.za>
Subject: Re: [9fans] warning of putchar
it's a good stop-gap. i'm pretty sure the hueristics like this do
not work, in general.
the most consistant indicator of spam is the structure of the
Recieved lines. unfortunately, i have yet to figure out how to
write a set of rules for recieved lines that's 85% effective.
maybe the real problem is that spam is like porn. "i know it when
i see it." ;-)
- erik
lucio@proxima.alt.za writes
|
| > there is recourse. run your own mailserver. i blew some power
| > supplies, i've been using the third-in-line server, which i don't
| > control.
|
| Ah, that explains it. My approach to spam curbing consists of dumping
| unknowns to a folder in Cape Town and forwarding to my home only
| summary headers. Occasionally, I spot mail from a desired source,
| otherwise I check the folder on a whim.
|
| It's not ideal, but it does diminish my frustration level without
| depriving me of important mail. Now to figure out how to use the
| notification as a remote mechanism to prompt forwarding or discrding.
|
| ++L
sendmail lucio@proxima.alt.za quanstro@quanstro.net
From: erik quanstrom <quanstro@quanstro.net>
To: lucio@proxima.alt.za,
quanstro@quanstro.net
References: <a75cdbce8f12d43125d85da97b6aa622@proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <a75cdbce8f12d43125d85da97b6aa622@proxima.alt.za>
Subject: Re: [9fans] warning of putchar
it's a good stop-gap. i'm pretty sure the hueristics like this do
not work, in general.
the most consistant indicator of spam is the structure of the
Recieved lines. unfortunately, i have yet to figure out how to
write a set of rules for recieved lines that's 85% effective.
maybe the real problem is that spam is like porn. "i know it when
i see it." ;-)
- erik
lucio@proxima.alt.za writes
|
| > there is recourse. run your own mailserver. i blew some power
| > supplies, i've been using the third-in-line server, which i don't
| > control.
|
| Ah, that explains it. My approach to spam curbing consists of dumping
| unknowns to a folder in Cape Town and forwarding to my home only
| summary headers. Occasionally, I spot mail from a desired source,
| otherwise I check the folder on a whim.
|
| It's not ideal, but it does diminish my frustration level without
| depriving me of important mail. Now to figure out how to use the
| notification as a remote mechanism to prompt forwarding or discrding.
|
| ++L
prev parent reply other threads:[~2006-01-16 2:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 14:11 cej
2006-01-13 16:41 ` erik quanstrom
2006-01-13 22:33 ` geoff
2006-01-14 0:30 ` erik quanstrom
2006-01-13 22:36 ` C H Forsyth
2006-01-13 22:43 ` geoff
2006-01-14 0:03 ` erik quanstrom
2006-01-14 0:33 ` Devon H. O'Dell
2006-01-14 0:59 ` Paul Lalonde
2006-01-14 1:07 ` erik quanstrom
2006-01-14 12:15 ` erik quanstrom
2006-01-14 18:22 ` Russ Cox
2006-01-14 21:27 ` erik quanstrom
2006-01-16 2:57 ` erik quanstrom [this message]
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=20060116025735.6F47332554@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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;
as well as URLs for NNTP newsgroup(s).