Carlos E. R. wrote:
I thought, without thinking, that the command would differentiate between options and filenames automatically. No, it is not so, not in Linux. The shell expands the '*' and gets all options and filenames as just strings in the same command line. MsDos doesn't get this confusion, it is the app which has to do the expansion after it parses the command line.
---- It's very much the same way in linux -- in MsDOS, a Win32 lib is called to open a dir and sift through the entries. In linux, a dir is opened and a .so lib is called process the dir format and return info. MS-DOS, maybe didn't have the confusion, but as soon as NT hit and supported WinServer2000 & XP, the direct-access MS-DOS model became a a relic. Vista and Win7 added another level(or more) of hardware virtualization, and more indirection was added in Win8 & 10, with Win10 -- so if anything, Windows has ALOT more confusion with it showing in how many "updates" released by MS have unforeseen effects and "bluescreen" / no-boot problems. Linux (the kernel) has considerably fewer "blue-screen" events that disable a system booting. A notable uptick in problems preventing booting w/no easy fix has risen in the past few-to-several years with as traditional and incremental development has been replaced with large, "one-way" systems that don't co-exist with the previous development & design model. Unfortunate. "One-wayism" is as hazardous to the linux ecosystem as monotheism and mono-political systems are to the human ecosystem. C'est la vie. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org