Jason A. Donenfeld wrote:
Gentoo Linux now supports Network from Scratch in 5
easy steps.
Looks like you're off to a good start with this.
using jolly's branches for the live ebuilds.
I think the ebuilds needs to use master by default, but I think it
would be lovely to be able to opt for a different branch. One easy
way would be a USE flag, but that's perhaps not the best way. Ideas?
(ETA on when we can ship master?)
The ETA likely depends on the reason that the branch hasn't been merged.
Maybe you can help with that?
2. Make sure your portage tree is up to date, and
emerge the right packages:
$ sudo emerge --sync
$ sudo emerge openbsc osmobts osmotrx
openbsc should indeed not depend on osmobts but I think osmobts
should have a USE flag to make it DEPEND & RDEPEND on osmotrx
Thoughts?
3. Download configuration templates:
$ wget -O ~/.osmocom/open-bsc.cfg
http://bpaste.net/raw/236987/
$ wget -O ~/.osmocom/osmo-bts.cfg
http://bpaste.net/raw/237000/
Please add config examples in files/ and install them into
/usr/share/doc/{openbsc,osmobts}-9999/examples/ or so.
$ mkdir ~/.osmocom
What do you think about hooking into emerge --config for copying the
installed example configuration files to the user's home?
One snag is that --config is rather for system-wide configuration.
4. Edit configuration templates to work on spectrum
you have a license for:
$ vim ~/.osmocom/*.cfg
5. Start these babies up, in separate shells:
shell1 $ osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C
--debug=DRLL:DCC:DMM:DRR:DRSL:DNM
shell2 $ osmobts-trx -c ~/.osmocom/osmo-bts.cfg
shell3 $ osmo-trx
I think the tmux startup file {c,sh}ould also go into files/ along
with the example configs. :)
Maybe things in your git repo can go to either osmocom or gentoo
repos?
//Peter