From rob at landley.net Sun Jul 9 22:20:38 2017 From: rob at landley.net (Rob Landley) Date: Sun, 9 Jul 2017 17:20:38 -0500 Subject: [mkroot] [landley/mkroot] Bunzip2 from toybox or from busybox? (#7) In-Reply-To: References: Message-ID: <941d34db-77a8-15a1-c775-85c06314c665@landley.net> On 07/09/2017 01:13 PM, test4d wrote: > Since the toybox can bunzip, there no need to build bunzip2 in the > mkroot's busybox? > > I've excluded |CONFIG_BUNZIP2=y| from busybox configuration. |tar xf| > seems to work with bunzipped tars when bunzip2 links to toybox in the > root filesystem. Huh. Last time I looked busybox tar could only use the built-in compressors. (If you disabled buzip2 in busybox, busybox tar stopped understanding "j".) If they've fixed that, then yes I can yank bunzip2 (and I have gunzip and xz decompression code in toybox I need to clean up and promote as well.) I'll take a look, thanks. (Although really, the proper fix is cleaning up and promoting toybox's tar.c and switching off busybox's. But right now I'm trying to clean up and promote dd.c...) Rob From rob at landley.net Mon Jul 24 20:30:57 2017 From: rob at landley.net (Rob Landley) Date: Mon, 24 Jul 2017 15:30:57 -0500 Subject: [mkroot] [Aboriginal] s390x architecture....? In-Reply-To: <6c025cd1-94d0-36c9-4c1d-9891327a312d@vsoft-software.com> References: <89ba44dc-a045-57a7-111f-fd8b6c506be7@vsoft-software.com> <87fb4e95-0993-0b75-ac6b-800a891096bb@landley.net> <6c025cd1-94d0-36c9-4c1d-9891327a312d@vsoft-software.com> Message-ID: On 07/20/2017 08:50 AM, Dave Jones wrote: > Hello, Rob. > Tank you very much for your response; the new project appears to be > exactly what I am looking for....a way to build s390x z/Linux systems > with a minimal amount of stuff in it. > > I'll give it a go here in a bit and let you know how it turns out. > DJ How did it turn out? :) Rob From atoussaint1976 at gmail.com Mon Jul 31 20:59:28 2017 From: atoussaint1976 at gmail.com (Alain Toussaint) Date: Mon, 31 Jul 2017 16:59:28 -0400 Subject: [mkroot] Design issue: uploading binaries. In-Reply-To: References:

Message-ID: [resurrecting an old thread] Got the linode (hosting http://mailtrain.alphafinancialservices.net/ and http://launchpad.alphafinancialservices.net/ for a client) and building up an in-house build server (old box core2 based pentium with 1TB disk and 4GB of ram) of which both (linode and in-house) are or will be running LFS-SVN and another use of linode that I plan is to host images (mkroot, my own LFS images to install on usb keys and whatever else will be needed). I'll keep you posted on the build server when it'll be done and ready to build things but do you have any suggestions, advices, etc.. for me? Al 2017-06-21 17:53 GMT-04:00 Alain Toussaint : > Could be both but at least mkroot. Basically, it's been slightly over > a year I've been building LFS svn on a bi-monthly basis and would like > to automate that. Automating mkroot & musl-cross-make would be a > useful addition to the linode server. > > Alain > > 2017-06-21 17:41 GMT-04:00 Rob Landley : >> On 06/21/2017 04:08 PM, Alain Toussaint wrote: >>> Would it be useful to have a linode server for that. I've been mulling >>> for one myself and would likely rent one soon which I can make >>> available to mkroot and install travis-ci on it. >>> >>> Alain >> >> For mkroot, or for musl-cross-make? >> >> For mkroot I'm ok building binaries as part of a release. (I already >> have to do that to test everything before shipping it.) >> >> For musl-cross-make, I'm fuzzy on the details of Rich's plans. >> >> Rob >> >>> 2017-06-21 16:46 GMT-04:00 Rob Landley : >>>> I built mkroot binaries for a bunch of targets, but am not quite sure >>>> where (or if) to upload them. This remains an unsolved problem and I'm >>>> open to suggestions. >>>> >>>> I can stick them on landley.net/mkroot pretty easily, but the project >>>> doesn't have the same kind of website the old one did. It's a >>>> self-contained github project with a README. In theory github has a >>>> "releases" mechanism that lets you attach binaries to a tag, but the >>>> web-based mechanism is very manual and >>>> https://developer.github.com/v3/repos/releases/ is not making a lot of >>>> sense to me. (Googling for this sort of thing finds stuff for the older >>>> https://developer.github.com/v3/repos/downloads/ mechanism that was >>>> deprecated and removed in 2012.) >>>> >>>> (I'm also leaning towards not posting binaries until I get busybox >>>> cleaned out of the build. At which point everything would be bsd/pd >>>> licensed.) >>>> >>>> As for toolchain binaries, I've been poking Rich Felker about uploading >>>> musl-cross-make binaries for ages (although he's now waited long enough >>>> that https://lwn.net/Articles/726023/ happened and kinda took the >>>> thunder away from that), and _he_ wants to use >>>> https://docs.travis-ci.com/user/deployment/releases/ to produce and >>>> automatically upload them for each new tag. Which is nice, but neither >>>> of us has sat down to work out how to actually do it, and github has a >>>> 1gb quota per account that could get eaten pretty quickly by that sort >>>> of thing. >>>> >>>> Meanwhile, the kernel guys are using >>>> https://www.kernel.org/pub/tools/crosstool/ which doesn't have a C >>>> library (so you can pretty much _only_ build the kernel with them, no >>>> userspace). And I have a todo item to try to build stuff with Android's >>>> NDK when the next version ships. >>>> >>>> Lack of native compiler binary tarballs (which only musl-cross-make >>>> builds, and it's still not providing downloadable binaries) is >>>> semi-blocking the next major design stage, which is reproducing >>>> aboriginal linux's build control images under mkroot. What it's building >>>> right now isn't a development environment. I have to compile make from >>>> source (and/or implement one in toybox), but without a toolchain it's >>>> not much use. >>>> >>>> That said I do have an mcm-buildall.sh script checked in, and I can just >>>> have this _also_ depend on the mcm symlink like cross.sh does now... >>>> >>>> Rob >>>> _______________________________________________ >>>> mkroot mailing list >>>> mkroot at lists.landley.net >>>> http://lists.landley.net/listinfo.cgi/mkroot-landley.net >>> From phil at pricom.com.au Mon Jul 31 21:27:07 2017 From: phil at pricom.com.au (Philip Rhoades) Date: Tue, 01 Aug 2017 07:27:07 +1000 Subject: [mkroot] aboriginal / mkroot as a basis for a container? In-Reply-To: <4e5abfa5-37a3-a824-6e06-7a90f0e2c8ef@landley.net> References: <4e5abfa5-37a3-a824-6e06-7a90f0e2c8ef@landley.net> Message-ID: Rob, I never got around to thanking you for the detailed response below - so thanks! Recently I had cause to want a docker alternative and I found this: https://coreos.com/rkt https://github.com/rkt/rkt/releases/tag/v1.28.0 - I'm not sure if it is useful for you or not. P. On 2017-05-21 05:36, Rob Landley wrote: > On 05/19/2017 10:41 PM, scsijon wrote: >> If you want to play with containers, (he may hate me for this) but > > At LCA I attended a tutorial on how container technology is implemented > under the covers, the git repo of which is: > > https://github.com/fewbytes/rubber-docker > > I have a todo item to build better container technology into toybox > based on that, but Android already has minijail... > >> BarryK has been playing with that and called his build Easy Linux, >> http://barryk.org/easy/how-easy-works.htm may be of assistance and it >> can be downloaded from >> http://distro.ibiblio.org/quirky/quirky6/amd64/releases/easy-0.2/. >> It's >> a couple of build types back though, he's gone on to other ideas >> since. > > I'm not annoyed, just amused. :) > > Everybody who works through Linux From Scratch creates a build script > to > automate it, then turns it into a distro briefly, then loses interest > unless they can figure out something more to do with it. > > I have literally seen over a _hundred_ of these since I first did it > myself in 2001, and my direction that kept me going through multiple > reboots (http://landley.net/aboriginal/history.html) was replacing all > the gnu packages with busybox (starting about 13 years ago): > > http://lists.busybox.net/pipermail/busybox/2004-May/045630.html > > My goal was to see how _simple_ I could get the result (and disentangle > the FSF's inappropriate claims from Linux). And then after that worked > (whenever aboriginal linux's 1.0 release was, 2013-ish I think) the > toybox/android stuff started to build on top of that work. > > Others had their own angles, from http://www.staticramlinux.com/ to > https://github.com/sabotage-linux/sabotage which still weren't enough > to > sustain them. > > The point of mkroot is that by adding musl-cross-make as a dependency I > figured out how to jettison 80% of the complexity of Aboriginal Linux > while still accomplishing that project's goals (from > https://landley.net/aboriginal/about.html), and this forms a _much_ > better basis for both a toybox test environment (you need an emulator > with a known canned system to properly test ifconfig, ps, insmod...) > and > to eventually take apart the Android Open Source Project and rebuild it > as a series of orthogonal layers. Layer 0 would be the Android NDK, > layer 1 would be mkroot (once busybox is cleaned out and it's pure > toybox), then build Android's init in that. I.E. I have goals I'm > working towards. > > I also plan it to exemplify https://www.youtube.com/watch?v=Sk9TatW9ino > when I'm done. (I'm aware that's maybe 1/3 of the proper tutorial on > that topic; I need to make it a podcast series or something). > > My 2008 presentation had a warning about accidentally creating your own > distribution, starting at slide 78: > > https://speakerdeck.com/landley/developing-for-non-x86-targets-using-qemu?slide=78 > > If you're _going_ to create a distro, you need to understand the scope > of the resulting responsibilities (package management is a red queen's > race that _will_ eat multiple developers' full time just to stay in > place), and have a purpose your distro serves which isn't already > better > fulfilled by existing distros. Otherwise it'll be abandoned after a > year > or two and join the pile. > > Rob > _______________________________________________ > mkroot mailing list > mkroot at lists.landley.net > http://lists.landley.net/listinfo.cgi/mkroot-landley.net -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil at pricom.com.au From dave at vsoft-software.com Wed Jul 26 19:12:49 2017 From: dave at vsoft-software.com (Dave Jones) Date: Wed, 26 Jul 2017 14:12:49 -0500 Subject: [mkroot] [Aboriginal] s390x architecture....? In-Reply-To: References: <89ba44dc-a045-57a7-111f-fd8b6c506be7@vsoft-software.com> <87fb4e95-0993-0b75-ac6b-800a891096bb@landley.net> <6c025cd1-94d0-36c9-4c1d-9891327a312d@vsoft-software.com> Message-ID: <11d1ec85-3aab-0ccf-6aa0-e0c00f6e62be@vsoft-software.com> Don't know yet, haven't had a chance to try it out yet....:-) DJ On 07/24/2017 03:30 PM, Rob Landley wrote: > On 07/20/2017 08:50 AM, Dave Jones wrote: >> Hello, Rob. >> Tank you very much for your response; the new project appears to be >> exactly what I am looking for....a way to build s390x z/Linux systems >> with a minimal amount of stuff in it. >> >> I'll give it a go here in a bit and let you know how it turns out. >> DJ > How did it turn out? :) > > Rob > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -------------- next part -------------- An HTML attachment was scrubbed... URL: