Computers are like servants. They do whatever you ask of them. But to be able to ask them things, you must do so in their language. On the extreme low level that means writing code to make programs, but on a higher level, it means talking to programs someone else already wrote using special commands.
The buttons and switches on a GUI that you can click on with a mouse are like pre-recorded commands that instruct the computer to do some specific thing. The button or whatever will have a symbol or text description that lets you intuitively know what it’s for, and when you click on it, it plays a pre-recorded command to the computer in its language that tells it to do that thing. With these buttons, you can ask things of the computer in its language without having to know that language.
As you get more intimate with the computer, this system can start to feel a bit stiff. You’ve essentially got a butler who doesn’t speak your language, and any time you need to give him a task, you have to fumble through a basket of pre-recorded tape recorder messages to find the one for the task at hand, and play it to him. For more complex tasks, you may need to chain several of these together. It gets slow and awkward. And god forbid you don’t even have a tape recording for the thing you need.
It’s easier if you learn the butler’s language yourself. Then you can ask him for things directly. You’re not bound to any collection of pre-recorded messages to use, you can tell him exactly what you need. And if you don’t happen to know the word for something, you can look it up. It cuts out all the faffery with fumbling over a tape recorder looking for the messages you need to play.
Using a terminal is roughly the computer equivalent of speaking to your butler in his native language. You’re not limited to only the buttons and features any particular program lets you have; you can make up exactly what you need on the spot. And you never have to bounce your hand between a mouse and keyboard to do it, you can keep your hands in one position at all times, which really adds up over time in both speed and comfort.
Practicing this will also give you the side perk of better understanding how the computer actually works overall, and what it’s actually doing. This knowledge can come in super handy when diagnosing problems with the thing. When a GUI gives up, a terminal can keep digging.
Not sure if this is the root cause of your boot failure, but underscores in hostnames are not allowed. A- Z, 0-9 and - are the only allowed characters.
You’re welcome to use whatever init system you want, but Systemd solves a lot of the bullshit problems and limitations that come from init.d init scripts. Systemd also has a lot of its own bullshit and bloat, but it does an excellent job at actually being an init system and service manager if you know how to properly use it.
Almost everything you said is mere brochureware perpetuated by a tribe stronger than the vi mafia.
Sysvinit starts fast, starts well, and doesn’t try to control mounts, cron, Getty, and everything else.
The"but it retries things" whine was a solved problem in 2001. So easy.
The EL6 machines I have in storage start faster than the el7 machines joining them. PCLinuxOS is a very valid non-systemd system that only lacks a documented kickstart emulant.
solves a lot of the bullshit problems and limitations that come from init.d init scripts.
So do the other ~7 init systems developed since then. And, as far as i know, all of them print their relevant trouble directly to stderr. Who cares about SysV still?
Hey guys, why all the downvotes? Systemd is known for throwing all the irrelevant stuff at you, making it troublesome to debug. Which is why i switched. And i can confirm: Runit, S6, OpenRC and even simple Dinit are way better in that regard (and they do make less trouble generally).
Snap is a steaming pile of excrement. So much of the crap on the Snap Store is obsolete and out of date. Anyone and their monkey can post a snap on snapcraft, and… they do. Canonical is just as bad. They took it upon themselves to package up a lot of commercial-level open-source software 3 or 4 years ago… and then have done fuck all with it ever since. Zero updates to the original snaps they put there in the initial population of the Snap store (yes they do maintain a select few things, but only a small percentage of the flood of obsolete software in the Snap store). The result is people looking to install apps who poke the Snap store, go “oh hey, the application I want is there”, install it, and then get all pissy with the vendor… who looks about in surprise wondering how a potential customer managed to find such an old version (happened with at least 2 of my employers, and I’ve come across many more). Go search Reddit (or Google) for obsolete snap discussions. There’s no shortage people pointing at the same issue.
This doesn't seem to be a problem with snap. Canonical probably tried to show vendors a way how to distribute software commercially. But vendors are on the level of cavemen and don't know shit about Linux even after serving a solution. Or they simply don't care about building up a market opportunity.
I don't want to defend Ubuntu. I don't like Ubuntu especially, but it might be a simple explanation.
It’s a problem with Canonical. They stepped up and created the snaps and then abandoned them instead of maintaining them. They still maintain the core that they include with the distro… it’s all the extras they created to pad out the store… and then abandoned. “Look the snap store has so many packages”… yeah… no… it doesn’t.
Why would a company who makes a commercial level open source package want to add snaps to their already broad Linux offering? They typically already build RPM (covering RHEL, Fedora, openSUSE, Mandriva, etc.) and DEB (covering Debian, Ubuntu, all Ubuntu derivatives, etc.)… and have a tar.gz to cover anything they missed. Why should they add the special snowflake snap just to cover Ubuntu which is already well covered by the DEB hey already make?
Sure, show vendors what’s possible, but if Canonical stepped up to make the snaps, then they should still be maintaining them. It’s not a business opportunity… its more bullshit from Canonical that no one wants.
I’m not sure what was wrong with the opensuse install, since I’m pretty sure I got the nvidia drivers to work, but I definitely have everything working with nvidia on fedora
If I ever feel like going back I may do that. In the meantime I’m very happy with what fedora has to offer me so far. Just finishing installing the software I use regularly now!
https://appledb.dev/device/iPad-2.html Select 9.3.5 and choose the jailbreak method you want. After that, download a newer browser with the jailbreak or even just run Linux on it.
You’ve probably got your answer already, but just wanting to confirm that Kdenlive can do all the things you listed.
Though the editor itself is very easy to use and obvious (if you previously have used premiere etc), you might find the UI for some of the individual effects a bit confusing. There’s tool tips and sometimes help videos and stuff, but you might find yourself dragging a few sliders left and right to find out what they actually do :)
Note that generally speaking, Kdenlive doesn’t currently support graphics-card-accelerated timeline preview very well, so if you’re packing on the effects, you might not get real-time playback in the timeline without “preview rendering”. If you ever used Premiere 20 years ago, it works the same as that.
From memory, Olive has the best “in-timeline” graphics card acceleration - but is otherwise at a much earlier stage of development.
As others have mentioned, some or all of these are also doable in Shotcut, Openshot, Olive.
Also, you might be interested in TJFree Tutorials on YouTube, which has a playlist of Kdenlive tutorials - for older versions, but it’s mostly going to be the same. He also has tutorials in loads of other FOSS creative software. I found he tended to be “clear and efficient” and doesn’t take 5 minutes to give you 1 minute’s information.
Thank you, I’ll keep that in mind if I need to do more.
Currently, I just have a 5 minute clip that needs cutting, stabilizing and some color correction, and Shotcut let me do that without tutorials or manuals.
You can do almost exactly this with keyword bookmarks. The only change is that you need to put the “keyword” at the start of the URL. So @l linux rather than linux @l.
Create a new bookmark with these settings:
Name: Whatever you want.
URL: The search query you want with the text replaced by %s. For example https://kagi.com/search?q=%s+site:https://lemm.ee.
Keyword: The tag you want. Such as @l.
Now you can type @l foobar in the URL bar and it will go to https://kagi.com/search?q=foobar+site:https://lemm.ee. (Or whatever search engine you have configured.
Keywords can also be used for non-search bookmarks and javascript bookmarklets which are very convenient.
Yeah, it is sadly not advertised. Even the “Keyword” box helper text isn’t very obvious how it works. They should link to a help page.
Not to mention that they also have search engines which work in a very similar way, but have a different UI, are harder for users to manually define and don’t sync across devices via Firefox Sync.
It’s a big mess. But it works! So that is enough for me.
I know I’m not making a helpful contribution here, but I’ve been wondering about this stuff for a while myself and this thread has some great answers. Thanks for asking this OP.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.