Mailinglist Archive: opensuse-factory (341 mails)
| < Previous | Next > |
Re: [opensuse-factory] issues with command-not-found speed
- From: Patrick Shanahan <ptilopteri@xxxxxxxxx>
- Date: Mon, 9 Feb 2009 09:45:39 -0500
- Message-id: <20090209144539.GD16118@xxxxxxxxxxxxxxx>
* Rob OpenSuSE <rob.opensuse.linux@xxxxxxxxxxxxxx> [02-09-09 09:38]:
+1
--
Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535 @ http://counter.li.org
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
That looks great. I wonder though if this is as clear as can be?
Would you mind considering a suggestion as feedback.
"Now it prints this info immediately:
$ blender
If 'blender' is not a typo you can run the following command to lookup
the package that contains the binary:
command-not-found blender
bash: blender: command not found
$ ifconfig
Absolute path to 'ifconfig' is '/sbin/ifconfig', so it might be
intended to be run only by user with superuser privileges (eg. root).
bash: ifconfig: command not found
"
Suggested simpler text
$ blender
If 'blender' is not a typo you can use command-not-found to lookup the
package that contains it, like this :
command-not-found blender
bash: blender: command not found
$ ifconfig
'ifconfig' has path '/sbin/ifconfig', so it may require root
privileges should typing /sbin/ifconfig fail to work correctly
bash: ifconfig: command not found
This seems simpler to understand, and avoids geek speak words like
'binary', without being ambiguous, and gives good hints towards 'best
practice'.
+1
--
Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535 @ http://counter.li.org
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |