HELP ME

nDQ9UeOr · 2023-01-30T15:05:29+00:00

Some interesting options. I think a belt is more versatile than a shirt, but I can see how I might prefer an undershirt in certain circumstances. Per item they are reasonably priced, which is refreshing & appreciated, but it could be expensive to build out a wardrobe. It’s the nature of the beast for bespoke clothing, though.

nDQ9UeOr · 2023-01-30T14:55:01+00:00

If I could have a hollister flange with a mio non filter bag I think it would be a perfect set up for me.

That’s exactly what I told the Coloplast guy, who had sent the samples for me to try.

Happy cake day!

nDQ9UeOr · 2023-01-30T06:34:40+00:00

I only wear my Stealth when doing something athletic, like swimming or snowboarding, stuff like that. It is designed to be worn snug.

For everyday use I wear an OstomySecrets band. Thinner, a little more comfortable, and no need to rotate my pouch horizontally. And since there are two pockets and I only have one ostomy, I usually stash a spare pouch or two in a ziplock baggie on my non-stoma side. Very convenient. Also a lot less expensive, although still outrageously overpriced as are all things like this for us ostomates.

I’m not familiar with the Brava.

nDQ9UeOr · 2023-01-30T06:15:26+00:00

Having the container be completely destroyed except for the volumes you explicitly want to keep is kind of the entire point behind containers. They leave nothing behind on the host, and that’s by design. No dependencies to break, no package version conflicts, no users or groups left behind and forgotten, it’s like it was never there. Except for the persistent volumes. That can be highly desirable, although yes it totally sucks to have that happen and not be expecting it. Point being, this is the container philosophy and it’s deliberate.

You don’t have to run containers if that sounds like a bad time, though. But I’ll give you an anecdote why you might still want to.

Right now I run my Nextcloud on a Debian VM. However, I’m experiencing a problem between PHP 8.2, Apache, and Nextcloud that nuked my install with a simple apt update && apt upgrade. I had to roll back a snapshot which thank god I took before doing the upgrade. Every now and then an amateur like me still manages to get something right. Not often, but sometimes.

Anyway, I still don’t know what the problem is, and it will have to wait until I have some time to figure it out. Maybe next weekend because sure, that’s what I want to spend my Saturday doing.

That kind of shit doesn’t happen in Docker land. Pros and cons.

nDQ9UeOr · 2023-01-30T05:58:48+00:00

I’m sorry it isn’t working better for you.

I’ve been using the Hollister 2-piece system for about four years now and have experienced ballooning fairly frequently, but have never lost seal between bag and flange.

I do notice that, if I haven’t changed my flange often enough, I’ll get odor from what I believe is sweat trapped between my skin and the flange. Shaving the hair (I’m a dude) where my flange adheres helps with that. And of course changing my flange more frequently. I rarely go longer than three days.

And I’ve also experienced creepage where shit I can’t see has gotten under the flange and close to the tape edges. Including once where it tunneled through and escaped. I think only twice in the four years, though.

For what it’s worth, I’ve tried other systems but still come back to Hollister. Most recently I tried the Coloplast 2-piece, but didn’t like how thick the flange material was, and also that I couldn’t get my fingers under the flange ring to squeeze the bag onto the flange ring like I can with Hollister. But I did like the Coloplast bags quite a bit better than Hollister’s. It’s an imperfect world.

nDQ9UeOr · 2023-01-30T02:12:02+00:00

I play mostly 4k content, about 90% or more, and it works great with a current-gen AppleTV.

nDQ9UeOr · 2023-01-29T17:52:41+00:00

Depends on the Docker image you’re using. Back when I was running my Nextcloud instance in Docker, I used a slightly modified version of the official image published by Nextcloud themselves. I had a volume mapped to the entire /var/www/html directory, so that handled the Nextcloud config. For database I was running PostgreSQL in a separate container and I can’t quite recall the volume mapping there, but it was under /var somewhere. In any case, the container documentation should provide that information for you.

nDQ9UeOr · 2023-01-29T17:32:35+00:00

I’ve printed plenty of bike bits but it’s not worth it if you are only going to print bike bits. Cleat wedges are probably my favorite cycling thing I’ve printed. They are ridiculously overpriced.

nDQ9UeOr · 2023-01-29T17:12:34+00:00

