The anti🚫-derailment🚃 & thread🧵 hijackingšŸ”« thread🧵 ⁉

If anyone has a solution for the type of acid reflux that keeps you awake at midnight, let me know.

I’m thinking about taking pictures of my mouse and keyboard collection to get my mind off my esophagus, but this doesn’t seem optimal.

Someone upload me into an Atlas already, I’m tired of this fleshy body and all the problems that it has… :sob:

2 Likes

Have you tried prilosec? Worked for me in college, though I heard it has some pretty rare and bad side effects. I’ve done no research to confirm that though

Short term I assume you tried Tums?

Though probably the best method would be lifestyle changes unfortunately

3 Likes
2 Likes

Omeprazole, that stuff is effective but it’s not great for long term use.

I should buy some…

I should probably start by reducing my anxiety and eating better…

2 Likes

Yeah, really sucks when the advice is always ā€œeat better, sleep better, have a good schedule, exerciseā€ etc.
I’m sure you’ve heard this before, but don’t skip meals, don’t eat right before bed.

Seems like you can try drinking some water with a bit of baking soda mixed in for a super short term solution.

This isn’t health advice, do your own research, be smart, etc etc etc

2 Likes

For here?

2 Likes

I’ve never had it, but logically I would suggest sleeping reclined rather than flat.
Let gravity be your friend?
Is that something you have tried?

1 Like

Papaya enzymes worked wonders for me

2 Likes

Wow, I don’t know anyone else who takes them. They’re great. Though I find they work best on indigestion and bloating, not so much acid reflux

1 Like

The solution needs to be catered to your specific problems and behavior really. if it’s been going on for too long you might be in GERD stage which means, probably, permanent drug management.

my wife

she had esophageal encephalitis with gastric involvement… but we were able to sort out some issues with diet and behavior and it’s gone and she’s off proton-pump inhibitors now. if you want to DM chat about it or open a public thread i’m game… will be asking some PII questions though.

1 Like

Why would sacrificing a really useful UI that doesn’t need a GUI and works over a network with very little bandwidth for those crazy ideals help Linux?

Most shells have autocomplete, just press the tab key.

Most distrios are not made for the average user and that’s ok. Your home router/modem/wifi box wouldn’t be running Linux without the command line. And the same applies to servers. It’s supposed to be close to Unix in form and function, hence why it’s very different from Windows and that’s ok.

Besides, open source is about freedom. Forcing developers to create GUIs and requiring video hardware would be absurd.

Can you show me on the doll where did VIM touch you? I know that you were not allowed to leave. :flushed:

4 Likes

I’m really trying to understand Linux as well, and it’s been a struggle. I was primarily Windows and I switched to Mac about 10yrs ago. Not because I like the apple ecosystem, but because I wanted to easily learn multiple OS’s. At the time Apple have the option to dual boot and with a VM I could bring in Linux to the mix as well.

It let me dive into a command line a bit more. But it was hard to learn the slight difference from Windows command line.

I wouldn’t say I’m proficient but I can get around. Switching into my Linux VM I’m still very very basic. I want to really like WARP and I feel like it has helped me understand some of the command structure. I feel like if WARP was around when I first started it would have made the transition easier for me to grasp and understand.

I’m still completely ignorant to Linux networking and how that works.

I’ve been trying to fix a Windows 11 VM for 6 days now that doesn’t have Internet access but can ping everything on the network except the gateway. It’s irritating.

What is your host OS?
I’m assuming the VM is W11.
What Hypervisor are you using?
Can you dump your Hypervisor network settings?-Screenshots/etc?

2 Likes

Proxmox.

I have other vms in the setup and they get DHCP just fine.

Windows11 Pro

I’ve reinstalled Windows from iso and the latest virtio drivers 13 times. It never gets DHCP, cannot see the gateway.

It can see every other device on the network.

It worked fine for about a year and then it off no where no longer gets Internet.

I’ve built the VM from scratch at least 6 times.

Next I’m going to just try to do Windows 11 home thinking maybe it’s expecting some group policy to be added for Internet or something…

Okay, I had a Win10-KVM get the same issue about a year ago too. I’ll check those settings on my rig when I get home as I’m pretty sure proxmox just uses KVM for everything.

1 Like

Charging you to stream your own media from your own connection. The sheer balls… but we all knew it was coming at some point. Frankly I’m glad. This means projects like Jellyfin are just going to get that much more attention and development.

5 Likes

Digging into this more assuming the issue is Proxmox Networking.

I did notice this isssue after updating proxmox. So assuming the kernel changed the naming convention of the adapters.

My current /etc/network/interfaces

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

iface eno3 inet manual

iface eno4 inet manual

iface enp130s0f0 inet manual

iface enp130s0f1 inet manual

iface enp132s0f0 inet manual

