Flint, Yeah, I know 'which' and 'find'. vim was not installed, but now it is. Yes this was on SLES15S0 on Dave's system. Scary part is there are no man pages. Hopefully we find out tomorrow how to add them back.
-Mike On Sun, Jun 9, 2019 at 9:23 AM Paul Flint <fl...@flint.com> wrote: > Dear Michael, > > Check if "vi" is in the root path... > > (Type what is in the qoutes) > > # "which vi" > ^ > | > Note you are presumed to be root... > > If this comes back empty, then you got to go find it. > > The best way to find it is the following: > > "find / |grep vi$ | less" > > This will show you every file ending in 'vi'. > > If this comes up snake, then it is time to start the dreaded "yast", > something I have not done in a while... > > On of my favorite ways that AT&T Unix 'saved money' on a USDA system > installation was to not install any 'man' pages... Wow what a > nightmare... > > Call me for more silly suggestions... > > Regards, > > Paul > > On Sun, 9 Jun 2019, Michael MacIsaac wrote: > > > Date: Sun, 9 Jun 2019 07:47:27 -0400 > > From: Michael MacIsaac <mike99...@gmail.com> > > Reply-To: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> > > To: LINUX-390@VM.MARIST.EDU > > Subject: SLES 15 - no help? > > > > Hi, > > > > I get my hands on a minimal SLES 15 for the first time. I try to edit a > > file: > > > > # *vi foo* > > -bash: vi: command not found > > # *vim foo* > > -bash: vim: command not found > > > > HUH? A UNIX with no vi? NEVER seen that before. > > > > So I install it: > > > > # *zypper install -y vim* > > ... > > > > > > Now I need to check a flag: > > > > #* man vim * > > -bash: man: command not found > > > > > > So I try to install man: > > > > # *zypper install -y man* > > ... > > No provider of 'man' found. > > > > > > HUH? A UNIX with no man pages at all? NEVER seen that before either. > > Hopefully there's another way to install man. > > > > So I try to get help another way: > > > > # *info vim* > > info: No menu item 'vim' in node '(dir)Top' > > # *help vim* > > -bash: help: no help topics match `vim'. Try `help help' or `man -k vim' > > or `info vim'. > > > > > > No 'info', no 'help' (which suggests to use man or info - hehe) > > > > Am I just spoiled with the backward compatibility baked into the > mainframe? > > > > -- > > -Mike MacIsaac > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or visit > > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > > > Kindest Regards, > > > > ☮ Paul Flint > (802) 479-2360 Home > (802) 595-9365 Cell > > /************************************ > Based upon email reliability concerns, > please send an acknowledgement in response to this note. > > Paul Flint > 17 Averill Street > Barre, VT > 05641 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- -Mike MacIsaac ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
