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/.
Ivan Kluchnikov Ivan.Kluchnikov at fairwaves.ruHi all, This is new version of patch for review and merge: - more user-friendly interface for command: rach access-control-class 2 barred rach access-control-class 11 allowed - added 'write' implementation 2013/7/13 Alexander Chemeris <alexander.chemeris at gmail.com> > On Sat, Jul 13, 2013 at 1:46 PM, Holger Hans Peter Freyther > <holger at freyther.de> wrote: > > > > On Sat, Jul 13, 2013 at 10:50:40AM +0400, Alexander Chemeris wrote: > > > > > > * The 'current' VTY rule is that unless there is a common prefix use > > > > '-' in the command. So it would be 'rach access-control-class" > right > > > > now until we have someone else at 'access-control'.. > > > > > > Huh, is that a new rule? > > > > Not exactly, the rule has been there before we used the VTY.. I just > > never used cisco stuff before. ;) > > Me either :) > > > > I see commands like "rach max transmission", "rach tx integer" and so > > > on which do not use "-". > > > > Yeah, we have plenty of violations (and I don't think it is worth > > fixing). For new ones just try to get it right. > > Ok. > > -- > Regards, > Alexander Chemeris. > CEO, Fairwaves LLC / ООО УмРадио > http://fairwaves.ru > -- Regards, Ivan Kluchnikov. http://fairwaves.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20130725/d7ea10d3/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Added-vty-command-for-setting-Access-control-classes.patch Type: application/octet-stream Size: 3560 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20130725/d7ea10d3/attachment.obj>