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. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] "Why should we subsidize intellectual curiosity?" - Ronald Reagan ------------------------------------------------------------------------- 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
