evanjrowley

I use a case on my MacBooks to protect them from damage. These cases are made of softer materials that are easier to chamfer. I make a similar modification when necessary. Sometimes it's worse with the plastic cases because the injection mold seam is that sharp edge.

Does the ">" mean "greater than" or is it meant to symbolize an arrow in a ordered sequence?

Finding laptops that can support multiple hard drives is becoming more challenging every year. The 15"-17" workstation class Dell Precision, Lenovo P*, HP Zbook, and Framework 16 laptops are well suited to this purpose. Some of them even came with Xeon CPUs and ECC RAM support.

I use IncusOS when I need the Linux kernel for some specific hardware like the latest graphics or some AI accelerator. FreeBSD for when none of those things are necessary.

Considering the amount of Linux distros based on Debian, it is truly a shame that Debian/kFreeBSD stagnated. We could have had Proxmox/kFreeBSD with support for ZFS Boot environments! The evolution of FreeNAS/TrueNAS demonstrates things have been going in the opposite direction.

I'd like to know more about what it takes to turn on PCI pass through for laptop hardware. On desktops and servers it's typically the IOMMU setting in the BIOS. Is that also commonly available on laptops?

Definitely not independent kernels but my guess is he's referring to Virtualization-Based Security (VBS) - it gets turned on by default if your Win10/11 system has virtualization enabled.

  One such example security solution is memory integrity, which protects and hardens Windows by running kernel mode code integrity within the isolated virtual environment of VBS. Kernel mode code integrity is the Windows process that checks all kernel mode drivers and binaries before they're started, and prevents unsigned or untrusted drivers or system files from being loaded into system memory.

I suppose this applies to Wi-Fi drivers?

Link: https://learn.microsoft.com/en-us/windows-hardware/design/de...

>But docker

Maybe one day! One of the things that has changed in the past 20 years with FreeBSD is the addition of bhyve. Virtualization on FreeBSD was not great prior to bhyve. Because FreeBSD waited to implement it, they ended up with an arguably more modern hypervisor versus what Linux had at the time. Maybe history will repeat when it comes to application containers / docker images. Podman came 5 years after Docker and the result was better. It could happen with FreeBSD too.

I thought he was gonna talk about inodes: https://en.wikipedia.org/wiki/Inode

Maybe someday someone will expose these in the form of a graph database API (just for fun).

>It truly is not a choice, as I cannot sustain my family / lifestyle

Success and failure are choices. Accepting this allows us to take responsibility for the worlds we've created. Ignoring this is self-destructive act of cognitive dissonance and we pay for it years later.

  Set Linux as router in one command. Support Internet sharing, redsocks, Wifi hotspot, IPv6. Can also be used for routing VM/containers

https://github.com/garywill/linux-router

Novel. A similar approach could be taken by other SaaS tools to comply with age verificaiton laws. Just write an entry to the client's hosts file that points to a subdomain corresponding to a particular birth year. Simple enough for legislative representatives to understand.

/s

Addition of a "Dark Mode" button would be much appreciated!

That is very much true. Lack of knowledge in a legal context is a very weak defense.

Generally speaking, open source ecosystem knowledge is not something that shows up in job descriptions, interviews, or regular training for non-technical staff in most software companies. Hopefully that will one day be the case but until then there is a high likelihood that misleading statements can be made accidentally.

It's possible their spokesperson was not informed about SimStudio being the basis for Delve. Lots of people in sales and marketing do not know little about how open source software works.

Looks good overall, but that huge seamless trackpad looks like it will be a nightmare for touch typists. It blends in so well with the palm rest that it will be hard to avoid accidentally moving the cursor if you type with your palms resting. Dell will need that extended battery life to make up for time spent correcting typos.

I have employer-provided XPS 14 9440 and it's never unplugged from the dock because this annoying touchpad issue is too much trouble.

Why would they target professionals with a laptop that has such an anti-feature? I can understand it makes it easier to clean, but wouldn't that be more important for non-computer enthusiasts who don't care for their laptops?

I like the way the problem of "m" is solved by Ubuntu Mono: https://fonts.google.com/specimen/Ubuntu+Mono

It's what I landed on after completing the Coding Font game submitted to HN yesterday: https://news.ycombinator.com/item?id=47575403

Like printing a document, scanning it, and saving as a PDF, all without the printer and scanner.

I'm talking about this, basically: https://www.linuxquestions.org/questions/*bsd-17/howto-zfs-m...

There have since been implementations for Linux but no distribution is designed to support them.

As a Proxmox Backup Server user... I still want ZFS roots with native rollback support. FreeBSD is more likely to execute this well vs. Proxmox.

I'm talking about this, basically: https://www.linuxquestions.org/questions/*bsd-17/howto-zfs-m...

There have since been implementations for Linux but no distribution is designed to support them.

Regardless of the number of drives available, you gain an advantage when your file system can leverage snapshots to roll backwards or forwards. There are other Linux-native filesystems that can provide this capability too, but many admins prefer ZFS because the full range of capabilities is unparelleled.

Anecdotally, Bhyve has worked in FreeBSD for a decade now. Eventually it got ported to Illumos because it was better than their implementation of QEMU.

Without looking at the Sylve docs, I'll conjecture that it has deeper integration with ZFS. With a foundation on FreeBSD, there is a likelihood Sylve can support ZFS-on-root rollbacks better than hacking it into Proxmox. A rollback capability is why I'm looking for Proxmox alternatives. In the Linux world, Talos Linux and IncusOS provide A/B updates which achieve a similar rollback capability. With something based on FreeBSD, your "immutable" OS and all of it's data can be treated equally as ZFS datasets. There's also a higher risk that a Linux kernel update will break ZFS.

I wonder if my grandmother had heard of this book. She lived 10 minutes from the German border in the Netherlands During this time, she mentioned there were radioactive clouds flying in from Chernobyl.

Thanks. One of the things that confuses me about the wiki is the official one contains a disclaimer about the potential for the content to be out of date. The unofficial wiki has an easier to use domain name and no disclaimer, so unless someone find it beautiful the wiki home page, it can be easy for them to interpret the unofficial one as being the de-facto/preferred source of information.

Good luck! Talos Linux seems like an amazing project. I wish Sidero much success.

I totally agree with the idea of replacing Proxmox with something more immutable.

IncusOS seems like a strong contender.

I've also considered installing Proxmox with ZFS Boot Menu to get a rollback capability. I'd need to figure out how to properly manage state when multiple storage providers are in use. Like for example, what would happen if the pool for VMs had newer data than the root snapshot I roll back to? Even with the answer, obviously the overall theme is Proxmox is not designed to operate this way.

Agree that this is a very messy situation.

Most health information transferred online between patients and other entities goes through a portal rather than email to ensure PHI isn't transmitted over unencrypted SMTP or simply forwarded on to some insecure mail server. I.e. data loss prevention.

Wherever it goes, there are a various services that can be used to ensure the file is not malicious. Probably API integration with Palo Alto WildFire or ICAP protocol with Opswat would be the best choices. Neither would be affordable for small government offices.

Glad to see Talos Linux there!

Another interesting, though less radical take on an immutable container OS is IncusOS. Made by the same people behind LXC: https://github.com/lxc/incus-os

I wish the article's NixOS section had mentioned impermanence features which can be used to make NixOS actually immutable: https://nixos.wiki/wiki/Impermanence

I would like to explore the interoperability/compatibility limits of LXC and OCI support in FreeBSD 15. Both with FreeBSD as an OCI container and Linux OCI containers within FreeBSD.