- Joined
- Dec 3, 2021
Having to label nonsensical edgy trolling as "hate speech" is a great example of how lobotomised PC corpospeak is, totally mischaracterises this as some kind of serious political statement of chudliness.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
to be fair, overwriting permissions on a system folder is generally a bad idea. media/ is used to automatically mount any plugged in drivesI kinda hate how finicky permissions are in Linux. I changed permissions in /media/ to give me read/write permissions but it completely broke my install in Mint. I saw someone jump off a bridge to his death 2 years ago right in front of me and I could only assume he did the same thing as I did.
I didn’t change permissions for anything else but that folder so how it fucked up my entire install is beyond me. I had an issue with permissions after trying to go into gnome disk tools and manually setting the drives to mount at system startup and it telling me to eat shit and die.to be fair, overwriting permissions on a system folder is generally a bad idea. media/ is used to automatically mount any plugged in drives
I kinda hate how finicky permissions are in Linux. I changed permissions in /media/ to give me read/write permissions but it completely broke my install in Mint.
It's hard to figure what's going wrong based off of the little that you said.I didn’t change permissions for anything else but that folder so how it fucked up my entire install is beyond me. I had an issue with permissions after trying to go into gnome disk tools and manually setting the drives to mount at system startup and it telling me to eat shit and die.
It's hard to figure what's going wrong based off of the little that you said.
If you could offer more information (redacting anything personal), what are/were your errors exactly? If you have logs/error messages, could you post them? What permissions did you set on /media/ and/or it's contents (or what commands did you run to do so)?
Maybe you fat-fingered the command and did chmod <...> / media instead of /media. It wouldn't necessarily have instant effects, but the next boot would fail catastrophically. I know systemd also likes to occasionally mount random crap in /media, so that might also have caused problems, but I've never heard of it completely failing because of that.I tried pulling up the journald to see the logs but nothing came up. I ended up being forced to reinstall mint and when I changed permission’s everything worked just fine.
I might be a little retarded, yes.Maybe you fat-fingered the command and did chmod <...> / media instead of /media. It wouldn't necessarily have instant effects, but the next boot would fail catastrophically. I know systemd also likes to occasionally mount random crap in /media, so that might also have caused problems, but I've never heard of it completely failing because of that.
NVIDIA today published their first R545 Linux driver beta series with a number of shiny new features.
The NVIDIA 545.23.06 beta Linux driver was just posted as what will be their next feature series. With the NVIDIA R545 Linux driver series come a number of exciting features:
- Experimental HDMI 10 bits-per-component "deep color" support can be optionally enabled using a new "hdmi_deepcolor" module parameter.
- Support for CTM, DEGAMMA_LUT, and GAMMA_LUT DRM-KMS CRTC properties that are used for the GNOME and KDE Night Color / Night Light features under Wayland.
- The NVIDIA Open GPU kernel driver support using the open-source out-of-tree kernel modules is now considered to be beta quality for GeForce and Workstation GPUs.
- Experimental support for run-time D3 (RTD3) power management for NVIDIA desktop GPUs.
- Experimental support for frame-buffer consoles provided by the NVIDIA DRM kernel driver. This will replace the Linux boot console driven by the system frame-buffer.
- Support for the NVIDIA Linux installer to allow installing the driver when an existing NVIDIA driver is already loaded.
- Support for virtual reality (VR) displays such as SteamVR when using Wayland compositors with DRM leasing support.
- Fixing Variable Rate Refresh (VRR) support under Wayland.
- Support for using NVIDIA VDPAU video decoding when running in XWayland.
- Various bug fixes and other improvements.
Hopefully this will mean we'll finally get high-resolution boot consolesNew NVIDIA beta driver adds a bunch of new shit.
Last month I was playing around with Mint on a small computer. I wanted to upgrade the kernel, but it said there were not enough space left on the /boot partition... so I deleted everything related to kernels. When I ran apt-get install, they said I was missing "vm-linuz" files and thus couldn't update my system.I tried pulling up the journald to see the logs but nothing came up. I ended up being forced to reinstall mint and when I changed permission’s everything worked just fine.
It happens to all of us. Inevitably. I once wiped my entire home NAS with a misplaced /, back before rm complained if you tried to rm -rf on root. So many lost movies...I might be a little retarded, yes.
That's what backups are for.It happens to all of us. Inevitably. I once wiped my entire home NAS with a misplaced /, back before rm complained if you tried to rm -rf on root. So many lost movies...
Backups didn't exist in 1999. We just prayed the drive would last until we could afford a new one.That's what backups are for.
I've gotten messed up a couple times before I fully internalized that "/file" is absolute location and "file" is relative locationIt happens to all of us. Inevitably. I once wiped my entire home NAS with a misplaced /, back before rm complained if you tried to rm -rf on root. So many lost movies...
Ooooh, does this mean we're finally getting it? Maybe I'll get a 4090 and it finally won't be unable to open so much as a spreadsheet!The NVIDIA Open GPU kernel driver support using the open-source out-of-tree kernel modules is now considered to be beta quality for GeForce and Workstation GPUs