I've got a smaller 3D video compression algorithm - just promise not to tell anybody else, since I'm planning on patenting it - it runs from a shell, too!:
#!/bin/sh cat $1 >/dev/null
elegant, isn't it? The algorithm is small, and the compressed data is so tiny, even your OS can't find it!
Yes, speed will increase, and bandwith will also increase, but there's another factor. People. There continue to be more people on the Internet, whether with cable modems, xDSL, or dial-ups. As this continues to be a bigger part of our culture, more people each pulling down more bytes all the time creates problems faster than we can run fiber and install new routers.
Compression will be essential, since it will be one of the only things helping the backbone keep from choking. People can either download a 40-50MB version of 'Debbie does Dallas 2000" or a 300MB version (assuming, of course, that people would actually use the web for porn)... that saves a lot of bandwith. The other side of that is that people then download 5-10x the amount of content... either way, compression needs to be an intergral part of the Internet in the future.
The article mentions that the wavelet concept started in motion back in the early 80's. Reasons that you haven't seen wavelets in action that much might include:
[] No standard, just a few people playing with things, so they never introduced a product. [] More obscure than 'typical' compression, more effort and background is required to implement it. [] Cowboy Neal (not really, this was just starting to look like a poll)
Nah - everyone will have a cluster... all those home networks with net appliances...
"My kitchen cluster is comprised of 7 dual-processor GHz 21464 Alpha devices: my toaster, microwave, icemaker, blender, coffee maker, dishwasher, and Mr. Popeil GigaRotisserie! And that's not counting the 16-way NUMA fridge!!!"
Your site is pretty amusing, if I do say so, as is your post. Quite a nice bit'o'trollin'.
If your page is an accurate representation of your views, I respectfully disagree. I, myself am a Christian and have many moral and ethical concerns with various goings-on in the world, I find yours rather extreme, and I would encourage you to read through the scriptures, and evaluate your interpretation.
Last time I looked, race didn't have a lot to do with who was using napster... at my former college (just down one stretch of hall): Indians, Native Americans, Japanese, African Americans, Hispanics, Saudis, Jews, and 'White people' were all using Napster...
The hell with justifying it... at this point, everyone who tries to is dismissed as "oh, you're just trying to get free (gratis) stuff", even if they have some sort of 'stuff should be free (libre)' argument (though many who make that argument *are* just trying to get free stuff).
A lot of large stores here in the US let you sample music, but usually only a select few (the top 40 or whatever for each category). Little listening booths. Some smaller shops with more of a clue let you listen to almost anything...
Yeah - here (and back at school) we ran with a fairly sizable AFS cache (~30-200MB in RAM, depending on the machine).
>So, at a particular local machine you can see some files that other machines in the cell see, but not others
I've run into that in my AFS admin days, too... nothing is really perfect, but as a rule, it seemed to work better than most. Plus, it's a pretty nice solution across AIX/SysV/Sol/Linux. DFS is nice, too (and has better NT support), but some strange things tend to happen with the local cache and tickets (more often than AFS, it seems).
The ACL/mode bit deal does get confusing now and then... such are the problems with certain filesystems. Personally, I much prefer the ACL control - it's far more flexible and, in most cases, more useful. Usually, if most of your stuff is on AFS, the users never have to play with the local drive and the different security model.
I'll have to look more into the details of Sprite, since I'm still not exactly sure where all of these files are kept... if the files are distributed across the different workstations, and one goes down... that would be a bad thing. Backups would suck up tons of network bandwith (nobody there in the middle of the night anyway, but hey)... I probably need to do some more reading on it, but it doesn't seem like that great a solution right off the top...
Reading his comments about AFS vs. Sprite I... well... still prefer AFS. I looked into Sprite a while back, and I either didn't "get it" (a favorite Katz phrase), or we're talking about two totally different things...
>AFS and other file systems to share name spaces, but the end result is that all these machines still have their own disks and their own name spaces built above them. Resources are scattered all over the network
and...
>Sprite provided a single system image across a cluster of machines, including a single file system image; so, although there may be many computers and thus many disks in the network, there is one file system shared by all of them.
This is where AFS seems to have a nice advantage over Sprite for some instances, but Sprite would work well in others... Sprite seems to assume a lot of things, and moves itself into more of a niche, rather than a nice broad-purpose file system. Anybody feel any different on this one or want to point out what I don't see?
We have a GE microwave oven that has possibly the worst UI design of any one ever built... normal touch-sensitive buttons, but the biggest two buttons (and colored differently from the numbers) on the bottom of the pad are: "clock" and "timer"(the non-cooking countdown timer)... "start" and "stop/cancel" are hidden to the side, and even smaller than a number button. Very, very strange.
Raid5 performance with a decent controller (non-software RAID) is a very good performer. You won't get quite as much write advantage as RAID 0, but it's better for writing than RAID 1. Reading back is very fast, especially with a decent number of arms.
If you are planning on running a 30GB+ database, I'd hope you could shell out a few bucks for a halfway decent RAID controller... Even the ones with only a small cache perform admirably.
Slashdot Mirror
Well, if we had black, dark black, black metallic, and mirror black, I'm sure everyone could be happy :-0
--
>Besides, how else am I to get my official redhat sticker?
Go to an expo, or get one from your local LUG.
8^)
--
Note that PGP plugs into several Windows mail clients, including Eudora Pro. This can cover several of these concerns.
--
gotcha:
[] Need specialized hardware...
--
I've got a smaller 3D video compression algorithm - just promise not to tell anybody else, since I'm planning on patenting it - it runs from a shell, too!:
/dev/null
#!/bin/sh
cat $1 >
elegant, isn't it? The algorithm is small, and the compressed data is so tiny, even your OS can't find it!
--
Ah yes, I knew I was missing an important one :)
--
is often lost in the text world...
--
Yes, speed will increase, and bandwith will also increase, but there's another factor. People. There continue to be more people on the Internet, whether with cable modems, xDSL, or dial-ups. As this continues to be a bigger part of our culture, more people each pulling down more bytes all the time creates problems faster than we can run fiber and install new routers.
Compression will be essential, since it will be one of the only things helping the backbone keep from choking. People can either download a 40-50MB version of 'Debbie does Dallas 2000" or a 300MB version (assuming, of course, that people would actually use the web for porn)... that saves a lot of bandwith. The other side of that is that people then download 5-10x the amount of content... either way, compression needs to be an intergral part of the Internet in the future.
--
Yup, I love it when the guy wiggles the camcorder, too... or somebody coughs.
--
The article mentions that the wavelet concept started in motion back in the early 80's. Reasons that you haven't seen wavelets in action that much might include:
[] No standard, just a few people playing with things, so they never introduced a product.
[] More obscure than 'typical' compression, more effort and background is required to implement it.
[] Cowboy Neal (not really, this was just starting to look like a poll)
--
Nah - everyone will have a cluster... all those home networks with net appliances...
"My kitchen cluster is comprised of 7 dual-processor GHz 21464 Alpha devices: my toaster, microwave, icemaker, blender, coffee maker, dishwasher, and Mr. Popeil GigaRotisserie! And that's not counting the 16-way NUMA fridge!!!"
Gotta love those $500 electric bills...
--
"You'll also be able to see how it will look after you knock out a wall, reapaint the rooms, and drop in new furniture from a 3-D catalogue"
...but will it allow wireframe/noclip mode, so I can track the plumbing, electrical, and network connections through the walls?
--
He was the hijacker, not the hijackee... at least, he wasn't the first...
--
Your site is pretty amusing, if I do say so, as is your post. Quite a nice bit'o'trollin'.
If your page is an accurate representation of your views, I respectfully disagree. I, myself am a Christian and have many moral and ethical concerns with various goings-on in the world, I find yours rather extreme, and I would encourage you to read through the scriptures, and evaluate your interpretation.
--
>Napster is the White man's form of looting.
Last time I looked, race didn't have a lot to do with who was using napster... at my former college (just down one stretch of hall): Indians, Native Americans, Japanese, African Americans, Hispanics, Saudis, Jews, and 'White people' were all using Napster...
The hell with justifying it... at this point, everyone who tries to is dismissed as "oh, you're just trying to get free (gratis) stuff", even if they have some sort of 'stuff should be free (libre)' argument (though many who make that argument *are* just trying to get free stuff).
"Bah!" - Dogbert
--
A lot of large stores here in the US let you sample music, but usually only a select few (the top 40 or whatever for each category). Little listening booths. Some smaller shops with more of a clue let you listen to almost anything...
--
Yeah - here (and back at school) we ran with a fairly sizable AFS cache (~30-200MB in RAM, depending on the machine).
>So, at a particular local machine you can see some files that other machines in the cell see, but not others
I've run into that in my AFS admin days, too... nothing is really perfect, but as a rule, it seemed to work better than most. Plus, it's a pretty nice solution across AIX/SysV/Sol/Linux. DFS is nice, too (and has better NT support), but some strange things tend to happen with the local cache and tickets (more often than AFS, it seems).
The ACL/mode bit deal does get confusing now and then... such are the problems with certain filesystems. Personally, I much prefer the ACL control - it's far more flexible and, in most cases, more useful. Usually, if most of your stuff is on AFS, the users never have to play with the local drive and the different security model.
I'll have to look more into the details of Sprite, since I'm still not exactly sure where all of these files are kept... if the files are distributed across the different workstations, and one goes down... that would be a bad thing. Backups would suck up tons of network bandwith (nobody there in the middle of the night anyway, but hey)... I probably need to do some more reading on it, but it doesn't seem like that great a solution right off the top...
Ah... well, then - if the viynl says so ;-)
I'm 22, and the albums are mine... what does that say?
Some need practice
Others have great Haiku style
Trying to sound smart
Um... I've installed Linux over a network since 1995... a simple boot/rootdisk combo, then you're off to the FTP/NFS install. Easy.
FYI: Burning an install CD (~$.50-.80) is a rather nice way to have a lot of the extra packages on hand, too...
wasn't it coo-coo cu-choo (or koo-koo ku-choo)? Certainly no 'b' on the end (rifiling though CDs to find it...) [damn, no lyrics printed]...
Reading his comments about AFS vs. Sprite I... well... still prefer AFS. I looked into Sprite a while back, and I either didn't "get it" (a favorite Katz phrase), or we're talking about two totally different things...
>AFS and other file systems to share name spaces, but the end result is that all these machines still have their own disks and their own name spaces built above them. Resources are scattered all over the network
and...
>Sprite provided a single system image across a cluster of machines, including a single file system image; so, although there may be many computers and thus many disks in the network, there is one file system shared by all of them.
This is where AFS seems to have a nice advantage over Sprite for some instances, but Sprite would work well in others... Sprite seems to assume a lot of things, and moves itself into more of a niche, rather than a nice broad-purpose file system. Anybody feel any different on this one or want to point out what I don't see?
We have a GE microwave oven that has possibly the worst UI design of any one ever built... normal touch-sensitive buttons, but the biggest two buttons (and colored differently from the numbers) on the bottom of the pad are: "clock" and "timer"(the non-cooking countdown timer)... "start" and "stop/cancel" are hidden to the side, and even smaller than a number button. Very, very strange.
GE toasters are pretty cool.... I mean, hot...
Heck, even a 'low-end' F80 (1-6 500MHz copper Power-III CPUs with up to 16GB of RAM) would be able to take on PC hardware...
Raid5 performance with a decent controller (non-software RAID) is a very good performer. You won't get quite as much write advantage as RAID 0, but it's better for writing than RAID 1. Reading back is very fast, especially with a decent number of arms.
If you are planning on running a 30GB+ database, I'd hope you could shell out a few bucks for a halfway decent RAID controller... Even the ones with only a small cache perform admirably.