We have a picture of it right? Seriously what if every time somebody did something new that spot was forbidden to be stepped on again? asinine. What if nobody as allowed to visit the beach of Columbus's first landing sites? BFD, send a plaque or something and stop wasting your time worrying about whether a footprint is going to disappear someday. It will.
meh it's easy to circumvent though isn't it? Couldn't Apple just say that os x is nextstep rebranded and next owned the copyright on openstep. Since pple owns all next trademarks os x has therfore been trademarked since 1989 (or whateer). Sorry if this is ignorant IANAL.
# zeroing out a drive while test 1; do dd if=/dev/urandom of=/dev/dsk/c0t0d0s2; done
-- this would take a long time and doesn't 'zero' but fills the drive with random junk. It would be a lot faster to use/dev/zero as it doesn't require the CPU to calculate a random number every millisecond before writing it to disk.
It might not sound like a big deal, but as HD's get bigger so does seagates 'edge' over the competition. They get to trim 73MB (or so) off every gig. This means that a 250GB drive from seagate is missing 18,435,456,000 bytes. A 500GB drive: 36,870,912,000. In the olden days, this wouldn't have mattered (much) because you weren't talking about a lot of space. People complained back then too. Now it's getting a little silly. If you need to build a 5TB array, there will be 368GB that's just missing (and that's not even counting the FS overhead).
Seagate isn't doing it to be a champion of change for a switch to base10 counting (if they were then it would make more sense), they are doing it to rip people off on a technicality.
I seem to remember those days too. I was thinking a few days ago that I remember going to more websites per day. I tried to remember their names, but got stuck at geek.net. Now I pretty much just hang around slashdot, and userfriendly, with occasional stop-offs at multiply or linkedin.
Slashdot Mirror
Can you find me an example of a hole in SELinux? Even one? I don't mean a flaw in policy affecting some distros, but an actual flaw in the subsystem?
http://linux.slashdot.org/story/10/09/20/0217204/Linux-Kernel-Exploit-Busily-Rooting-64-Bit-Machines?from=rss
Yeah but just wait... The decade isn't quite over yet. One more year to go.
We have a picture of it right? Seriously what if every time somebody did something new that spot was forbidden to be stepped on again? asinine. What if nobody as allowed to visit the beach of Columbus's first landing sites? BFD, send a plaque or something and stop wasting your time worrying about whether a footprint is going to disappear someday. It will.
Go back to you BBS, and Gopher protocols. We've no more use for you here.
So the pipes are clean then?
http://ars.userfriendly.org/cartoons/?id=20070101
btw can't they 'rollback' the changes to the DB?
meh it's easy to circumvent though isn't it? Couldn't Apple just say that os x is nextstep rebranded and next owned the copyright on openstep. Since pple owns all next trademarks os x has therfore been trademarked since 1989 (or whateer). Sorry if this is ignorant IANAL.
I know this is likely to get lost in all the comments, but bookmark this: http://www.unixwiz.net/techtips/be-consultant.html
http://www.faronics.com/html/Deepfreeze.asp
The tell me if something worked command would be a lot shorter like so ./command && echo $?
who links /bin to /usr/bin? That's dumb. Especially if the system makes /usr it's own partition. Boot into single user mode to see why.
meh, good OS but lacks a decent editor.
IIRC 9/11 had a lot more.
# zeroing out a drive
while test 1; do dd if=/dev/urandom of=/dev/dsk/c0t0d0s2; done
-- /dev/zero as it doesn't require the CPU to calculate a random number every millisecond before writing it to disk.
this would take a long time and doesn't 'zero' but fills the drive with random junk. It would be a lot faster to use
most newer linuxes I've used have more aliased to less.
now THAT's what I'm talking about here!!!!
and we liked it that way!!! ;-)
I use the 'douche' command for that. It's also more compatible with other oses: du -sh
...that maybe control of ReiserFS will now be in the hands of someone who is not a total cock...
;) someone else will take it over.
Bingo.
From TFA "ReiserFS4 has been on hold pending his legal trouble". Now that his legal woes are 'over'
Seems like nobody remembers Eazel anymore (gnome users I'm looking at you).
*hint: think 'nautlius'
I'm thinking they're just going to block us anyway.
My squirrelmail seems to be working just f$#$^$%^$*@((((((#@34..........NO CARRIER
or worse, the police disable a bystanders pacemaker.
Hey! You made it in the "10 hot comments" box on the front page with this one. :-)
Wonderful I come in here to make a joke, but 100+ others had the same joke... ;)
Because computers are base2.
It might not sound like a big deal, but as HD's get bigger so does seagates 'edge' over the competition. They get to trim 73MB (or so) off every gig. This means that a 250GB drive from seagate is missing 18,435,456,000 bytes. A 500GB drive: 36,870,912,000. In the olden days, this wouldn't have mattered (much) because you weren't talking about a lot of space. People complained back then too. Now it's getting a little silly. If you need to build a 5TB array, there will be 368GB that's just missing (and that's not even counting the FS overhead).
Seagate isn't doing it to be a champion of change for a switch to base10 counting (if they were then it would make more sense), they are doing it to rip people off on a technicality.
I seem to remember those days too. I was thinking a few days ago that I remember going to more websites per day. I tried to remember their names, but got stuck at geek.net. Now I pretty much just hang around slashdot, and userfriendly, with occasional stop-offs at multiply or linkedin.