It seems appropriate to describe Facebook itself as a cybersecurity threat because of the OS platform it runs on. Perhaps they should also ban all the technologies named on this page … just to be safe.
Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.
#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork
It seems appropriate to describe Facebook itself as a cybersecurity threat because of the OS platform it runs on. Perhaps they should also ban all the technologies named on this page … just to be safe.
I think that what you’re looking for is “CPU affinity”, but that is not something I know anything about.
In the 40+ years I’ve been playing with computers, I’ve always let the OS worry about where and when to run a process and only rarely do I renice
a process that needs to run, but not at the expense of everything else.
A Docker container is a security framework. The process running “inside” the container is just a Linux process like any other.
So, as I understand it, the performance will be identical to a process that is running “outside” a container, subject to the overhead associated with any security restrictions.
To answer your post title question, I suspect that at this point it seems counterintuitive to introduce complexity in an environment already rife with exploits.
It’s not like it’s a new idea either. Microsoft published research on this in 2009, 16 years ago.
The abstract on that link holds the promise of many benefits, but it appears to carefully avoid specific claims, which makes me wonder if the idea ran into unexpected hurdles, which is common in software development.
The abandonment of the Barrelfish project is probably an indicator that this is an idea that didn’t pan out.
Having said that, I haven’t dug into kernel development over the past 40 years of my career, so it might well be that aspects and nuances of this idea were adopted and are in common use.
If you run dmesg -T
you can see the entire boot log with human readable timestamps.
TL;DR - Essentially you’re attempting to mix two types of output, a pipe with a terminal. This is pretty much not going to work as expected.
To make colour in a terminal, commands like ls
add so-called Escape sequences, a series of bytes that your terminal knows how to interpret as colour.
Whilst you might be able to force those characters though a pipe, they’re just characters, so if you only grab part of those characters, you’ll create invalid Escape sequences and all hell will break loose, exactly like what happens if you run cat
on a binary file and the terminal display goes haywire. You can often recover using the reset
command.
This is why programs like ls
and grep
detect if they’re running as a terminal command or a pipe command and suppress the Escape sequences when you are sending their output to anything other than a terminal.
On any command line you can likely just run a single letter command: w
The file you create using the dd
command is just a file. It can live on any filesystem capable of storing a 256 GB file.
Make sure that you compare the checksum between the drive and the file and store a copy of it with the file, so you can check it after restoring the data.
Note that you can even mount that file using a loopback interface, so you can read the content, but if you alter it, the checksum will change.
Welcome to Linux where all manner of magic is built-in.
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 have no idea what Bazzite is.
The error says that there’s a missing file. If it used to work, but after you updated, upgraded, compiled, installed or something to get a new kernel, it broke.
I’m guessing that you installed the wrong kernel or didn’t update the initial ramdisk correctly.
You might be able to boost using the previous kernel, but I’d start with trying to figure out what you did to get here.
You should be able to boot from the installation media in rescue mode to fix this, but that won’t happen until you know what’s broken.