I'm not sure if this is what you are looking for but I found https://github.com/wolfpld/tracy to work rather well. There is an integration for the tracing crate that can get you very far: https://lib.rs/crates/tracing-tracy. If you're just looking for a very high level report then this might be a bit too much detail.
> Depending on the configuration Tracy may broadcast discovery packets to the local network and expose the data it collects in the background to that same network. Traces collected by Tracy may include source and assembly code as well.
I can only really talk about Germany here, the perspective might be different in other countries. The big challenge is the large number of people coming in, both from legal and illegal immigration. Our system simply can't deal with it. Ideally you would get these people out of the asylum centers (might be the wrong term, no idea) and into jobs so they can actually start living and integrating here. But the harsh reality is that people are stuck for years, waiting for the approval process to happen at some point, and they aren't even allowed to do something useful in the meantime. This, unsurprisingly, creates a lot of tension on all sides and doesn't help anybody. Lowering the numbers might not be the best solution but at least that seems doable.
I feel a lot of this comes from a big resistance to change. Germany tries to take in all immigrants and make them fully German without any trace of their original culture (not socially, but economics wise etc). And that creates huge tension. In my mind, Germany needs to decide which of those various aspects of culture are important and then focus on them, and allow for diversity in other parts.
But why should they change? Ultimately immigrants need to assimilate. Maybe not the first generation but the second generation should be assimilated.
People always talk about integration but that's easy. Assimilation is the harder goal.
This highlights the key, difficult issue with immigration into Europe: people from vastly different cultures and religion who don't assimilate even in some cases at the third generation. But it's very difficult to openly discuss this because anyone who dares say, for example, "there are too many muslim immigrants" is immediately piloried and so the debate is poisoned.
1. Gender equality : probably very high on list of desirable qualities in assimilation
2. Language : may be somewhere in middle
3. Being required to Celebrate Christmas in kindergarten : even lower I say and may be counterproductive
Not all sides of assimilation are same. With Germany, it seems like it's all or nothing though. The debate is poisoned because no one is listening to the other side. One side says, "why should we change?" And other side say, "well, why should we?" And nothing goes anywhere.
No, there are no "different levels of assimilation", by definition.
Language is a basic requirement for integration, by the way, way before assimilation.
I think your last sentence misses the point that there is no obligation to accept immigrants and that the host country is sovereignly free to accept or reject anyone they wish.
Thats what OP was saying though, if countries want assimilation to that high of a degree, they should encode it in a law. Otherwise, they are being duplicitous by inviting skilled workers on one hand and then creating structures which drive them away.
For example, there can be a legal requirement to have a B2 level of German within 3 years of being in country, if the requirement is so important.
Right now, the policies say one thing and politics say another.
P.S. : the real reason such a law would never exist is because it would drive a huge amount of skilled immigration away and this is something also politicians cannot afford.
I have the "honor" of getting to use IBM $PRODUCT at $COMPANY.
- it uses some form of consensus algorithm between all nodes that somehow manages to randomly get the whole cluster into a non working state by simply existing, requiring manual reboots
- Patches randomly introduce new features, often times with breaking changes to current behaviour
- Patches tend to break random different things and even the patches for those patches often don't work
- For some reason the process how to apply updates randomly changes between every couple of patches, making automation all but impossible
- the support doesn't know how $PRODUCT works, which leads to us explaining to them how it actually does things
- It is ridiculously expensive, both in hardware and licensing costs
All of this has been going on for years without any signs of improvement for now, to the point that $COMPANY now avoids IBM if at all possible
Your starter kit inspired me to finally bite the bullet and write my own emacs config from scratch instead of using doom. I'm not sure yet if I'm thankful for that, time will tell ;)
I'd guess it's similar to a job in the entertainment industry, like being a host of a TV show.
You won't get very far by just sitting there playing some games, you have to be entertaining, engage with the audience, provide commentary etc. And do all of this with a happy face/mood for 6-12 hours, preferably every single day. And when you're not streaming you most likely do social media stuff.
I know of a streamer who got "big" (enough to earn a living) by playing factorio. At some point he burnt out on the game and tried different things but his audience didn't really care for that and income broke down substantially, so it wasn't sustainable anymore. So he continued playing factorio without actually enjoying that so that he could make a living for his family. Just like a "real" job.
This might be a "person in a country with pretty fast internet connection" opinion but I don't think I ever had that issue. Might also depend on the container size, pushing > 1GB containers might be more error prone than pushing small(ish) containers.
While this is definitely a valid option I'm not sure that introducing Nix/Guix simplifies the stack compared to using Docker. Depends on the setup and experience, I guess.
Why would you assume that these are fakes? There are fan translations for the game (a quick google search would bring this up) and you can download savefiles for Magnasanti. Maybe the person simply recreated the Screenshots with their russian client? Seems a lot easier to me.
I say this, because it's very hard to write the policy yourself at the beginning. So let the system run for a week and then use the tools to build the policy for you.
I wish it's easier to sit down and write it, but it's not atm.
How does that work? If you run selinux without a policy, you also get no type transitions and no file labels. That means that after a week, you only have a list of things your system does, with every action coupled to the init_t domain (or possibly even kernel_t), and file access targeted at unlabeled_t (unmanaged_t?).
At the bare minimum, you need a base policy that already contains separate type contexts for each of your services, file contexts to apply to the service daemon binaries, and type transitions so that each service gets run in its proper context. If your daemons run in the wrong context, then immortalizing that in policy with e.g. audit2allow only deepens the swamp you're in.
I don't think there's any practical way to build an selinux policy from scratch by just running your system and recording it, even if the tools allow you to do that. You can only start from your OS' reference policy or indeed write the initial base policy by hand.
