hpb42

I use ZFS on my laptops and desktop but kind of considered Btrfs for this new NAS. What made me decide to use ZFS instead is that Btrfs does not have [yet] transparent encryption, I'd need to use dm-crypt/LUKS. ZFS has that natively, so :shrug: When transparent encryption lands on Btrfs, I may consider it for new machines (or Bcachefs if it gets back in the Linux Kernel).

Wouldn't a ZFS Scrub get the job done?

> Also, has anyone though of how mind-numbingly wasteful solar fusion is? All that energy, and only a tiny fraction makes it to Earth with the rest getting dumped wastefully into space. Seems like an area that's ripe for disruption by a startup.

That energy can be captured by a Dyson sphere:

> A Dyson sphere is a hypothetical megastructure that encompasses a star and captures a large percentage of its solar power output

- https://en.wikipedia.org/wiki/Dyson_sphere

Maybe Incus[0] as an alternative instead of fork.

- [0] https://linuxcontainers.org/incus/docs/main/

In case one wants to switch from Hashicorp to alternatives that are similar enough or forks, what would that stack be?

Hashiternative stack:

- vault -> openbao (fork)

- terraform -> opentofu (fork)

- consul -> ?

- nomad -> slurm + something that runs/orchestrates windows jobs?

- hcl -> dhall + nix?

Oh, cool. They implemented a `download_more_ram()` function![0]

Does it crash safely as well? I did not test it, I more than 640 KB of ram.

- [0] https://github.com/Speykious/cve-rs/blob/d51f52dd64f148a086e...

> billions of dollars' worth of safety measures

Is this a bad thing? Investing a lot into safety measures to avoid catastrophes seems better than investing significantly less because we assume is safe.

Could you elaborate on why this investment is an argument against nuclear?

I once talked to people that worked at Angra Nuclear Power Plant in Brazil and they said the real danger is actually the spent nuclear fuel. The power plant itself is safe due to many redundant safety measures, continuous tests and monitoring. I don't have a source for this, and don't take my words for absolute truth, I'm not an expert in the subject.

> kept from harming us by a large crew of skilled people

I'm glad to hear people working with nuclear are skilled ;) I assume people working in solar/wind/hydro are also skilled at their craft. And I'm sure you didn't imply that, maybe the phrasing wasn't the best?

Brazil abolished daytime change a couple of years ago. Our time is the same all year, no more +1 and then -1 hour.

It was mess on the day there should a change, many people arrived on their appointments one hour before or later. Many automatic systems changed their time, different clocks at home reported different hours.

This chaos lasted one morning. After some time, nobody now complains about not having it. Many people don't remember about the change anymore. The only people that complains about daylight change are the ones that work with people from countries that have that.

Abolishing daytime change is not the same as adopting an "universal" (country-like?) timezone, but shows that it is _possible_ to do on a "big country spanning a lot of latitude as well as longitude and tens of millions on wildly different work and sleep schedules".

Maybe the main issue is that many people fear change? (Which is quite "funny", as winter/summer time is a change in time...)

Don't confuse extremely large telescope[0] with Extremely Large Telescope[1].

[0] https://en.wikipedia.org/wiki/Extremely_large_telescope

[1] https://en.wikipedia.org/wiki/Extremely_Large_Telescope

One of those left out features is `sudoedit` or `sudo -e`. I use this a lot when editing files in /etc or any file that my user does not have permissions. The flag first copies the file to a temporary location with permissions for my user to edit, then opens my text editor (defined via $SUDO_EDITOR env var) as _my user_, without any sudo permissions. After I close the editor, the file is copied back with the original permissions only if there were any changes.

The cool thing is running the editor via my user, which loads my user's configuration/plugins, instead of the root user's.

I really liked the calculus book by Swokowski. The books starts with a revision of the requirements to start learning derivatives, has sections dedicated to applications of that and then goes on to integrals, analytical geometry and differential equations. It will keep you entertained for months.

I worked with designing a local oscillator for NMR spectroscopy, seeing this in LEGO makes me remember all the nice things from that period :)

Would love to buy a LEGO set to have my own NMR machine at home. I couldn't find online, maybe they will release someday?

It would be nice to extend the room with the actual racks of electronics and power amplifiers, they only added the operator computers.

> CERN’s data store has now crossed the remarkable capacity threshold of one exabyte, meaning that CERN has one million terabytes of disk space ready for data!

1MTB -> 1EB ready for data. It is _effective space_, not raw space. And it keeps growing.

Kudos for making it daemonless!

I think Servicer can be a good starting point for people to learn how to use Systemd services and systemd-run. Systemd is huge and can be scary to learn, so providing a set of steps to get a service running is very instructive.

But then, Servicer requires super user priviliges to modify the system, instead of running everything as the non-privileged user, via `--user` flag for systemctl or via systemd-run...

There are few commands to learn the basics when setting up a new system wide service: systemctl and journalctl. Some examples: - systemctl daemon-reload: reload all unit files - systemctl start/stop/status/restart <service>: quite intuitive, don't you think? - journalctl -u <service>: to see all logs from that service. I like to also use `-f` flag to follow new log entries. - man systemctl: the manual for systemctl - man journalctl: the manual for journalctl

Writing new service units is the "hard" part, but there are plenty of "templates" on the net, or you can browse `/usr/lib/systemd/system/` for examples.

But don't let the critics here demotivate you. You made a tool, you published it, congrats!

The article links to the benchmarks in https://arewefastyet.com/linux64/benchmarks/overview?numDays...

Some benchmarks evaluate "execution time", so the lower the better.

Some benchmarks have a "score" instead, that the lower the higher in the chart. I'm not familiar with these benchmarks and don't know how to interpret it. Is higher score worse or better?

Cool! Thanks for the link.

A 10 kWh flywheel that can charge/discharge at 20 kW (lasts for 20~30 min at this power) costs ~11500 USD + installation and control system.

A Tesla Powerwall has 13.5 kWh capacity, delivers power at ~6 kW and costs ~11500 USD.

That doesn't seem a large difference to me.