• 2 Posts
  • 21 Comments
Joined 3 years ago
cake
Cake day: August 2nd, 2021

help-circle



  • It is a lot of fun! Right now I’m back to arch, since I don’t have a lot of time, but funtoo does right those older decisions in gentoo which do not make sense in these day and age. And the updates are fast, really fast, since they use git!

    The downside is the docs aren’t as good. Not even close. The wiki for gentoo is a great source of information.















  • I remember there were talks about merging the patches and making it an option when building. I don’t know the current status of that.

    On real time operating systems, like freertos, not only the kernel is real time but everything else is too. Like: you can guarantee your call on the I2C and SPI won’t take more than 5ms, for example, even with hardware issues. The whole environment is built around the hardware realtime concept.


  • It is possible! But not so easy.

    You need to build a “reputation” with other servers. If your server is online, then some instances lose messages or just plain fail to load your content. So, first off, you need to be online all the time.

    And it takes a lot of bandwidth! Each message, like and post anyone makes on every instance might come from any other instance, so servers need to have enough bandwidth to talk to each other all day.

    There’s also the problem of storage. You don’t only store your own content, but also a “cache” of other people’s content, so you don’t need to request it again every time.

    There’s even a need for energy. Your server might connect to a lot of other servers, so you might need to have a beefy cpu to process all of that (so no running on batteries)

    What you describe exists, actually. It’s called “peer to peer” (often called “p2p”). There are some p2p networks, like scutterbutt which runs on top of the “gossip” network.

    They have their own problems, tho.

    Federated networks, where you join a server and servers can talk to each other (instead of directly running on the users device) are a middle ground.

    On a server only network, like reddit, means everything is controlled by one entity (reddit).

    With a p2p network, you have the problems I’ve described before (and lots more)

    And finally, a federated network like lemmy exists in between. You join a server, but are not limited to that server. If you don’t like something in your server, you can join some other server or even mount your own, and still be part of the bigger network. With the rules you desire to follow!




  • The only real “problem” would be the lack of certifications, which are quite hard to get.

    Real Time Operating Systems (RTOS) are normally used for these tasks, but, AFAIK there are already projects using linux with patches to make it run a RTOS kernel.

    In my opinion, I think it all depends on what part of the plane it is running. If it is a core sensor, providing real time data, it makes a lot of sense to use a RTOS. It needs to prove it can run its tasks on time, and the scheduler needs to be understandable. There’s also a lot of overhead with running a full OS with processes, which don’t make sense for a sensor which only function is to provide data over a CAN/LIN bus.

    But, for other things, like dashboard visualizations, music for the aircraft, entertainment, and those non-critical-realtime needs, then it makes a lot of sense to run linux. After all, you’d get access to a lot of already built software and a working dev environment.

    And don’t get me wrong, this is clearly BS from boeing to keep selling their closed source software. There are already open source RTOS systems, like FreeRTOS. I do not mean to keep those real time systems closed, but to use a full OS where it makes sense and a RTOS where that makes more sense. Both open source!