#flowcontrol — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #flowcontrol, aggregated by home.social.
-
A useful reminder in fluid mechanics: maximizing velocity is not the same as maximizing momentum or energy transfer. This paper explores how global mass balance constrains synthetic jet actuator performance.
🔗 https://doi.org/10.1063/5.0326035
#FluidDynamics #Physics #FlowControl #SyntheticJets #NonlinearDynamics
-
The best hose nozzles of 2026 for gardening and beyond, tested and reviewed https://www.allforgardening.com/1685459/the-best-hose-nozzles-of-2026-for-gardening-and-beyond-tested-and-reviewed/ #FlowControl #FlowNozzle #garden #GardenHose #gardening #HoseNozzle #HoseNozzles #JetSetting #SprayPatterns
-
Any idea why xon/xoff flow control would suddenly become enabled? I am working on a remote Ubuntu host, and suddenly ctrl-s is borderline malicious. I use emacs, and I don't even think about ctrl-s before I do it, so the xon/xoff flow control is very disruptive. The machine uptime is 18 days, and this has happened in the last hour. I haven't messed with any network config. I guess a system administrator could have updated packages. Could that have enabled xon/xoff flow control?
-
Any idea why xon/xoff flow control would suddenly become enabled? I am working on a remote Ubuntu host, and suddenly ctrl-s is borderline malicious. I use emacs, and I don't even think about ctrl-s before I do it, so the xon/xoff flow control is very disruptive. The machine uptime is 18 days, and this has happened in the last hour. I haven't messed with any network config. I guess a system administrator could have updated packages. Could that have enabled xon/xoff flow control?
-
Any idea why xon/xoff flow control would suddenly become enabled? I am working on a remote Ubuntu host, and suddenly ctrl-s is borderline malicious. I use emacs, and I don't even think about ctrl-s before I do it, so the xon/xoff flow control is very disruptive. The machine uptime is 18 days, and this has happened in the last hour. I haven't messed with any network config. I guess a system administrator could have updated packages. Could that have enabled xon/xoff flow control?
-
Any idea why xon/xoff flow control would suddenly become enabled? I am working on a remote Ubuntu host, and suddenly ctrl-s is borderline malicious. I use emacs, and I don't even think about ctrl-s before I do it, so the xon/xoff flow control is very disruptive. The machine uptime is 18 days, and this has happened in the last hour. I haven't messed with any network config. I guess a system administrator could have updated packages. Could that have enabled xon/xoff flow control?