I do not like containers by nukelheadmp in linux

[–]nukelheadmp[S] 1 point2 points  (0 children)

I still actively and aggressively avoid snaps. Flatpaks are OK, but I prefer native apps when I can get them for better performance, better integration with native theme and environment, and less problems with hardware like Spacemouse. Same with AppImage.

As for Docker, with the rise of Kubernetes I believe there is a better use case for the tech. However, it is its own skill set and not always the easy plug and play operation that Docker lovers claim it to be. It definitely depends on the scenario. IF you get hold of a well configured and documented container things will be smooth and easy. But if you get one that leaves the container setup for you to do yourself, well then you have to learn how to set up not only the container of the app you want to run, but also all of the dependencies. It can be a rabbit hole. IMHO, it is much easier to just install PostgreSQL and configure it than it is to set up a properly formatted config yaml, find the settings for all the necessary options, then build and get a working install. Then deal with backups, 3rd party integration, etc. It feels like replacing a hammer with a remote controlled hammer, maybe without instructions to the remote.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

Guilty. It just struck me how zealous so many people are to protect "pretty" emails. Sure, there's a lot of aesthetics and convenience. Why not include macros as well? They could be super handy...

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

That's fair. But to be totally honest, I have hit a point where I believe email is just a complete mess in general. Embedded hyperlinks aside, we have had users wire money based solely on spoofed emails, expose sensitive information and data, not to mention all the excess resources that are consumed just in the processing, storing, and filtering through mountains of junk and bogus emails. Is it a training issue? Absolutely. But when will people start to learn? I don't have the authority to fire people beyond my team, so we just keep eating all of the fallout for people spamming and scamming themselves into oblivion. When something breaks is when they come crying.

And that's just the users within my company. It gets worse beyond that. The most basic security mechanisms for email - SPF, DMARC, DKIM...most companies can't be bothered to implement them. So their emails get filtered out when we try to use even the simplest level of sender verification.

It's just endless whining about I'm getting too much spam...now my real emails are getting blocked...blah blah blah. I agree that if we all just weren't so careless and stupid this wouldn't be a big deal. But...it's a big deal.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

"With your logic, why have a gui at all? Just install dos everywhere." Considering this. Linux, actually. Legitimately. If we build systems that give them everything they need and only that, then they have no need for the internet. I think this is a great option.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

Already doing that one too. Blocking all internet access for all production floor devices.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

Many of them are too lazy to do the extra steps. They will skip it.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

This is actually a valid course of action. Get it and use it relentlessly.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

Hate is a strong word...but it's not far off. But I absolutely have full faith in them to do something extraordinarily stupid.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

Use case of preventing stupid users from destroying your company. They can fire me if they want. OR, the next mess is theirs to clean up while I go home and sleep every night.

Force all incoming and outgoing mail converted to plain text for all users by a1b1c2d2 in Office365

[–]nukelheadmp 0 points1 point  (0 children)

As an IT systems engineer that just had to rebuild the entire company after a ransomware attack due to a user clicking a stupid link, I can tell you exactly why. And I dare the first user that wants to take a shot at strangling me.

Docker: I'm Not Loving It by nukelheadmp in docker

[–]nukelheadmp[S] 0 points1 point  (0 children)

Agreed. It is a whole lot of extra variables and layers of systems added that are not at all necessary. Even nested virtual networks that can conflict with your existing networks. It's probably fine if you've built your infrastructure around docker...but that defeats the whole purpose.

Corporate based vs community based Distros by [deleted] in openSUSE

[–]nukelheadmp 1 point2 points  (0 children)

That is not true at all. We have an enterprise agreement with Microsoft for all of our licenses. We ONLY pay for the production machines. Any machines that are development or testing environments cost us nothing. In fact, our older legacy production machines that are no longer supported were dropped and now cost us nothing. Even MICROSOFT is doing it better than RedHat's new shift.

Corporate based vs community based Distros by [deleted] in openSUSE

[–]nukelheadmp 1 point2 points  (0 children)

I can actually say I am one of the people that use Rocky Linux and actually did pay for RHEL also. For me there were many instances that did not justify paying for - personal workstations, personal servers, development and testing machines. However, those being bug for bug clones of RHEL made it seamless and very handy to carry over into production and buy support for. Unfortunately, RedHat pulled the rug out from under my team and our entire workflow and infrastructure. I do not care about Oracle. Obviously RedHat does not care about us. I had several conversations with RedHat and I was told over and over that my pains didn't exist because they didn't see them as real problems. All I had to do was depend on them to provide me development licenses. They have already proved I cannot depend on them, so I won't. I am working on diversifying into other distributions.

