Jump to content

boilerhorn

Certifiably Surly
  • Posts

    1733
  • Joined

  • Last visited

Posts posted by boilerhorn

  1. Just now, Brew said:

    So you’re saying the corruption caused them to make the call the first time, then it drug on so long they decided it was too obvious and backed down? Seems reasonable. 

    You did not read my edit.  Regardless, nevermind.  I’m grumpy and we’ve shot ourselves in the foot.

  2. 3 minutes ago, AUS-97HORN said:

    dude... we got an overturn of DPI penalty which is technically NOT possible. but it happened.     It was clearly the right call... and the replay being done in the stadium clearly influenced the refs who realized how horribad the PI call was.

     

    thats literally the anti Kirby call.... and it got us 7.  thats all we can ask for. 

    Agree, but the call should have never occurred in the first place.  That’s the corruption angle and SEC office…

    Or incompetence.

    Do not attribute to malice which can easily be attributed to incompetence.

    • Hook 'Em 1
  3. Just now, SlingeroGuitaro said:

    I played for Gerry DiNardo and Terry Hoepner at Indiana. I love the successes we have had over the last 10 years or so with various coaches. 
    cignetti makes me very happy

    Nice!  I was about 14 years ahead of you at Purdue.  Did not play football, but got to experience the Fred Akers eras in both Austin and West Lafayette :).  Aside from the Tiller years - and a small part of the Brohm era - Purdue has not been that great.

    Many of my friends - and now my niece - attended IU.

    I certainly hope they find a way to keep Cignetti for some time.  He's the real deal.

  4. IU exposing how mediocre Nebraska is.  I saw it in person against a really shitty Purdue team.  IU still has Michigan and tOSU on the schedule.  I can see them winning both.  Not super-high likelihood, but it's not out of the realm of possibility.  I believe they beat Purdue by 35+ to close out the season.

    • Hook 'Em 1
  5. There are a bunch of great comments on here already, but I will add my opinion, for what little it is worth.

    Problems w/ Windows, its support for peripherals, intermittent failures, etc. are reasons to get frustrated.  To me, migrating everything to Linux would be my 4th or later option.  Option 1: get a different Windows laptop.  Option 2: Get a Mac laptop.  Option 3: wipe and reinstall Windows.  Option 4: Linux.  Your windows laptop may have strange compatibility issues that can be solved by reinstall or using a PC from a different vendor.  As noted, the Linux Desktop is subpar (to some) compared to the Win or OSX desktops.  

    To address the "I really want to learn Linux, I would say that it is indeed worth it.  Tons of code development is done in a Linux environment.  If you've never used Linux, there will be a learning curve.  I am not sure how much of your hardware swap, repair, upgrade tech experience will transfer.  The intellectual curiosity will.  The desire to get things to work will.  It might frustrate you at the beginning, but it will make you smarter - just the intellectual stimulation alone will.

    Also, Mac's OSX is a derivative of BSD Unix and its terminal and command line interfaces will feel a lot like a linux experience, but with a far more seamless integration into the entire product.  Most Mac users do not use the terminal or command lines on a daily basis.

    I use Mac and Windows interchangeably as "daily drivers" to access the professtional and personal world.  The OS/Desktop integration to almost every piece of production software is important to me.  You will not get that with Linux.  I have not messed with MS Office, evernote, Chrome, etc. on Linux, but its integration is quite good on both Mac an Win (as one would expect).  However, I do use Linux when I develop just about any code of any sort.  The tools supporting development, compilation, debug, etc. are all there and are actively being supported and developed.

    So, I think you are really asking 2 questions.  What do I do with this laptop problem? and Should I learn Linux?  For the first, I offered 4 possibilities above and could also offer, "solve it w/o using BlueTooth," which is not really helpful.  For "Sould I learn Linux?" I say, yes.  And there are myriad approaches you can use to get started:

    1. Grab a box and install linux on it.  It wil be standalone and any damage you do is isolated easily be fixed w/ reinstall.
    2. Install a virtual machine manager on your Win machine (VirtualBox is what I have used) and install linux there.
    3. Create a bootable Ubuntu USB and dabble
    4. Continue using Win and install Windows Subsystem for Linux

    Personally, I would do #1.  It's pretty easy to find old-ish hardware for cheap/free that folks are wanting to discard.  In many cases, Linux extends the life of these platforms, as the resource requirements for basic linux is considerably lower.

    • Like 1
  6. 2 hours ago, MonkeyDoughnut said:

    Glad it is found/fixed.  So there wasn't any visible indication of a leak outside?  Like standing water or wet ground or such?  Just wondering where the water went

    Thanks.  There was no visible indication outside.  In fact, the 2nd leak required ~12" of digging in the correct space before there was softer ground.  Without the new CoA meters, we might not have seen the extra consumption until Nov/Dec.  An extra 2500 gals/month in the summer is easy to miss.

    • Hook 'Em 1
  7. As of yesterday, I believe the problem is solved.

    First leak detection test isolated a leak near where a pipe was entering the garage.  When the house was built (decade before I bought), the builder installed a water softener in the garage.  Instead of running from the utility source directly to the household plumbing, the builder redirected the main line to the garage and then cut back in toward the main plumbing access to the house.  The test process found a leak in a PVC coupling as the water entered the garage.  The fix was trivial and hardly worth what I spent - it was not very deep.  It was something that anyone with a small background in PVC work could have done.  And there's a reason I mention this.

    As noted, water flow persisted.  Leak detectors detected another leak - this one near where the line entered the house - around 40 feet away.  Given my experience from the initial leak, I decided to DIY.  After about 1 hour of digging, I declared, "screw this," and called a pro.  Turns out a coupling from PVC to copper had failed.  Plumber put a PVC -> PEX -> copper repair.  No more leak.  

    Both repairs involved something like the picture below - involving 4 90-degree angle couplings.  There seems to be no material impact to pressure or water flow.  Hoping I do not have to deal with this again for a while.

    My guess is that leak #1 was not the original leak, but that the testing accelerated a future failure.

    Screenshot 2024-10-17 at 9.02.01 AM.png

×
×
  • Create New...