This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn Wed, Jun 21, 2017 at 09:54:40PM +0300, Harald Welte wrote: > In terms of left/right: I think there is no obvious or correct way. > > > Based on the fd it's unfortunately not possible to have an explicit > "CLIENT -> SERVER" kind of notation replacing the bi-directional arrow > that we currently print. This would require that we keep a lot more > state and nothing that can be derived from the fd alone :/ > > On Wed, Jun 21, 2017 at 05:17:18AM +0200, Neels Hofmeyr wrote: > > On Wed, Jun 21, 2017 at 12:58:59AM +0200, Max wrote: > > > > +1, I'd even favor writing out 'remote:' and 'local:'. > > My original idea was that a system administrator would inherently know > which of the two sides is the local side of the socket, based on his > configuration. In this output: 127.0.0.1:2905<->127.0.0.1:60661 it is always unclear who is using 2905 and who 60661. > L/R I can still live with, but please don't make it even longer. But then it looks like "Left" and "Right", with Left on the right and Right on the left ... I'd still prefer explicit strings, they're not taking up much space. If you guys outvote me on "L" "R", it's still better than nothing... I just posted both variants: https://gerrit.osmocom.org/3000 https://gerrit.osmocom.org/3001 Let your votes decide which one wins. (I picked '=' instead of ':' because ':' is already used as the port number separator.) ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170621/2d88958e/attachment.bin>