The Linux Thread - The Autist's OS of Choice

Systemd-boot doesn't support any form of scripting or probing, its just a kernel boot parameter text file and the kernel itself, everything is handled by the kernel EFI stub.
Hey, look, we re-invented LILO. It sucked then and it sucks now.

Although even LILO allowed you to chain-load Windows.

All these people saying "Just tell your UEFI to boot the other drive." Yea, that sucks, press F8(usually) at the right time, select the other bootloader, no way to control how long it waits for F8, etc. GRUB lets me set a long timeout so my monitor can finish switching resolutions, can boot anything, can change parameters on the fly if troubleshooting or playing with options.

It's funny that people then recommend: oh just use a UEFI menu program to select what to boot. You mean like GRUB?
 
Hey, look, we re-invented LILO. It sucked then and it sucks now.

Although even LILO allowed you to chain-load Windows.

All these people saying "Just tell your UEFI to boot the other drive." Yea, that sucks, press F8(usually) at the right time, select the other bootloader, no way to control how long it waits for F8, etc. GRUB lets me set a long timeout so my monitor can finish switching resolutions, can boot anything, can change parameters on the fly if troubleshooting or playing with options.

It's funny that people then recommend: oh just use a UEFI menu program to select what to boot. You mean like GRUB?
I'm currently running it like that with my 2 different drives. And yes. It actually does suck doing it like that like you said.

The reason I am, is because every time I have to run os-prober during grub-mkconfig. To find the boot entries on the other drives it takes forever. So I decided the annoyance of that was more than the annoyance of having to catch it in the 2 second window during a reboot to go into my other drive.

Not really happy with that solution either. But idk. It seemed that at one point when I had the other drive mounted actually when running grub-mkconfig with os-prober it was actually fast. So maybe the better solution is write a script to mount the drives before os-prober runs, because however they are doing it, is shit.



Oh. And yes. Arch should update it's wiki, to say, whites only, niggers please install manjaro.
 
You guys realise you could just hold F8 after you press the power button and it will immediately hop into the boot selector?
 
  • Lunacy
Reactions: Betonhaus
The reason I am, is because every time I have to run os-prober during grub-mkconfig. To find the boot entries on the other drives it takes forever.
You could just add the stanzas in manually to grub in grub.d(or your OS equivalent) if they don't change too often.
 
You guys realise you could just hold F8 after you press the power button and it will immediately hop into the boot selector?
At least with mine. It seems to stop before the screen indefinitely if I'm pushing the button. Like not even holding it. If I'm just pushing it every second or half a second. Nothing will happen until I stop wait for the logo screen. Then I can press or hold it, and it does what you said.

Also for me it's f12 but same thing.
 
  • Thunk-Provoking
Reactions: Susanna
If you can't handle the old way, then you're clearly not ready for Arch.
Being real slackware is only for a certain type of autistic these days.

I do like that it is still around to show the old way Linux distros did things. And also gives a very different experience than any other modern distro will give you. If you have a specific set of things you want to do, and those these involve stuff outside of what they provide. You are very much on your own.

For the people reading this, that don't know how slackware does things.

