Don't tug on that, you never know what it might be attached to
1–10 of 98 posts
Re: Don't tug on that, you never know what it might be attached to
#2Great debugging, and an example of the sort of behaviour that long dependency chains can expose.
Or rather, I did until this week, when it suddenly stopped working.
When this happens to me, the first thing that I ask myself is "what changed?", and I'm usually able to track down the cause to some configuration change. Incidentally, this is also why I never like modifying a working system unless it's absolutely necessary.
The fact that it ultimately was caused by some security features that would be very important for a multiuser shared server but nearly irrelevant for the (presumably) single-user local machine that he is using suggests that perhaps we shouldn't be thinking of "one size fits all" paradigm for OSs, since a lot of problems like this one stem from the unnecessary extra complexity introduced by such thinking.
Re: Don't tug on that, you never know what it might be attached to
#3tl;dr Don't use unnecessary amount of scripts and tools to do what vim + git do just fine.
Re: Don't tug on that, you never know what it might be attached to
#4> This computer stuff is amazingly complicated. I don't know how anyone gets anything done.
Indeed.
Re: Don't tug on that, you never know what it might be attached to
#5This drives home the point that (almost) no one actually knows the details of their full stack.
Re: Don't tug on that, you never know what it might be attached to
#6Great debugging, and an example of the sort of behaviour that long dependency chains can expose. Or rather, I did until this week, when it suddenly stopped working. When this happens to me, the first thing that I ask myself is "what changed?", and I'm usually able to track down the cause to some configuration change. Incidentally, this is also why I never like modifying a working system unless it's absolutely necessa…
> this is also why I never like modifying a working system unless it's absolutely necessary.
this is safe, but it paints you into a corner over time, where you become paralyzed and can't improve anything. Needs better testing, so changes are safe.
Re: Don't tug on that, you never know what it might be attached to
#7Great debugging, and an example of the sort of behaviour that long dependency chains can expose. Or rather, I did until this week, when it suddenly stopped working. When this happens to me, the first thing that I ask myself is "what changed?", and I'm usually able to track down the cause to some configuration change. Incidentally, this is also why I never like modifying a working system unless it's absolutely necessa…
> this is also why I never like modifying a working system unless it's absolutely necessary. this is safe, but it paints you into a corner over time, where you become paralyzed and can't improve anything. Needs better testing, so changes are safe.
Tests don't magically make changes safe or give the confidence to make changes.
Re: Don't tug on that, you never know what it might be attached to
#8As a sysadmin on a Windows network of ~100 computers, this story makes me want to cry, although maybe for the wrong reason:
I see weird problems of the sort "It did work before I went on my lunch break" on a fairly regular basis. How often would I like to go down the rabbit hole and explore these problems in such depth, but if I did that, I would hardly get any work done. The frequency at which our users run into these problems is just too high.
It is so frustrating so restart a computer or maybe re-install it and see the problem disappear, because now all hope to understand what caused the problem in the first place is gone. And problems that disappear for no good reason have a tendency to return for no good reason, most often on a Friday afternoon, just when you're about to call it a day. ;-/
Re: Don't tug on that, you never know what it might be attached to
#9What's funny is that in this case the dynamic loader was sanitising something irrelevant to the actual capability granted, which seems to me should be a bug.
Also, I'll be an advocate for just starting emacs with systemd, and never worrying about it again.
Re: Don't tug on that, you never know what it might be attached to
#10No reference to the full quote? :)
"You can check your anatomy all you want, and even though there may be normal variation, when it comes right down to it, this far inside the head it all looks the same. No, no, no, don't tug on that. You never know what it might be attached to. " - Buckaroo Banzai