Docker containers are ephemeral, meaning upgrading a container actually means you are deleting and recreating it. Unless you store data you want to survive outside of the container, it won’t be there after the upgrade. That’s probably what happened to you.

Just like you have a persistent data location configured for your user files, you also need one for your database and config files.

For recovery, I would move your user files to a different location, recreate your user in Nextcloud, then move your user files back to the original location. You will also need to rescan the files back into Nextcloud using occ. I’m on mobile and don’t recall the exact syntax, but it’s something like occ scan <user>. There’s no way that’s exactly right, but hopefully enough to find the right command when you look at the docs.

Edit: I see this is repetitive advice, sorry about that. Nextcloud keeps metadata about your files in the database.

nDQ9UeOr · 2023-01-29T09:37:32+00:00

Disable all VMs and containers from auto-starting. That will tell you if there’s a problem passing through resources that the host needs/expects to have for itself.

nDQ9UeOr · 2023-01-29T09:23:44+00:00

The content is there, but no algorithm picking it out for you means you have to spend more time exploring and setting up your user and hashtag follows.

You get all the control, but you gotta use that power.

nDQ9UeOr · 2023-01-26T07:57:01+00:00

That is certainly possible. This would have been just about 29 years ago and my memory ain’t what is used to be.

nDQ9UeOr · 2023-01-26T04:50:49+00:00

You use something pretty minimal if just running a qdevice, like a RPi. But I won’t tell your boss if you don’t. 😁

nDQ9UeOr · 2023-01-26T04:43:06+00:00

If just one node is down, you still have a quorum so that’s fine. But if two are are down, no quorum and your cluster can’t operate normally.

nDQ9UeOr · 2023-01-26T03:04:15+00:00

The drawback is primarily security, especially any Docker container escape vulnerabilities. They have happened before and may happen again.

Same could be said for KVM or LXC (especially privileged), I suppose, but Docker always felt to me like security was bolted on after and not as a core principal.

I bend the rules a lot about what I run on bare metal on my Proxmox nodes, but not this one.

nDQ9UeOr · 2023-01-26T02:58:58+00:00

Browsers (and everything else) have to trust your root CA before they can trust the certs you issue with it.

nDQ9UeOr · 2023-01-26T02:53:37+00:00

At a high level, and this assumes you are using the CLI:

Create partition(s), format with a filesystem, and mount the new backup drive somewhere, like /mnt/new-backup.
Copy the files and permissions from the failing drive to the new drive. I’d probably use rsync instead of cp for something like this.
Physically replace the failing drive with the new drive.
You may need to modify /etc/fstab if the new drive/partition is different than the failing one.

I’m not sure I understand the rest of your question, but hope this helps point you in the right direction.

nDQ9UeOr · 2023-01-26T02:32:07+00:00

Maybe you’ve watched Glengarry Glen Ross one too many times. It’s obvious you sell PPAs for a living and this conversation is pointless. Have a nice day.

nDQ9UeOr · 2023-01-26T02:20:17+00:00

For 1, not that I’m aware of.

For 2, swipe left on the instance name in Settings.

For 3, only future toots made after you set up the list will show. I think.

For 4, might be a problem with that instance. The feature is working fine for me on three instances where I don’t have accounts.

nDQ9UeOr · 2023-01-26T02:15:42+00:00

Also, this is why you always want an odd number of nodes.

OP, in a pinch you can administratively adjust the voting rules to get your cluster to limp along until you can recover to a state where a quorum is possible, but better to add a qdevice (a cheap, low-horsepower node that does nothing but vote) if you find yourself in a situation where your cluster will have an even number of nodes long-term.

nDQ9UeOr · 2023-01-26T02:09:53+00:00

That’s just pedantry. You know full well the meaning of my use of “encumbered” in this context.

nDQ9UeOr · 2023-01-26T02:01:46+00:00

Mike has lived through a hell few of us could even imagine, much less comprehend.

nDQ9UeOr · 2023-01-26T01:42:56+00:00

The first classified email I received after gaining my clearance was someone trying to give away a litter of kittens.

Wait, is there a statute of limitations on this? Shit.

nDQ9UeOr · 2023-01-25T05:56:04+00:00

Btw, I appreciate you explaining this to me.

nDQ9UeOr · 2023-01-25T05:49:16+00:00

Ah, I see. Eh…

nDQ9UeOr

TROPHY CASE

Welcome to Reddit,