The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
I can never remember the ffmpeg syntax so I made a script to do this for me a while ago, cut-video.sh
Fun fact: there's a difference between doing -i input -ss 100 and -ss 100 -i input and you normally want the latter so you don't decode the entire stream up to the starting point just to discard it. Normally not an issue, of course, but might matter if you want to cut something from a couple hours into the video.
 
Fun fact: there's a difference between doing -i input -ss 100 and -ss 100 -i input and you normally want the latter so you don't decode the entire stream up to the starting point just to discard it. Normally not an issue, of course, but might matter if you want to cut something from a couple hours into the video.
Neat, I changed it and tried to benchmark, it does seem faster but not like an order of magnitude -- I tried a cut near the end of a two 4h 30m videos to avoid cache, 38s down to 20s.

But it's definitely stuff like this that leads me to just have a pile of scripts to call ffmpeg rather than trying to remember all this stuff.
 
Maybe I can commit to moulding FreeBSD into a proper Linux replacement
I've probably already sperged to much about how much it sucks trying to get the bsd's to be a proper replacement to linux. They feel noticeably far behind where linux is now. It sounds like you might have an idea of how rough it is. But my advice, honestly don't waste your time. I've heard freebsd is finally spending some money, and time to get it's desktop support at least partially up to where linux's is. But until then, seriously I recommend finding something more productive to do. It will probably just leave you frustrated.
I have no aptitude for bash scripting, let alone Python, because I never bothered to try either.
I highly recommend starting with bash scripting. It's really easy to start, provided you at least understand how the terminal/command line works. It has the benefit of having a repl that you can always test things out of (python and other do too, but the cli is very intuitive imo). Install texinfo if you don't already have it. Then you can type

Code:
info bash
It will give you full proper documentation to bash. It's easy to navigate through the hyprlinks, it is helpful to learn the keybinds for info just because it will make some navigation easier, but really you just need to know you can click on the highlighted links and jump around and push the up and down keys to move up and down. There is also man bash, imo info bash is better though.

something else helpful. in the termninal in bash you get the help command. when you don't want to pull up the full documentation, and you just want to know about one specific thing. help will give you a quick summary of it, if it's a shell builtin.

so you can type

Code:
help if
or
help test
or
help echo

etc.

Also something else that can kind of make learning bash scripting not so bad. Is a lot of the time. You are just taking outside commands or utilities and chaining those together in creative ways to get the desired result. And you can do some really creative stuff with it, (you can also do a lot with just the internal shell stuff), but the core part of bash scripting is justing tests and doing different actions based on the condition of that test. like if else statements, case statements, even the different loops. You are just performing something until a condition is true or false.


also I recommend watching this guys channel. He gives some nice tips and tricks, a lot of his videos are super short. He also has ones where he made a supercut of all of the short videos. there are a lot of other nice reasources for it. but that's probably enough for now.

99% of what they do is in the browser unless they play games
I hope trump will finally hear my prayers, and throw all of the gamers in FEMA camps. I we need weinmar solutions for weinmar problems as the kids like to say now days. And I see gamers as the number one threat to democracy, and freedom as we know it today. Gamers being the most oppressed race is no longer enough. Ck's shooter? gamer. All of them are gamers. Troons? gamers. And no playing videos games didn't cause it, being a game-crickets caused them to play the video games, and it also caused them to act out their sick gamer fantasies.

I hope linus at least cracks down on proton and wine. We need these vidya-niggers back on windows where they belong. Don't you degenerate freaks touch my beautiful pure penguin.
 
I highly recommend starting with bash scripting. It's really easy to start, provided you at least understand how the terminal/command line works. It has the benefit of having a repl that you can always test things out of (python and other do too, but the cli is very intuitive imo). Install texinfo if you don't already have it. Then you can type
I would also recommend The Linux Documentation Project. Here's one for if/conditionals: https://tldp.org/LDP/Bash-Beginners-Guide/html/sect_07_01.html -- I even use it regularly to double-check my flags when building scripts.

Strangely enough, zero issues with bash. I can do a crap-ton with it. But python I struggle a bit more with. Could just be understanding workflow and syntax differences.
 
