Bug 9330 - pico but no vi on installer/rescue image
Summary: pico but no vi on installer/rescue image
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer   
(Show other bugs)
Version: 6.2
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-02-11 03:59 UTC by Jeremy Katz
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-11 21:22:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jeremy Katz 2000-02-11 03:59:27 UTC
I realize that for a newbie vi might be harder to use, but if a system is
really hosed and you really want to fix the system, pico will _really_ hurt
to have to use.  The size of a minimal vi is next to nothing when the
instimage/ dir is already 50+ megs :)

Comment 1 Tim Waugh 2000-02-11 14:27:59 UTC
For a newbie vi is *impossible* to use; that's the difference.  A vi user can
use pico -w, even if they don't like it. (Besides, once you've fscked /, use the
vi that's on your root partition why not?)


Note You need to log in before you can comment on or make changes to this bug.