Removing the Bootloader and other Projects

[@RazoBeckett.]

"This could break the system" ... Titus: "Oh yeah, TRY ME" 🤣

[@hexisXz]

Titus in a nutshell

[@MouseHunteR77n]

Don't worry Chris I'm enjoying some of your old videos 😉 Thank you

[@trenthekman2334]

The archinstall script has an EFI stub option. Which I just started using recently, and it's great.

[@HaroldCrews]

That's the benefit of an immutable/atomic OS. If you have a kernel update that breaks something, just roll it back to a prior image. I'm loving Bluefin so far and always keep three images pinned. Universal Blue has images for Framework laptops.

[@MrAlanCristhian]

Debian already give you the option to boot from an older kernel.

[@ehtrude]

Please add an option to linutil that removes Debian bloat and/or switches to testing/Sid. That would be really useful. Great work as always, anyways!

[@DarinMiller]

The suspend/resume issue occurred post 6.6 kernels and affects more than Xenon processors. It is still an issue with the latest kernel release 6.11-rc7. Bug report submitted but no traction. (using an AMD 7800X here with said issue. 4 other PC's with mix of AMD and Intel processors are working fine...)

[@th3Tyk3]

I've run Arch on my Framework 13 AMD for about a year now and I've never had an issue. Not even small ones.

[@maxpoulin64]

Re: autologin and display managers: some distros have per-user encrypted homes which makes a lot more sense to have a login screen and password prompt. My laptop auto decrypts the root partition through TPM, and it also decrypts my home ZFS dataset and mounts it through PAM upon login in SDDM using the login password. Once the session ends, it's unmounted and the key forgotten. Same process happens for any user that logs in, or even guests, and the worst one can do is destroy the entire dataset. Without encryption, if you lock down the BIOS and other users don't have root access, then it's also harder to break into as you'd need to take the drive out of the machine to backdoor it which is more effort and can't be done discretely if it's a shared computer in an office or something.

[@pavelskripec7133]

Congrats for the run script numbers ;)

[@archygonzalez3086]

RHEL/Fedora partition scheme is derived from a base "Kickstarter"/"Kickstart" file, if user wants different scheme user should modify or create the file. But if file is provided it needs to include all installatioon base configuration its not as simple as just the partition scheme. There are sample files on Fedoras RPM/Git type thing. Or if user is subscribed to RHEL's developers site theres an automated online form app to create that file PS: There's almos none documentation on the subject. I got to know it due to an IITPro TV course I took on basic RHEL Sys Admin. Fedora documentation is very behind an almost any subject on their documentation section or if its present its very basic or surface level explained

[@mobilturka]

Would you review Turkman Linux?

[@norikoteiko3791]

I decided to boot directly into a unified kernel image on artix a while ago you since bootloaders are just bloat😂 ... broke the bios on my asus notebook wasent been able to acess my bios afterwards would just freeze ... so i had to manually remove the entry via efibootmgr and reverted back to grub

[@FreshTattoo71]

good morning

[@adjusted-bunny]

Chris, what is your goal today?

[@genericgamer1319]

i thought he was gonna remove the bootloader & use the UEFI boot manager + the kernel image thus dodging having to use a bootloader oh wait he actually did

[@Aoitori365]

fyi the linux util's install dwm-titus does not work right on fedora based distros

[@Johan87577]

Solution: go to arch 🥲💀

[@H3cJP]

let me guess, efistub i love it, i no longer have to deal with grub and the boot is faster because i dont have a non-point grub, i had always wondered why grub existed for choosing what to boot... like when i learned about how uefi works, and that it uses .efi files that launch the bootloader, either grub or the windows bootloader or something else so i wondered why the fuck was grub needed instead of loading directly the linux kernel... turned out it wasnt actually needed

[@jackknight7070]

framework already baked

[@Johan87577]

That’s a early stream for you in the US lol

[@CVLova]

if u are going to make a discord ever again, u need very strict rules, like VERY.

[@TuxCraft-tech]

blah-blah-blah

[@shrikedecil]

This all *screams* 'NixOS' to me. Two hours in you give a detail view somewhat like: "I want it to be a rock. A reliable, crash-free lifeboat." And then talk about pulling this in, and that in. The problem from the NixOS side is "Yeah, you can get that all to work, it's the switching and swapping that is tricky". ... But. ... You're making a nice switching and swapping util?