iface enp132s0f1 inet manual

iface enp132s0f2 inet manual

iface enp132s0f3 inet manual

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.5/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

And my curent ip a

root@proxmox:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp130s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:0a:f7:82:db:fe brd ff:ff:ff:ff:ff:ff
3: enp130s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:0a:f7:82:db:ff brd ff:ff:ff:ff:ff:ff
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether c8:1f:66:ec:9c:a7 brd ff:ff:ff:ff:ff:ff
    altname enp1s0f0
5: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:1f:66:ec:9c:a9 brd ff:ff:ff:ff:ff:ff
    altname enp1s0f1
6: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:1f:66:ec:9c:ab brd ff:ff:ff:ff:ff:ff
    altname enp1s0f2
7: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:1f:66:ec:9c:ad brd ff:ff:ff:ff:ff:ff
    altname enp1s0f3
8: enp132s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:36:9f:a8:8e:78 brd ff:ff:ff:ff:ff:ff
9: enp132s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:36:9f:a8:8e:79 brd ff:ff:ff:ff:ff:ff
10: enp132s0f2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:36:9f:a8:8e:7a brd ff:ff:ff:ff:ff:ff
11: enp132s0f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a0:36:9f:a8:8e:7b brd ff:ff:ff:ff:ff:ff
12: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c8:1f:66:ec:9c:a7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.5/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::ca1f:66ff:feec:9ca7/64 scope link 
       valid_lft forever preferred_lft forever
13: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
    link/ether ba:21:e3:66:5c:26 brd ff:ff:ff:ff:ff:ff
14: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b6:18:55:85:b2:1b brd ff:ff:ff:ff:ff:ff
15: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 1e:5e:60:c3:f0:fc brd ff:ff:ff:ff:ff:ff
16: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether b6:18:55:85:b2:1b brd ff:ff:ff:ff:ff:ff
26: tap107i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr107i0 state UNKNOWN group default qlen 1000
    link/ether 4a:85:21:d1:fe:33 brd ff:ff:ff:ff:ff:ff
27: fwbr107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 2a:1b:7b:3e:10:3a brd ff:ff:ff:ff:ff:ff
28: fwpr107p0@fwln107i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 5a:ad:05:b4:8f:1e brd ff:ff:ff:ff:ff:ff
29: fwln107i0@fwpr107p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr107i0 state UP group default qlen 1000
    link/ether 2a:1b:7b:3e:10:3a brd ff:ff:ff:ff:ff:ff
140: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether f6:10:89:eb:99:98 brd ff:ff:ff:ff:ff:ff
144: tap103i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether 52:e0:dc:00:56:dd brd ff:ff:ff:ff:ff:ff
148: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr102i0 state UNKNOWN group default qlen 1000
    link/ether be:ec:1b:06:2a:35 brd ff:ff:ff:ff:ff:ff
149: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f6:9e:4c:8d:86:37 brd ff:ff:ff:ff:ff:ff
150: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether c2:19:40:0c:b1:6f brd ff:ff:ff:ff:ff:ff
151: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
    link/ether f6:9e:4c:8d:86:37 brd ff:ff:ff:ff:ff:ff
1 Like

The answer to all these questions is simply Windows.

Windows need competition. It is currently the only viable OS out there for mainstream use. Yes, I’m ignoring apple, and I’ll stop when they come out of their little walled garden to play with everyone.

So, Windows needs competition. Real viable Competition.

  • Linux is the only currently viable option.
  • Linux has sucked all the oxygen out of the room in a way that makes any other potential competition die stilborn.
  • There are GUI’s for Linux, but any time a user has a problem the solution is always, just pop open the command line and ā€œsudoā€ ā€œbashā€ and see how easy it was? Spoiler, for most people it’s incomprehensible.
  • The result is a defacto Windows monoply with all the associated behavior.

So when you see Windows components being offered as subscriptions, Massive bloatware, being forced into the Windows ā€œstuffā€ a.k.a. needing a Microsoft account just to run it, and the blatant data harvesting / and deliberate refusal and/or obfuscation of opt out for any of it. l look around, and blame Linux.

I blame them for being unadoptable for the average user, and for cock blocking anyone else by their simple existence.

1 Like

Totally agree. Linux is really terrible. Like how expensive it is. Luckily for the developers, they’re getting paid a ton of money. It’s crazy how Linux is such a walled garden too. You’d think they’d have some support for old hardware but I guess you have to keep the profits going. I wish they’d invest some of that huge profit into hiring developers who actually gave a shit.
I really hope Microsoft will gain some more market share and save us from this insanity. Their software is so much more reliable. I’ve never had any program on windows crash. And thank god for their descriptive error messages. It makes troubleshooting any windows issue a breeze.

4 Likes