On 7/15/2011 11:33 AM, Bernd Blaauw wrote: > Op 15-7-2011 5:08, Michael B. Brutman schreef: >> - How do I use the new installer that Jim has been working on? > It's in the new ISO that I plan to upload by Sunday evening. Still need > to work out some things to make it a smoother experience. The initial > menu showing which CD drives were found for example (which I also should > add plain directories to, but that's more difficult).
Good - I await the next revision. I'm trying to do my part here by testing it .. >> - Are all of the binaries always put into the one "bin" dir? I expected >> the optional packages to be separated into subdirectories, not lumped in >> with the critical OS commands. > All is together. Nothing is preventing an additional directory called > EXTRA, putting subdirectory PACKAGES below it and a BASE directory below > that, and then install from that location, allowing a 2nd directory. The following is just a matter of personal preference and/or opinion .. On all of my machines (DOS, Windows and Unix) I try to keep the optional packages separate from the core OS functions. So DOS will live in /DOS and nothing else will be in that directory. Smaller utilities wind up in something like "/utils/text", "/utils/disk", "/utils/zip", etc. If something has a lot of files that deserves it's own directory. mTCP usually lives in "/mtcp" or "/packet/mtcp" depending on what other networking code I have installed. I can see where DHCP, FTP, PING, SNTP, and TELNET could be considered core OS functions so I'm not entirely opposed. It's just different than what I'm used to seeing, not just on DOS. >> - I noticed the PCNet packet driver, which was a happy coincidence >> because I was installing under VMWare. Has their been any thought to >> including other common packet drivers? > FreeDOS 1.0 has lots of packet drivers, I didn't include them so far to > keep the CD minimalistic. Rebuilding for every change on batchfiles can > be a pain :) Does this mean that they will be put on the CD later, or that the user has to find a different way to get them on the machine? I think that every packet driver known to man probably fits within 1MB of space. :-) (Ok, maybe 2 ...) Is the intent of the CD to provide a minimal install? >> - Did I miss the option to install the WATTCP based programs? > See above, minimising things. WATTCP programs are usually compiled as > DJGPP programs, having kind of huge disk footprint compared to your > drivers for example. Same question as above - the capacity of a CD is quite large, and 12MB for an OS install image is tiny. As an end user I would much prefer that what I need is on the CD already even if it means a larger download size. (Or give me a choice of ISO images to use.) I'm new to this, so if this is already addressed in some way then forgive me and just point me on my way ... >> - Do I have time to do a minimal mTCP configuration program that can be >> used to walk users through setting up the configuration file? > Ofcourse, knock yourself out :) I noticed the problem with the improper CR/LF in the mTCP configuration file that you reported a week or two ago, and I assume that we can just fix the original file. Depending on your time table I can either fix DHCP to be more tolerant of improper new lines in files or I can try to do something more comprehensive that looks like an installer. In a perfect world the installer would just prompt for a few things like the IRC user name, FTP buffer sizes, MTU size, etc. If that doesn't happen in time having those fields in the mTCP config file (but commented out as I do in the sample) would be a reasonable substitute. BTW, I'm happy/honored to be part of the group. I just want to ensure that the mTCP code looks/behaves more like the OS so that it doesn't cause usability problems or stick out too much. It's not a full networking stack, but the idea of a coherent set of networking utilities available at install time with the OS is very appealing. Mike ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
