In fact, being able to push static images directly to such a registry with Guix would be a great feature. Both for continuous integration (without needing Hydra) and for coupling with a cluster scheduler such as Kubernetes.
1 karma · joined December 26, 2022
In fact, being able to push static images directly to such a registry with Guix would be a great feature. Both for continuous integration (without needing Hydra) and for coupling with a cluster scheduler such as Kubernetes.
Just perused their job page and will apply this week. Sound like they could use some Varnish and Ceph talent :)
Do you have a source for this? I'm not doubting you, but I've played copious amounts of XCOM2 (until it broke on NixOS..) and didn't notice. But now that I think about it, the hit chances are less predictable than in the prior games.
The presentation is focused on how the fuzzing technique works rather than individual file system performance, but the "time to first bug" is quite telling. Copied here:
ext4 (2h)
XFS (1h45)
GFS2 (8m)
NTFS (4m)
NILFS2 (1m)
HFS (30s)
HFS+ (25s)
ReiserFS (25s)
OCFS2 (15s)
F2FS (10s)
BTRFS (5s)
I've had miscellaneous failures with the bottom three, but XFS and ext4 have been rock solid. Unfortunately ZFS and CephFS were not included.Would love to see a Jepsen-style analysis of the various file systems too.
The session is initiated from the client, but if you can MITM it or compromise the provisioning server all bets are obviously off.
I have mixed feelings about TR-069, but don't see how devices can stay current without something like it.
I think part of the reason they are now cruising past Nix (despite 1/10th of the users) is that it's written in a proper programming language, and not a home-made language that relies heavily on bash.
That said, I'm really happy with NixOS after two years, and would not consider going back to any "conventional" distro for my own workstation. Coming from a Gentoo background, there is nothing like screwing up your system and simply booting into the previous generation :)
Having the entire system configuration in one place that can be version controlled is a big plus too. You can create a live CD, VM, container etc from the very same code.
Nix and Guix can also be used standalone (think Homebrew or Gentoo Prefix), and can be very handy shell tools. E.g. `guix environment foo`[1] will drop you to an ephemeral shell environment with all build dependencies of package foo available.
0: https://www.gnu.org/software/guix/manual/html_node/Security-...
1: https://www.gnu.org/software/guix/manual/html_node/Invoking-...
See https://github.com/LibreSignal/LibreSignal/issues/37 and discussion upthread.
Security problems are usually clearly marked in the changelog: http://www.openbsd.org/errata59.html
What really annoys me with OpenBSD is that users are expected to download the CVS source and compile it to fix problems rather than upgrade to a dot-release.
For a normal user that's fine, but if you have a bunch of servers you'll need a sophisticated build/deploy infrastructure to stay updated.
What if the inside of the network is further segregated, and the Prometheus instance does not have access to all endpoints. Can I use the push gateway as a "proxy", or is a direct route required.
Sorry for the stupid questions. Now it's getting entirely academic of course :)
Edit: just re-read your post and saw the proxy note. Time to read the documentation again. This setup should make for a good blog post.
1. make it highly available
2. play nice with firewalls
If I deploy Prometheus outside a NAT, and want to monitor 100 physical machines on the inside with node_exporter, as well as a dozen different services, how to make these metrics available?
What if I have four identical NATed sites and want them all monitored by the same outside Prometheus instance(s)?
Nothing prevents you from paywalling a GPL program as long as you distribute sources to legitimate users on request. Free as in freedom, not as in beer.
Of more recent software "clones", there is guix vs nix, mcron vs vixie-cron, shepherd vs systemd, gnutls vs openssl, all high-quality implementations of good ideas.
Sure, lsh has a way to go before it's a viable alternative to OpenSSH, but I wouldn't say it's low-quality. I don't think I've come across a GNU project which felt "half-put-together", rather the opposite.
The GNU projects' motivation is very clear-cut and not at all different from e.g. the BSD camp or suckless. How are they questionable?
The Openstack documentation is terrible, the user interface is awkward and clunky, and the configuration files for each component are several-thousand lines of Python code. Unsurprisingly it has more bugs than New Zealand, and regularly breaks in inexplicable ways. Additionally it does not support crucial features such as node evacuation or rebalancing, and you can't even use the built-in scheduler to pick a new host when live migrating.. And good luck upgrading from one version to the next.
If you're a small shop, oVirt or Proxmox are both solid options. Ganeti fits here too, but has a much higher barrier to entry (no web UI or guest OS support by default).
Source: used Ganeti for 6 years at three different sites, and recently resigned from my current job after one year of fighting Openstack because I could not convince my colleagues to pick a better platform.
I've used Ganeti Web Manager[0] in the past, but would probably try out Ganetimgr[1] for future installs. The command-line tools are very good however, and I don't think the web interfaces expose the full functionality (i.e. rebalancing, node evacuation, master-failover, etc).
It doesn't look like much, but is rock solid and supports everything Proxmox does and more, save for the lack of a built-in web UI (but there are several 3rd party ones, as Ganeti is 100% API driven).
No affiliation, but have successfully deployed it at multiple sites (and would love to do so again, wink wink).
DNS Name: wired.com
DNS Name: *.condenast.io
DNS Name: *.wired.com
DNS Name: ads.thestudio.condenast.com
DNS Name: allure.com
DNS Name: *.allure.com
DNS Name: architecturaldigest.com
DNS Name: *.architecturaldigest.com
DNS Name: bonappetit.com
DNS Name: *.bonappetit.com
DNS Name: brides.com
DNS Name: *.brides.com
DNS Name: builtwhileflying.com
DNS Name: *.builtwhileflying.com
DNS Name: cntraveler.com
DNS Name: *.cntraveler.com
DNS Name: cntraveller.com
DNS Name: *.cntraveller.com
DNS Name: condenast.com
DNS Name: *.condenast.com
DNS Name: condenast.io
DNS Name: condenastdigital.com
DNS Name: *.condenastdigital.com
DNS Name: condenaststudio.com
DNS Name: *.condenaststudio.com
DNS Name: condenet.com
DNS Name: *.condenet.com
DNS Name: details.com
DNS Name: *.details.com
DNS Name: epicurious.com
DNS Name: *.epicurious.com
DNS Name: glamour.com
DNS Name: *.glamour.com
DNS Name: golfdigest.com
DNS Name: *.golfdigest.com
DNS Name: gq.com
DNS Name: *.gq.com
DNS Name: newyorker.com
DNS Name: *.newyorker.com
DNS Name: self.com
DNS Name: *.self.com
DNS Name: style.com
DNS Name: *.style.com
DNS Name: teenvogue.com
DNS Name: *.teenvogue.com
DNS Name: vanityfair.com
DNS Name: *.vanityfair.com
DNS Name: vogue.com
DNS Name: *.vogue.com
DNS Name: webmonkey.com
DNS Name: *.webmonkey.com
DNS Name: wmagazine.com
DNS Name: *.wmagazine.comMany people on this site care about the language, so why should we not include it? People who dislike the Y ecosystem are free to ignore it, and people who have been looking for an X implementation save some brain cycles figuring out what it's written in.
Personally I think more articles should include this. I'm always disappointed when a cool-sounding project is written in Node..
http://aux.messymatters.com/pgnames.html (2006)
And later this from 2015: http://www.paulgraham.com/name.html
The gist of it is that anything will do, as the name will be associated with your product, not the other way around. Hopefully this can boost your confidence a bit :)
Source: chronic procrastinator who has been studying MBTI for years.
The thing that has always disturbed me about O_DIRECT is that the whole interface is just stupid, and was probably designed by a deranged monkey on some serious mind-controlling substances.
Still does ~20 hours with extended battery after more than a year of heavy usage. And they're some of the most robust portables available.
* "more or less 1535 customers"
* ansible would fail if variables are unset (though they could be empty)
* no mention of --no-preserve-root
* who mounts an off-site backup, instead of pushing with scp/curl/whatever
* googling his name does not dig up any company
http://portix.bitbucket.org/dwb/
It's fully keyboard driven (to the extent possible) and has a decent amount of extensions, including ad blocking and a great requestpolicy manager for controlling 3rd party requests.
I always fill these with awkward or absurd questions/anwers that would be amusing if a human operator ever needs to verify them. E.g.
Would you like to go on a date with me?
What color pants am I wearing?
What is the square root of insanity?
Obviously you need to store these in a password database in order to remember them, which kind of defeats the purpose. If I have to choose from predefined questions, it goes along these lines.
Q: What was your mothers maiden name?
A: Why, are you stalking her?
Q: Where were you born?
A: Oh I can't remember, it's been so long!
That whole list is gold. My favourite so far is "space station": -+-
Oh, and I think tmux' "mouse on" lets you wheel-scroll the buffer, although I haven't used it.