They have their repo, and instead of having a collection of packages they send out in an iso, they recommend installing everything they have packaged from the iso. (It's about 15Gb of programs if I recall correctly). They get updates when they decide they have the next version good enough to send it out. So not exactly like Debian stable where its more or less a long, but fixed schedule. It's just when they feel they have the next version done.

Part of the idea behind installing the entirety of the package is, that, that is what a distro is. A combined set of curated packages. So that is what slackware does. The other reason, why they recommend installing everything is, because while they do have package managers. There is no dependency resolution. So you have to deal with all of that yourself. And if you left out packages you might have actually needed when installing it. Things can get very tedious, very quickly.

There are 3rd party packages managers, that can do that for you, as well as 3rd party binary repos, along with slack builds. Which is basically the aur but slackware as you could have probably guessed.

Other things are also a bit different than what you might expect if you are coming from a more modern distro. Like the way the paths are separated for the root users, from the user accounts. So you are expected to su into the root account to do things like run the package manager. Rather than being able to access them with sudo in your normal account. Of course you can change things like that. But that isn't the default behavior.

There are a lot of other things that are done differently than what you might expect now days. But you can look into it yourself if you are still interested.

Like I said in the beginning of this. It's interesting, and I'm glad it is still around. I just don't know how many people would want to use it still.
 
You guys realise you could just hold F8 after you press the power button and it will immediately hop into the boot selector?
depends on the system, my old laptop was fucking retarded in that if you repeatedly pressed a button, it'd hold up the bios. the amount you pressed caused it to hold up longer, and it would still take input during this time.
so if you held the damn thing down, you could actually fucking soft lock it for a bit. as far as i know, there's no limit for how long it'll do it for.
you can easily just hold down the power button to shut it off and try again, but I'm impressed that such a obvious oversight made it's way into the final product.
 
Like I said in the beginning of this. It's interesting, and I'm glad it is still around. I just don't know how many people would want to use it still.
I did because it got me street cred for the year or two I used it but the more I used it the more I enjoyed how manual it was and started genuinely enjoying the tedium strangely enough. FOR THE LOVE OF GOD NEVER FORGET TO RUN GENINITRD AND LILO AFTER UPDATING. For regular old gaming it was pretty solid and I never had issues running modern games at the time or even burning up my GPU to try AI stuff.
The slack builds for Nvidia and Steam were up to date but forgetting to set the Nvidia SlackPKG builds to have 32 bit multilib support caused me a few headaches but they were a simple fix.

I personally wish the Slackdocs website got some more love but what's there is helpful and doesn't look like a technical manual that is the arch wiki but doesn't feel as fleshed out and complete like the Gentoo handbook but at least Slackware has GUI installation :^D
The few times I ran into errors I was able find the solution on the Linux Questions forum which is surprisingly active for Slackware.
 
It does not use systemd but BSD-style init scripts. That alone is a good reason to use it in the first place. RedFag will not take my shell scripts away.
:jaceknife:
I think I like the openrc way personally. Though over time runit has grown in me a bit. Openrc uses bash scripting to start services, and for me it's a pretty solid init system.

That and it's available in most places that offer systemd alternatives.

the more I used it the more I enjoyed how manual it was and started genuinely enjoying the tedium strangely enoug
This speaks to me. It's the reason Gentoo scratches a special sperg itch for me. Just in a slightly different way.
 

from the mati thread. Now stfu editor cucks, and git good.
Except Blender is still shit for video editing since no one uses Blender for video editing so that component gets zero meaningful development, unlike everything modelling oriented, which is it's main purpose.

Just get Resolve for free and have something that's meant for video editing, you'll have a much better time than trying to deal with Blender's video editor.
 
Been messing around with udevil, great utility for mounting USB drives when you don't have a dedicated tool for it provided by your DE. I've also been slacking on making aliases for tedious things, even though automation is supposed to be a part of why the command line's good, gotta pump those numbers up.


from the mati thread. Now stfu editor cucks, and git good.
I don't even edit videos, but I get the feeling that the workflows that people use to edit videos and what this guy managed to accomplish with Blender aren't the same. Awesome Latvian guy, no doubts about that, but an animation project probably doesn't require all the layering you get when heavily editing videos.
 
I don't even edit videos, but I get the feeling that the workflows that people use to edit videos and what this guy managed to accomplish with Blender aren't the same. Awesome Latvian guy, no doubts about that, but an animation project probably doesn't require all the layering you get when heavily editing videos.
I believe that Blender's video editor is meant to be an extra over it's entire 3D/2D animation feature set, where you do the bulk of the work there and then use the video editor for some small finishing touches, and it's controls are oriented around Blender rather than conventional video editors so the Latvian guy had no problems making the whole thing in Blender only.

However, Blender's video editor is miserable to use if you want to use it like a conventional video editor, where Kdenlive will fare better, will be familiar to editors like Premiere or VEGAS, but will still be jank and annoying. I know because I've tried various editors and Kden had the most technical annoyances. Resolve is the best free video editing software you can use, it's so good that people who were locked into Premiere Pro and After Effects, who did this work professionally, moved their entire workflow over to Resolve and never look back. It's free, it's available on Linux, there is no reason to not use it unless you're religious about keeping everything FOSS, but then your mian priority is not good software.

If I were to rate video editors, it would be Resolve > Premiere Pro > VEGAS > Kdenlive > Blender. Resolve is eating Premiere's lunch, and unlike Premiere it's available on Linux, VEGAS is a relict but it's still okay-ish, Kden is a tinker toy and Blender is an afterthought.
 
Back