zare_st

But the stuff that carries TCP is IP. That's why TCP can work seamlessly, because it uses identification from a previous layer. Consider I bind a server to an ID, and not IP:port, the operating system running it must know how to communicate that via IP, so there will be a corellation map somewhere and that map needs to be synchronized between all peers that wish to host the roaming server.

Otherwise you're just switching port (16-bit) value to arbitrary 32-bit identifier.

Yeah it's a shortsighted plan. How would i set up rules on firewall if I don't know how to distingush the connections?

I don't think is wise even if you had written guarantees from their state via the business, because how your state might look at it.

It's a war, things have changed.

Absolutely no.

If a line of code belongs in a project with one file and a main() function, the presumption of impact of that code line on overall code paths is trivial.

If that line of code belongs in a library procedure used by a million LOC project, presumption cannot be done if you don't the project internals and tooling.

Rewriting entire systems or frameworks because one thinks that it's hard to implement a certain class of features is almost always a recipe for disaster.

For specific cases, asm is faster than c.

I'll show myself out

Valgrind will show these as "still reachable"

Never. Individuals with that kind of mutation have to be born per random chance, and then selected via sexual preference.

Why would systemd unit files matter for FreeBSD? FreeBSD has its own rc system and its own ports and packages and maintainers. If and when some major software starts lagging behind the upstream because of runtime issues, then it's time to discuss the alternatives. Right now such things do not happen.

FreeBSD had to mock several parts of systemd in order to port newer GNOMEs that are dependent on systemd. rc still runs this software, but unfortunately software depends on systemd sockets which is absurd design choice but here we are. Again mocking the absurd interprocess part is the way to go, as opposed to supporting entire specification and API of systemd.

"Any unix" doesn't cut it, too general, too broad. You did ask in dual sense in your original question but then you specifically stated FreeBSD as an example; so I'm answering for FreeBSD specifically.

The problem that I have with opinion in your post is an implication about groups of people - people with skills that should supposedly write a systemd clone for FreeBSD or other Unices, and people without skills that are supposedly waiting for the first group to do some work so they can enjoy systemd on *BSD or wherever. Let me be blunt here, I can assure you this is not the case. Systemd is not a factor for anyone in BSD world and it's a factor only for people that would like to migrate from Linux and retain their usual workflow and muscle memory.

Answer to question - yes, and more. Jails+rctl (available since 2012) is not cgroups it's cgroups+SELinux+APParmor. Vanilla linux container is not a security barrier, vanilla FreeBSD jail is.

In practice this means more seamless 'isolation' in Linux case but that isolation is weak. Which perfectly corresponds to FreeBSD looking at server uses 99% of the time and Linux looking at the desktop too.

About your conclusion, I don't think that's based on anything so please do write on what facts do you base the assessment that FreeBSD has no resource limiting and isolation features, and that it would be a 'separate implementation', as FreeBSD always tends to upgrade and not change tools and interfaces, and that there is not enough interest from anyone to implement it, as most major FreeBSD features are actually paid for by FreeBSD sponsors.

Yes

Organization proven to use and abuse the security via obscurity model.

Tricky? Checking if you're bound to TTY is trivial, checking whether you have a parent is trivial, checking whether interactive shell is somewhere in the tree is trivial, having some if's in signal handlers is trivial, etc.

Besides "daemon writers" could just default to foreground, because if it's ran as a daemon it is ran from a script hence nobody cares for extra option typing such as -d --daemon, it's written once in a file, as opposed to doing "program --foreground" every time you want it to run in front of you

Romhacking by refactoring disassembly is something that most experienced (decade+) developers do for a grand project lasting years.

You'd rather start here https://www.romhacking.net/games/884/ and read a romhacking guide. The asset editors and utilities might be enough. More advanced stuff by some asm hacking which may come in form of preexisting patches. Usually it requires understanding only a portion of game's architecture and memory layout.

If you're really keen to start such a project, as I would be keen on playing it, you're likely to spend entire first phase development in level editor getting the sprites and maps right.

Average person doesn't have strong opinion about some bit of data irrelevant to their life.

If there is a thing, and topic about it has reached the internet discussions, the participants will have an opinion regardless of their actual practical knowhow about the thing. They'll form their opinion otherways. Platforms like Reddit favour a master opinion due to score and moderation system, so one out of N wrong theories will surface as the master opinion.

In real life, if you ask bunch of random people about the thing they don't know, you get wildly different answers, and largely no-one will back up anyone there. Certainly not in enough force to push a confidently wrong answer up as the "people's opinion"

I don't know what's their deal with glyphosate but I'm pretty confident that avg Redditor never held a can of WD in their life.

Supermicro gave us same type of assistance. Then new feature of bifurcation did not work correctly. Without it, enterprise telecommunications peripheral that costs 10x more than 4 socket Xeon motherboard can't run at nominal speed, and it was ran on real lines, not test data.

They sent us custom BIOSes until it got stabilized and said they'll put the patch in the following BIOS releases.

The thing is neither Intel nor AMD nor Supermicro can test edge cases at max usage in niche environments without paying money, but they would really love to claim with backup they can be integrated for such solutions. If Intel wants to test stuff in space for free they have to cooperate with NASA; the alternative is in-house launch.

