nanook

@data1701d Ok in that case, boot the os off of a USB and mount all the partitions, start with root on /mnt, then any other partitions relative to /mnt as they would be to root, then mount --bind /dev /mnt/dev, mount --bind /dev/pts /mnt/dev/pts, mount --rbind /sys /mnt/sys, mount --rbind /proc /mnt/proc, and then cp /etc/resolv.conf to /mnt/etc/resolv.conf, now chroot /mnt. Once there remove all existing versions of grub and install grub-pc, which is the bios version, next do grub_install /dev/sda or whatever your primary drive is, then exit chroot and halt the system. Now you should have a bios bootable system you can boot on your bios device.

Ubuntu will boot on either legacy or UEFI.

@MangoPenguin Same thing that happens to your car motor when you slam the accelerator from a dead stop rather than gradually accelerating and maintaining a steady speed. Everyone knows stop-and-go traffic is hard on cars, disk drives too.

When you spin up the drive, the motor has to overcome the mass of the disks to bring them up to speed, requiring more torque, current, and wear, than just keeping them at that speed. On the other hand, bearings don’t wear out at zero RPM. Bearings go, motor goes, either way drive is dead. Regarding bearings ALWAYS mount drives so that they are horizontal, this results in minimal bearing wear and load.

I don’t know how clonezilla works, but one thing I’ve discovered that causes issues when you copy a Linux distro from one machine to another, assuming you do a file system copy and not a raw partition copy so the new file system partition has a different UUID than the old, you need to fix the UUID in both /etc/fstab and /etc/initramfs-tools/resume before it will work properly.

@delirious_owl @gwilikers I’ve been trying to setup a store and forward server with postfix and not having a lot of luck.

@IceFoxX @merthyr1831 I just keep a handful of color coded thumb drives. I know the red one for example is Ubuntu-Mate 24.04, the black one Win10, the yellow, Gparted Live disk, the Green Boot-Repair, etc.

@NOOBMASTER @Artemis_Mystique So google can make money.

I have several machines with Nvidia GPUs, they are all working fine, one thing I like about Intel internal graphics that you can’t do with Nvidia is to use pass
through of virtual GPU’s to get OS’s in kvm-qemu virtual machines, giving the ability to play Windows video games in a virtual machine with usable performance.

From what I’ve read 1e100.net belongs to Google, so yea it’s a virus.

@sxan @beta_tester EXACTLY, I am glad SOMEBODY gets it.

What it means is that you’re getting the libs the program uses with the program instead of using the system libs, this defeats the whole point of shared memory and wastes RAM, it is inefficient but saves them from having to compile for each distro, still, the system loader has to resolve and load these making loading slower, if they had to include the libs, a better way to do it is to simply compile the binary as a static binary with all the libs compiled in, at least that way it saves the loader overhead.

They sure are huge on my system and spread their shit over half the file systems. Firefux is a complete disaster now that it is flatpack.