CoolCold

embedding transparent containers into Windows native apps looks huge, extra cool is GPU access from container and mentioned OpenClaw like tool cases in mind, ports and folders.

Like the idea!

Yep

Try to search vacancies for FreeBSD or candidates with FreeBSD knowledge/background, you will be surprised, its desert.

Even TrueNAS realized it's a dead end for reaching wide audience needs and migrated to Linux (as you mentioned zfs, your probably heard a thing or two on TrueNAS).

I have not tried in the last 10 years, so don't have numbers, my ballpark figure about having small infra team say of 5 persons and try to hire for FreeBSD would be longer and more expensive.

I see somewhat tolerable Linux Corp fleet of laptops (still meh, but somewhat works), what you will reply to your users when they complain on WiFi or Zoom not working and how will procurement work for you interesting questions for me.

Red Book for FreeBSD animal, can meet somewhere deep in tundra, but not a widespread species- extinction form my POV.

Hard to tell about FreeBSD, it's basically extincted, but think of webhosting servers, wordpress, cPanel/Plesk and alike.

often it's ssh'able with things like rbash and other restrictions and almost always you, well, can run something there (as you can edit php/other files right from web management ui).

Hordes of this (in Linux world).

You can wire lsyncd for near real-time syncs and btrfs snapshots for offline storage

I had bad feelings on MC, as it's flaky.

Far Manager or Dos Navigator are much better IMO.

a RCE vulnerability is the type of thing that nation state actors in Russia and North Korea dream of

Does this mean other state actors are beyond needs of RCE vulns as their tools belt and North Korea and Russia lagging behind? Some other interpretation from security-involved practitioners here - like, I don't know - we already have Pegasus, phew on OpenCode RCE?

Well, there is Aider-CE aka Cecli, which moves, updates almost every day (I'm tried to try it but much).

Opencode is totally different beast comparing to Aider and I mostly stopped using Aider for 2 months or so - it just iterate simpler and faster with OpenCode for me.

Genuine question, as someone who never used Claude Code, but used OpenCode/Aider/GeminiCli - as many here say Opencode is better, mind sharing why (from end user perspective)?

I was thinking to try Claude Code later and may reconsider doing so.

Figure 9: Durable writes with io_uring. Left: Writes and fsync are issued via io_uring or manually linked in the application. Right: Enterprise SSDs do not require fsync after writes.

This sounds strange to me, of not requiring fsync. I may be wrong, but if it was meant that Enterprise SSDs have buffers and power-failure safety modes which works fine without explicit fsync, I think it's too optimistic view here.

Note that Aider is not much maintained over last 3 months or so, there is a fork Aider CE, though I'm just watching their changes through rss and not used myself.

I'm more in Opencode world now and its in general more efficient for me (I'm sorta sysadmin by day, not a programmer, so agentic mode with Opencode saves a lot of time cuz you can just tell - write adhoc Python script and check which objects/methods present at that library- savings me from a boring part of you know programming/diving deep in unknown languages).

On Aider part, I especially liked ability to nitpick the function name, which is great for more focused changes/investigations.

Am I reading something wrong on Racknerd? https://www.racknerd.com/kvm-vps

1 GB RAM 2 vCore 50 GB RAID-10 SSD 1 TB @ 1Gbps 1 Free IP $17.99 /month

that's far from any sort of cheap, may be there is something very special with them?

by WSL? Not my own experience, but I have couple of guys who still on Win10/WSL. Myself I've migrated to Win11 not sure when exactly, likely 4 years ago

I'm 99% sure ive seen such questions/requests on Reddit for Windows server.

I feel your pain - bites me from time to time, especially in KVM ;)

it may happen that you just don't need it - the same way not everyone need to use vim/neovim.

without tmux/screen though, it's much harder, even less reliable, to work over ssh, so it becomes natural need for such sort of tools.

Say I use screen and later tmux since I believe ~ 2010 but not using "advanced" features like "panes" and screen splitting every month, most of the time for me it's just switching between windows in session and different sessions (not that often) and that's all.

As a helper, for some projects, I do use predefined layouts (say first 4 windows opens with inventory dir, other 2 with root folder of ansible repo) so on, but need this also not very often, like when laptop reboots (which is every ~ 3 week on Win11 nowdays)

Ctrl+Shift+F on my Windows Terminal - don't remember, have I've adjusted it or it's default behavior

I see in config file, actions { "id": "User.find", "keys": "ctrl+shift+f" },

so probably I did

Indeed, I agree here, Linux, and basically Unix was not designed to work without administrator.

