Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 2439 - vi(m) on instimage shouldn't require !
Summary: vi(m) on instimage shouldn't require !
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-04-30 14:25 UTC by hermann.lauer
Modified: 2008-05-01 15:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-07-15 22:03:28 UTC

Attachments (Terms of Use)

Description hermann.lauer 1999-04-30 14:25:17 UTC
i386/RedHat/instimage/usr/bin> ldd vi => /usr/X11R6/lib/

A useable vi(m) is very helpfull during install/upgrade,
so why needs the vi(m) on instimage the X11 lib ?
Please use a version which doesn't require,
which is hardly available (and not needed) in the
install/upgrade environment. Or, please provide another
useable editor. (vi(m) would be my choise...)

Comment 1 Jeff Johnson 1999-04-30 16:09:59 UTC
There are several versions of vim that can be installed. Use
/bin/vi(m) for install/upgrade work, and /usr/bin/vi(m) for
all the bell's and whistles. There's also a /usr/X11R6/bin/vi(m)

Comment 2 hermann.lauer 1999-05-04 10:15:59 UTC
This is a problem during install, not with an installed system:

Sorry, on boot.img is no /bin/vi or /bin/vim available - also not
on netboot.img. And the directory /usr/X11R6/bin does'nt exist - why
should it ?

During that second stage of the install/upgrade the harddisk of the
computer is generally not available (there may be no linux system
on it !).

I still see no way to get a running editor after pressing <alt>-F2
in the second install stage of redhat-6.0 - this has worked with 5.2
and earlier and I see still no reason, why the
RedHat/instimage/usr/bin/vi(m) on the CDROM should require the X11

Comment 3 Bill Nottingham 1999-05-10 14:08:59 UTC
*** Bug 2645 has been marked as a duplicate of this bug. ***

I ran ldd on a fully installed system to get this output,
the reference to libX11 causes vim to fail when run from the
text console during the install.

 ldd RedHat/instimage/usr/bin/vim => /usr/X11R6/lib/
(0x40007000) => /usr/lib/
(0x400aa000) => not found => /usr/lib/ (0x400e9000) => /lib/ (0x400ef000) => /lib/ (0x400f2000) => /lib/ (0x4010b000) => /lib/ (0x401b0000)
        /lib/ => /lib/

Comment 4 Jeff Johnson 1999-05-15 19:30:59 UTC
Per msw, the wrong version of vi was included. The /bin/vi
is what shopuld have been included.

Comment 5 Jeff Johnson 1999-05-18 15:11:59 UTC
*** Bug 2902 has been marked as a duplicate of this bug. ***

Hi.  Executing vi while the VC2 window is available reports:

vi: error in loading shared libraries: cannot
open shared object file: No such file or directory.

Hmm.. This is really beat.  Can't even attempt to fix my
PCMCIA problem.. (which is why I marked it has "high"

Dave Wreski

Comment 6 Jeff Johnson 1999-06-15 11:26:59 UTC
*** Bug 3459 has been marked as a duplicate of this bug. ***

When booting with the Red Hat floppy, you can use,
after some menus, virtual console 2 with Alt-F2,
where you have a bash prompt:  bash#
Listed in /bin are some programs (not much), amongst
others vi and vim. However, when you call vi or vim,
you get this error:

"vi: error in loading shared libraries:
 cannot open shared object: No such file or directory"

This is somewhat awkward, as I wanted to edit a file
on the Win98 (vfat) partition, namely a log file of
what I was doing :-)
Note that I was able to mount it:
  /bin/insmod fat.o
  /bin/insmod vfat.o
  mkdir /dos
  mount -t vfat /dev/hda1 /dos
I also was not able to run 'more' (or 'less') and gpm
at installation time.
My idea was to keep a log of what I was doing and
copy it with gpm, so I would not have to write it on
paper and type it in again, should I need to install
again (which I did :-)

------- Additional Comments From  06/14/99 13:58 -------

*** This bug has been marked as a duplicate of 2262 ***

Comment 7 Bill Nottingham 1999-07-15 22:03:59 UTC
fixed in latest install instimage, available in next rawhide

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