[01:10] <Takyoji> It's pathetic how it takes up like over 80% of my CPU when using Pandora (music streaming service) on my laptop.
[01:10] <Takyoji> of which is just AUDIO
[01:10] <Takyoji> But contained in Flash
[01:11] <Takyoji> there's also no DRM/cryptology of the service either, yet still takes as much CPU power
[02:01] <Alpha_Cluster> cause flash is like the greatest thing ever
[02:01] <Alpha_Cluster> you know great things must use lots of CPU power
[02:04] <Takyoji> Of course, it shows how great they are, after all.
[02:05] <Alpha_Cluster> yep
[02:06] <Alpha_Cluster> only great programmers can use up that much cpu while doing so little
[02:08] <Alpha_Cluster> ok anyone have a problem where evolution refuses to ask for a password for a new account?
[02:14] <Alpha_Cluster> god evolution is still such a piece of shit
[11:28] <kermit> why does flash eat so much CPU anyway?
[18:22] <Obsidian1723> Here's a bash script I made which will download and install programs, setup iptables (for a desktop PC, not a server) and provide a good first step after doing a new Ubuntu 10.04LTS desktop installation. wget -c -t0 http://dl.dropbox.com/u/914191/install-script.sh and then sudo chmod +x install-script and then do sudo ./install-script.sh and it just runs. This is a solid script that is ever-evolving.
[20:06] <rlaager> Obsidian1723: You should make this into one or more packages and put them in a PPA.
[20:07] <rlaager> Obsidian1723: Why do you run apt-get install a million separate times? For the firewall stuff, using ufw would probably be better.
[20:13] <Obsidian1723> How would I do this in a PPA?
[20:13] <Obsidian1723> I ve never packaged
[20:13] <Obsidian1723> Well, iptables is more configurable
[20:15] <rlaager> Obsidian1723: I manage all of our configs (desktop and server) via packages. For something like this, you might make a package named obsidian-desktop. It'd be a "native" package, which means it has no upstream tarball.
[20:16] <Obsidian1723> gotcha... how would I make this into a package though?
[20:16] <rlaager> Basically, any time you're creating a file, you'd create that as part of the package build process. Any time you're running a command, you'd put that in the package's postinst script.
[20:16] <rlaager> And when you're install a package, you'd instead make that a dependency of your package (in debian/control).
[20:17] <rlaager> Obsidian1723: I have to run to a client's place, but perhaps I can find a good example to share with you so you don't have to start from scratch.
[20:17] <Obsidian1723> that'd b ed appreciated
[20:17] <rlaager> Packages are nice in that, properly done, they can cover both initial installs and upgrades.
[20:17] <Obsidian1723> sweet
[23:41] <tonyyarusso> Yeah, I've been meaning to put together some packages to control network-wide common configurations too.
[23:42] <tonyyarusso> Meanwhile, my new Das Keyboard Model S properly fixes my KVM switch problem :)