I've probably already sperged to much about how much it sucks trying to get the bsd's to be a proper replacement to linux. They feel noticeably far behind where linux is now. It sounds like you might have an idea of how rough it is. But my advice, honestly don't waste your time. I've heard freebsd is finally spending some money, and time to get it's desktop support at least partially up to where linux's is. But until then, seriously I recommend finding something more productive to do. It will probably just leave you frustrated.
Believe it or not, I'm actually quite fond of FreeBSD. I've experimented with it many times over the years, with the most recent time being 2022-2023. I'm keenly aware of its shortcomings, but I feel like the most common objections to it are overblown. I'm intimately familiar with the tooling and the packaging ecosystem more broadly. My personal gripes boil down to fundamental differences in design philosophy between Linux and FreeBSD. There is no distinction made in Linux between the base operating system and external applications, since the entire operating system is effectively "external applications." FreeBSD does make this distinction, so you have make vs. gmake, config files in /usr/etc instead of /etc, the list goes on. The only hardware that I own, which hasn't yet worked on FreeBSD, is my Xbox One controller. Even then, I have a near-mint DualShock 4 controller collecting dust that I can utilise in FreeBSD with minimal headache. Citra, DuckStation, PPSSPP, all those emulators worked perfectly on FreeBSD via Flatpak. I didn't bother testing Steam at the time; the thought escaped my mind before the urge to distro-hop took hold. I dislike how the Linux compatibility module was based on CentOS 7 for the longest time, since it's now EOL. The module's now built from Rocky Linux 9, but you still need to use the CentOS 7 module if you want to fiddle with any 32-bit Linux applications. I think you can do some debootstrap shenanigans in FreeBSD as a workaround, but it can conflict with the Rocky Linux module if you're not careful.


Cheers for all the other recommendations, mate. Much appreciated :)
 
Most people don't do anything on their computer and if you forced them to use something like Mint, Fedora, or Ubuntu they would get by fine. 99% of what they do is in the browser unless they play games. Windows and Mac are the paths of least resistance so that's where people go. If you suddenly had to download Windows and install it yourself and store bought computers came with some flavor of Linux, then people would use Linux and probably install Chrome and be happy.
this has been an experiment ive been running at a thrift store
they get old computers in as donations, i reimage them with linux mint, and i give them back and they sell them
so far nobody's complained
i then also sold or donated some computers to the employees at the store running various versions of linux and they haven't asked me how to do anything yet
 
I'm keenly aware of its shortcomings, but I feel like the most common objections to it are overblown
I've ranted about all the things I had problems with/didn't like with freebsd somewhere further back in this thread. I don't want to repeat all of it. Since I'm sure most people don't care anyway.

But it came down to not having the level of documentation I'm used to with Linux, for one thing. Which mattered most when it was a freebsd only issue I was trying to troubleshoot shoot.

Device support is nowhere near where it is on Linux, which just comes with the territory of having a smaller kernel (if freebsd ever does catch up to Linux they on't be able to use the "Linux is bloated" line anymore).

The Linux compatibility layer was more frustrating than anything. It partially worked. But then things would just be broken. It would leave zombie processes behind consistently.

In general I saw a lot of crashes, and bugs in my time using freebsd. Many that I have never seen on Linux.

Logs getting so filled up with error messages from some process that I could no longer use it to see the kernel messages I wanted to look at.

Their filesystem support is something I don't see mentioned a lot. But that is maybe one of the places it is lacking the most. Some filesystems do have user space drivers. But really you are out of luck if you happen to have a drive with a filesystem that isn't well supported.

This is by no means a complete list of my grievances. But it should at least give an idea of my experience using freebsd. Openbsd, their device and driver support is even more limited than freebsd's so take that for what you will. (At least it should have better security).

I say all this. I want to clarify that I don't hate freebsd or anything. But it is just no where near where Linux is. At least in desktop. I would say it's 10 to 15 years behind Linux at least as a desktop operating system.
 
Last edited:
Even more-so, why do some icon themes installed on Arch call for a secure boot signing???

I should probably be a bit more specific when I point stuff like this out.

It's specifically sbctl, installed through the repository support for Arch Linux on Artix Linux.

Either the lack of an upstream component or something else that's making the secure boot signing hook go rogue, it just wants to sign vmlinuz-linux-lts when it already has a valid key.
 
Last edited:
Fun fact: there's a difference between doing -i input -ss 100 and -ss 100 -i input and you normally want the latter
"you normally want the latter" isn't helpful. The difference between the two is precision. -i first is more precise, -ss first is less precise, but sometimes faster. See https://trac.ffmpeg.org/wiki/Seeking
 
"you normally want the latter" isn't helpful. The difference between the two is precision. -i first is more precise, -ss first is less precise, but sometimes faster. See https://trac.ffmpeg.org/wiki/Seeking
As of FFmpeg 2.1, when transcoding with `ffmpeg` (i.e. not stream copying): "-ss" is also "frame-accurate" even as input option.
Seems "you normally want the latter".

And if you're just copying, you'll have to usually adjust things a bit to get a keyframe that you like anyway.
 
I've rented about all the things I had problems with/didn't like with freebsd somewhere further back in this thread. I don't want to repeat all of it. Since I'm sure most people don't care anyway.

But it came down to not having the level of documentation I'm used to with Linux, for one thing. Which mattered most when it was a freebsd only issue I was trying to troubleshoot shoot.

Not saying your experience was invalid, it's just weird for me to see this because it's the opposite of my own. I first used FreeBSD version 4 back in the dialup days to set up a router and firewall box, and my dad and I were very impressed with not just the quality of the documentation but how complete it was, with basically everything we needed right there in the man pages where it belonged.

Fun fact: there's a difference between doing -i input -ss 100 and -ss 100 -i input and you normally want the latter so you don't decode the entire stream up to the starting point just to discard it. Normally not an issue, of course, but might matter if you want to cut something from a couple hours into the video.

This would have saved me even more time on the old machine. It makes a huge difference and I can't tell you how grateful I am. God bless the Farms. (I'll do more testing to see how 'imprecise' this faster way is, but it seems perfectly fine so far. I always used to use -c copy, but it kept causing too many problems so I just went with transcoding every time.)
 
