From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: RE: Elks Distribution Date: 28 May 2002 12:39:32 +0100 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1022585972.4123.28.camel@irongate.swansea.linux.org.uk> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" To: Neil Holmes Cc: Riley Williams , Linux 8086 On Tue, 2002-05-28 at 08:14, Neil Holmes wrote: > 1. Bootable Install Floppy > - Shell Scripting > - Maybe look at some of the mini "curses" code that is lying around to try > and make it > look prettier later > - I would appreciate some feedback on what I can do with the bcc version > of "curses". > I noticed it in the ELKSCMD source. A minimal curses library normally has the 4BSD curses functions, which let you do rectangles of display, position text and some other minimal functionality. SYS5 "full" curses that came X/Open curses allows for overlapping objects handled by the library, form filling, function keys and other stuff most people don't need. Finally (and this may be useful if ash can handle it or a hacked version of it) some lunatic wrote a subset of curses equivalent in shell script! > - How do I resolve the kernel configuration for each platform/ disk layout > ? > - May be Linux controlled as per your information. Historically with its big brother vendors always shipped a kernel that worked. Might not be the best, might not be the smallest for the hardware but it worked > 2. SLIP Network Installation > - Automatic installation of a SLIP connection and test during install > - I have not really played with this yet though I do have Harry's notes in > my file. You can defer a lot of stuff to post install - Debian does a lot of that very nicely. It means you've got a working box to fight any weird configuration funnies As to packages. I'd suggest you figure out some kind of basic ruleset - where the manual goes (perhaps use the existing Linux File System Heirarchy standard), what goes in the README, where the README goes. Then ask people to contribute packages