fermuch

joined 3 years ago
[–] [email protected] 1 points 1 year ago

It was late yesterday and I didn't realize I made it sound scary! Yes to all you said! The heatsink is a great idea, too.

[–] [email protected] 2 points 1 year ago

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.

[–] [email protected] 10 points 1 year ago (1 children)

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!

[–] [email protected] 2 points 1 year ago (2 children)

Please also be mindful. These old devices don't receive security patches and are going to be connected to the internet. Any exploit or bug and you'll have a compromised device with local network access and even gps in the hands of bad guys.

There's also the battery as OP said. It's better if you take it out, if possible. Do not leave it running on 100% all the time or you'll have a fire in your house!

[–] [email protected] 10 points 1 year ago (1 children)

É normal ter instabilidade após um êxodo. Calma, gente. É nossa tarefa agora criar um comunidade digna de voltar sempre!

[–] [email protected] 7 points 1 year ago

I'm sad to hear you did not feel like a good explanation of the fediverse was given. Is there something you'd still want to know? I'm no expert but I've been here for a while, so I might be able to help or at least guide you!

Feel free to ask! And if you don't feel like commenting on here, feel free to DM me with questions too.

[–] [email protected] 13 points 1 year ago

Glad to have you around here!

[–] [email protected] 2 points 1 year ago

Boeing has their own RTOS, which they might be using on more than "real time critical" software. What I mean is: embrace open source, be it Linux or some other OS more specific for that task, but open source all the things!

[–] [email protected] 3 points 1 year ago

Thanks! I can't wait to finish the campaign to play the community made content! I took a quick look and saw a lot, LOT of content! Makes me feel nostalgic for HL2!

[–] [email protected] 9 points 1 year ago (4 children)

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!

[–] [email protected] 2 points 1 year ago

Thanks for your work.

[–] [email protected] 6 points 1 year ago (2 children)

I am currently playing Half Life Alyx with a Quest 2 and a cable to my PC. Incredible game, totally recommended. If you want to feel what Virtual Reality (VR) is about, please play that game.

view more: ‹ prev next ›