News for hackers. Stuff that matters.

4rtyui9xd

Re:Get better at Googling on Friday April 23, 2021 @07:26PM (#26920456)
For posterity, original title of this was "Googling is one of the most important skills for every developer"
Re:In the Beginning, There Were Taxes on Thursday April 22, 2021 @11:17PM (#26910648)
"Yes, even moreso than the rest of us."

But, generally, the wealthy do not pay more in taxes than the non-wealthy. They generally pay less.

Re:In the Beginning, There Were Taxes on Friday April 16, 2021 @08:30PM (#26840555)
Do the wealthy need the government's services, financed through taxes, as much as "the average person".

What if a US citizen obtainins citizenship in a country that does not tax non-residents, relinquishes her US citizenship and then moves to a country that has little or no taxes.

Re:The Sisyphean Task of DNS Client Config on Linux on Friday April 16, 2021 @05:24PM (#26839236)
If it is flyctl doing the resolution then another idea is to have flyctl do the resolution in a chroot with its own resolv.conf.
Re:The Sisyphean Task of DNS Client Config on Linux on Thursday April 15, 2021 @05:14PM (#26826186)
I can think of a variety of ways. Some involve running some code on the VM. For example, dnscache or dqcache would work. This can also be complished using tinydns. Tiny programs that use very little memory. But it sounds like you are trying to avoid asking the user to install anything other than flyctl on the "bare Linux VM". What is not clear is what programs are installed by default in the "bare Linux VM". The other question is how many ".internal" domains the VM will need to resolve. The simplest solution that comes to mind is when the user provisions an IP, flyctl writes the ".internal" domain(s) for that IP to /etc/hosts. /etc/resolv.conf can then point to whatever the user prefers. IMO, users should be running their own DNS servers, not setting /etc/resolv.conf to point to third party DNS addresses like 1.1.1.1 or 8.8.8.8 or whatever. In the case they are running their own DNS server on the VM, then it becomes trivial segregate internal from external domains. The configuration for dnscache is so easy that it could be done by the flyctl program, requiring no user interaction. (Something like tinydns-config.) One could even have configurations for a variety of DNS servers in flyctl, in case the user prefers unbound, etc.