I had a directory that I wanted 777 for all but user www. The solution was simple with ACL's; it eliminated the need for adding a new group for one measly dir.
At some point, you just have to cut the fat. If these ports have been broken for so long and no one has made an effort, then their disappearance should be transparent. In fact, I would like to see this logic applied to the entire PR system. Old PR's should be closed and archived as "known issues."
....but the articles in the BSD section are often far more interesting than the crap on the front page. They `matter' a lot more. Who cares what Bond would use for wireless hacking.
Let me elaborate: I newfs'ed the disk, started copying data to it, and it started failing. FreeBSD umounted it and the whole nine yards. cp exited; otherwise nothing `bad' happened. As mentioned, it was sveet.
This is good, one thing off the TODO list! Thats assuming its good, which I'm sure it is; I've never had problems with the ATA driver (only the devices themselves). In fact, I bought a broken (!) disk off of ebay, and freebsd detected that it sucked, and "removed it from config." The box kept humming along like nothing happened. It was sveet.
Every line of code written for X is a waste of time. Where is our better, faster, more well-intergrated window system that doesn't use the network? Why do we still use this piece of crap implementation of a window system? Hey, while we're here, lets send keyboard and mouse data through the network too!
What we really need is to stop messing around with X altogether and roll something that actually works. Don't even get me started on extensions either; they are no better than NAT delaying ipv6. X has a purpose, just not as a primary window system.
Thanks for coming out though!
I think that as Kazaa-using teens get older, and eventually have kids, this whole deal will be irrelevant. More and more people will stop giving a fuck about paying for music, and will be increasingly aware of how to circumvent these types of things.
Don't listen to the rumours pal. I have 56k and I cvsup everyday. The more frequently you do it, the less time it takes (to a point). Don't let cvsup scare away from freebsd. Also, you can use CTM, which is supposedly very bandwidth friendly.
Slashdot Mirror
I had a directory that I wanted 777 for all but user www. The solution was simple with ACL's; it eliminated the need for adding a new group for one measly dir.
Go ACL's!
At some point, you just have to cut the fat. If these ports have been broken for so long and no one has made an effort, then their disappearance should be transparent. In fact, I would like to see this logic applied to the entire PR system. Old PR's should be closed and archived as "known issues."
Holy was that ever not funny. It doesn't make any sense! WTF did I type that? "44BSD." ROFL! Oh, thats a laugh and a half! Stop, you're killing me!
My answer is 44BSD
Dru Lavigne is a girl.
....but the articles in the BSD section are often far more interesting than the crap on the front page. They `matter' a lot more. Who cares what Bond would use for wireless hacking.
Let me elaborate: I newfs'ed the disk, started copying data to it, and it started failing. FreeBSD umounted it and the whole nine yards. cp exited; otherwise nothing `bad' happened. As mentioned, it was sveet.
This is good, one thing off the TODO list! Thats assuming its good, which I'm sure it is; I've never had problems with the ATA driver (only the devices themselves). In fact, I bought a broken (!) disk off of ebay, and freebsd detected that it sucked, and "removed it from config." The box kept humming along like nothing happened. It was sveet.
I think supporting older versions of FreeBSD important, to keep older systems secure and up to date (where they can be...).
They didn't review FreeBSD's, one of the best there is. What a fucking waste of time.
I checked the website, and there is no indication that any more code came from Poland in this release than 5.0.
It should be noted: I am Canadian(TM) (Yes, Molson copyrighted "Canadian." Too bad their beer is ass.)
Having recently gotten electricity up here, VoIP is a very nice touch indeed! Now we can communicate between igloos much more easily.
Life is good.
Every line of code written for X is a waste of time. Where is our better, faster, more well-intergrated window system that doesn't use the network? Why do we still use this piece of crap implementation of a window system? Hey, while we're here, lets send keyboard and mouse data through the network too! What we really need is to stop messing around with X altogether and roll something that actually works. Don't even get me started on extensions either; they are no better than NAT delaying ipv6. X has a purpose, just not as a primary window system. Thanks for coming out though!
I think that as Kazaa-using teens get older, and eventually have kids, this whole deal will be irrelevant. More and more people will stop giving a fuck about paying for music, and will be increasingly aware of how to circumvent these types of things.
Time will tell.
-Craig
Don't listen to the rumours pal. I have 56k and I cvsup everyday. The more frequently you do it, the less time it takes (to a point). Don't let cvsup scare away from freebsd. Also, you can use CTM, which is supposedly very bandwidth friendly.