Slashdot Mirror


Creating the Software Art In Tron Legacy

hownottowrite writes "A software artist has posted an overview of the coding behind the tools used to create Tron Legacy's special effects. 'In Tron, the hacker was not supposed to be snooping around on a network; he was supposed to kill a process. So we went with posix kill and also had him pipe ps into grep. I also ended up using emacs eshell to make the terminal more l33t. The team was delighted to see my emacs performance — splitting the editor into nested panes and running different modes. I was tickled that I got emacs into a block buster movie.' Ok, it's mostly a lot of awesome images, but there's a nifty reveal about an homage to Bit."

3 of 124 comments (clear)

  1. Re:So emacs was in a blockbuster movie by davester666 · · Score: 3, Interesting

    Who cares. The Net showed off Jasik's Debugger!

    --
    Sleep your way to a whiter smile...date a dentist!
  2. Anyone catch the output of uname? by tlhIngan · · Score: 4, Interesting

    Well, now everyone will copy and paste the output from the DVD, but I saw it in the theatre.

    And I saw Flynn key in "uname -a" and I tried to parse the listing for interesthing things.

    Alas, all I caught as the OS was named "SolarOS" and the arch was "sun4m". A tribute to ye olde SunOS, I guess (SunOS/sparc).

    Though, I'd love that nice popup history window...

    1. Re:Anyone catch the output of uname? by Anonymous Coward · · Score: 3, Interesting

      Since noone seems to actually do it, here you go:

      $ whoami
      Flynn
      $ uname -a
      SolarOS 4.0.1 Generic_50203-02 sun4m i386
      Unknown.Unknown
      $ login -n root
      Login incorrect
      login: backdoor
      No home directory specified in password file!
      Logging in with home=/
      # bin/history
      488 cd /opt/LLL/controller/laser/
      489 vi LLSDLaserControl.c
      490 make
      491 make install
      492 ./sanity_check
      493 ./configure -o test.cfg
      494 vi test.cfg
      495 vi ~/last_will_and_testament.txt
      496 cat /proc/meminfo
      497 ps -a -x -u
      498 kill -9 2207
      499 kill 2208
      500 ps -a -x -u
      501 touch /opt/LLL/run/ok
      502 LLSDLaserControl -ok 1

      And of course he straight goes to running it, instead of cat'ing the testament, or actually checking what it does ..
      # bin/LLSDLaserControl -ok 1