[12:36] <DaveMorris> superm1 for the docs, I've made it so you can stick the png/jpg file into the image dir, and it then auto gets generated into an eps file
[12:36] <superm1> cool
[12:36] <superm1> that will make it easy to update
[12:37] <DaveMorris> was a nice bit of scripting, http://www.pastebin.ca/625376 if you fancy looking
[12:37] <DaveMorris> yeah thats what I though
[12:37] <superm1> the amount of content is growing too i saw :)  Grabbed a lot from the mythtv.org
[12:37] <DaveMorris> yeah, also have a ref section
[12:37] <superm1> so make sure that you quote them in referenced
[12:37] <superm1> okay good
[12:37] <DaveMorris> when are we releasing version 1?
[12:38] <superm1> October or Novemnber
[12:38] <DaveMorris> and are we gonna feature freeze when gutsy does.
[12:38] <superm1> i'd like to have the docs ready at the same time as release
[12:38] <superm1> of 7.10
[12:38] <superm1> mythbuntu
[12:39] <DaveMorris> yeah, howeved you'll have to freeze the feature changes so we can get them done, proof read etc
[12:39] <superm1> right
[12:39] <superm1> i'd like to feature freeze in August
[12:39] <DaveMorris> I've not been proof reading yet, as it keeps on changing
[12:39] <DaveMorris> end of August?
[12:39] <superm1> well August/September
[12:39] <superm1> yea either end of Aug or begin of Sept
[12:39] <superm1> wow that's quite some magic in that script
[12:40] <DaveMorris> well it's gpl'ed in the bzr tree so feel free to use it etc
[12:41] <DaveMorris> http://greenacre.no-ip.com/dave/stuff/morris-fullcircle-graphic-cluster07.pdf is the arcticle I'm writing for the fullcircle magazine atm
[12:43] <superm1> graphic rendering clusters
[12:43] <superm1> wow
[12:44] <superm1> 12800x3600.  that's amazing
[12:44] <DaveMorris> yeah, I max out the network, I want around $40k for a 10 gigbit network, but we have no money left :(
[12:45] <DaveMorris> so I'm stuck with 1gigbit
[12:45] <superm1> ha.  stuck at 1gigabit
[12:45] <superm1> that's the first time i've heard someone say that
[12:45] <DaveMorris> also the company sold us the machines saying they had dual gigabit nics
[12:45] <DaveMorris> bullshit, 1 is 100mbit
[12:46] <DaveMorris> took me a while to work out why it was slow with the nic's bonded than on there own
[12:46] <superm1> did you end up getting them to replace it?
[12:47] <DaveMorris> no, the pointed to the small print saying product may vary sligjtly from the description
[12:48] <superm1> that's bogus
[12:48] <DaveMorris> you notice the pictures in that article shows XP running
[12:48] <DaveMorris> I wasn't ovely fused, its not my money
[12:49] <superm1> why?
[12:49] <DaveMorris> why XP?
[12:49] <superm1> yea
[12:50] <DaveMorris> it was hooked up via hardware cables, so was at crap res, but the pic was for something else.  I've just used it as a spacer for where the actual pic will go.  Since its the same hardware
[12:50] <superm1> oh i see
[12:51] <DaveMorris> well I best goto bed if I wanna get to work on time.
[12:52] <superm1> alrihgt
[12:52] <superm1> night DaveMorris
[10:12] <kap> anyone here?
[11:00] <DaveMorris> why am I getting mythtv releated bugs on the mythbuntu mailing list?
[04:02] <tgm4883> Not sure DaveMorris, but i'm getting them too (and questions).
[04:03] <DaveMorris> but I already get them via been part of the mythtv group, I dont need them twice
[04:10] <tgm4883> agreed, not needed twice
[04:17] <tgm4883> hmm, perhaps because the mailing list is for ubuntu-mythtv, not mythbuntu.  I thought the list wasn't going to get this stuff as it was going to be low volume?
[04:19] <keescook> superm1: the udev maintainer is at GUADEC this week, so it's likely I won't hear back on the udev patch for v4l until next week.  :P  How did your experimentation turn out?
[04:37] <felix_> join #mythtv-users
[04:39] <superm1> keescook, I ran into issues getting the other thing I wanted to test to work up until 2am last night, and consequently didn't get a cd built to test with the patches.  it will have to wait till tonight.
[04:40] <superm1> DaveMorris, tgm4883 the contact addresses for the ubuntu-mythtv and mythbuntu group are set to the mailing list, any one can then respond to bugs/questions via email.  There shouldn't be any doubles sent out afaik though.  Should things be switched around?\
[04:41] <tgm4883> not sure, i think DaveMorris is getting it twice because he is in mythtv group and mythbuntu group
[04:41] <superm1> so am i
[04:41] <tgm4883> i only get it once
[04:41] <superm1> and i only get things once
[04:41] <tgm4883> hmm
[04:42] <tgm4883> something on his end i suppose.  Is he registered with 2 emails and one forwards?
[04:42] <laga> maybe he's on CC for some mails
[04:42] <superm1> some of the mails were threaded
[04:42] <superm1> so perhaps they looked like multiples
[04:43] <DaveMorris> my address on the mythbuntu list is different
[04:43] <superm1> oh
[04:43] <DaveMorris> no I have filters set up, and I've got them in ubuntu folder (launchpad sent) and in my mythbuntu folder, sent on the mythbuntu list
[04:45] <superm1> well perhaps i'll blow away the mailing list contact addy for 'mythbuntu'
[05:00] <superm1> keescook, speaking of the troubles i ran into with the other testing, could you sponsor the new resultant versions i made last night: http://revu.tauware.de/details.py?upid=6101 (mythbuntu-default-settings) and http://revu.tauware.de/details.py?upid=6102 (mythbuntu-live-autostart)
[05:06] <keescook> superm1: mythbuntu-default-settings uploaded.  I can't find mythbuntu-live-autostart in the archive, though?
[05:12] <superm1> keescook, i wonder if the first version didn't clear binary new yet.  let me double check
[05:13] <superm1> woah.  what happened to LP overnight.  the fonts are huge...
[05:13] <superm1> yea its sitting in the queue still, if you upload the new version will it just override the old one? https://launchpad.net/ubuntu/gutsy/+queue?start=40
[05:14] <keescook> not sure...
[05:50] <superm1> keescook, as said in #ubuntu-devel, its safe to have both versions in the queue.
[06:00] <keescook> superm1: okay, cool.
[06:09] <keescook> superm1: -live-autostart uploaded.  :)
[06:10] <superm1> great thx
[06:13] <keescook> also, base-files uploaded too (now that freeze is over)
[06:14] <superm1> ah good.  so these "freezes" are more artificially created than the archive locking things out or putting them in queue then
[06:27] <superm1> mkrufky, i wanted to ask you a bit more about your desired CF configuration.  Could you see if the CF reader is automatically mounted in /media?
[06:27] <superm1> via gnome-volume-manager
[06:29] <mkrufky> hey
[06:29] <mkrufky> in my method, the CF is not hot-unpluggable
[06:29] <mkrufky> it works like any IDE hard drive
[06:29] <mkrufky> the computer does not know any difference
[06:30] <mkrufky> i think if you try to remove the CF disk, BAD BAD BAD things will happen
[06:30] <mkrufky> i have this very nice CF-to-IDE  adapter, so i mount the CF inside the case, and you do not have access to fiddle with it without opening up the machine
[06:30] <mkrufky> i can show you a pic of this adapter, if you're interested
[06:31] <mkrufky> .... only thing to keep in mind ....  you must set the linux configuration to treat the CF as a cdrom ....  do not attempt to write to it -- it should be read-only
[06:31] <mkrufky> otherwise, cf disks can only handle a limited amount or writes.... eventually it would die
[06:33] <mkrufky> [silence falls upon the crowd] 
[06:36] <Tari> any Flash media has a limited life span
[06:36] <Tari> it's governed by the number of times it can be erased
[06:37] <mkrufky> exactly.... thats why i just build the system like a livecd and then "burn" it to CF ... or a usb flash drive
[06:37] <mkrufky> http://techsounds.org/linux/cf/
[06:37] <mkrufky> (i wrote this a few years ago)
[06:42] <mkrufky> superm1: did i answer your question sufficiently?
[06:51] <tgm4883> mkrufky, i suppose your method would also work with a microdrive?
[06:53] <mkrufky> tgm4883: yes.... with a microdrive, then you do not have the limited write limitation
[06:53] <mkrufky> either microdrive or CF would both show as any standard IDE disk
[06:54] <mkrufky> using something like this:
[06:54] <mkrufky> http://pics2.spoonfeeder.com/AieFTPFiles/AIEUser/3JZ6TKVVPM6B/VXELSUZ3EZQK.JPG
[06:55] <mkrufky> the one i use is a bit different -- it allows two cf dists per adapter
[06:55] <mkrufky> s/dists/disks
[06:56] <tgm4883> that would be really nice is a epia
[06:56] <tgm4883> in one i mean
[06:58] <mkrufky> yes... actually... i'd love to build a mini-itx box that can do mythfrontend stuff w/ HD output
[06:59] <mkrufky> i'd really like to get this big clunker out of my living room -- taking up all that space
[06:59] <mkrufky> donate it to charity or something,. lol
[07:04] <tgm4883> yea, i almost built one, but the HD on it wasn't definite.  All I heard about it was that it "Should" be able to do HD
[07:07] <mkrufky> i havent really done the research yet....  ive read about a mini-itx board with built in HDMI outs .... that sounds nice
[07:13] <tgm4883> oh sorry, yea i built a mini itx system.  I was actually looking at building something a little smaller, but the HD wasn't definite.  I was looking at either nano itx or pico itx  http://www.via.com.tw/en/products/mainboards/
[07:14] <tgm4883> the problem is the processor, as it's built in and only goes up to a certain speed since its passively cooled
[07:14] <tgm4883> couple that with a microdrive, and you have 1 small quiet system
[07:15] <mkrufky> a flash drive would be faster....
[07:15] <mkrufky> (but read only, i guess)
[07:16] <tgm4883> true
[07:16] <tgm4883> once setup though, would you need to write?
[07:17] <tgm4883> actually the nano-itx board they have looks pretty good now, more info
[07:17] <tgm4883> wonder how linux compatible it is though
[07:17] <mkrufky> a perfect setup should never really need to write
[07:17] <mkrufky> well... ideally
[07:18] <mkrufky> what i would do .....  is keep the build for the system on a different hard drive somewhere, and maintain two cf disks
[07:18] <mkrufky> one for production ... always works
[07:18] <mkrufky> the other for upgrading
[07:18] <mkrufky> this way, you can upgrade the system without jeopardizing the stable system -- can always go back to it in the event of a regression
[07:18] <mkrufky> (also makes the dual cf-adapter that much more handy)
[07:45] <superm1> mkrufky, sorry i was out for lunch
[07:45] <superm1> i understand a lot better now
[07:45] <mkrufky> superm1: no prob
[07:46] <superm1> that method could be adapted to use the live disk (alpha 3 +) with mythbuntu-live-autostart
[07:47] <mkrufky> probably ... im not very familiar with mythbuntu-live yet....  but i intend to play with it soon
[07:47] <superm1> well you won't see this until the next alpha (next week or two)
[07:47] <superm1> i just finished the coding for it and such yesterday
[07:50] <mkrufky> ok
[07:51] <mkrufky> so then i wont try mythbuntu yet :-)
[07:51] <mkrufky> as it is ... my feisty mythfrontend works fine with my fc5 mythbackend server .... so i think its safe to assume that a mythbuntu frontend would work fine as well
[07:51] <superm1> now if something is mounted rw, but is only read from - does that still count against the requirement on mounts?
[07:51] <mkrufky> its a bad idea to do that
[07:51] <superm1> yes - up until final release at least
[07:52] <mkrufky> journaling stuff will still write stuff
[07:52] <mkrufky> you'd have to use vfat or ext2, i guess
[07:52] <mkrufky> better off to mount read only as read only
[07:52] <superm1> well what you will likely do then is two partitions
[07:52] <mkrufky> otherwise you risk shortening the life of the media
[07:52] <superm1> one that keeps the "cd image"
[07:52] <mkrufky> and the other for settings
[07:52] <superm1> and one for configuration file and ~/.mythtv
[07:53] <mkrufky> in *my* case, i would keep the system on cf, and use a usb key for settings
[07:53] <superm1> as long as the second is mounted in /media
[07:53] <superm1> that's all that matters
[07:53] <superm1> yea a usb key is cheap enough
[07:55] <mkrufky> yes
[07:55] <mkrufky> plus, you wouldnt need more that a few MB for the configuration
[07:55] <mkrufky> you can probably pick upa 4mb usb dohickey for a few cents, lol
[07:56] <superm1> well configuration is < 1k, the ~.mythtv directory is around 9-50 megs depending on the theme you choose
[08:00] <mkrufky> hmm... why store the themes there and not a symlink?
[08:00] <superm1> well its cached content
[08:00] <superm1> scaled
[08:00] <superm1> to your resolution
[08:00] <superm1> that you use
[08:01] <mkrufky> :-/
[08:01] <mkrufky> personally, i think i'd prefer to let it render every boot, and store it in a ramdisk
[08:06] <superm1> well there is an option for that
[08:06] <superm1> that i added
[08:06] <superm1> because i had a feeling not everyone would want to do it this way
[08:08] <mkrufky> ok, good :-)
[08:09] <superm1> actually if you really want, you can just inject the configuration into /media/SOMETHING in the cd image if you want then
[08:09] <superm1> and do it all read only
[08:10] <mkrufky> yes... but that would mean that if you re-do your backend config and / or network / db stuff, that you'd have to re-spin a new frontend system
[08:11] <superm1> well reinject the configuration file
[08:11] <superm1> at least
[08:11] <mkrufky> true
[08:11] <mkrufky> that would also work
[08:12] <superm1> i dont think i said above, but mythbuntu first release is going to be 0.21 based
[08:12] <superm1> so if 0.21 is pushed back we will be too
[08:12] <superm1> but laga is tracking trunk and has packaging to support it
[08:13] <mkrufky> very cool
[08:16] <superm1> laga, you missing a prerm?
[08:17] <superm1> laga, that appears to be your trouble
[08:19] <superm1> grab the mythweb.prerm from the -fixes branch