Not only that, reddit hive mind is plain wrong in most of the cases. Plus in number of occasions the "le reddit investigation", "we did it reddit" excrement caused real-world issues for people that they were targeting, and those people were innocent.

Reddit is ok and quite cool for targeted discussion on targeted sub-reddits. But all the general subreddits visited by general population and everything that pops once in a while on the front page is a target for hive mind.

For HN comparison, there is a lot of "wrong" here too, but here you can find a cited academic study from one good American university that reveals most of the botfarms and fake news disseminators come from western sphere. If you try to claim on Reddit or anywhere on the internet that fake news champion is not Russia+China+whoever is evil, your entry will get buried.

Also, ask yourself who's the median redditor. For my country's national subreddit the median redditor is a high school kid from the capital.

Unix terminology is older. FD is a kernel-user interface based on integer map. HANDLE is a typedef'd pointer. Apples vs oranges.

Curious how different a long time FreeBSD user feels. I have a strong distaste for anything not nvidia.

Official nvidia drivers have been added to FreeBSD repository 21 years ago. I can't count the number of different types of drivers used for ATi/AMD in these two decades. And none had the performance or stability.

When those "informational" sites were normal 15 years ago, browser like Opera had user-CSS that you could just override, and had a number of presets. You could format the site to look like C64 BASIC.

The stuff you're talking about isn't about browsers its about the websites.

If you had a website that uses javascript to parse MD or any other markup, spit it out as trivial HTML with light DOM, client-side formatting can do everything you want.

The problem is that modern websites use patterns that workaround users' capability to customize the presentation of the website. They do not want you to look at their site the way you want.

How is this any different than rendering PDF in browser? PDF is not a Web standard. Browsers choose to ship internal plugin to handle PDF.

PDF is done via an internal plugin. Standards compliant web browser doesn't have to do anything with PDF. Major browsers have internal type handler for PDF.

Similar type handler is engaged with XML. Unless you can utilize W3C standards to implement a custom markup language using XML/XSLT and have it work across browsers without plugins.

SVG is vector graphics.

For another full markup to be even considered there would have to be one that's widely adopted and realized through plugins. Nobody is making interventions in standards to open up venues for easy implementation of custom markups when those markups are used by 0.001% of publishers.

Agreed... but not what I was talking about. HTTP has no files or extensions, it's just URL that someone named dot something. Since it doesn't have to be that file type behind, I don't expect it to.

How many hypertext formats apart from HTML are supported without plugins on major browsers?

Asking genuinely, I don't know, but it's an important fact to take into account if you're planning ahead.

This is somewhat stupid from my angle (the W3C recommendation).

I don't expect that url.html is a static html file. I expect it to be server-side generated in 2024. For me site.com/page and site.com/page.html are the same. I do not expect different behavior from my web client side. So I may switch backend engine every year, and I'll just route the request sfrom page.html and that's it.

What's way worse than this is using non-HTML extensions for emitting html. I go to pichost.com/image.jpg and I get a webpage served. This is a bad pattern and it needs to go away. I'm not even going into responding differently depending on user-agent or referrer, if you have combination of these you get JPG returned, if you don't you get a webpage returned.

Which is exactly my point.

The question isn't whether Dyson speheres radiate, the question is can we detect an artificial megastructure and my answer is no, based on the hypothetical Dyson design.

Because the topic isn't about heat per se but heat signatures and detecting artificial heat signatures across the universe.

Of course everything radiates heat I did not think I have to get down to that level in commenting here.

A hypothetical megastructure Dyson's sphere would not radiate heat. And I'm not so sure that you can apply the stealth principle here. Stealth inhibits active measurement and astronomical measurements are passive. We have sensor resolution and we have a mass of data to sift through - each time sensor generation or data processing advances, we see stuff we haven't seen before.

The data is analyzed as a dynamic system. Radar just looks at a bounce. If you setup radar incorrectly you might get false hits and no returns on valid targets. If you use a wrong model in analysis of astronomical data you're never getting anywhere close to a correct result.

Practical thing is not having to recompile 3rd party drivers (vbox ko) every time kernel gets upgraded. Tho DKMS tries to take care of that without admin intervention, it's not always bug free.

On the other side VirtualBox the software application is designed to integrate with the desktop well, VNCing into the guest is not an alternative to this.

I hope efforts will be made in FreeBSD world too against its bhyve hypervisor.

The terminology issue is curious but it has been already covered here lately in a topic about Linux direct rendering manager, DRM. The acronym was used in a narrow circle of people compared to "the whole ICT", as were keyboard-video-mouse devices. Less than 1% of professionals deal with Linux internals on that level, and less than 1% of professionals are server room on-site engineers. There wasn't collective consciousness about these terms so they got reused.

Also LVM is taken by something else (storage) and LKVM would be confusing.

Yeah a lot has changed since then. We had to keep track of stable branch to get close to Linux desktop features most of the time, sometimes even 'current' branch. Today you can use release for 99.9% of use cases, and upgrading releases minor or major is pretty straightforward and way faster than it used to be.