Linux

It is absolutely not weird and I would argue it's even important. The whole point of the interview is that BOTH parties evaluate each other according to THEIR criteria. Maybe for them it is not important but for you it's a requirement, maybe you discover through that the culture is not aligned. It's great for both to understand this NOW rather than 3 months down the line, as you started to settle, they teach you everything about their specific infrastructure and... it doesn't work, now both needs to redo the process again.

So yes IMHO it doesn't matter how "silly" it might sound to you, now during the interview process, is the time to insure that it's going to be an actual fit.

You have to also be aware that they might say no, or that the question itself might lead to a rejection. They might just not want this due to internal policy, security, culture, belief system, etc. This might feel like a loss but again, better know now and look for a place that match your needs that later on.

I also don't conduct many interviews, especially not right now, but when I did anything that could help me understand what made the candidate tick, what got them genuinely excited or angry, was super important. Sure I wanted to insure the technical capability but beyond that I was looking for any clue to see if we were compatible beyond just task in, result out, because in the long run that's what would make us both happy.

TL;DR: yes, ask for whatever YOU want.