holoiso VS Pi-hole

If you're really feeling adventurous.. try Holo ISO

Today I tried to install this https://github.com/HoloISO/holoiso, a version of arch Linux, on a 64 gb Sandisk sd card. After installing, the linux would not start. I tried to boot it on multiple devices with no luck. And now the sd card seems to be stuck in read only. Windows says it requires a format to work, which fails. Linux is able to read it but in properties says only the user “root” can write things on the card. Is this the card dying or is there a way to gain access??

I have not personally tried it, but HoloISO claims to bring SteamOS 3 (the current arch-based version) to generic non-Steamdeck hardware.

https://github.com/HoloISO/holoiso

Check out HoloISO. Just as good

There's an open issue about it: https://github.com/ValveSoftware/SteamOS/issues/742—since Dec 2021. There is https://github.com/HoloISO/holoiso though, but I suppose they just use the same binary packages as the real stuff..

The Steam Deck is less powerful but can accommodate a cheaper pricepoint. I see you are fairly experienced with general Linux so I will spare you the details, other than that ProtonDB is an excellent resource. The Ally is said by many to be less comfortable and it also lacks 2 back buttons and touchpads. The Ally can actually run SteamOS via HoloISO and it is a fairly good experience. Alternatively, if you stick with windows, you can get the Steam Deck UI by using Steam Big Picture.

The Project you mean is called HoloISO - which according to their Github - This project attempts to bring the Steam Deck's SteamOS Holo redistribution into a generic, installable format, and provide a close-to-official SteamOS experience. (There is also ChimeraOS that features some more things)

You can use https://github.com/HoloISO/holoiso to get SteamOS on your desktop

Si te preguntas, ¿por qué no usar Adguard o Pihole? 🤔

This is an overreaction, almost to the point of absurdity.

Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).

A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods, rather than throwing the baby out with the bathwater.

[1] https://brew.sh/

[2] https://github.com/pi-hole/pi-hole

[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...

[4] https://rvm.io/rvm/install

Pi-hole to block ads and tracking for my less technically savvy relatives

https://pi-hole.net/

I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS.

Note: This isn't a shill for NextDNS; I love these kinds of projects and think they absolutely should exist, but NextDNS just happens to be one of those dead-simple SaaS tools that is an insanely good value.

0 - https://pi-hole.net/

1 - https://nextdns.io

It definitely IS an option, but at the network level.

https://pi-hole.net/

It runs on damn near everything, and is a DNS level adblocker for the whole network.

I recently switched to Wipr [0]. It’s dead simple to use, and will auto update its filter lists in the background.

Adguard [1] is a decent free option.

I also use a Pi-hole [2] on my network.

[0] https://kaylees.site/wipr.html

[1] https://adguard.com/en/adguard-safari/overview.html

[2] https://pi-hole.net/

Are you trying to build a DNS proxy (similar to Pi-hole) that intercepts DNS requests and checks for the ones that look harmful? If so, I would suggest trying to separately build a DNS client and a DNS server, before trying to integrate them together. Start with Beej's Guide to Network Programming if you need to learn the basics of sockets, and then take a look at the documents that define the DNS protocol itself (RFC1034 and RFC1035).

Setup a pi-hole.