[openFATE 305803] improve command_not_found_helper speed
Feature added by: Susanne Oberhauser (froh) Feature #305803, revision 1, last change by Title: improve command_not_found_helper speed openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' -- openSUSE Feature: https://features.opensuse.org/305803
Feature changed by: Susanne Oberhauser (froh) Feature #305803, revision 2 Title: improve command_not_found_helper speed openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), - I've suggested a different approach: I'd very much prefer bash to tell - me without any delay: Command not found. If this is not a typo, type - "man make-it-work" for help. And then the make-it-work man page will - tell you right away to run "make-it-work commandname' to locate and - install the package providing fancytool. with a little practice you - will go one back in history, prefix your last command with 'make-it- - work ' and have fun... imho the current solution is solving a problem - that doesn't really exist (pretend all software is preinstalled) and - creates a new one (lag). Michal Vyskocil pointed out that such magic - should at least look in /sbin and /usr/sbin and give a usefull message - if the command is found there: command found in /sbin or /usr/sbin. + I've suggested a different approach: + I'd very much prefer bash to tell me without any delay: + Command not found. If this is not a typo, type "man make-it-work" + for + help. + And then the make-it-work man page will tell you right away to run + "make-it-work commandname' to locate and install the package providing + fancytool. + with a little practice you will go one back in history, prefix your + last + command with 'make-it-work ' and have fun... + imho the current solution is solving a problem that doesn't really + exist (pretend all software is preinstalled) and creates a new one + (lag). + Michal Vyskocil pointed out that such magic should at least look in + /sbin and /usr/sbin and give a usefull message if the command is found + there: + command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' -- openSUSE Feature: https://features.opensuse.org/305803
Feature changed by: Gerald Pfeifer (GeraldPfeifer) Feature #305803, revision 3 Title: improve command_not_found_helper speed - openSUSE-11.2: Unconfirmed + openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' -- openSUSE Feature: https://features.opensuse.org/305803
Feature changed by: Michal Vyskocil (mvyskocil) Feature #305803, revision 5 Title: improve command_not_found_helper speed openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: - Command not found. If this is not a typo, type "man make-it-work" - for + Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' + Discussion: + #1: Michal Vyskocil (mvyskocil) (2009-02-04 10:11:18) + There was a bnc#435160[1], about a c-n-f handler speed and a most time + consuming part is a satsolver, so another approach is make satsolver + litle bit easier. But I suppose that output in mentioned form should be + enough too. [1] https://bugzilla.novell.com/show_bug.cgi?id=435160 + BTW: added prusnak as interested person. -- openSUSE Feature: https://features.opensuse.org/305803
Feature changed by: Pavol Rusnak (prusnak) Feature #305803, revision 6 Title: improve command_not_found_helper speed - openSUSE-11.2: Evaluation + openSUSE-11.2: Done Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' Discussion: #1: Michal Vyskocil (mvyskocil) (2009-02-04 10:11:18) There was a bnc#435160[1], about a c-n-f handler speed and a most time consuming part is a satsolver, so another approach is make satsolver litle bit easier. But I suppose that output in mentioned form should be enough too. [1] https://bugzilla.novell.com/show_bug.cgi?id=435160 BTW: added prusnak as interested person. + #2: Pavol Rusnak (prusnak) (2009-02-09 11:23:02) + Command-not-found handler now require COMMAND_NOT_FOUND_AUTO env + variable to be set. If it is set command-not-found binary is invoked + directly, otherwise it just prints info about invokation. -- openSUSE Feature: https://features.opensuse.org/305803
Feature changed by: Maximilian Maher (maxmaher) Feature #305803, revision 8 Title: improve command_not_found_helper speed openSUSE-11.2: Done Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' + Test Case: + set COMMAND_NOT_FOUND_AUTO variable and check the output of bash if + command is not found Discussion: #1: Michal Vyskocil (mvyskocil) (2009-02-04 10:11:18) There was a bnc#435160[1], about a c-n-f handler speed and a most time consuming part is a satsolver, so another approach is make satsolver litle bit easier. But I suppose that output in mentioned form should be enough too. [1] https://bugzilla.novell.com/show_bug.cgi?id=435160 BTW: added prusnak as interested person. #2: Pavol Rusnak (prusnak) (2009-02-09 11:23:02) Command-not-found handler now require COMMAND_NOT_FOUND_AUTO env variable to be set. If it is set command-not-found binary is invoked directly, otherwise it just prints info about invokation. -- openSUSE Feature: https://features.opensuse.org/305803
Feature changed by: Maximilian Maher (maxmaher) Feature #305803, revision 9 Title: improve command_not_found_helper speed openSUSE-11.2: Done Priority Requester: Important Requested by: Susanne Oberhauser (froh) Description: In the discussion on opensuse-factory [opensuse-factory] issues with command-not-found speed (Message-ID: <20081210084607.GA2988@taygeta>), I've suggested a different approach: I'd very much prefer bash to tell me without any delay: Command not found. If this is not a typo, type "man make-it-work" for help. And then the make-it-work man page will tell you right away to run "make-it-work commandname' to locate and install the package providing fancytool. with a little practice you will go one back in history, prefix your last command with 'make-it-work ' and have fun... imho the current solution is solving a problem that doesn't really exist (pretend all software is preinstalled) and creates a new one (lag). Michal Vyskocil pointed out that such magic should at least look in /sbin and /usr/sbin and give a usefull message if the command is found there: command found in /sbin or /usr/sbin. Maybe retry as root, e.g. with 'sudo $command' Test Case: - set COMMAND_NOT_FOUND_AUTO variable and check the output of bash if - command is not found + * First set COMMAND_NOT_FOUND_AUTO variable. + * Then check the output of bash if command is not found, it should be + different now Discussion: #1: Michal Vyskocil (mvyskocil) (2009-02-04 10:11:18) There was a bnc#435160[1], about a c-n-f handler speed and a most time consuming part is a satsolver, so another approach is make satsolver litle bit easier. But I suppose that output in mentioned form should be enough too. [1] https://bugzilla.novell.com/show_bug.cgi?id=435160 BTW: added prusnak as interested person. #2: Pavol Rusnak (prusnak) (2009-02-09 11:23:02) Command-not-found handler now require COMMAND_NOT_FOUND_AUTO env variable to be set. If it is set command-not-found binary is invoked directly, otherwise it just prints info about invokation. -- openSUSE Feature: https://features.opensuse.org/305803
participants (1)
-
fate_noreply@suse.de