IRC log for #utah on 20121001

00:09.06*** join/#utah RyanE (Piadas@rberick.dsl.xmission.com)
01:02.31*** join/#utah bonez2046 (~LiveWell@173-14-239-229-Utah.hfc.comcastbusiness.net)
01:03.27bonez2046How can I discover the specification level (spec 1.0, spec 2.0, etc) on a video card, when that information isn't printed or labeled on the card?
01:10.53*** join/#utah dfinn (~Adium@c-67-177-59-146.hsd1.ut.comcast.net)
01:58.22eightyeightbonez2046: what specification level are you referring to?
02:33.17*** join/#utah macnewbold (~macnewbol@c-67-172-228-255.hsd1.ut.comcast.net)
02:40.24*** join/#utah undertakingyou (~undertaki@c-98-202-42-89.hsd1.ut.comcast.net)
02:52.22*** join/#utah macnewbold (~macnewbol@c-67-172-228-255.hsd1.ut.comcast.net)
03:15.45bonez2046eightyeight: well, glad to answer
03:17.30bonez2046when I purchased a video card for this machine several months ago, it didn't work in this machine but it ran in another. I discovered 'this' machine's PCI express slot required a video card with spec 1.0 but the card I received was a spec 2.0 card, thus it wasn't recognized by 'this' machine, but it ran fine on my other machine
03:19.23bonez2046it acts as if the card isn't getting any power...and strangely, I notice that the gold foil on 2 pins on the card edge are covered about half the length of all the other pins...though i see the socket contacts do ride up the foil on both of these half covered pins
03:53.50*** join/#utah wps (~wps@208.53.57.58)
07:05.02*** join/#utah ezakimak (~nick@ns1.nickleippe.com)
07:27.03*** join/#utah JalenJade3rd (~JalenJade@c-24-10-186-68.hsd1.ut.comcast.net)
09:01.01*** join/#utah bonez2046 (~LiveWell@173-14-239-229-Utah.hfc.comcastbusiness.net)
09:25.34*** join/#utah gundy (~gabe@166.sub-70-196-194.myvzw.com)
09:29.31gundyveracitynetworks down anyone?
09:34.14gundyConfirmed.
09:34.40gundyOh well. It gave me a reason to drop in an say "hi."
09:35.00gundyNow, sleepy time.
09:54.42*** join/#utah jima (jima@2001:49f0:a057::8824)
11:07.13*** join/#utah ChanServ (ChanServ@services.)
11:07.13*** mode/#utah [+o ChanServ] by kornbluth.freenode.net
12:46.39*** join/#utah emcnabb (emcnabb@nat/redhat/x-uohadzbalnlmkaro)
12:46.40*** mode/#utah [+v emcnabb] by ChanServ
13:34.09eightyeightbonez2046: that still doesn't answer my question: what specification level are you referring to?
13:57.12*** join/#utah pdayton (~pjdayton@67.199.187.209)
13:58.12*** join/#utah resplin (~resplin@esplins.org)
14:24.20*** join/#utah bmidgley (~bmidgley@70.102.172.254)
14:25.56Q_ContinuumRandom Utah-question.  What is up with the big metal stars people put on their houses?  Is there any local/cultural significance, or is it just a popular decoration?
14:28.50jimauh-oh. he asked about the stars.
14:39.48*** join/#utah mahelious (~mahelious@ip65-46-59-10.z59-46-65.customer.algx.net)
14:40.41TodPunkQ_Continuum: I KNOW, RIGHT?!?!?!  It drives me nuts.  From what I've gathered, it's just a popular decoration (why? it's ugly as hell).
14:41.31resplinIt ranks up there with the silhouette cowboys.
14:42.09Q_ContinuumTodPunk: Someone offline told me that maybe they're all just wishing they lived in Texas?
14:42.18Q_Continuumlol
14:42.21programmerqI don't know that I know what stars you speak of. Anyone have a pic handy?
14:42.30programmerqI'd probably go "oh yeah" if I saw one.
14:43.13*** join/#utah wps (~wps@wfw.vivint.com)
14:47.14resplinGoogle for "barn star"
14:47.27TodPunkprogrammerq: well, they're metal, usually a dark color or silver, and they're star-shaped
14:47.49TodPunkhttp://www.outerbankscountrystore.com/servlet/the-214/barn-stars-black-12%22/Detail?gclid=CO65zOWH4LICFYdxQgodyRgAGQ
14:47.50jimawhat resplin said...the raised metal ones.
14:48.03TodPunkresplin has it, though, they'r barn stars
14:48.04Q_Continuumhttp://en.wikipedia.org/wiki/Barnstar
14:48.37*** join/#utah macnewbold (~macnewbol@wfw.vivint.com)
14:48.53jimagerman-american farming communities? and we haven't heard of this?
14:49.07Q_ContinuumYeah...
14:49.14Q_ContinuumI'm a little confused.
14:49.27Q_ContinuumI don't *remember* seeing them, doesn't mean I haven't. (Back in MN)
14:49.46Q_ContinuumThen again, that side of the family wasn't german.
14:49.52jimathey're fairly popular around here.
14:50.27Q_ContinuumThe german side was more modern in their barns.  (In age, design and materials)
14:50.39Q_ContinuumThat reminds me: I need to take picture of Tree-in-Silo when I go back to visit.
14:51.02*** join/#utah knicholes (~knicholes@64.122.179.21)
15:02.19*** join/#utah fungus (~olsonl@bromine.sosstaffing.com)
15:04.01eightyeightyeah... i don't get the stars
15:04.04eightyeightstrange
15:04.22eightyeightand they rust, and leave an awesome impression on the house when you take them down
15:04.27eightyeightepic
15:10.39*** join/#utah jalbretsen (~jalbretse@sonic.itransact.com)
15:20.23*** join/#utah nage (~nage@199.192.164.75)
15:20.24*** join/#utah nage (~nage@unaffiliated/nage)
15:26.16unumbut why did anglos start sticking them on their houses?
15:26.56eightyeighti think that's the point- they are
15:29.41*** join/#utah emcnabb_ (emcnabb@nat/redhat/x-ogtidrussmvohcrj)
15:34.50unumhttp://en.wikipedia.org/wiki/File:Carthage_jail_front_entrance.jpg <- barn star anchor plates
15:40.54programmerqsomeone should start one of those "list of" pages on wikipedia with a list of buildings featuring barnstars.
15:41.05programmerqQ_Continuum?
15:41.42Q_ContinuumThat involves effort.  AND editing wikipedia.
15:42.39*** join/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
15:43.31*** join/#utah utlemming (~ben@67.199.187.66)
15:47.20programmerqI think the wikipedia folks don't really like those pages anyway.
15:48.09Q_ContinuumThe deletionists and "No, this is MY page, gtfo!" made me stop caring.
15:49.36programmerqI probably have made about two edits ever
15:49.46programmerqI linkified something once
15:49.58programmerqthat was about it
15:57.39*** join/#utah romanovic (~romanovic@puritynine.com)
16:03.17jimai fixed a geotag once, i think
16:04.41bonez2046eightyeight: by 'specification level' I mean in the respect of USB 1.0 versus USB 2.0, or 3.0 ... i.e., one video card spec perhaps didn't have power via the card edge, while a later one might, or one earlier spec might be running a slower bus speed versus faster on a later model specification
16:06.14jimaoops, and one other edit that got dropped when they merged the page with another page
16:06.41*** join/#utah kendsnyder (~kendsnyde@70-58-44-211.slkc.qwest.net)
16:08.23jimamy geotag edit is still intact
16:21.14*** join/#utah utlemming (~ben@67.199.187.66)
16:51.41*** join/#utah utlemming (~ben@67.199.187.66)
17:10.37*** join/#utah zzzirk (~zzzirk@67.21.63.152)
17:11.38*** join/#utah tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net)
17:20.33*** join/#utah niso (~nisovin@64.55.129.66)
17:25.31programmerqso, I'm still fairly new to LVM. I just set up raid5 mode with two strips (three disks).
17:25.44programmerqIf I wanted to add a fourth disk into the mix, is this relatively straightforward?
17:26.00programmerqall the guides I've used so far are pretty beginnerish, and only touch on using the raid modes in LVM
17:26.09eightyeightyes. it's not difficult
17:26.28eightyeightadd the disk, the extend the volume group, and extend the logical volumes as necessary
17:26.35programmerqare there good lvm "official" docs?
17:26.36eightyeightbut, if i were you, i would avoid lvm
17:26.43programmerqeightyeight: any particular reason?
17:26.49eightyeightyes- caching
17:26.58programmerqwould you do hardware raid instead?
17:27.16eightyeightit's not the raid that's the problem. it's lvm.
17:27.47eightyeighthttp://serverfault.com/questions/279571/lvm-dangers-and-caveats/279577#279577
17:27.49eightyeightis a good read
17:27.59*** join/#utah utlemming (~ben@67.199.187.66)
17:28.02programmerqyeah, I just found that one when I googled for info on lvm caching problems
17:28.04programmerq:)
17:28.18eightyeightit brings awesome functionality for resizing containers, but also brings complexity to the table, and horrid caching problems
17:29.09eightyeightfor myself, on personal hardware, i don't do separate containers
17:29.18programmerqI don't think I'm too overly worried about that for what I'm doing.
17:29.19eightyeighti put everything in /, and be done with it
17:29.22eightyeightincluding the swap file
17:29.29programmerqI've done the put everything in / before
17:29.45programmerqpart of how I use my personal computer is to play with different technologies
17:29.45eightyeighti don't have a need to contain /var, /usr, /boot, /tmp, /home, etc
17:29.55programmerqI have a root and a home
17:31.53eightyeightif you really want to play with tech, i would recommend using zfs on liunx: http://zfsonlinux.org
17:32.02eightyeightyou can create a bootable zfs root, that grub supports
17:32.14eightyeightand it has all the software raid and volume grouping builtin
17:32.15programmerqinteresting
17:32.19eightyeightplus a lot more
17:32.48eightyeightor you could play with btrfs, although there is no compression, encryption (neither in ZoL), deduplication or parity raid
17:32.49programmerqlast I looked into zfs, you were definitely stuck doing fuse to use zfs on linux (it's been a while)
17:33.01eightyeightyeah. don't use fuse. heh
17:33.28programmerqI figured I'd get something like a freenas box set up if I ever wanted to play with zfs
17:33.41programmerqbut if zfsonlinux is fairly mature and stable, that might be fun too.
17:33.49eightyeightvery mature. very stable.
17:33.59eightyeighti've committed production data to it, with zero issue
17:34.03eightyeightand plan on committing more
17:41.26programmerqI'd also be happy with a drobofs
17:41.30programmerqoh, one more question
17:41.40programmerqhave you ever dealt with a drive failure on lvm in raid5 mode?
17:42.21eightyeightyes
17:42.45eightyeighti had a hot spare to replace the failed drive
17:42.49eightyeightso the data was fine
17:43.31eightyeighti just found the serial of the failed drive, powered down, and replaced the drive
17:43.33eightyeightesay as pie
17:49.10programmerqcool
18:04.39errstr-++ to zfsonlinux, it is super easy to setup and is a much better replacement for lvm+raid
18:14.10jimafire drill went well; everyone survived.
18:16.10Q_ContinuumWell, one person had trouble.  "I'm not climbing 4 flights of stairs, I'm in boots!"
18:16.23Q_Continuum(Elevators weren't back on when everyone re-entered)
18:17.11jimathank goodness firefighters aren't such prima donnas. ;-)
18:18.11Q_ContinuumHeh.
18:22.29jimahow bad is it that i can spot that integra block no matter where i go?
18:28.53*** join/#utah manithree (~blr@li4-76.members.linode.com)
18:30.23bonez2046I am upgrading wife's macbook. It is running OS 10.5.8 ... How would I upgrade to newer OS release?
18:30.40bonez2046I mean, aside from going to a mac store
18:30.49eightyeightpurchase the software
18:30.53eightyeightinstall
18:31.30*** join/#utah utlemming (~ben@67.199.187.66)
18:31.41bonez2046that's too obvious...I assume visit apple.com and find the d/l upgrade and go from there?
18:31.42jimaeightyeight: wait wait wait...what kind of capitalistic crap is this?
18:32.05eightyeight?
18:33.10jima:-)
18:33.25eightyeighti have deep internal conflicts, that i haven't personally settled yet
18:33.35eightyeighti am fighting for copyright and patent reform
18:34.21eightyeightand the letter from birmingham jail by dr. martin luther king, jr. makes me want to disobey unjust laws
18:34.49eightyeighthowever, i can't come to convince myself that the current copyright and patent laws are 'unjust'
18:34.57eightyeightso, as it sits, i don't engage
18:35.00eightyeightbut i want to
18:35.02eightyeightso, i'm torn
18:35.42eightyeightbut, mickey mouse comes up for public domain in 2013
18:36.07eightyeightif disney engages, and further screws up copyright, then maybe i'll engage by priating all disney films
18:36.08eightyeightto start
18:36.32bonez2046sounds like fun
18:38.33manithreeeightyeight: Count on more Mickey Mouse laws next year (I am, anyway)
18:38.45eightyeightindeed
18:43.35*** join/#utah knicholes (~knicholes@64.122.179.21)
18:59.33*** join/#utah knicholes (~knicholes@64.122.179.21)
19:10.04*** join/#utah youtah (~youtah@216.51.42.66)
19:10.07youtahHELLO!
19:10.10youtahI know you all missed me
19:10.18youtahThis should make you feel better: http://sphotos-a.xx.fbcdn.net/hphotos-snc7/576936_10151047209235060_1534243400_n.jpg
19:11.46jimawait...you were gone?
19:11.48jima;-)
19:11.59youtahthat was about 45 minutes after the sun had set, and about when the mice started coming out and climbing (literally) all over our bags.
19:12.01youtahouch
19:12.07youtahJust mentally Jima
19:12.14youtahactually, I think I still might be missing
19:12.32youtahInfact, I will be going to go find myself. So if I come back, before I return, please keep me here.
19:14.29*** part/#utah bonez2046 (~LiveWell@173-14-239-229-Utah.hfc.comcastbusiness.net)
19:22.48*** join/#utah undertakingyou (~undertaki@c-98-202-42-89.hsd1.ut.comcast.net)
19:27.25fadeinyoutah: nice pic
19:27.37fadeincould use some more oil derricks in the background, tho
19:53.11*** join/#utah knicholes (~knicholes@64.122.179.21)
19:59.49*** join/#utah dfinn (~Adium@c-67-177-59-146.hsd1.ut.comcast.net)
20:01.30*** join/#utah bmidgley (~bmidgley@70.102.172.254)
20:05.07youtahlol fadein
20:09.30*** join/#utah mahelious (~mahelious@ip65-46-59-10.z59-46-65.customer.algx.net)
20:56.46*** join/#utah ezakimak (~nick@ns1.nickleippe.com)
21:29.00*** join/#utah knicholes (~knicholes@64.122.179.21)
21:39.40*** join/#utah d3c4f (~d3c4f@64.55.129.66)
21:40.39*** join/#utah bmidgley (~bmidgley@70.102.172.254)
22:48.26*** join/#utah jelliott (~jelliott@208.97.56.66)
22:54.55*** join/#utah simonista (~simonista@ec2-184-72-231-143.compute-1.amazonaws.com)
22:58.52*** join/#utah jelliott (~jelliott@208.97.56.66)
23:23.59*** part/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
23:34.50*** join/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
23:38.17*** part/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
23:38.44*** join/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
23:40.39*** part/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
23:43.37*** join/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)
23:47.57*** part/#utah Nemus (~Nemus@c-76-27-99-15.hsd1.ut.comcast.net)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.