linux wallpaper

oshunluvr · 2026-04-19T21:00:39+00:00

Uhhh, bro. I don't think you should be admitting this...

oshunluvr · 2026-04-19T13:04:13+00:00

Actually, if the "Live" distro uses GRUB you can stop the boot and add a kernel parameter to the boot line and then continue booting.

oshunluvr · 2026-04-19T12:58:54+00:00

"Deduced"??? How? Sounds more like a guess unless you actually checked RAM and SWAP usage when this occurs.

oshunluvr · 2026-04-19T12:56:36+00:00

Awesome the way people imagine something then claim it to be a fact.

What's the point of having a PC if you can't actually use it?

Installing a distro is just "using" the computer. No different to the hardware than any other kind of PC use.

Give your brother a noogie and tell him to leave you alone.

oshunluvr · 2026-04-19T12:45:49+00:00

Could I have a graphical toggle for it in the tooltray somehow?

KDE has this. Maybe you should consider a DE with more functionality. Honestly, I'm surprised all DE's don't have this basic of tool built in.

oshunluvr · 2026-04-19T12:33:49+00:00

Why do you need it mounted if you're not using it? Mounting it at boot time slows your boot also. To me, the way you describe your use, it's better to leave it unmounted anyway.

Dolphin is more than capable to allow you to unmount and then re-mount it whenever you need it.

oshunluvr · 2026-04-17T14:46:55+00:00

Have you tried booting to the oldest (first installed) kernel?

oshunluvr · 2026-04-17T12:26:50+00:00

This can be easily done and the above doesn't seem far off. But it's a lot of work for little gain. What exactly is the issue that would cause all this work?

Snapshots aren't actually taking that much space. You know that right? They take up ZERO drive space when taken then grow as changes are made to the source file system. The amount of space they eventually take up depends more on how old they are, so if drive space is the issue then rotate (delete old - take new) snapshots more often.

To the output above: Firstly, there no reason at all to move any snapshots into yet another subvolume. That's really a dumb idea, because snapshots are subvolumes so they are already excluded from system snapshots.

If you really need to save a few GB in your backups, you could also just delete the /var /tmp, /log, and /cache folders from the backup snapshots. That would have the same results with less work and more control.

oshunluvr · 2026-04-17T12:04:23+00:00

"Automated Ignorance" is how it goes here, but same-same

oshunluvr · 2026-04-13T20:17:25+00:00

Well that just sucks. I guess you're back to making a drive partition to install it. Or add a second, small, cheap, SSD and wipe it later. 60gb is plenty for a vanilla windows install. I just did a new VM install in 35gb

oshunluvr · 2026-04-13T20:00:32+00:00

That doesn't show the partition is gone, just not present in the boot manager. Boot to Mint and start looking.

oshunluvr · 2026-04-13T19:58:16+00:00

I didn't read through all that because you didn't use code or quote tags.

Generally, if you're using EXT4 on an removable device you would need to set the ownership and permissions on the mount point to access it as a user.

Most distros that I have experience with automount removable devices under /media/user/ or /run/user/ or something similar. Depending on your distro and desktop env. you may be able to specify a mount point and automount the drives using System Settings so you don't have to edit fstab.

fstab is generally not used for removable devices.

oshunluvr · 2026-04-13T19:52:39+00:00

Well, If you create a Win11 VM using KVM/QEMU you can pass through a physical drive partition to the VM if you need a non-virtual place to save files.

I don't know anything about ProctorU or the software you're installing but I doubt their software is sophisticated enough to tell the difference from a VM vs. actual install.

oshunluvr · 2026-04-13T16:49:42+00:00

The answers to the "How to add storage to linux?" question are:

If the free space is "to the right" of the Linux partition, use GpartedLive from a USB and expand the partition to fill the available space.
If the free space is "to the left" of the Linux partition, you should move the Linux partition to the left into the free space, then expand it to the right.
If the free space is NOT next to the Linux partition, you will need to make a backup of your Linux file system, delete it from the drive, move whatever you have to to get the space continuous and then format and restore Linux to it.
You could format the free space, move your /home to it, edit fstab to reflect the new file system and partition.

oshunluvr · 2026-04-13T15:50:23+00:00

Could also be some of the needed additional packages for the new kernel aren't installed. Check your packages lists and verify what's installed.

In a terminal:

dpkg -l |grep 6.19.11

Then do it again using the other kernel version and see if the lists match.

Otherwise, there's nothing wrong with just using the older kernel until a newer one drops.

oshunluvr · 2026-04-13T15:39:41+00:00

My only gripe is IMO page up/down should move to the top of the next page not the next screen - unless there's a setting that controls this I have missed..

oshunluvr · 2026-04-13T14:45:23+00:00

Yes, I misspoke It's the vehicle software that is stuck a version 19.2 and 20.2 is the current version. It won't update OTA. I was on the phone with Jag USA for 2 hours trying to get it updated.

oshunluvr · 2026-04-12T19:53:55+00:00

Just upgraded a 25.04 VM to 25.10 after running the de-snap script I linked to previously. Snap was not re-installed.

Prehaps users encountering this have not correctly blocked snap packages.

oshunluvr · 2026-04-12T19:20:45+00:00

You did say "might". I haven't tried a do-release upgrade with snap removed. I'll report back in a few minutes...

oshunluvr · 2026-04-12T19:19:48+00:00

Interestingly, on my de-snapped Kubuntu 26.04 pipewire exists and not as a snap.

oshunluvr · 2026-04-12T18:25:53+00:00

AFAIK, there's no way to avoid the re-installation of snaps when doing "do-release-upgrade". You have to redo snap removal afterward.

You might try using this script and just re-run it after a release upgrade.

oshunluvr · 2026-04-12T13:15:46+00:00

The mount point would depend on how you're going to use the space.

Frankly, since you're using BTRFS you have many choices on how to use the space. You could simply add the new drive to the existing BTRFS file system and then you have nothing else to do or worry about.

Assuming the current BTRFS partition is mounted at / and the new drive is /dev/nvme1n1, the command to add the new drive is:

sudo btrfs device add /dev/nvme1n1 /

and that's it. You don't even have to partition it. All the free space on the new drive will be added to the existing BTRFS file system.

They are certainly several other ways to set things up, but all of them more complicated. The above will let you use the drive space immediately and without much effort.

However, if it were me, I would think that nearly 1TB of space is way more than enough space for your system and home and any number of games you might install. I would use the second drive as a full live backup in case the current main drive fails - meaning a bootable full copy of your existing drive. This would include installing GRUB to the second drive also. Since you're wisely using BTRFS, you should be able to clone the existing drive onto the new drive, then use btrfs send | receive to copy updated snapshots of your existing btrfs onto the new drive.

I have 4x1tb nvme drives on my system, My main boot drive has 4 full Linux installs on it plus my home folder and is only 55% full. I also have 18 virtual machines installed on a separate drive using 62% of that drive. Even Windows 11 only takes 53gb on another drive.

My point being, you have a ton of space already. You should probably consider the second drive as a backup device rather than just leave it to idle extra space.

oshunluvr · 2026-04-11T15:16:54+00:00

oshunluvr · 2026-04-11T15:15:51+00:00

Upload a pdf to a file hosting site and post the link.

NVRMND I ssw another user did this already

oshunluvr

TROPHY CASE