[12:25] <superm1_> keescook, thats a shame about qt not needing a recompile for a easy fix :(
[06:27] <superm1> majoridiot, did you encounter your troubles still with regard to the first time starting mythtv-setpu?
[06:27] <majoridiot> yes
[06:27] <majoridiot> emailed
[06:27] <superm1> tis craziness then
[06:28] <superm1> i really dunno what could be causing troubles
[06:28] <superm1> let alone why its fine after the first connection
[06:28] <majoridiot> dunno either
[06:28] <majoridiot> but it replicates every time
[06:28] <superm1> wonder if its your x server
[06:28] <superm1> locally
[06:29] <superm1> something about it
[06:29] <majoridiot> dunno what it would be.
[06:30] <superm1> perhaps this -
[06:30] <superm1> what if you try to run another x app first
[06:30] <superm1> say if you try to run xterm
[06:30] <majoridiot> sec
[06:30] <majoridiot> there is an x update available
[06:30] <superm1> see if it crashes during that process, and then zenity (and hence mythtv-setup are okay)
[06:30] <superm1> k
[06:30] <majoridiot> lemme update and try another quick install
[06:31] <superm1> k
[06:43] <superm1> majoridiot, i'm scaling these all to 550x350
[06:43] <superm1> is that adequate?
[06:44] <majoridiot> sure
[06:44] <majoridiot> tyvm
[06:44] <superm1> dont worry about it.  'tis been on the todo for ages
[06:45] <majoridiot> well... i think i have all of the major things covered in the feisty guides
[06:45] <superm1> vg.  so troubleshooting is its own section now?
[06:45] <majoridiot> i'll mess around with the plugins page for a day or two to try and get a fresh set of eyes... and then look them over again.
[06:46] <majoridiot> yes.
[06:46] <superm1> great :)
[06:46] <superm1> i'll have these done and ready to go in about 10-15 min
[06:46] <superm1> i'm half way through cropping and scaling
[06:46] <majoridiot> and all of the prompts are correct for all setups
[06:47] <majoridiot> ok... how do you want me to do this install?
[06:47] <superm1> just as normal server install
[06:47] <superm1> well normal command line system
[06:47] <superm1> install moreover
[06:47] <majoridiot> yes
[06:48] <majoridiot> updated and upgraded
[06:48] <majoridiot> ssh and xauth installed
[06:48] <superm1> and right after you are at the point to run mythtv-steup
[06:48] <superm1> run something else
[06:48] <superm1> like xeyes
[06:48] <superm1> or anything you can think of thats installed and uses x
[06:48] <superm1> to see if it crashes
[06:48] <majoridiot> so go ahead and install mythtv-backend master and then run some other xapp from a remote term?
[06:49] <superm1> exactly
[06:49] <majoridiot> k
[06:50] <superm1> i'm hand modifying these screenshots to make my drives appear bigger too
[06:50] <superm1> since someone complained at some point
[06:50] <superm1> that the text didnt match the screenshots
[06:50] <superm1> and they got confused
[06:50] <majoridiot> yeah
[06:50] <majoridiot> wah wah.  really.
[06:50] <superm1> haha
[06:50] <superm1> well it got to me
[06:50] <superm1> so
[06:50] <superm1> you know
[06:50] <majoridiot> i'm not partial to the aspect ratio of the VM on your laptop, myself.
[06:50] <majoridiot> :P
[06:55] <majoridiot> xeyes np.
[06:55] <superm1> can you do zenity on its own
[06:55] <majoridiot> mythtv-setup?
[06:55] <superm1> no problem
[06:55] <superm1> like
[06:55] <superm1> zenity  --question --title "Alert"   --text  "Microsoft  Windows
[06:55] <superm1>               has been found! Would you like to remove it?"
[06:56] <superm1> (from the man page)
[06:56] <majoridiot> nope
[06:57] <superm1> it crashed on that?
[06:57] <majoridiot> The program 'zenity' received an X Window System error.
[06:57] <majoridiot> This probably reflects a bug in the program.
[06:57] <majoridiot> The error was 'BadAccess (attempt to access private resource denied)'.
[06:57] <majoridiot>   (Details: serial 165 error_code 10 request_code 147 minor_code 5)
[06:57] <majoridiot>   (Note to programmers: normally, X errors are reported asynchronously;
[06:57] <majoridiot>    that is, you will receive the error a while after causing it.
[06:57] <majoridiot>    To debug your program, run it with the --sync command line
[06:57] <majoridiot>    option to change this behavior. You can then get a meaningful
[06:57] <majoridiot>    backtrace from your debugger if you break on the gdk_x_error() function.
[06:57] <superm1> try again and see if it still crashes?
[06:57] <majoridiot> exact same error as the first myth try
[06:57] <majoridiot> k
[06:57] <majoridiot> second one works
[06:57] <majoridiot> zenity
[06:57] <superm1> okay log out of ssh
[06:57] <superm1> and back in
[06:57] <superm1> and try it again
[06:58] <superm1> see if it does it again
[06:58] <majoridiot> nope
[06:58] <majoridiot> worked the first time
[06:58] <superm1> wow this is so freaking bizarre
[06:59] <majoridiot> is the diff that i'm truly in a remote ssh session and your VM session isn't?
[06:59] <superm1> well mine still was a remote session
[06:59] <superm1> i mean i still ssh'ed and all
[06:59] <majoridiot> hm
[06:59] <superm1> can you reboot the machine
[06:59] <superm1> and see if it still does it
[06:59] <majoridiot> backend?
[06:59] <superm1> (from the zenity command)
[06:59] <superm1> the backend install aye
[06:59] <majoridiot> sec
[07:01] <majoridiot> yes
[07:01] <majoridiot> zenity errors first connect after reboot
[07:02] <majoridiot> fine on second try
[07:02] <superm1> hm
[07:02] <superm1> perhaps ask in #gnome if they'd have any ideas
[07:02] <superm1> as to why zenity would be crashing
[07:02] <superm1> on the first time for you on an x forwarded connection
[07:02] <superm1> oh wait
[07:03] <superm1> i have an idea
[07:03] <superm1> completely overlooked its prospect
[07:03] <superm1> reboot once more
[07:03] <superm1> and this time use "-Y -X"
[07:03] <majoridiot> do this... do that...
[07:03] <majoridiot> geez/
[07:03] <superm1> haha
[07:03] <superm1> well if i could reproduce your troubles :)
[07:03] <superm1> we have to use that at school so cadence doesn't give us errors JUST like that
[07:04] <superm1> i dont know why i didnt think of that first
[07:04] <majoridiot> same
[07:05] <majoridiot> identical.
[07:05] <superm1> man you serious?
[07:05] <majoridiot> i wouldn't kid about this.
[07:05] <superm1> okay i'm going to #gnome
[07:05] <majoridiot> bil@incinerator:~$ ssh bil@192.168.1.102 -X -Y -p 22
[07:05] <majoridiot> bil@192.168.1.102's password:
[07:05] <majoridiot> Linux ubuntu 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686
[07:05] <majoridiot> The programs included with the Ubuntu system are free software;
[07:05] <majoridiot> the exact distribution terms for each program are described in the
[07:05] <majoridiot> individual files in /usr/share/doc/*/copyright.
[07:05] <majoridiot> Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
[07:05] <superm1> and asking about htis
[07:05] <majoridiot> applicable law.
[07:05] <majoridiot> Last login: Thu Apr  5 00:01:15 2007 from 192.168.1.103
[07:05] <majoridiot> bil@ubuntu:~$ zenity  --question --title "Alert"   --text  "Microsoft  Windows"
[07:05] <majoridiot> The program 'zenity' received an X Window System error.
[07:06] <majoridiot> This probably reflects a bug in the program.
[07:06] <majoridiot> The error was 'BadAccess (attempt to access private resource denied)'.
[07:06] <majoridiot>   (Details: serial 165 error_code 10 request_code 147 minor_code 5)
[07:06] <majoridiot>   (Note to programmers: normally, X errors are reported asynchronously;
[07:06] <majoridiot>    that is, you will receive the error a while after causing it.
[07:06] <majoridiot>    To debug your program, run it with the --sync command line
[07:06] <majoridiot>    option to change this behavior. You can then get a meaningful
[07:06] <majoridiot>    backtrace from your debugger if you break on the gdk_x_error() function.)
[07:06] <majoridiot> sec
[07:06] <majoridiot> lemme try something first
[07:07] <majoridiot> hm.  nm.
[07:10] <superm1> can you try with -Y only (no -X)
[07:10] <majoridiot> yes
[07:10] <superm1> (from what those in#gnome said)
[07:11] <majoridiot> err/
[07:11] <superm1> err?
[07:12] <superm1> same thing you mean
[07:12] <majoridiot> exactly
[07:13] <superm1> okay next idea -
[07:13] <superm1> on your local box
[07:13] <superm1> xhost +
[07:13] <superm1> before the ssh session
[07:14] <majoridiot> both boxes are local.  hehe.
[07:14] <majoridiot> let local=backend?
[07:14] <majoridiot> LOL
[07:14] <superm1> well local as in the one you are sshing "from"
[07:15] <majoridiot> k
[07:15] <majoridiot> -
[07:15] <superm1> your command for the ssh with -Y was just "ssh bil@192.168.1.102 -Y"
[07:15] <superm1> right?
[07:15] <majoridiot> -X -Y or -X or -Y?
[07:15] <majoridiot> with a port
[07:15] <majoridiot> -p 22
[07:15] <superm1> okay so you have tried all 3 combos then
[07:16] <superm1> and got the same access to private resource denied
[07:16] <superm1> for all 3
[07:16] <majoridiot> yes
[07:16] <majoridiot> now do the same after xhost + ?
[07:16] <superm1> well what "xhost +" does
[07:16] <superm1> it opens up permissions
[07:16] <superm1> for any connection from anywhere
[07:16] <superm1> just make sure xhost + is done before you ssh in
[07:17] <majoridiot> xhost + made no diff with -X
[07:18] <superm1> nor the -Y
[07:18] <majoridiot> nor -Y
[07:18] <majoridiot> rebooting to try -X -Y
[07:18] <superm1> k
[07:19] <superm1> you've got what kind of graphics card in that local machine (that you are sshing from)
[07:20] <majoridiot> no change
[07:20] <majoridiot> 2xnvidia
[07:20] <majoridiot> 7650gtko-sli X 2
[07:20] <majoridiot> 7600\
[07:20] <majoridiot> hehe
[07:20] <superm1> haha
[07:21] <superm1> okay let me try this from my machine with an nvidia
[07:21] <superm1> directly over ssh
[07:21] <majoridiot> you are welcome to ssh into mine (if you can tell me how to set that up)
[07:22] <superm1> i'd say sure, but X *crawls* over the net
[07:22] <majoridiot> you'd never get that far.
[07:23] <superm1> worked fine on my machine with an nvidia
[07:23] <superm1> sshing into a feisty
[07:23] <superm1> that had zenity
[07:23] <majoridiot> from an edgy?
[07:23] <superm1> yes
[07:23] <majoridiot> hm.
[07:23] <superm1> i say do tihs
[07:23] <superm1> add a little blurb
[07:23] <superm1> that if you get an error like that
[07:23] <superm1> ctrl c the connection
[07:23] <superm1> and do it over
[07:23] <majoridiot> (did that last night)
[07:23] <majoridiot> :)
[07:25] <majoridiot> https://help.ubuntu.com/community/MythTV/Install/Live/Feisty+/Config_BE_S
[07:25] <majoridiot> that's the common server page
[07:26] <superm1> k
[07:26] <superm1> just make sure that -X also has the -Y
[07:26] <superm1> for the general case
[07:26] <majoridiot> you don't actually have to close the connection... just run setup immediately again
[07:26] <superm1> right
[07:27] <majoridiot> Y added
[07:27] <superm1> k vg
[07:27] <superm1> okay now back to those screens again :)
[07:27] <majoridiot> k
[07:27] <majoridiot> i'm off to bed.  worn out.
[07:28] <superm1> ah okay
[07:28] <superm1> well you'll you have mail tomororw then
[07:28] <superm1> with all of these
[07:28] <superm1>  :)
[07:28] <majoridiot> vg. ty.
[07:28] <superm1> have a great night
[07:28] <majoridiot> talk tomorrow.  night dude.
[07:28] <majoridiot> you too.
[07:56] <superm1> hey jetsaredim
[09:52] <xzai> anyone here?
[10:37] <superm1> Chadarius, Chad I presume?
[10:37] <Chadarius> Hey yeah
[10:37] <superm1> same chad over email that recently had a child?
[10:37] <Chadarius> Yep!
[10:38] <Chadarius> How's things?
[10:38] <superm1> ah wonderful, glad to you see you stop by
[10:38] <superm1> well - outside of mythtv stuff - stressful as hell.  inside mythtv stuff, on hold for me atm with regard to packaging
[10:39] <Chadarius> work stuff?
[10:39] <superm1> well school stuff
[10:39] <superm1> got final projects and such that all take 28 hours a day
[10:39] <Chadarius> Yeesh yeah I remember school. That's why I'll never go back :)
[10:39] <superm1> haha
[10:40] <superm1> Chadarius, so if you want to help with any last minute bug fixes before feisty release, i think thats the most ideal thing right now
[10:40] <Chadarius> OK I've just got my test box setup and was going to give it a spin this weekend. I noticed a new package for myth that came down on my laptop this week
[10:40] <superm1> this week?
[10:41] <superm1> i think last week
[10:41] <superm1> well whichever...
[10:41] <Chadarius> well it came down this week for me on feisty... I hadn't updated recently
[10:41] <superm1> ah okay
[10:41] <superm1> well if you want to look over the list here: https://bugs.launchpad.net/ubuntu/+source/mythtv/
[10:41] <Chadarius> I just inplace updated my laptop to feisty and I have Myth Frontend on it
[10:41] <superm1> ah okay
[10:42] <Chadarius> I'll take a look
[10:42] <superm1> there are a few in there that should be pretty straightforward things hopefully.
[10:42] <superm1> just where is the time to sit down and make sure that they work correctly for me :)
[10:42] <Chadarius> you want me to focus on feisty bugs only for now?
[10:42] <superm1> well i think for now the very best thing is to get as many of these fixed before april 19th
[10:43] <Chadarius> ok
[10:43] <superm1> because after that we are locked in with the packages, and then its all stable release updates which are more of a pain then i'd like to deal with
[10:43] <superm1> after feisty release, these can be lower priority and focus efforts on mythbuntu related items
[10:44] <superm1> jetsradiem is still hacking away at ubiquity afaik, but i havent touched bases for a few days
[10:45] <superm1> and majoridiot is handling all the docs and cleanup for them.  with the -.0001 minutes a day i have for free time, i'm doing short spurts of proofing on them and getting more screencaps that he can't capture since they need to be done in a VM and such
[10:46] <superm1> majoridiot, speaking of which:
[10:46] <superm1> go ahead and move the ssh stuff for desktop installs to what next
[10:46] <majoridiot> :)
[10:47] <majoridiot> LOL grabbed the list and the only things not crossed off other than "plugins" is a great big "SSH???"
[10:47] <majoridiot> so we DID discuss it already. ;)
[10:47] <superm1> haha
[10:47] <superm1> told you these last few days are a blur for me
[10:48] <superm1> i dont know if events i'm remembering like this i thought or really happened...
[10:48] <majoridiot> all my days are a blur unfortunately.  i would be lost with my notes.
[10:48] <majoridiot> so i'm rowin the boat with ya.
[10:48] <superm1> majoridiot, so the other thing, on the frontend only desktop page - there is a section about setting up additional hardware just prior to installing the frontend itself
[10:48] <superm1> i think that should be pulled on frontend only
[10:49] <superm1> since the only applicable things were proprietary graphics and remotes
[10:49] <superm1> and both can just fit under the what next category (well proprietary graphics is already there)
[10:49] <superm1> most people do the remote last apparently anyhow
[10:49] <majoridiot> ah.
[10:50] <majoridiot> wasn't sure which you were referring to in your email.  will remove immediately.
[10:51] <superm1> majoridiot, did you identify what was causing several of the ToC links on pages to work and others not to?
[10:51] <superm1> hopefully something silly that just needs to be changed on all pages...
[10:51] <majoridiot> unfortunately, no.
[10:52] <majoridiot> but i'm working on it.
[10:52] <superm1> i have a feeling its directly related to nested pages
[10:52] <majoridiot> splitting things up into modules and combining seems to have helped to some degree.
[10:52] <majoridiot> agreed.
[10:52] <superm1> i think the pages that have the ToC in the top level are okay
[10:52] <superm1> but the ones that embed the ToC mess up
[10:53] <majoridiot> hm.
[10:53] <majoridiot> will look at that.
[10:53] <majoridiot> had not considered it.
[10:53] <superm1> well no that isn't it, because the first feisty page has the first two links working
[10:53] <superm1> and the rest dont
[10:53] <superm1> hm
[10:54] <majoridiot> the WEIRDEST is the Top page.  the simples one there is and it's broken.
[10:56] <majoridiot> (HW section removed from frontend onlies.
[10:59] <superm1> lol
[10:59] <superm1> well some of those aren't necessary obv
[10:59] <majoridiot> i'll look...
[10:59] <superm1> but are there for completeness sake
[11:00] <majoridiot> but i did receive a number of compliments on the caps and instructions for the desktop installs, which had many more caps
[11:00] <majoridiot> so i'm glad you did. :)
[11:00] <superm1> see... there ya go :0
[11:00] <majoridiot> yup
[11:00] <superm1> how do you like my odd partition sizes?
[11:00] <majoridiot> (was just bustin yer balls a little.)
[11:01] <superm1> 224.3 GB HD for you?
[11:01] <majoridiot> what was the complaint you got about that?
[11:02] <majoridiot> other than the text not matching, which we knew.
[11:02] <superm1> well the text not matching was the only complaint
[11:02] <superm1> so i made a 10G, 214.3 G and 2G partition
[11:02] <superm1> in these caps
[11:02] <superm1> but mind you my virtual drive was only 4.3
[11:02] <superm1> so you can see the odd numbers that copying and pasting resulted in
[11:03] <majoridiot> LOL
[11:03] <superm1> but they can for sure be used for describing the section better
[11:04] <majoridiot> it should all be fixed in a bit...
[11:04] <majoridiot> taking a look at the caps now.  it'll all be laid out like the desktop pages are.
[11:05] <majoridiot> layed out?
[11:05] <superm1> huh?
[11:05] <majoridiot> laid or layed... layed.
[11:05] <majoridiot> nm.  LOL
[11:05] <superm1> mkay
[11:36] <superm1> majoridiot, sigh... http://ubuntuforums.org/showthread.php?p=2408100#post2408100
[11:36] <superm1> man i can't wait for feisty to start
[11:37] <majoridiot> egads.  this one didn't bother to even look at basic myth info first?
[11:38] <majoridiot> a frontend without a desktop... and it errored?  imagine.
[11:38] <majoridiot> er... without a backend.
[11:39] <superm1> oh yikes i didnt even catch the fact that he forgot a backend
[11:39] <superm1> lol
[11:39] <majoridiot> hehe
[11:39] <gardengnome> "< majoridiot> egads.  this one didn't bother to even look at basic myth info first?"
[11:39] <gardengnome> dude, you need to hang out more in #mythtv-users.
[11:40] <gardengnome> that'll teach you.
[11:40] <gardengnome> :)
[11:40] <majoridiot> where is that chan?  it doesn't show in my list.
[11:40] <superm1> gardengnome, can we just get rid of all the stuff on wiki.mythtv.org
[11:40] <superm1> in regards to howtos
[11:40] <superm1> and point it to the help.ubuntu.com/community ones
[11:40] <gardengnome> superm1: sure, nobody reads them anyways.
[11:40] <gardengnome> ah, you mean the ubuntu ones.
[11:41] <superm1> because seriously they cause so much crap when people try to use them
[11:41] <superm1> they are never complete, updated or easy to follow for new people to this
[11:41] <superm1> or reflect the latest changes in terms of packaging, user management etc
[11:42] <majoridiot> hehe
[11:42] <gardengnome> superm1: the mythtv packages are a moving target. :)
[11:42] <superm1> gardengnome, hence why those pages should go away.  these are following that moving target
[11:42] <superm1> majoridiot, speaking of which, caught a bad side effect on the edgy desktop page seems to have caught a bad side effect of feisty's modularization
[11:43] <superm1> majoridiot, see the two ToCs on the page now?
[11:43] <gardengnome> superm1: i'll do it now.
[11:43] <superm1> gardengnome, wonderful :)
[11:43] <majoridiot> which page?
[11:43] <superm1> majoridiot, edgy FEBEDE
[11:43] <majoridiot> (i have tried to seperate all feisty-specific things from edgy common pages)
[11:43] <superm1> troubleshooting sec
[11:44] <superm1> gardengnome, we're eventually gonna troll through the forums for ubuntu specific issues and add them to our troubleshooting page.  if you want to give that link to the mythtv-users bot, i think it will help save you guys a lot of trouble in #mythtv-users too
[11:44] <superm1> just something that you guys can do like !ubuntu
[11:45] <superm1> that would call up the bot to call our link
[11:45] <superm1> scroll down to where Troubleshooting is first listed
[11:45] <majoridiot> ah... whizzed past that.
[11:45] <gardengnome> superm1: we dont have a factoids bot, unfortunately. there's been talking about it.
[11:45] <majoridiot> np.  will fix asap/.
[11:45] <superm1> gardengnome, oh i thought you did
[11:46] <superm1> gardengnome, well then there is always keeping it somewhere easy to copy and paste :)
[11:46] <superm1> gardengnome, hopefully all of those password issues die down once feisty packages get around
[11:46] <superm1> gardengnome, so your biggest ubuntu gripe goes away
[11:47] <gardengnome> superm1: i'd hug you for that. :)
[11:47] <gardengnome> superm1: no worries, that problem has been around since the debian packages
[11:47] <superm1> gardengnome, you've seen what they do yet or no?
[11:47] <gardengnome> superm1: no.
[11:49] <superm1> gardengnome, https://help.ubuntu.com/community/MythTV/Install/Live/Feisty+/Config_BE_S
[11:49] <superm1> gardengnome, right after the ssh you will see the 3 popups that happen
[11:50] <gardengnome> superm1: nifty.
[11:50] <superm1> gardengnome, both mythfrontend and mythtv-setup are now wrapper scripts that check group membership.  if your not in "mythtv" they offer to add you before starting the frontend
[11:50] <superm1> gardengnome, so permissions should be fine after you log out/in
[11:50] <gardengnome> superm1: will this still break if you say "no" and ~/.mythtv/mysql.txt is created?
[11:51] <superm1> yes
[11:51] <superm1> gardengnome, i really hope people are intelligent enough to read that and hit okay though
[11:51] <gardengnome> heh
[11:51] <gardengnome> seriously. enough people will get it
[11:52] <gardengnome> but i fear the few people who will break it
[11:53] <superm1> well at least the number will decrease for those who try
[11:53] <gardengnome> yep
[11:53] <gardengnome> thanks a lot :)
[11:53] <superm1> gardengnome, it only solves half the problem though.  still if someone puts the wrong password in that root password box at the start
[11:53] <superm1> things break
[11:54] <superm1> i want to fix it before feisty, but i'm not sure i will be able to
[11:54] <gardengnome> superm1: mysql is crucial, yes.
[11:54] <superm1> but again its one of those things.  if you read and follow what it says.  it works
[11:55] <superm1> if you dont, then you have to be responsible for fixing your error
[11:55] <gardengnome> the problem is that exactly those people don't know ;)
[11:55] <gardengnome> re-inventing the wheel might nto be necessary.
[11:56] <gardengnome> the random database passwords have caused much more grief than mysql < mc.sql.
[11:57] <majoridiot> (troubleshooting sorted)
[11:58] <superm1> gardengnome, agreed
[11:58] <superm1> gardengnome, but then debian and ubuntu would be scrutinized for insecure default setups
[11:58] <superm1> so your damned if you do and damned if you dont
[11:59] <superm1> cant win both worlds
[11:59] <gardengnome> varka's quit message translates to "i'd change the world, but god doesn't give me the source code" in case someone was wondering.
[11:59] <gardengnome> superm1: have the user set one. *shrug*
[11:59] <gardengnome> the root password is empty by default.
[11:59] <superm1> what a wonderful quit message
[12:00] <superm1> gardengnome, you think setting a password is a better way to do it?
[12:01] <gardengnome> superm1: the mythtv-database package seems.. self-contained. the user thinks everything is done for him - but instead, it put in a random passwort and doesn't tell him where it lives.
[12:01] <superm1> well i am assuming that was the original goal of the package.  back before myth even had the dialog popping up asking you to enter the DB password when it wasnt able to connect
[12:02] <gardengnome> hum
[12:02] <superm1> in the .16/.17 days
[12:02] <gardengnome> i'd even feel *betryed* by my linux box. ;)
[12:02] <gardengnome> betrayed* :)
[12:02] <gardengnome> a small popup telling the user the password is in /etc/mythtv/mysql.txt would be cool
[12:02] <superm1> that can be feasible
[12:02] <majoridiot> agrees
[12:02] <superm1> or just telling them immediately
[12:03] <gardengnome> yep.
[12:03] <majoridiot> or both
[12:03] <superm1> this is your password, its here in case you forget
[12:03] <gardengnome> and add something like
[12:03] <gardengnome> "print it." :)
[12:03] <superm1> when i get my root password check/change finished up i'll add this
[12:03] <superm1> just hoping i get some time this weekend :)
[12:04] <gardengnome> that'd be nice :)
[12:04] <gardengnome> i need to get $stuff with $her sorted out and study for my finals. ;)
[12:05] <superm1> hehe
[12:15] <majoridiot> superm1: will it cause flak that the server caps you did set up /var instead of /var/lib?
[12:16] <superm1> oh didnt think about that.
[12:16] <superm1> since /var was an option
[12:16] <superm1> how many of them are that way?
[12:16] <superm1> its just one right
[12:16] <superm1> or 2? or more
[12:16] <majoridiot> more
[12:17] <majoridiot> it shows on the summary and the summary after setting up swap
[12:17] <superm1> set it up right now assuming /var
[12:17] <superm1> i'll see if i have the originals
[12:18] <gardengnome> it's not that easy to delete those ubuntu howtos on wiki.mythtv.org because they contain additional information
[12:18] <gardengnome> eg compiling from scratch.
[12:18] <superm1> gardengnome, oh
[12:18] <gardengnome> superm1: i could.. spam a bit, though. ;)
[12:18] <superm1> lol
[12:19] <gardengnome> actually, the edgy guide doesn't even mention the packags.
[12:19] <gardengnome> packages.
[12:19] <gardengnome> oh, never mind. it does.
[12:19] <superm1> why have a guide centered around a distro that would do things from source
[12:19] <superm1> thats above me
[12:19] <gardengnome> apt-get build-deps? :)
[12:22] <superm1> someone who is willing to build from source is typically much more experienced then needing a guide
[12:23] <gardengnome> not when you need svn
[12:23] <gardengnome> i used to run svn head.. back then
[12:24] <superm1> yea i remember back then doing that too
[12:24] <superm1> nowadays you dont need to do that anymore
[12:24] <superm1> things in 0.20-fixes are stable and mature and such