what is easier? learning how to build one's own images or learning how to do aftermarket RAM & Flash upgrades like you find on taobao etc
@rra If you're doing things with OpenWrt then learning to build your own images is probably better. Anything they remove as legacy can potentially be re-included.
I'd say it depends on what's easier for you, and you're the best judge of that.
Configuring and building router firmwares could be easy for me, for example, if I wasn't in the habit of making things complicated. I still do, because I think it's interesting or necessary (harder with the latter motivator).
Even though the procedure is usually similar, how easy it is to flash pre-compiled images onto various routers depend on the router model and make.
@320x200 Yeah it's for the bibliotecha project so I guess it is fine. It would be really good if OpenWRT project could indeed move to different 'tiers' of releases so you don't end up unpatched software. A bit like is suggested in the link:
"Full ⇒ allows for running gui, has working opkg and plenty of space to allow packages
Medium ⇒ allows for running gui, has working opkg and at least enough space for setting up extroot
Small ⇒ bootable images can be built when either sacrificing gui or opkg while still having configuration persistence
Micro ⇒ only choice are heavily tailored custom images that require special measures like pre-shipped configuration, NFS mounts, preconfigured extroot etc."
I don't think that this is unreasonable, considering the expectations people have of what they should be able to easily do with their router and that developers are supporting OpenWRT in their spare time.
It will still be possible to build your own tailored image, stripped down to your needs, just don't expect active or any support for your issues.
Welcome to post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.