Bruce Perens is currently working on a new licensing model called Post Open requiring that business with sufficient revenue to pay up.

https://postopen.org/

In my opinion it’s criminal just how often this happens. Big business making obscene profit off the back of volunteer work like yours and many others across the OSS community.

Is it just me who is sceptical about anything new from Intel at the moment?

Mind you, this is not the first time that this feeling has existed, there was a standing joke amongst IT professionals in the mid 1990s that the sticker “Intel Inside” was actually a warning label, referencing the Pentium FDIV bug.

And many of them are heading to BlueSky…

My first recommendation is to become familiar with one flavour of Linux. Debian is a solid choice and it will give you a good understanding of how a great many derivatives operate.

The command line is a tool to get things done, it’s not an end to itself. Some things are easier to do with a GUI, many things are easier to do with the command line interface or CLI.

Many Linux tools are tiny things that take an input, process it and produce an output. You can string these commands together to achieve things that are complex with a GUI.

Manipulation of text is a big part of this. Converting things, extracting or filtering data, counting words

For example, how many times do you use the words “just” and “simply” in the articles you write?

grep -oiwE "just|simple" *.txt | sort | uniq -c

That checks all the text files in a directory for the occurrence of either word and shows you how many occurred and what capitalisation they used.

In other words, learning to use the CLI is about solving problems, one by one, until you don’t have to look things up before you understand why or how it works.

Given your “updoot”, I figured that you’d get it, seems that others were not so lucky…

This precious token was gifted to me and I pass it to you…

Thank you for the links, never heard this, much appreciated.

Unfortunately, with that comes no assistance to your query.

If you’re not a programmer, then what you’re saying sounds reasonable, but if you are, it’s not.

Different operating systems use different ways to interact with the outside world, in fact, it’s pretty much the only thing an operating system does.

Consider for example responding to a mouse click.

Each operating system handles this differently, sometimes within the same OS it’s different depending on what else is happening, (Linux X11 vs Linux Wayland).

A mouse is pretty trivial on the face of it, but the operating system needs to be able to track each pulse from a mouse and respond to that and then it needs to tell your program about it. In other words, it needs to interrupt your program, deal with the pulse, update the relevant information, then resume your program.

The same is true for the screen, disk storage, keyboard, memory and even the CPU itself.

Even if the various operating systems use the same CPU, and these days they mostly don’t, running the same program in multiple places is extremely rare, and that’s for companies who have the source code to the software they sell.

Some programs are more universal, because they’re written in a language like python that’s compiled when you launch it, but dig inside and you’ll find code specific to each operating system.

Source: I’ve been writing software for over 40 years.

I’d set-up a static website on an AWS S3 bucket. Then you can use AWS Cloudfront to distribute access around the planet.

Cost is mostly negligible unless you are serving big files.

There is not enough information in your post to help you. Here’s a preliminary list of questions that need an answer before anyone can give you a meaningful contribution.

Where did you get “Davinci resolve” from?

What instructions were you following to install it?

Did the installation finish?

Have you attempted to login using a text console?

Which version of Kubuntu were you using and which version of “Davinci resolve” were you attempting to install.

I use Docker and (currently) VMware and host whatever I need for as long (or short) as I need it.

This allows me to keep everything separate and isolated and prevents incompatible stuff interacting with each other. In addition, after I’m done with a test, I can dispose of the experiment without needing to track down spurious files or impacting another project.

I also use this to run desktop software by only giving a container access to the specific files I want it to access.

I’m in the process of moving this to AWS, so I have less hardware in my office whilst gaining more flexibility and accessibility from alternative locations.

The ultimate aim is a minimal laptop with a terminal and a browser to access what I need from wherever I am.

One side effect of this will be the opportunity to make some of my stuff public if I want to without needing to start from scratch, just updating permissions will achieve that.

One step at a time :)

Make sure that it’s the one you think it is.

Also, how did you “remove” it? Just yank the cable, or something a little more refined like unmount or eject?

It’s a package management system in the same way that Flatpack, yum, apt-get, snap and dozens of others are.

If you use MacOS and Linux, it’s not inconceivable that you might want to use the same package management system across both.

I’ve used it, didn’t particularly warm to it and didn’t install it on my most recent MacOS install after it shat all over itself on a previous installation.

I didn’t know that it was available for Linux. Not tempted to try.

I’m a firm believer in apt-get and failing that, Docker with side journeys into podman.

Also, the word you’re looking for is: “headless”, as in, “headless install”

The traditional way is to use a serial console from another device.

Back propagation happens during the creation of the model, not after it’s deployed.

In my opinion, you’re solving the wrong problem with the wrong solution.

The user base for Canonical, Red Hat and SUSE is not the general public watching traditional TV to decide that they want to install Linux across their enterprise data centre, it’s ICT professionals who talk to other ICT professionals and read white papers and implementation guidelines, then pay installation, management and subscription fees to get ongoing support across their shiny new data centre.

Growing the user base with mums and dads is not something that Linux vendors are interested in, since it only costs money instead of generating an income stream.

Linux as a commodity comes from rolling out Android phones and tablets, from deploying embedded Linux on network routers, security cameras, in-car entertainment systems, set top boxes, etc.

The final hurdle for general desktop Linux is not resolved by getting more users through advertising, it’s through having a product that can be purchased. Chromebooks were promising, but missed the mark.

System76 are trying, but the scale is too small and Linux isn’t ready as a general computing platform yet. I say that having been a Linux user for 25 years.

If you don’t agree with that last statement, consider what all computer manufacturers would do at the drop of a hat if they thought it would be cheaper, they’d drop Windows like the hot mess it is.

Unfortunately, it’s still cheaper to pay the Microsoft tax because the associated support network is already in place for the general public.

That’s not there, yet, for Linux.

It remains to be seen if ever will be.

I don’t have a touchscreen, so I have no lived experience, but this should get you started at least:

https://wiki.debian.org/TabletAndTouchScreen

What about something novel, like installing actual Debian?