Wolfgang Denk a écrit : > In message <[EMAIL PROTECTED]> you wrote: >>> That's why I think we should have an explicit "builtin" command, i. e. >>> command with the name "builtin" that will always run the corresponding >>> builtin command, no if there is a "command alias" or not - similar to >>> the bash command >> ... and make sure that one can *never* define an environment variable >> called 'builtin', and even remove any such definition if found in the >> environment when reading it from persistent memory at boot. > > No. That's where the "always" in my sentence above comes into play. > Even if you define such a variable I would just issue a warning and > then ignore it when it comes to command execution.
My bad. I'd analyzed your "always" to apply to builtin's argument (the second word in the command), not to 'builtin' itself (the first word in the command). Amicalement, -- Albert. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