I genuinely think Ubuntu is better for new users than Mint, its really not that complicated and it doesn't make it way too familiar so that there's still a dependency on Windows or Windows familiar visuals.
That used to be true before default snap package installs and other retardation canonical has shoved down Ubuntu users throats. Mint may be ho-hum with less online help but at least it has sane people running it to keep it beginner friendly.
 
That used to be true before default snap package installs and other retardation canonical has shoved down Ubuntu users throats. Mint may be ho-hum with less online help but at least it has sane people running it to keep it beginner friendly.
Yep. Ubuntu used to be easier. Easily the easiest of them all. That's been a while.
 
The Linux compatibility layer was more frustrating than anything. It partially worked. But then things would just be broken. It would leave zombie processes behind consistently.
ill be real the main thing stopping me from using freebsd is why would i use freebsd to run linux programs when linux is better at that
theres nothing i can do on freebsd for my use that i can't use linux for but there's a hell of a lot of things i can do on linux that i can't do on freebsd
 
Yeah, I decided to just go back to i3wm and got XLibre up and running lol.

Gotta figure out why apps seem to be running at 60fps while I have a 160hz panel but that shouldn't be too difficult.

Wayland just really isn't usable if you have anything beyond outdated/poorfag hardware probably lmao
 
Yeah, I decided to just go back to i3wm and got XLibre up and running lol.

Gotta figure out why apps seem to be running at 60fps while I have a 160hz panel but that shouldn't be too difficult.

Wayland just really isn't usable if you have anything beyond outdated/poorfag hardware probably lmao
from working on older computers i found wayland works ((when it does work) on modern hardware while older hardware has a lot of bugs
 
Wayland just really isn't usable if you have anything beyond outdated/poorfag hardware probably lmao
Eh? The Wayland hate is a bit overblown. Despite the faggotry surrounding the greater project, Sway is excellent, and Hyprland is also very nice if you like ricing. Truth be told I would much rather live on XLibre/i3, but until our boy Enrico can implement proper app isolation, fix xsecurity or otherwise rework how global keys work, its Gayland for me.
 
I feel like this thread used to not be so hostile towards wayland not that long ago. It still had the expected wayland vs xorg stuff. But it didn't feel as one sided as it does now.

I just can never pretend wayland is as bad as the people here say it is. It's not perfect, but it's definitely not some unusable piece of shit. It has improvements over xorg in some places even. It also has some areas where it's lagging behind xorg. If you aren't emotionally tied to your display server (a weird thing to care that much about to be honest), it's pretty easy to see the pros and cons of both. The truth almost always is somewhere in the middle, and this is a perfect example of that.

I think I would understand the level of rage wayland gets if I didn't use wayland half the time. And it didn't work fine.
 
Much of the Wayland hate comes down to 1) an attempt to force adoption for it 2) by tranny faggots.

I don't hate Wayland, but I also can't use it. I don't know if it's because I have nvidia, but it won't even load my DE if it attempts to use Wayland. It works on my work laptop, but I still run into issues with the interface being laggy or certain apps I have been using not being compatible with Wayland.
 
Back
Top Bottom