> On Nov 11, 2015, at 11:39 AM, Mateusz Viste <[email protected]> wrote: > > On 11/11/2015 17:23, Jerome E. Shidel Jr. wrote: >> Converted FDI to use a single package for both binary and sources and >> to use Mateusz’s all_cd.iso as the layout for packages and to use >> FDINST instead of unzip. > > Sounds cool! So if I slap your boot floppy inside all_cd.iso's, we > should end up with a working install CD ?
It seems to. > Any chance you could send me the 1.44 image for that? (or is it > available somewhere online?) At present, it is only on github at http://github.com/shidel/fdi with directions in the README.md file on what to do to create the boot floppy. Basically, you just clone it, then download V8 binaries to a sub directory, and do the same with FDNPKG. Make sure V8 tools are in your path env var. Then run mkFDI.bat with a floppy in drive A:. It formats the disk, transfers current system files, and basically assembles the floppy. With some memory managers it is really really slow. I should have it use the packages from the ALL_CD.iso for the stuff that goes onto the floppy. Also, need to figure out a way to insure the floppy is using the latest kernel an such. I will probably add a pre-built floppy image to my download server (http://up.lod.bz) at some point. > >> no idea what to put in the “all” package list. > > No idea either. To be honest, the whole "install all" idea is a heresy > to me. I'd expect only the base things to be installed, and if I want > anything else, I can fdinst / fdnpkg it (using the repositories on the > CD, or network). But well, if people want this, then whatever :) I > simply won't use it ever myself. > >> However, there is an issue with using FDINST. If a package is already >> installed, it creates an error. Need a simple way to determine if it >> FAILED or is already installed. > > I think that "already installed" doesn't mean that it can be skipped > anyway, because it might be installed, but in an older version. Maybe > best would be to try a FDINST REMOVE for every package, and then only > FDINST INSTALL ? This way we are sure we end up with the 'right' > versions of everything. If FDI uses FDINST remove, how will it be able to tell if it failed to remove a package because of an error or if it fails to remove it because it is not installed? > > Mateusz > > > ------------------------------------------------------------------------------ > _______________________________________________ > Freedos-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-devel > ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
