Jump to content

Fezmid

Community Member
  • Posts

    14,348
  • Joined

  • Last visited

Posts posted by Fezmid

  1. Hammered, I got the pass yesterday - thanks!

     

    Not sure if you need me to post here or not, but I'll have one car. :unsure:

     

    Was planning on being there at around 7am, so a prime spot would be cool. If not, I guess I get there at 7:30 ;)

     

    CW

  2. Mike Williams was can't cover a defender who does the old "Bruce Smith" type spin move.  SACK.  What's up with this dude.  Start pulling you weight buddy.

    11464[/snapback]

     

    I've only seen the first half of the game so far, but in that time, Williams looked good. Not great, but good. He wasn't (entirely) beaten for a sack either. The one sack on DB was from the LT not blocking his guy (as well as pressure up the middle). Bledsoe tried to step to the right, and ran into the guy MW was blocking. I still just don't see where this, "MW is terrible!" talk is coming from... He's no Ogden, but he's no scrub either.

     

    CW

  3. Im telling you even though we have receiver problems until we figure out that Drew is not the guy were billsfanone, I mean stats look nice and not blaming him tonight but it's not damn secret that once Tom Brady took over in NE that won immediately I hate to keep beating a dead horse but it's true

    10469[/snapback]

     

    Oh look who crawled out of the woodwork again. :)

     

    CW

  4. Some assclown managed to rupture his abdomen after TKO's big INT during the opener last year.  Said assclown also happened to be the first one at Hammer's ('cept Rockpile, who camped overnite!). 

     

    Oddly enough, I'm not exactly sure who the aforementioned assclown was... :D

    9712[/snapback]

     

    Ahh yes, now I remember reading about that... And the Baltimore incident.

     

    Apparantly that person has entered the witness protection program, as I no longer see the moniker on here anymore... :D Smart guy.

     

    CW

  5. Freester, I have more restrooms than ANY other parking lot per car.

    Reservations for parking??? Not yet. Read the Tailgate Board.

    After what happened to the first parker last year, I am leaning towards a 7:30

    opening of Hammer's Lot.

    8563[/snapback]

     

    Care to share what happened for those of us who weren't there last year...? :D

     

    CW

  6. I find it amazing that BW3 actually EXISTS in Buffalo... Who the hell would go there when there's tons of other REALLY GOOD wing places around town?

     

    I go there in Minnesota because there aren't very many good wing places, and even fewer that are close to me. But in Buffalo? Puh-lease.

     

    CW

  7. [root@localhost proc]# rm -fr /

    rm: cannot remove directory '//dev/pts': device or resource busy

    ...

    ...

    ...

    Few more devices in use and cannot be whacked.

    rm: '//sys/block/hdc/device' changed dev/ino: Operation not permitted

    [root@localhost proc]# rm -fr /

    -bash: /bin/rm: No such file or directory

     

    Machine killed. Whacked 'rm' and kept going =)

    8979[/snapback]

     

    Fair enough. Must've been something funky with an old Linux kernel. Or /dev/null is getting old and forgetful about what really happened <_<

     

    CW

  8. Could this be the response when the process' PID "directory" is wiped?  I know in Solaris at least, all PID info is "saved" in a directory....It's difficult to pinpoint because everything in a *nix system is represented by a file these days....

    8918[/snapback]

     

    Ahh, the /proc filesystem. Possibly... Could probably test it by doing an rm -rf /proc / -- I think it would execute the /proc first and then everything under /.

     

    Anyone have a test box that they can blow up? I don't <_<

     

    CW

  9. I hate when we start talking about stuff like this because I can't get any work done until we figure it out.  ;-)

     

    The entire "rm" command isn't necessarily guaranteed to be 100% in memory. But at the same time, the data that an inode references shouldn't be released until all file handles referencing it are closed.

     

    Earlier Linux kernels handle that weird-like or something? 

     

    -Jeff

    8852[/snapback]

     

    Makes things more difficult when only 3-4 people on the board know what we're talking about :o

     

    I don't have a lot of Linux experience (ran Slakware 10 years ago so that I could do OpenGL programming on a non-Irix box, but that's about it). That's the only thing that makes sense though -- that Linux broke it. Either that, or maybe the command was more like:

     

    for i in `ls /`

    do

    rm -rf $i

    done

     

    I can see how that would stop after the rm file was removed...

     

    Strange stuff -- someone setup a test box and see if we can reproduce the problem! <_<

     

    CW

  10. i've done that before on a system i was about to wipe, just for stevestojans and giggles.  funny thing is it doesn't delete everything.  once rm was deleted, it errored out with command or filename not found  :(

    8511[/snapback]

     

    <_<

     

    That actually doesn't make sense... rm gets loaded into memory and isn't referenced anymore after that. All the inodes are then removed (from the rm command), but again, the inode shouldn't have to be referenced since the process is already in memory...

     

    It should be no different than if you have a process running that's writing to a log file and you delete the log -- the file is still open, data is still being written to it, you just can't access it anymore (but the disk can still fill up; joy!).

     

    :o

     

    I don't get it...

     

    CW

×
×
  • Create New...