They’ll appear removable but if you don’t put users in the option it shouldn’t be unmountable.

I’ve read some posts about editing fstab to mount them at startup, but they don’t cover whether the drives will be available to other users or not. Can I just add them to fstab and mount them somewhere that’s available to all users, then sort out the permissions? If so, where’s the best place to put them?

Yes pretty much. It just explicitly tells the system where to mount it, and for some filesystems you can even force the UID/GID and modes.

Usually /mnt/whatever for static mounts and /media/whatever for removable mounts (those appear as drives in file managers, whereas /mnt doesn’t). You can set the users option in fstab and it’ll let users mount and unmount it without sudo as well, or auto to always mount it on boot.

From there usually you can make a shared group, chown the mount to root:thatgroup, then chmod g+s to make sure the group is inherited. And you should mostly be good to go.

Patience. It really helps to have all the latest set up: SPF, DKIM, DMARC. Then after that it’s a matter of IP reputation, you can email the various blocklists and you wait for the rest of them to clear on their own.

I’ve had that IP for 10 years and it has never sent spam, and I’ve sent enough emails that people open that it actually does get through fine. I haven’t had to think about it for a long time, it just keeps on working. Barely had to even adjust my Postfix config through the upgrades.

The developer benefits from reaching more people, some of whom are likely to purchase the proprietary license. Or sometimes you dual-license just so that licenses are compatible. Each license has pros and cons for both the developers and the users.

Qt for example, the LGPL means you need to dynamically link to it, and if you ship your own Qt libraries you must provide the source code for it. But if you’re a company that writes proprietary software and can’t dynamically link, then you can purchase the proprietary license which allows you to do a lot more, but you’re compensating the devs for it. And for the Qt devs that’s good because either you pay them, or you use it for free but must share your changes with everyone.

For ElasticSearch, that makes it so Amazon can’t just patch it up and sell the modified version without sharing what they changed. They wanted to add back a FOSS license to stop the bleed to OpenSearch which many in the FOSS community switched to purely for the license because even separate software should be compatible license-wise if you want a sustainable FOSS project. But the AGPL requires sources merely for being able to talk to it over the network, so Elastic gets the free dev work, or the juicy license payments. The other free licenses achieve similar goals with technical differences that might matter for the user. But as a developer using ElasticSearch maybe you do want to ship your software under the SSPL, so you can pick the SSPL version.

Dual-licensing MIT/GPL for example, you can build proprietary software, or GPL software where you can vendor it in as GPL-only as well, and thus guarantee your user their GPL rights.

The SSPL is irrelevant, you pick the AGPL license and the SSPL doesn’t apply to you.

Qt is dual-licensed as proprietary and LGPL and nobody complains about that, KDE is in most distro’s repos. You pick the LGPL licensed version and you’re good to go, the proprietary license doesn’t apply to you.

I consider it to be AOSP. It’s not super usable, it misses some important apps by default. But base means bare minimum to have a launcher and being able to install your own apps, even if that includes providing your own dialer and camera and music player and stuff. AOSP does that well, it’s the base, the starting point to make a ROM.

It depends where you draw the line of what is GrapheneOS. Everything they do is free and open-source. If you build it for emulator or Waydroid, it would indeed be FOSS: no proprietary blobs in sight unless you count your host’s GPU firmware to taint the whole thing. The build scripts to dump your firmware blobs from your own device, building GrapheneOS, bunding it all back together, sign the build and flash it on your device, all open-source.

The only part where blobs are involved is the downloadable prebuilts which does include the blobs otherwise it wouldn’t boot at all. They’re not including blobs in their project. They’re including the blobs that are already on your device and also downloadable from Google. It’s not like they made their own proprietary blobs they hide the source for.

The GNU guys say that’s unacceptable as any proprietary software is unacceptable, therefore the whole thing is tainted and worthless. They think the same thing of coreboot/libreboot.

In my opinion, GrepheneOS is fine. It’s the best that can be done, and their project in itself is FOSS, even if running it on actual hardware requires a few blobs to be added, and it allows users to opt-in to installing a sandboxed Google package. The same I call Linux FOSS even if it can upload a firmware to my GPU so amdgpu works. At least the entire loading of the firmware is in my control, and I can verify that the blob being uploaded is the one I expect, even if the blob is proprietary.

Nothing that you replace with GrapheneOS is proprietary. The blobs are a no-op. Running sandboxed proprietary code is better. It’s a net positive and reclaims some of your freedoms by being able to control and monitor the sandbox.

If they want to see my green screen colored walls, it’s up to them. I think the background looks better when it’s dark abstract art, less distracting than bright green.

How can one not have a clean desk when working remotely? Do people just print random documents for no good reason when you can just have it on the screen?

I don’t even think my work would even let me plug in a printer to my MacBook, they disabled all the USB drivers except mouse and keyboard to prevent usage of flash drives and other unauthorized peripherals.

They made damn sure the only thing displaying sensitive information is the computer screen, which automatically locks after 5 minutes and cannot be configured by the user. I’d really have to willingly show company data for this to be a problem.

That really shouldn’t matter at all for remote workers as everything should be self contained in the company provided computer, with encryption enabled, strong password policy, 2FA, the whole thing.

