Mail Archives: opendos/1997/02/05/03:54:42
Brian Dukes writes:
> The original question/idea was to have an IFS= type command in
> CONFIG.SYS ... all I was saying is that its not practical because
> its too damn easy to change and to mess things up for one.
Like with OS/2 for example?
> I haven't missed your point Dave, I just didn't dwell on it. Your
> point if I may paraphrase was that in order to read the IFS=
> instruction from CONFIG.SYS, the boot process would need to know
> something about the IFS in place in order to locate the config.sys
> and start processing it! And what tells the boot process which IFS
> is installed?
Correct. OS/2 does it, so it should be possible. I was just wondering
out loud about hwo you do this.
> The fact that these instructions were in the CONFIG.SYS would mean
> that ANYONE would have the ability to alter the current IFS= without
> any pre-thought!
Like with OS/2.
> How many times have you had to go in and tidy up someones CONFIG.SYS
> after they messed! What if someone took out the IFS= line by
> accident then rebooted?
You boot from a boot floppy, change to C: (or whatever) and fix it,
just like with OS/2.
> I think we should look at operating systems like OS/2 or Linux to see
> how they achieve the same goal
Indeed, OS/2 does it from CONFIG.SYS. :-)
--
Take a look in Hagbard's World: | w3ng - The WWW Norton Guide reader.
http://www.acemake.com/hagbard | ng2html - The NG to HTML converter.
Also available in the UK: | eg - Norton Guide reader for OS/2.
http://www.hagbard.demon.co.uk | dgscan - DGROUP scanner for Clipper.
- Raw text -