I would argue that more time was spent on thinking "how we do hotplug CPU on our machine" than on "how that user will work with USB drives".

Well, built in feature of Reset PC will even download fresh iso for you and will boot in fresh install. Optionally you may ask to keep your files too.

[1] to be honest, I'm not sure I understand the intent of open_file_cache... Opening files is usually not that expensive

I may have a hint here - remember, that Nginx was created in the times of dialup was a thing yet and having single Pentium 3 server was a norm (I believe I've seen myself that wwwXXX machines in the Rambler DCs over that time).

So my a bit educated guess here, that saving every syscal was sorta ultimate goal and it was more efficient in terms of at least latency by that times. You may take a look how Nginx parses http methods (GET/POST) to save operations.

Myself I don't remember seeing large benefits of using open_file_cache, but I likely never did a proper perf test here. Say ensure use of sendfile/buffers/TLS termination made much more influence for me on modern (10-15 years old) HW.

You are probably talking about VMs - those do have traffic limits. Servers, on the other side, with default 1Gbit NICs doesn't (let's say until you consume 80%+ of bandwidth for months)

Quoting:

Traffic

All root servers have a dedicated 1 GBit uplink by default and with it unlimited traffic. Inclusive monthly traffic for servers with 10G uplink is 20TB. There is no bandwidth limitation. We will charge € 1 ($1.20)/TB for overusage.

I don't know how much traffic they have, but say even on overexpensive IBM servers hosting, serving ~ 100TB/month was around 5000$

+1 from me for

With swap enabled, it is very, very, VERY common for the system to become completely unresponsive - no magic-sysrq, no ctrl-alt-f2 to login as root, no ssh'ing in ...

It's usually enough to have couple of times when you need to get into distant DC / wait for some IPMI connected for couple of hours, to learn "let it fail fast and gimme ssh back" on practice vs theory on "you should have swap on"

just curious, what would be the business direction to "Linux-only code"? Don't need any trade secrets, just quick expression on the area/target auditory.

I.e. - I have tried WSLg (running GUI apps in WSL) but disabled it all together, as after running xclock and couple of things like that to ensure it works, I couldn't find any interest in running GUI apps on Linux.

I can somewhat imagine need for work purposes, if you are falling into some webdev area and need to run some tests against local browser, but that's different from my POV.

just doublechecked with "Confirm-SecureBootUEFI" - says True on my laptop which used > 1 year. I'm pretty sure on the previous system which was used for 4 years it was on too - have not noticed any issues.

Windows 10 and then 11

Interesting - using WSL on Thinkpads (T460 and some Carbon from ~ 2018 till 2020, 2020-2024 on T480 and T16 G2 now) with WSL (WSL2 mostly) and cannot say it was/is resource hog or blasting the fan out of the blue. Working with balanced power mode mostly

isn't 3128 port is mostly used by proxies (squid and alike)? https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbe...

I personally run my proxy there and overall I'd take some > 10000 port for such kind of stuff

I'm not arguing on venv to isolate installs, I'm saying that relying on Python coming from UNIX-like OSes is close to impossible for, at least web related projects. I.e. Ansible does a lot [in terms of what code it generates] to keep itself compatible with whatever Python3 versions it may find on systems ( remote hosts )

things like virtual envs

I consider my point as still valid with UV, what you wanted to express?

On UV specifically - say 'asdf' compiles python right on your system from official sources - means using your ssl libs for example. UV brings Python binary - I feel worried on this.

Not only because the syntax is more human-friendly, but also because the Python interpreter is natively integrated in all Unix distros

That's kind of very optimistic evaluation - literally anything beyond "import json" will likely lead you into the abyss of virtual envs. Running something created with say Python 3.13.x on Ubuntu 22.04 or even 24.04 (LTSs) / Rocky 9 and the whole can of worms opened.

things like virtual envs + containers (docker like)/version managers become a must quickly.

Thank you!

Indeed, container live migration is limited and a bit unclear on "network devices" - bridged interface is network device or not?

Bit ironic, that even with using CRUI, which AFAIK was created by the same Virtuozzo guys which provided OpenVZ back then, and that VEs could live migrate, was personally testing it in 2007-2008. Granted, there we no systemd by that days, if this complicates things. And of course required their patched kernel.

Live migration for containers For containers, there is limited support for live migration using CRIU. However, because of extensive kernel dependencies, only very basic containers (non-systemd containers without a network device) can be migrated reliably. In most real-world scenarios, you should stop the container, move it over and then start it again.