It looks like you’re looking at the entire PolyMC process group so in this case memory usage also includes PolyMC itself, which buffers a chunk of the logs. It shouldn’t be using that much, but it will add a hundred MB or two to your total here as well.

When you control the memory allocation for Minecraft, you really only are configuring the JVM’s garbage collector to use that much memory. That doesn’t include any shared resources outside of the JVM, such as Java itself, OpenGL resources and everywhere else that involves native code and system libraries and drivers.

If you have an integrated GPU, all the textures that normally gets sent to a GPU may also live on your regular RAM too since those use unified memory. That can inflate the amount of memory Java appears to use.

A browser for example, might not have a whole lot of JavaScript memory used, couple MBs maybe. But the tab itself uses a ton more because of the renderer and assets and CSS effects.

Also, lame article? 😖

It’s pretty short, it could be improved with benchmarks or at least some examples of how that would be implemented efficiently. Maybe a bit of pros and cons, cursor pagination for example doesn’t handle “go directly to page 200” very well. I’ve also seen some interesting hacks to make offset pagination surprisingly fast with a clever subquery.

I wouldn’t call it lame though.

A bit of an extra tidbit of information, that’s why things like /usr/local exists: to keep things separate from the distro provided packages. A lot of things have directories in /etc for the sole purpose of isolating “what the distro provides” vs “what the user provides”. Often you can mask distro-provided settings by symlinking the same in /etc to /dev/null.

So it’s best to assume /usr is managed by your package manager and you shouldn’t touch it because it’ll be overwritten on next update. Or in the case of immutable distros, you can’t even write there yourself.

Plus when you do backups and restores, you can backup /etc, reinstall your distro, then restore your /etc and you should mostly end up back where you were.

If you use ext4 or other filesystem that supports fscrypt, you can use fscrypt to encrypt specific directories.

There’s also gocryptfs for a fuse-based userspace implementation.

ZFS has built-in encryption: https://klarasystems.com/articles/openzfs-native-encryption/

Don’t overwrite system files managed by pacman and it won’t break your setup.

Put your script in the corresponding place in /etc where it’ll be handled properly, or better yet, do it correctly and set it up directly in your xorg.conf config. Or just use localectl set-keymap dvorak which will do the same thing but also handle non-X11 use cases such as the virtual consoles and Wayland.

PDFs are inherently not designed to be edited, the format lacks a lot of the information necessary for layouts to work correctly and as expected.

That’s why you have to open it with LibreOffice Draw, and the mess you see is basically the information that’s contained within the PDF. It is just a bunch of random text cells randomly placed over the page. That makes it really difficult to get back an editable version that’s sensible. Page wraps and such will never work correctly. Your only chance at recovering it is if you can figure out what software wrote it, and how different constructs might end up when translated to PDF and a lot of heuristics.

I believe they open a bit better in Xournal++ but it still sucks.

Those that do build such tools realize it’s all big companies with big budgets that really have a serious need to do this, so they tend to be proprietary and expensive, and still not super great.

I would really beg for the files to be provided in a suitable format for editing.

I switched as a kid too, but that makes it really easy because I never ended up depending on a bunch of proprietary Windows only apps. I never learned stuff like Photoshop and Illustrator and Premiere, not even on pirated versions like most kids do. Photoshop CS2 technically ran under wine but the experience was so miserable I learned GIMP instead. My last Windows was XP.

The older you get the more “serious” software you have too, like tax stuff, the whole Windows-centered workflow at work. The deeper you are into the ecosystem the worse it is.

The issue I see over and over and over is not that using Linux in itself is that hard, it’s dealbreaker software and hardware. Oh your capture card isn’t supported. Your audio mixer’s not supported. It sucks. So basically what OP said: you have to switch to Linux friendly software first, then it’s basically just swapping the OS and not flipping your entire computing experience over.

The major problem with dual-booting is if you get lazy and end up never booting the Linux install. Sure you can do most stuff on Linux but Windows does all your stuff, so you end up with “I might play after those YouTube videos” and boot into Windows to save the possible upcoming reboot. And then you’re always on Windows.

But it’s a very good option if you can manage to get yourself into the opposite situation: avoiding having to reboot into Windows and find workarounds and alternatives.

Both GTK and Qt have good Python bindings.

GTK example: https://github.com/Taiko2k/GTK4PythonTutorial

There’s also PyQt but it looks more complicated and I couldn’t find as nice and straightforward of an example as GTK but I found this: https://realpython.com/qt-designer-python/

If you want to go to C, GTK works about the same way. If you want C++, Qt is pretty good there.

Otherwise you can go SDL and just put whatever pixels you want on the screen on your own.

The worst is it’s not even like you buy a share of a single unit to share and keep well maintained, it effectively behaves like a hotel you have a stake in and and get to go 1-2 weeks a year for free and they’re usually quite poorly maintained too.

For some reason boomers thought it was a good idea, because gotta buy and own properties. I guess the idea was you could buy a vacation home but for only the few weeks a year you really want it.

It’s such a con, if you inherit it from your parents it’s really hard to get rid of it too, because nobody wants them now that it’s well known to be bullshit. You might as well just rent an Airbnb, it’s probably cheaper.