From: Georg Potthast 2 <nospam@georgpotthast.de>
To: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: Condensing and re-coding programs to save space
Date: Tue, 28 Feb 2017 12:54:32 +0100 (CET) [thread overview]
Message-ID: <994626183.125220.1488282872735@com4.strato.de> (raw)
In-Reply-To: <CACpuWU=dSnp5A5UUVQygj8yJGYmM1Z_yNdOSqP7wNKp4cn21vQ@mail.gmail.com>
I have not tested it, but my understanding is that the Makefile puts different files on the floppy images depending on the type selected. So a 360 Kb image has fewer files than a 1.44 image. As long as the list of files for each format in the Makefile is maintained I think this would be sufficient for now.
With the new ethernet support one could set up a repository ;)
Georg
> Marc-François LUCCA-DANIAU <mfld.fr@gmail.com> hat am 28. Februar 2017 um 10:31 geschrieben:
>
>
> > Well, see...that's a problem. The ELKS kernel uses a really old copy of
> > Kconfig from Linux and when I looked at extracting the one used in a more
> > modern Linux source code base the task was far from trivial. A lot of ELKS
> > was cobbled together well over a decade ago. I'm open to moving to a more
> > all-encompassing build system if someone wants to do it, but it certainly
> > will not be a simple task.
>
> Mmm... let us be pragmatic and stop dreaming with stuff like "changing
> the compiler", "moving to another build system", etc. ELKS is
> definitively a "hobby" / "educational" project, with a few active
> contributors, and is intended to have fun, not for business (except
> data erasing / recovery on antic machines ?). So our development
> strategy should be consistent with that matter of fact : little steps
> forward, and keep consistency and stability. Obsolescence is
> absolutely NOT a concern here, as long we find compatible emulators
> and embedded systems to play with.
>
> Back to the current Kconfig: it works quite well, fulfills the need,
> so why breaking it with an hazardous upgrade ? I only propose to use
> it not only for the kernel, but also for the applets and image format
> selection. Not to upgrade it.
>
> MFLD
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-28 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:53 Condensing and re-coding programs to save space Jody Bruchon
2017-02-27 22:02 ` Marc-F. LUCCA-DANIAU
2017-02-27 22:11 ` Jody Bruchon
2017-02-28 9:31 ` Marc-François LUCCA-DANIAU
2017-02-28 11:54 ` Georg Potthast 2 [this message]
2017-02-28 12:17 ` Jody Bruchon
2017-02-28 21:12 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=994626183.125220.1488282872735@com4.strato.de \
--to=nospam@georgpotthast.de \
--cc=Linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox