• 0 Posts
  • 55 Comments
Joined 6 months ago
cake
Cake day: March 30th, 2025

help-circle
  • @pastermil If you want a newer kernel than is provided in the apt package manager, you can download the latest from kernel.org, unxz it with unxz kernel-version.tar.xz, then untar it. It will give you a directory like linux-6.14.6, cd to that directory and do a make mrproper to remove any residual crap that might have been left there by the maintainer or a previous build, then if you want the stock debian configuration copy the current config file from /boot to .config, then make any adjustments to the .config, including some automatic adjustments that get made for your environment with make config, make menuconfig, makexconfig, make gconfig, whatever you prefer. For xconfig and gconfig which are graphical configuration GUIs you may need to install some libs that aren’t installed by default on Debian but ARE provided in your apt package manager. Then make -j$(NPROC) bindeb-pkg, for example on my machine 18 cores, 36 threads, I would do make -j36 bindeb-pkg to fully utilize the CPU cores, on the 18 core machine this takes about 7 minutes, on my 8 core workstation about 18, when it’s done you’ll be left with three or four .deb packages (depending upon whether or not save DEBUG is turned on or off in the kernel config). When you are done install the packages with dpkg -i *.deb, check /boot and your new kernel should be installed.








  • @FooBarrington You didn’t just specify memory safe, you advocated stripping away a number of features. Yes memory safe anything is a good idea and I’ve got no objection to the use of rust, I think it’s a good language, one of the few worthwhile efforts to emerge in recent years, but if it is going go be re-implemented, do so fully. Yes, anything that runs with privileges should be memory safe else it’s open to attack and Rust certainly makes that more possible, I am just concerned about the limiting feature set aspect. I’m not in favor of protecting users from themselves, I don’t want a car that is capable of reading speed limit signs and prevents me from exceeding them even if doing so might be unsafe or illegal, that not the car manufacturers job to be come an arm of the government, likewise I don’t want Linux protecting me from myself, I already address potentials with regular backups, etc.





  • The BIOS does not know about the RAID, the is why the EFI partition has to be a regular partition, but there is nothing forbidding more than one EFI partition so simply duplicating that across both drives ensures the same redundancy the RAID offers, but GRUB DOES know about RAID 1, so if you setup a raid1 array as the boot partition and then just write the boot block to both drives along with the EFI partition you can RAID everything except the EFI boot partition. Sorry your motherboard reduces your speed if you have more than one nvme, sounds very odd. Mine does share bandwidth if the SSD’s are SATA but NOT if they are nvme.



  • You don’t need a RAID controller, I have dual NVME set up with RAID1 and boot off the RAID one partition, the only partition I can’t raid is the EFI partition because BIOS doesn’t know about it, but that I simply duplicate by hand on both drives using dd, since it only gets updated at kernel updates, it just adds a dd to the kernel upgrade process.