Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 1212 - visudo built with bad hardcoded paths
Summary: visudo built with bad hardcoded paths
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Donny Davies (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-17 23:51 UTC by Pete Shinners
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pete Shinners 2002-03-17 23:51:24 UTC
the "visudo" command is built to use a hardcoded editor path of "/usr/bin/vi".
none of the gentoo packages provide for "vi" (afaik, although i'm happily using
vim). visudo is also built to ignore the EDITORS variable. it seems there is no
way to run visudo without manually symlinking some other editor to /usr/bin/vi.

the visudo manpages suggest it can be built for other behaviours (for example a
different set of hardcoded editors to try, or reading the EDITORS variable).

i'll warn i'm brandspaking new to gentoo (as of today), but it seems like if the
'sudo' package was built to better represent the gentoo environment, it would
certainly feel nicer. in the meantime, i've built myself a symlink and have
moved on. :]
Comment 1 Daniel Robbins (RETIRED) gentoo-dev 2002-03-18 22:19:55 UTC
EDITOR is set to /usr/bin/nano in our current default /etc/profile.  It should
find nano by default unless you explicitly unset this var.