The iPod video has a special decoding chip for compressed video. It's a BCM2722, if I recall correctly. (And we still don't know how to work it.) The nano doesn't have that chip, so playing compressed video on it is going to be much, much harder, maybe impossible. We're working on it though.
-- Josh
It's COMPLETELY uncompressed: 2GB for 30 minutes of color video 220x176 15fps. Unfortunately, FAT32 doesn't support files bigger than 2GB, so you can only get about that much video at once.
To PostScript, a letter/word/line is just another shape that can be put on the page. You'd need to break lines manually, control line spacing yourself, etc. Want it justified? Forget it.
You'd be much better off using (La)TeX for this sort of thing.
4G and later iPods have been, in development, running at 110% realtime with the Tremor OGG player. So yes, recent iPods can play OGG. However, these iPods aren't officially supported yet.
Tyan's motherboards have consistently large amounts of DDR slots. Try the "Thunder K8W" (S2885), with 8 slots and 2 processors, or the "Thunder K8QS" (S4882) with 16 slots and 4 processors.
That would be 16 or 32 gigs, respectively.
The K8W is $500 or so, the K8QS around $1700. Your RAM will go around $600 for a 2GB stick. Opterons are anywhere from $200 (for a 2-way) or $750 (for a 4-way) and up - that's just 1.4GHz.
In summary: You can do it, but it's pretty darn expensive.
Is there any documentation about how VMware works?
I find this really interesting. Obviously some of it is going to be secret/NDA, but if there's a paper or something about the techniques that you use that we're allowed to see, please point me to it.
Thanks!:-)
However, the reason most people use a 'minimum' resolution is that they do not have the skills to make sites that can scale easily so they choose a size that they can work with
Actually, how about because one long line of text across a 1920x1600 screen (or whatever it is) looks horrible? It's the same reason newspapers design in columns: thinner lines are easier on the eyes. I only run at 1280x1024 and I can still see it on some sites.
So take your pick: eyesore or blank space. Alternatively, one could design a site that was laid out in several columns on high resolutions and one on low resolutions, but that's really too much work for most designers.
Hitachi's drives are not applicable to 24hr operation - they include a warning specifically against this. So for servers (which is a lot of where this storage goes), this is the first real 400GB drive.
As another poster mentioned, you could use an external Firewire/USB enclosure.
But if you just can't get over that "pop in a tape" feel, buy an SATA hotswap bay ($70) and a few, say, 120GB drives ($100 each).
Cost per GB: $1.20 (hd) vs. $.25 (tapes)
but the initial investment is $70 vs. $6e+3 (tape drive figure is an educated guess).
So unless you're going to be backing up more than, oh, six terabytes (really 5930 GB) concurrently, the hotswap bay is a better investment:-)
Thanks for everyone's insightful, interesting, and on-topic posts. To address some questions that were posed...
"Why are you doing this?"
Because I want to learn more about how the x86 works, and I want to provide something that doesn't yet exist.
"The Pentium is not virtualizable. You won't learn about virtualization in general, you'll learn about the Pentium."
Great!:-)
"Don't make a new project. Work on XYZ."
I don't know anything about the internals of other projects, and I want to do something unique.
To clarify: I'm wondering about virtualization because I'm working on a self-hosted VM monitor. (Think "ESX Server Lite".) It will be Open Source, of course, once I have anything remotely usable. (So far all I've done is set up page tables, IDT, IRQs, and use the timer interrupt to cycle the character in the upper-left corner.) Tentative name: XenOS. (Don't hold your breath...)
(Are there any well-known patents on dynamic code recompilation in software? Just curious...)
P.S. I'm using a virtualization thingy (VMware Workstation) to develop a virtualization thingy. Ironic.
plex86 only runs Linux under its VM. I assumed that the implementation for something like this is different from the implementation of a full x86 VM monitor. Is the code similar enough to warrant perusal, or will it just hopelessly confuse me even more?
Thanks for your help!
-- Josh
Slashdot Mirror
The iPod video has a special decoding chip for compressed video. It's a BCM2722, if I recall correctly. (And we still don't know how to work it.) The nano doesn't have that chip, so playing compressed video on it is going to be much, much harder, maybe impossible. We're working on it though. -- Josh
It's COMPLETELY uncompressed: 2GB for 30 minutes of color video 220x176 15fps. Unfortunately, FAT32 doesn't support files bigger than 2GB, so you can only get about that much video at once.
And yes, we're working on improving it.
It's called SDL.
To PostScript, a letter/word/line is just another shape that can be put on the page. You'd need to break lines manually, control line spacing yourself, etc. Want it justified? Forget it.
You'd be much better off using (La)TeX for this sort of thing.
4G and later iPods have been, in development, running at 110% realtime with the Tremor OGG player. So yes, recent iPods can play OGG. However, these iPods aren't officially supported yet.
Tyan's motherboards have consistently large amounts of DDR slots. Try the "Thunder K8W" (S2885), with 8 slots and 2 processors, or the "Thunder K8QS" (S4882) with 16 slots and 4 processors.
That would be 16 or 32 gigs, respectively.
The K8W is $500 or so, the K8QS around $1700. Your RAM will go around $600 for a 2GB stick. Opterons are anywhere from $200 (for a 2-way) or $750 (for a 4-way) and up - that's just 1.4GHz.
In summary: You can do it, but it's pretty darn expensive.
Is there any documentation about how VMware works? I find this really interesting. Obviously some of it is going to be secret/NDA, but if there's a paper or something about the techniques that you use that we're allowed to see, please point me to it. Thanks! :-)
Actually, it works quite well. I've installed Gentoo on a Power Mac 6500 (I'm using it as a server) and it worked quite well.
Could have been worse:
.*
/home would be like rm -rf /.
:-)
rm -rf
in
Consider yourself lucky!
I swear by IceWM. I just reinstalled most of the stuff on my system (FC1 -> Gentoo) and I use IceWM + Infadel2 theme for everyday GUI stuff.
:-)
I don't use a file manager. REAL users don't need no stinkin' file manager! (xemacs dired works too
For GUI apps: aterm, xemacs, firefox, xpdf, vmware.
And back on topic...
My favorite console apps are:
- mutt (I even use it in X)
- screen
- irssi
- zsh
- xemacs -nw
- nasm, yasm, gcc, make, cvs
and of course...
- emerge
-- Josh
So take your pick: eyesore or blank space. Alternatively, one could design a site that was laid out in several columns on high resolutions and one on low resolutions, but that's really too much work for most designers.
Hitachi's drives are not applicable to 24hr operation - they include a warning specifically against this. So for servers (which is a lot of where this storage goes), this is the first real 400GB drive.
Cost per GB: $1.20 (hd) vs. $.25 (tapes) but the initial investment is $70 vs. $6e+3 (tape drive figure is an educated guess). So unless you're going to be backing up more than, oh, six terabytes (really 5930 GB) concurrently, the hotswap bay is a better investment :-)
To clarify: I'm wondering about virtualization because I'm working on a self-hosted VM monitor. (Think "ESX Server Lite".) It will be Open Source, of course, once I have anything remotely usable. (So far all I've done is set up page tables, IDT, IRQs, and use the timer interrupt to cycle the character in the upper-left corner.) Tentative name: XenOS. (Don't hold your breath...)
(Are there any well-known patents on dynamic code recompilation in software? Just curious...)
P.S. I'm using a virtualization thingy (VMware Workstation) to develop a virtualization thingy. Ironic.
plex86 only runs Linux under its VM. I assumed that the implementation for something like this is different from the implementation of a full x86 VM monitor. Is the code similar enough to warrant perusal, or will it just hopelessly confuse me even more? Thanks for your help! -- Josh