Pretty much every industry works by tricking people into liking things.

Like the razors with four+ blades on them, people buy them cause the commercials say "more blades is better".

People wouldn't seek out extra blades if they weren't tricked into liking it. They are objectively worse than single blade razors.

Oof that stance on dependency resolution is a big no for me. As much as I hated building gnome from source it was amazing that Gentoo can do that in a single command.

Ah my mistake. I'm just generally curious about what distros use an alternative to systemd (not that I have any issues with systemd myself but I like variety).

So I googled what init system Slackware uses and read this page.

http://slackware.com/config/init.php (no https)

They mention several scripts on that page and that's why I thought they use scripts.

But I haven't actually used the Slackware yet. Suppose I should though since I'm interested.

I was reading about Slackware today and it seems their init system still uses system V and lots of scripts.

So I'd definitely recommend that OS to anyone curious about the old style of init system.

I tried both. They have the exact same questions.

However the one op posted respects the "I don't want systemd" request. And I personally prefer to get multiple answers.

But the mobile webdesign on ops posted link was not great. So it's a wash for me.

I've definitely made similar errors dual booting. I don't know what your budget or hardware is like but if you can fit a second hard drive in your computer it is very worthwhile for distro hopping.

The second hard drive will let you install whatever boot loader the USB installer wants to install without overwriting the bootloader on the first hard drive.

Modern grub is pretty magical and should detect both OSs either way.

But yeah that's why there are so many warnings in every Linux distro about installing grub. You do not want to mess with a currently working bootloader.

This is mostly because the bootloader needs to be in a very specific location on the hard drive and so you can't just install it anywhere. Which means you have to overwrite the old boot loader if you choose to install a new one.

I'm gonna try these out. The history search one is cool.

Plus I had no idea you could use args in an alias. I had to make a function in my .bashc the last time I needed args.

Thanks. I see the word boot is referenced 200 times on the related manual page. So I suspect a thorough read through of that page will help me.

Alright thanks. Well if you know of any good resources for xorriso particularly with the -b (boot) flag I'd like to read them.

Google has been mostly serving me 15 year old SO posts that aren't relevant to modern Linux anymore.

I found Gentoo more helpful than LFS because with LFS you compile about 80 packages from source one at a time but you don't learn too much about the packages.

LFS gave me much more awareness of what packages actually come with a Linux install but Gentoo taught me more about configuring and booting a Linux system.

Although I'd definitely recommend both to anyone wanting to learn. I'd do Gentoo first then LFS.

Edit: LFS is also a masterclass in cross compiling so if that's something you're curious about LFS is the way to go.

I've been struggling to make a bootable iso. I did Linux from scratch and I wanted to boot it in virtual box. I found a sparse amount of info about mkisofs/genisofimage but I couldn't actually get a successful boot after following a few tutorials.

I have to imagine there are more modern tools for something like this but I didn't have any luck googling.

Sorry to hijack but it sounds like you might have an answer I need. I just want a way to put together an iso with a bootloader that works in virtual machines. (I'm good with 32bit grub but I'd work with uefi too).

Viruses don't need to be .exes by the way. There were spectre/meltdown proofs of concept that only ever used front end JavaScript.

Because the modern style of CPU attack (zenbleed too) usually side chains access to private memory (where your authentication details exist) they can get full system control without executing any .exes.

That computer would need a firewall disabling all incoming traffic, the latest bios firmware patches and js disabled on Firefox to be close to safe. And that's the base level stuff.

Edit: changed VPN to firewall. That was silly.