Actually, OpenAFS supports servers only on NetBSD now, and there's no current work on clients for NetBSD in 1.3. All that said, I suspect the work I'm going to need to do for MacOS shortly will make NetBSD support much easier, but one thing at a time.
I work at Carnegie Mellon, and am one of the OpenAFS gatekeepers, we have gotten no contributions of NetBSD code for AFS ever from anyone at CMU, so I'd like to know who your liar is.
Everyone wants more OpenAFS documentation, and no one seems to be actively working on it. The volunteers don't seem to be tripping over each other to do it.
This was in the Heroine Virtual forum on Sourceforge and is dated 4 days ago. It certainly isn't "the reason" but it's amusing to see that it was a consideration that recently (when a fresh copy of source to Cinelerra, the successor to Broadcast, was uploaded to Sourceforge)
Verizon doesn't need to build a new CO to serve you; They need to stop buying e.g. GTEs long enough to drop a box which cost on the order of $6000 2.5 years ago in a vault near you. In my case I am more than 3 miles from my CO, but such a vault exists about 1/2 mile from my house; There is still fiber in my house from a no-longer-present T1 which ran first to that vault. The information about the box, which my recollection was called something like a "DSL Remote Terminal" was provided in response to a query of mine to comp.dcom.xdsl. I may have a product name and model number somewhere, but my complaints to Verizon at the time fell on deaf ears, and now I have a cable modem because I still lack any other choice.
You say "If you're in on of the top 25 Metropolitan Areas in N.A., you might have a fiber line within a mile or so. Outside there, well, if you've got one within 10 miles, consider yourself lucky."
Yeah, that's nice. I have fiber *physically in my house* from a no-longer-in-service T1, and I *still* can't get any reasonable and affordable service.
So, just having fiber nearby does not make one lucky. I wish...
Oops, so I was wrong. Now, hopefully my bank situation will be straightened out sometime in the near future. You'd figure a bank which offered "online banking" could figure out what to do with an email address instead of falling back to the phone and trying it literally every day I was out of town before giving up:-)
I got the Redhat letter and then let that opportunity get away what with all the problems; This one I didn't get. Pffft. Guess I should be happy I had one chance to screw it up, eh?;-)
Slashdot Mirror
Comes with SonicWall in Pittsburgh too. Don't try to order a g string for your viola, it won't work.
Actually, OpenAFS supports servers only on NetBSD now, and there's no current work on clients for NetBSD in 1.3. All that said, I suspect the work I'm going to need to do for MacOS shortly will make NetBSD support much easier, but one thing at a time.
I work at Carnegie Mellon, and am one of the OpenAFS gatekeepers, we have gotten no contributions of NetBSD code for AFS ever from anyone at CMU, so I'd like to know who your liar is.
Sure, IBM is killing IBM AFS. What does that have to do with OpenAFS?
Try a nightly snapshot? Post actual problems (not "it didn't work") to openafs-info, and you'll probably even get useful feedback.
Crap. I better go turn mine off then. Wouldn't want to accidentally be able to get at my files when I travel, or go to work.
Everyone wants more OpenAFS documentation, and no one seems to be actively working on it. The volunteers don't seem to be tripping over each other to do it.
Actually, there's been a FreeBSD port in CVS for a while, it just hasn't made it into a release yet.
Someone at Michigan's already porting it.
Wow. You've proven you read memepool. Congratulations.
This was in the Heroine Virtual forum on Sourceforge and is dated 4 days ago. It certainly isn't "the reason" but it's amusing to see that it was a consideration that recently (when a fresh copy of source to Cinelerra, the successor to Broadcast, was uploaded to Sourceforge)
Verizon doesn't need to build a new CO to serve you; They need to stop buying e.g. GTEs long enough to drop a box which cost on the order of $6000 2.5 years ago in a vault near you. In my case I am more than 3 miles from my CO, but such a vault exists about 1/2 mile from my house; There is still fiber in my house from a no-longer-present T1 which ran first to that vault. The information about the box, which my recollection was called something like a "DSL Remote Terminal" was provided in response to a query of mine to comp.dcom.xdsl. I may have a product name and model number somewhere, but my complaints to Verizon at the time fell on deaf ears, and now I have a cable modem because I still lack any other choice.
You say "If you're in on of the top 25 Metropolitan Areas in N.A., you might have a fiber line within a mile or so. Outside there, well, if you've got one within 10 miles, consider yourself lucky." Yeah, that's nice. I have fiber *physically in my house* from a no-longer-in-service T1, and I *still* can't get any reasonable and affordable service. So, just having fiber nearby does not make one lucky. I wish...
Oops, so I was wrong. Now, hopefully my bank situation will be straightened out sometime in the near future. You'd figure a bank which offered "online banking" could figure out what to do with an email address instead of falling back to the phone and trying it literally every day I was out of town before giving up:-)
I got the Redhat letter and then let that opportunity get away what with all the problems; This one I didn't get. Pffft. Guess I should be happy I had one chance to screw it up, eh? ;-)