> - FreeCOM stops to run external commands sometimes > (internal commands keep working) is that a (newly introduced ? ) kernel or Freecom bug ?
> - FreeCOM leaves a batch file or (if you are not inside one) > even shuts down completely when you use pipes or redirects > and the input "runs dry" for internal commands. A very old > bug but maybe worth fixing before the next file release: could you give an example for that ? > - the history.txt files need a lot of updating, any doc- > writing volunteers for that? You would have to read the > svn log and summarize it, just wondering: are mere mortals supposed to be able to find a way from www.freedos.org somehow to kernel or freecom sources ? just asking because my attempts to follow http://www.freedos.org/cgi-bin/freedos-lsm.cgi?q=f&a=base/kernel.lsm leeds to some historic stuff only :( no idea how I should be able to locate SVN, 'most recent' or 'what Bart recently build' kernels Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
