Re:Rather Interesting Concept
by
NightmareDNS
·
· Score: 1, Informative
Since it doens't use anyhting but transparency effects, you wouldn't be too impressed with the end result. All you'd see is some lines and opaque boxes. My first reaction to looking at the mpeg was "yeah, so?". It doesn't look too original, and certainly isn't very interesting. I guess I just don't get it, but it doesn't seem to serve any real purpose.
This would have been a lot more impressive
by
pcx
·
· Score: 3, Informative
This would have been a lot more impressive if they had actually used java to animate the schematic instead of a static movie. Something along the lines of this...
http://www.visualthesaurus.com/index.jsp
Still cool, just not _slashdot_ cool.
Now available in P2P
by
10Ghz
·
· Score: 3, Informative
I shared the files in Kazaa. Look for "Linux Kernel 3D"
-- Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
Gnutella mirror
by
Henk+Poley
·
· Score: 2, Informative
The server will fade out sooner or later, so I put up a gnutella mirror of the first linked video "A guided tour of Linux-2.4.5: 9 MB MPEG (384x288, 2000 frames)."
I'll keep them there for some hours, depending on the load induced to my puny 384 kb/s (<48 kB/s) bandwidth.
So far it seems though that the actual site is enduring pretty good too.
Re:Rather Interesting Concept
by
jejones
·
· Score: 2, Informative
It doesn't do much of anything; it just shows off some of the more perverse corners of C, and that you can't get away with writing a minimalist parser to pull off something like this project--you have to go nearly whole hog, including at least enough of a symbol table to tell whether a * b; is a pointless expression or a declaration of a pointer to some typedef-ed type.
Re:Stupid quicktime format
by
Anonymous Coward
·
· Score: 1, Informative
Um, true, mplayer is your friend, but these aren't quicktime videos...
Playing 120-241.mpg
Cache fill: 5.37% (450560 bytes) Detected MPEG-ES file format!
VIDEO: MPEG1 384x288 (aspect 1) 30.00 fps 131071.5 kbps (16383.9 kbyte/s)
Mod parent down!
by
Anonymous Coward
·
· Score: 2, Informative
Geez!
That's not actual code from the kernel source. It's an example of what kind of code gcc compiles and why it's hard to write a gcc-C parser.
The real kernel code is mostly easy to read for humans (because they have no problem with context recognition).
Re:Browsing is step one
by
plugger
·
· Score: 2, Informative
Interesting, but flawed...
by
Junta
·
· Score: 2, Informative
At least the evolution animation was flawed. The evolution would imply the linear progression, but at fork points, stable releases with lower numbers were released well after development versions of higher numbers. For it to be the most accurate, you would have to only follow a kernel series to the fork point, then switch to the newer fork and ignore releases in the stable fork. 2.0.38 was released well after 2.1.0, though the animation suggests 2.1.0 as the immediate succesor to 2.0.38
I know, it's just eye candy, but thought I'd call them on it since no one else has...
-- XML is like violence. If it doesn't solve the problem, use more.
Re:watching the bits on an Atari ST
by
StormReaver
·
· Score: 3, Informative
Tandy's line of CoCo computers worked the same way with video. Set a couple registers to tell the video generator which part of system RAM to treat as video and watch the operating system state displayed on-screen.
It was mildly amusing from time to time.
My workplace recently bought all us programmers new Gateway systems where the integrated video card (a GeForce model) uses the same technology for video as the CoCo from the past. Figure out how to tell the board which part of system memory should be treated as video, and the same effect could be had.
Since it doens't use anyhting but transparency effects, you wouldn't be too impressed with the end result. All you'd see is some lines and opaque boxes. My first reaction to looking at the mpeg was "yeah, so?". It doesn't look too original, and certainly isn't very interesting. I guess I just don't get it, but it doesn't seem to serve any real purpose.
NightmareDNS =)
I'm going to go ahead and test my university's bandwidth by mirroring the movies at http://www.public.iastate.edu/~omikron/linux3d/
I'll leave them there for 2 hours. Good luck.
http://somacore.com/slash3d/
NightmareDNS =)
http://mynetpad.com/mirror/perso.wanadoo.fr/pascal .brisset/kernel3d/kernel3d.html
I like to build things and wire stuff together.
http://somacore.com/slash3d/
they really aren't worth it.
NightmareDNS =)
This would have been a lot more impressive if they had actually used java to animate the schematic instead of a static movie. Something along the lines of this...
http://www.visualthesaurus.com/index.jsp
Still cool, just not _slashdot_ cool.
I shared the files in Kazaa. Look for "Linux Kernel 3D"
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
The server will fade out sooner or later, so I put up a gnutella mirror of the first linked video "A guided tour of Linux-2.4.5: 9 MB MPEG (384x288, 2000 frames)."
magnet:245.mpg
gnutella://245.mpg
ed2k://245.mpg"
More to follow?
>P.S. Does anyone else think that it would be nice to have such a map printed in high detail on a large black poster?
i e/3884/
You can get something like that here http://www.thinkgeek.com/cubegoodies/posters/tech
That link again: Linux Kernel Poster
http://bisqwit.iki.fi/kala/kernel3d/
I'll keep them there for some hours, depending on the load induced to my puny 384 kb/s (<48 kB/s) bandwidth.
So far it seems though that the actual site is enduring pretty good too.
It doesn't do much of anything; it just shows off some of the more perverse corners of C, and that you can't get away with writing a minimalist parser to pull off something like this project--you have to go nearly whole hog, including at least enough of a symbol table to tell whether a * b; is a pointless expression or a declaration of a pointer to some typedef-ed type.
Um, true, mplayer is your friend, but these aren't quicktime videos... Playing 120-241.mpg Cache fill: 5.37% (450560 bytes) Detected MPEG-ES file format! VIDEO: MPEG1 384x288 (aspect 1) 30.00 fps 131071.5 kbps (16383.9 kbyte/s)
Geez!
That's not actual code from the kernel source. It's an example of what kind of code gcc compiles and why it's hard to write a gcc-C parser.
The real kernel code is mostly easy to read for humans (because they have no problem with context recognition).
Check Doom as a Tool for System Administration.
At least the evolution animation was flawed. The evolution would imply the linear progression, but at fork points, stable releases with lower numbers were released well after development versions of higher numbers. For it to be the most accurate, you would have to only follow a kernel series to the fork point, then switch to the newer fork and ignore releases in the stable fork. 2.0.38 was released well after 2.1.0, though the animation suggests 2.1.0 as the immediate succesor to 2.0.38
I know, it's just eye candy, but thought I'd call them on it since no one else has...
XML is like violence. If it doesn't solve the problem, use more.
Tandy's line of CoCo computers worked the same way with video. Set a couple registers to tell the video generator which part of system RAM to treat as video and watch the operating system state displayed on-screen.
It was mildly amusing from time to time.
My workplace recently bought all us programmers new Gateway systems where the integrated video card (a GeForce model) uses the same technology for video as the CoCo from the past. Figure out how to tell the board which part of system memory should be treated as video, and the same effect could be had.