Hi Andrew;
Am Donnerstag, 28. Juli 2016, 12:24:58 schrieb Andrew:
> Hi.
>
> I think that we should move root, config and maybe some other 'core'
> packages to initrd - to make it possible to run on tiny systems with
> small amount of RAM and available persistent ROM for permanently mounted
> initrd (like SOHO routers).
Looks almost like a packaging task, or am I wrong?
Do you expect space savings or just simplification?
I think the most important task for very small platforms is to get rid of
modules.sqfs.
E.g. the modules for rpi kernel is still 4.9MB, and of course it can be
reduced nect to zero, if decisions are made what devices will be supoorted and
what not - though rpi is still an somewhat open platform and with enough space
on the CF and RAM, so I'm not bothered too much; but for closed SOHO routers
this won't be acceptable.
Not shure if we should add it to 6.0.0 (for a beta), but if we do make steps
forward it could be at least for 6.1.0, which could be targeted until end of
year if things goes well.
Will you try in a new branch??
For 6.0.0 an issue with perf needs to be solved, may I ask you to have a look
at it first?
> Also, on beta release we should also freeze uClibc-ng version for this
> branch.
Agreed.
kp
> 27.07.2016 20:03, kp kirchdoerfer пишет:
> > Hi all;
> >
> > I've comitted changes to support the linux 4.4.x kernel for raspberry pi
> > boards rev 1.
> > While the raspberry pi 1 was mainly a proof-of-concept, we now support all
> > the platforms that we did with 5.2.x.
> > With the changes for rpi rev 1, we do have an example how to support
> > booting architectures depending on device trees (and overlays) - though
> > it shurely can be improved.
> >
> > Done that it, I think we are on the way to a first beta version for 6.0.0.
> > Therefor I'd like to pint you to some errors during a complete build amd
> > packaging of the sources in git.
> >
> > There aren't many, but
> >
> > perf fails to build
> > initmod fails to build (no surprise, as we do not need initmod anymore)
> > ... maybe i forgot one more?
> >
> >
> > Any help to fix that errors are welcome.
> >
> > Any ideas what should be accomplished before moving forward to a first
> > beta?
> >
> > regards kp
> >
> > --
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> > traffic patterns at an interface-level. Reveals which users, apps, and
> > protocols are consuming the most bandwidth. Provides multi-vendor support
> > for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using
> > capacity planning reports.http://sdm.link/zohodev2dev
> >
> > ___
> > leaf-devel mailing list
> > leaf-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
>
> --
>
> ___
> leaf-devel mailing list
> leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
--
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
