How does one sign up for a contrib directory these days?
I tried the addresses in
http://www.plan9.bell-labs.com/wiki/plan9/how_to_contribute/
http://9fans.net/archive/2013/05/231
a few months ago, but never heard anything back.
-- David
/n was introduced (i believe) in 8th edition for weinberger's neta (and
later netb) remote filesystem.
there was a directory in /n for each remote machine. the gmount() system
call was used to mount a stream, usually a datakit connection, to the
remote machine. it was great.
brucee
On 13 Januar
When I first met plan9 (2nd ed) I realized that /n was a very powerful
ordering concept. (Since then I usually create a /n or ~/n on every
unix where I will use mount to customize my ns.)
I'd like to know
- what's the story of /n? (why was it invented?)
- what does n stand for? (a set of n things?)
this patch is wrong. it changes fsysversion() which leaves
t.msize uninitialized.
static
Xfid*
fsysversion(Xfid *x, Fid*)
{
Fcall t;
if(x->msize < 256)
return respond(x, &t, "version: message size too small");
if(t.msize > Maxblock)
t.msize
the buffer isn't big enough for SHA1 hashes, which are larger than MD5
hashes.
- erik
; 9diff devtls.c
/n/sources/plan9/sys/src/9/port/devtls.c:732,738 - devtls.c:732,738
{
OneWay *volatile in;
Block *volatile b;
- uchar *p, seq[8], header[RecHdrLen], hmac[MD5dlen];
+
i pushed out a small update to upas/fs that should be a big help
for mailboxes with >5000 messages. with my test mailbox of
8868 messages, the old fs requires 41mb to read the mailbox
and the new just 12mb. it also shaved the startup time from
18s to 3s.
the gnarly details:
upas/fs uses 1 Hash
On Tue, Jun 24, 2008 at 11:00 PM, Russ Cox <[EMAIL PROTECTED]> wrote:
> before i poked through the archives, i would have
> credited dan cross with the idea. is dan still on this list?
Dan is still on the list, but has been kept very, very busy by the US
Marine Corps lately. Semper Fidelis (Plan
> pardon me for the correction, but i believe the original
> idea (and implementation, under inferno) was mine.
>
> http://9fans.net/archive/2002/07/327
i stand corrected. (and we'd already established my
memory of the event was faulty. ☺)
I honestly don´t remember, but according to our dump, it seems that
autofs, then autodirfs, then mntgen was added on Jul 16th, 2002 to our dump.
Looking at Rog´s mail, (Jul 15th) I think that probably I did read his
idea on the list
and implemented it for Plan 9.
A nice thing of Plan 9 is that it
On Wed, Jun 25, 2008 at 4:00 AM, Russ Cox <[EMAIL PROTECTED]> wrote:
> mntgen appeared on the scene relatively late.
> there was a time when you just ran mkdir a lot in /n.
> looking through the archives, it looks like nemo
> came up with the idea as "autodirfs" in 2002.
pardon me for the correcti
where is dan? he's a fine man.
brucee
On Wed, Jun 25, 2008 at 1:00 PM, Russ Cox <[EMAIL PROTECTED]> wrote:
>> why do files in /n exist on the distributed image?
>> when would they be necessary?
>
> mntgen appeared on the scene relatively late.
> there was a time when you just ran mkdir a lot in /
> mntgen appeared on the scene relatively late.
> there was a time when you just ran mkdir a lot in /n.
> looking through the archives, it looks like nemo
> came up with the idea as "autodirfs" in 2002.
>
> before i poked through the archives, i would have
> credited dan cross with the idea. is d
> why do files in /n exist on the distributed image?
> when would they be necessary?
mntgen appeared on the scene relatively late.
there was a time when you just ran mkdir a lot in /n.
looking through the archives, it looks like nemo
came up with the idea as "autodirfs" in 2002.
before i poked th
why do files in /n exist on the distributed image?
when would they be necessary?
- erik
> for me, there's one problem with this alternative to
> the "stupid" spamhaus solution — it requires i run
> a linux server.
It does not.
There are content-based filters for Plan 9.
Or I bet you could port many of the standard
Unix ones over without much trouble.
Mail Avenger is a little harder
> I don't have a false positive mailbox to skim.
> I run Mail Avenger, which lets me run shell scripts
[...]
> I run Spam Assassin. If SA thinks the mail is spam,
> SMTP rejects it rather than saving it or deciding to
> reject it later and having to send a bounce. That
for me, there's one proble
On Tue, May 13, 2008 at 4:07 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
>
> at work we have a barracuda box which seems to
> be completely content based. it's false positive
> rate is significant. so you actually need to skim
> up to a hundred questionable messages per week.
>
more troubl
My mail server does not run Plan 9, so my own
setup would require some implementation work,
as I mentioned before.
> how do you maintain content-based filtering without
> spending time on it on a regular basis?
I typically see one or two spams a day that make
it through, and I save those into a
>> your solution for backscatter is a good one. but
>> how does it do against non backscatter? this
>> is also a significant problem. generally >100
>> messages per day for me.
>
> content-based filtering works fine for me.
how do you maintain content-based filtering without
spending time
> your solution for backscatter is a good one. but
> how does it do against non backscatter? this
> is also a significant problem. generally >100
> messages per day for me.
content-based filtering works fine for me.
> am i an idiot for objecting to this?
i never said you were an idiot.
i
> I use Greylisting [1], and it's been really effective. No false
> positives (so far), and 0 to 2 spam messages a day. All this for a
> mild ~15 minute delay on genuine emails (but only for the first time).
sites like plan9.bell-labs.com tend not resend email with prec. bulk
even when given
On 13-May-08, at 4:17 AM, erik quanstrom wrote:
what's a better idea. having an extra 6400 spam emails
is the problem. how to i solve this without using spamhaus?
I use Greylisting [1], and it's been really effective. No false
positives (so far), and 0 to 2 spam messages a day. All this for
> So you're blocking mail from forsyth in order
> to block spam bounces from <>?
>
> I already told you how I solved this when it
> happened to me, and it has been 100% effective
your solution for backscatter is a good one. but
how does it do against non backscatter? this
is also a significant
> the problem is that spf only validates that the sender is an
> allowed sender. this is ineffective against backscatter
> attacks. i've gotten as many as 500 backscatter spam in 4 hrs.
> so this is a significant issue for me.
So you're blocking mail from forsyth in order
to block spam bounces f
Charles Forsyth wrote:
this is all reminiscent of the nonsense of RFC1413
I think that people are finally ready to accept the fact that packets on the outdoor highway do not disclose the
intentions of their senders and that they contain no meaningful information about the identity of their
// rfc 2317 allows arbitrary cidrs to be delegated. so far,
// i've always been able to get reverse mappings set up
// for static addresses.
I think you've been lucky, or have been dealing with better ISPs.
Apart from my home ADSL line, I share a commercial SDSL with
some folks. We've got a /123
>> The solution for people on dynamic addresses (typically with some
>> generic and non-matching PTR record, though I haven't checked yours) is
>> likely to relay out through your ISP's mail server.
>
> because of the way the DNS is put together, PTR records cannot be relied upon.
> ownership of t
> The solution for people on dynamic addresses (typically with some
> generic and non-matching PTR record, though I haven't checked yours) is
> likely to relay out through your ISP's mail server.
because of the way the DNS is put together, PTR records cannot be relied upon.
ownership of the DNS en
The botnets have ruined the sandbox forever.
On 5/12/2008 18:34, Charles Forsyth wrote:
> well, i'm now on the list for the simple reason that i got a different
> cable modem, which prompted a new IP address.
The solution for people on dynamic addresses (typically with some
generic and non-matchi
i agree that spamhaus is a big hammer. i'm open to suggestions.
preferably ones that do not require daily maintence.
> Things like SPF don't catch as much spam (yet; it'll improve as the
> acceptance improves), but have a very attractive false hit rate.
the rate just isn't good enough for me. h
> please don't, or at least check spf before spamhaus.
> the quality of their data is at best questionable,
> and there is no (usable) way to correct it.
the problem is that spf only validates that the sender is an
allowed sender. this is ineffective against backscatter
attacks. i've gotten as m
// Althrought I'd like it to be different, blacklists are quite effective
// blocking spam. It's the best solution as long as we continue using SMTP.
This entirely depends how you prioritize things. If "best" and "effective"
are measured on what percentage of spam emails get blocked, yes,
service
was:
Mon May 12 21:57:03 BST 2008 connect to net!quanstro.net:
554 5.7.1 rejected: spamhaus: sh policy
===> 2/ (message/rfc822) [inline]
To: [EMAIL PROTECTED]
Subject: re: [9fans] /n/sources/patch/spamhaus
From: Charles Forsyth <[EMAIL PROTECTED]>
Date: Mon, 12 May 2008 21:56:46 +0100
ailed (code smtp 2838130:
> Permanent Failure).
> The symptom was:
>
> Mon May 12 21:57:03 BST 2008 connect to net!quanstro.net:
> 554 5.7.1 rejected: spamhaus: sh policy
>
> ===> 2/ (message/rfc822) [inline]
> To: [EMAIL PROTECTED]
> Subject: re: [9fans] /n/sources/patch/spamh
CTED]
Subject: re: [9fans] /n/sources/patch/spamhaus
From: Charles Forsyth <[EMAIL PROTECTED]>
Date: Mon, 12 May 2008 21:56:46 +0100
> what leads you to say spamhaus's data is questionable?
well, i'm now on the list for the simple reason that i got a different
cable modem, which prompted a new IP address.
> the quality of their data is at best questionable,
as is their rationale
please don't, or at least check spf before spamhaus.
the quality of their data is at best questionable,
and there is no (usable) way to correct it.
37 matches
Mail list logo