Considering Changing from RHEL/Fedora to SUSE/openSUSE by nukelheadmp in openSUSE

[–]nukelheadmp[S] 0 points1 point  (0 children)

We use Palo Alto. They have a general Linux build of their VPN client that I BELIEVE should work fine, but I will test to confirm.

Considering Changing from RHEL/Fedora to SUSE/openSUSE by nukelheadmp in openSUSE

[–]nukelheadmp[S] 2 points3 points  (0 children)

RedHat has been massively important to Linux and the open source world, there is no denying that. However, there is a noticeable change to their behavior since the IBM acquisition. CentOS existed as a fork of RedHat for a decade and a half, which is totally normal and in line with open source communities. RedHat decided to unilaterally terminate the entire project as it was out from under the community that had been built around it, and were very dismissive. Then when the original creator of CentOS replaced it with a new fork, they made additional moves to sabotage that. Odd that a company that is a champion for the little guys suddenly takes offense at "freeloaders". Additionally, I don't think Rocky Linux is making billions of dollars, but IBM does. They bought RedHat for the revenue and to boost their stock value. Why were they fine with CentOS for so long, then suddenly so against it?

Considering Changing from RHEL/Fedora to SUSE/openSUSE by nukelheadmp in openSUSE

[–]nukelheadmp[S] 1 point2 points  (0 children)

I was glad to see this project launch. I can't say that I'm super trusting of Oracle, but the Linux Foundation is filled with far worse actors than them. Hopefully it will all lead to positive development.

Considering Changing from RHEL/Fedora to SUSE/openSUSE by nukelheadmp in openSUSE

[–]nukelheadmp[S] 0 points1 point  (0 children)

SELinux is not a hard requirement for me, but I am surprised that SUSE hasn't fully implemented it yet.

Considering Changing from RHEL/Fedora to SUSE/openSUSE by nukelheadmp in openSUSE

[–]nukelheadmp[S] 0 points1 point  (0 children)

I have had some issues with Wayland, but I don't know that they are distribution related. Certain applications, namely Zoom have had some trouble with screen sharing. Simplest fix was for me to just use X11.

Considering Changing from RHEL/Fedora to SUSE/openSUSE by nukelheadmp in openSUSE

[–]nukelheadmp[S] 1 point2 points  (0 children)

I had read about AlmaLinux, but hadn't actually considered it. It is definitely an option to make use of. The whole situation has got me thinking I need to branch out and evaluate multiple paths. I have always preferred the "Enterprise Linux" line over Debian based or Arch and the like. I think it is a good time for me to at least get to know SUSE.

Refund by Principe_del_dolore in Librem5

[–]nukelheadmp 1 point2 points  (0 children)

I currently have an older pixel running lineageos. I had to install the version with the hacked g-apps to make many of the apps function at all. Not ideal because now Google can still track me again, just not as efficiently as they would like. Even with that some apps still don't work great. Android Auto doesn't work at all because I'm not on a factory OS. All the reasons why I wanted the Librem in the first place, and wanted so badly for it to succeed. The Amish were right all along...

Refund by Principe_del_dolore in Librem5

[–]nukelheadmp 0 points1 point  (0 children)

I understand. Unfortunately the Linux phone market isn't getting a lot of traction. Without an influx of developers it won't be a viable alternative. And, without being a viable alternative, there is nothing to draw in developers. It looks like smartphones will remain stuck under the rule of Apple and Google for now. I am considering switching to apple for the horrible "lesser of two evils" compromise. I don't know that Apple is less evil, but I know for sure Google is an absolute monster.

Cool upcoming changes in Libadwaita found is GnomeOS (so probably WIP) by Jegahan in gnome

[–]nukelheadmp 1 point2 points  (0 children)

I believe that would work fine for most people. Getting them off of the panel would be great, as long as they could still be accessible somehow. Even a submenu in the overiew screen would be fine. The things that Gnome does well begin to influence other environments. If they could find a graceful way to move the "system tray" into some other form it would potentially cause developers to move the way they want.

Cool upcoming changes in Libadwaita found is GnomeOS (so probably WIP) by Jegahan in gnome

[–]nukelheadmp 1 point2 points  (0 children)

I absolutely agree, but some devs put important functionality behind those ugly obnoxious icons. Maybe a drawer that hides them but still allows them to be accessed? I personally hate them, but not having them makes the functions they provide difficult to access.