Hacker Newsnew | past | comments | ask | show | jobs | submit | tstack's commentslogin

I tend to agree with ProZD's tier list[1] where "Kiki's Delivery Service", "Porco Rosso", and "Totoro" are at S rank. Those might also be a good introduction since they're pretty "normal".

[1] - https://www.youtube.com/watch?v=g_8uHtL6V0Y


> There's also a new "https boot", which is supposed to be a PXE replacement, but TLS certs have time validity windows, and some clients may not have an RTC, or might have a dead CMOS battery, and those might not boot if the date is wrong.

I think the lack of entropy right after boot can also be a problem for the RNG. But, maybe that has been solved in more modern hardware.


> ... push it into overload ...

Oh, oh, I get to talk about my favorite bug!

I was working on network-booting servers with iPXE and we got a bug saying that things were working fine until the cluster size went over 4/5 machines. In a larger cluster, machines would not come up from a reboot. I thought QA was just being silly, why would the size of the cluster matter? I took a closer look and, sure enough, was able to reproduce the bug. Basically, the machine would sit there stuck trying to download the boot image over TCP from the server.

After some investigation, it turned out to be related to the heartbeats sent between machines (they were ICMP pings). Since iPXE is a very nice and fancy bootloader, it will happily respond to ICMP pings. Note that, in order to do this, it would do an ARP to find address to send the response to. Unfortunately, the size of the ARP cache was pretty small since this was "embedded" software (take a guess how big the cache was...). Essentially, while iPXE was downloading the image, the address of the image server would get pushed out of the ARP cache by all these heartbeats. Thus, the download would suffer since it had to constantly pause to redo the ARP request. So, things would work with a smaller cluster size since the ARP cache was big enough to keep track of the download server and the peers in the cluster.

I think I "fixed" it by responding to the ICMP using the source MAC address (making sure it wasn't broadcast) rather than doing an ARP.


Yeah broadcast with iPxe commonly has this issue, I’ve also run into it in my career more than once.


> We just don't want your sexuality shoved in our faces.

The flag simply acknowledges that certain people have the right to exist. Extrapolating anything else out of that is you being weird.

> I've been hearing claims of the necessity of doing so for over a decade.

It seems to be necessary because you want to "turn the power of the state against you". All because of a rainbow?

> We won the last election.

Did the whole of humanity have an election that I missed? Just because an election at one time and in one place went one way or the other doesn't mean much to something that is global. If you're speaking of the US Election, a certain person didn't even get 50% of the vote. So, I don't see how you act like this is some mandate that means you get to silence other people.

> We can and will, with sadness but determination power, turn the power of the state against you and make you leave us the hell alone.

You don't seem sad about this at all.

My small site now sports a flag because it is clear it is needed. Are you going to come after me too?


What are you talking about? The commenter above says "We won the last election" and goes on to say:

> Don't trouble yourselves with removing the flag. We will be removing it for you soon enough.

They are very much talking about the government doing this.


The PRQL[1] syntax is built around pipelines and works pretty well.

I added a similar "get results as you type" feature to the SQLite integration in the Logfile Navigator (lnav)[2]. When entering PRQL queries, the preview will show the results for the current and previous stages of the pipeline. When you move the cursor around, the previews update accordingly. I was waiting years for something like PRQL to implement this since doing it with regular SQL requires more knowledge of the syntax and I didn't want to go down that path.

[1] - https://prql-lang.org [2] - https://lnav.org/2024/03/29/prql-support.html


If you want to get started with prql check out qstudio https://www.timestored.com/qstudio/prql-ide it allows running prql easily against mysql postgresql duckdb etc



Nice work! The TUI looks really sharp and I like the histogram on top. Going to play with this today.

TIL awk patterns can be more than just regexes and can be combined with boolean operators. I've written a bit of awk and never realized this.


There's a ton of overlap between "powerful stuff that's easy to write in (g)awk" and "powerful stuff that's trivial to write in perl", but I find awk to be succinct without losing readability.


The article makes it sound like it uses various command-line tools (bash/awk/head/tail) to process the logs. So, I imagine it's not a huge leap to extend support to using journalctl to do that work instead.


One small hitch I found is that this kind of tools are fixes in what to process, so for example I can't use them for structured logging. If it has an escape hatch where I can supply my own pipe (for example `process = 'vector ....'`) then it will be enough.


> the Wayfarers series starting with “The Long Way to a Small, Angry Planet” is maybe the best collection of before-bed reading I’ve ever found.

I agree wholeheartedly and do, in fact, read them in bed. I transitioned to the Wayfarers after souring on The Expanse (I enjoyed most parts of those books, but the black ooze is not for me). The low-stakes, slice-of-life content is more up my alley.


Not exactly Seattle, but the Bellevue library has a makerspace — https://kcls.org/bellevuemakerspace/


Oh nice, the access to a professional quality sewing machine is a cool feature. I do some hobby upholstery and using my homegamer Singer is a real limiting factor.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: