> Lennart Poettering is that you? Because considering it's quite common in larger installations to hash those directions, that is HILLARIOUS. We have for example done upto three letters: > >/home/f/foo/home/b/bar/home/ba/baz/home/kap/kappa > > etc. Some of us do actually use *IX on multi user systems.
The purple haired pinheads in charge have no idea what you are on about. They're 100% clueless.
The whole purpose of shared libraries is that multiple applications can mmap the same.text area.
The reason you don't see large memory usage is only because applications take proportionally orders of magnitude more bss/heap/stack compared with.text than they used to.
To that extent, fine. Let's ditch shared libraries. But you could do the same by just statically linking all of your binaries.
> Many times the package maintainer will actually submit something but when they get the WTF that isn't how we want our software handled from the devs they disappear and never some back.
This is because many upstream developers don't think it is their responsibility to help package maintainers.
It may not be their responsibility, but it is certainly in their interest to at least provide a few different packaging options *built into* the upstream sources,.deb and.rpm being the most common.
But they've all thrown up their hands and said "it's not my problem", leaving us with the cancer that is snap and docker, then complain that Debian is trash.
Guess what, docker, lxd, and snapd won't even run on debian if you can't even be bothered to make functional docker, docker-compose, snapd, lxd et al debs upstream.
Slashdot Mirror
I'm guessing it is safe to say you never played sports.
How about chess?
Competition draws psychopaths? Ok.
I'm told that in still air, the AoA sensor vanes droop, showing a negative AoA. I am not a pilot, let alone an avionics experts, so YMMV.
Error detection is distinct from error correction.
The first is sufficient for many systems, even critical systems.
> Lennart Poettering is that you? Because considering it's quite common in larger installations to hash those directions, that is HILLARIOUS. We have for example done upto three letters: /home/f/foo /home/b/bar /home/ba/baz /home/kap/kappa
>
>
>
> etc. Some of us do actually use *IX on multi user systems.
The purple haired pinheads in charge have no idea what you are on about. They're 100% clueless.
https://airfactsjournal.com/20...
https://99percentinvisible.org...
https://vimeo.com/159496346
Fly the plane not the technology
https://www.youtube.com/watch?...
> fairly easy to detect AoA sensor failures....it is not.
GTFO out.. one is clearly fucked here:
https://static.seattletimes.co...
I would love to see the damn raw AoA data.
http://nefariousmotorsports.co...
The /. editors are trash. Betcha $100 they never fix the link in the summary. They're completely incompetent.
I believe there are two, not one, that are inputs to MCAS
Jesus you suck at being an editor, msmash
https://boeing.mediaroom.com/n...
msmash: that alternative link has even less useful information than the truncated wsj article.
> non standard repositories
Meaning non-free. Wonderful how far Debian has regressed.
>so they don't take massive amounts of RAM
The whole purpose of shared libraries is that multiple applications can mmap the same .text area.
The reason you don't see large memory usage is only because applications take proportionally orders of magnitude more bss/heap/stack compared with .text than they used to.
To that extent, fine. Let's ditch shared libraries. But you could do the same by just statically linking all of your binaries.
> Many times the package maintainer will actually submit something but when they get the WTF that isn't how we want our software handled from the devs they disappear and never some back.
I've seen this happen as well.
This is because many upstream developers don't think it is their responsibility to help package maintainers.
It may not be their responsibility, but it is certainly in their interest to at least provide a few different packaging options *built into* the upstream sources, .deb and .rpm being the most common.
But they've all thrown up their hands and said "it's not my problem", leaving us with the cancer that is snap and docker, then complain that Debian is trash.
Guess what, docker, lxd, and snapd won't even run on debian if you can't even be bothered to make functional docker, docker-compose, snapd, lxd et al debs upstream.
Oh hey look, another unfixed debian bug.
https://bugs.debian.org/cgi-bi...
What do you know.
I've got a long list of unfixed bugs as well.
https://bugs.debian.org/cgi-bi...
As I said "Debian devs will drop one by one due to these people."
Debian will die because of that idiotic attitude, and all that will be left is containers. Wonderful.
If the debian bug system wasn't so outdated, you could search by submitter.
Don't even get me started on snap. What a steaming pile of shit.
The people who unceremoniously close PRs and bug reports as "won't fix" or "stale" are the whiny kids.
The youth just close bug reports and PRs unilaterally. Not a solution.