Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Kshrc custom prompt will not work Post 303040389 by zoomer on Monday 28th of October 2019 09:28:29 AM
Old 10-28-2019
So I tried what both of you said and it still does not do anything. I looked and I am running KSH 2020.0.0 Stable, which is the latest release. I tried to compile KSH93u and KSH93v from the ast github but both failed due to lack of nmake. Every time I run ksh the prompt is still $.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

kshrc

An odd problem using .kshrc, if I run with this in my home login directory it works fine other than if I use 'man', where each word of the manual entry is on a seperate line ?. I'm using AIX 5.3 (it worked fine on 5.2). Anyone seen this before ? (3 Replies)
Discussion started by: gefa
3 Replies

2. UNIX for Dummies Questions & Answers

Getting current work directory in Command Prompt

How to get the current working directory as part of the command prompt? Every time I chage the folder, my command prompt path shoud change. I am using Korn Shell. Any help is greatly appreciated. (3 Replies)
Discussion started by: MeganP
3 Replies

3. Shell Programming and Scripting

.kshrc is not executing

Hi, I am facing two problems in my environment. Anyone can help on this? Thanks in advance. Problem 1 --------- When i login into my new unix system, only the .profile is executing. .kshrc is not executing. But my default shell is .ksh Any setup to be changed ? Problem 2... (7 Replies)
Discussion started by: senthil_is
7 Replies

4. AIX

Custom AIX Prompt

In my .profile, my prompt is set like this: set -o vi PS1=`logname`@`hostname -s`:'$PWD>' Is there a way to show what the history number would be of the command I'm typing in the prompt? For example, I frequently run commands then run 'history' to pull up the history number of a command... (2 Replies)
Discussion started by: ptrotter
2 Replies

5. AIX

"/" doesn't work on command prompt for searching commands last typed

When I use "/" to look for a particular command that I typed in the current session it says D02:-/home/user1/temp> /job ksh: /job: not found. D02:-/home/user1/temp> previously it used to fetch all the commands which had job in it.. for example subjob, endjob, joblist etc... may I... (7 Replies)
Discussion started by: meetzap
7 Replies

6. Shell Programming and Scripting

Ksh93 vs. Pdksh88: Custom PS1 prompt not working

Greetings! I have to work with a NFS user id between two hosts: A running Ksh 93 and B running pdksh 88. My problem has to do with the custom prompt I created on A: it works like a charm and display colors: PS1="$'\E But I switch over to B, it all goes to hell (private info... (4 Replies)
Discussion started by: alan
4 Replies

7. Shell Programming and Scripting

Change / Setup bash custom prompt (PS1)

I am trying to create my custom prompt and I have almost succeeded. Right now I have PS1='\n\\$\ ' What I have not figured out is how to make the directories bold when I'm using commands ls or ls -la. Any idea how to do it??? Many thanx. (2 Replies)
Discussion started by: emailkia
2 Replies

8. Shell Programming and Scripting

Color prompt with file numbers does not work anymore

I have used this color prompt on my servers for long time, in file ~\.bashrc Black="\" Dark="\" Blue="\" LBlue="\" Green="\" LGreen="\" Cyan="\" LCyan="\" Red="\" LRed="\" Purple="\" LPurple="\" Brown="\" Yellow="\" LGray="\" White="\" Reset="\" PS1="$Yellow\u@\h $LBlue\w... (4 Replies)
Discussion started by: Jotne
4 Replies

9. Red Hat

RHEL6 customizing prompt do not work

Hi, I'm trying to customize the ksh prompt for users on a RHEL 6.6 system for having user@host pwd : $ and user@host pwd # in red color for root. I think it's possible but i do not even succeded for a non root user : I added in my ~/.kshrc : PS1="Hello : " and it works but when i... (4 Replies)
Discussion started by: Fundix
4 Replies

10. Linux

How to make this command work wihtout password prompt?

Hi, I am trying to run this command to connect to each server without being prompted for the password. How can I do this in Linux redhat 7.2: for HOST in $VIPS; do su - Myadminid -c "ssh -o ConnectTimeout=10 $HOST 'date; hostname; pkill -9 -f -u Myadminid xx00 ; ps -ef |grep Myadminid'" ... (7 Replies)
Discussion started by: mrn6430
7 Replies
PERLNETWARE(1)						 Perl Programmers Reference Guide					    PERLNETWARE(1)

NAME
perlnetware - Perl for NetWare DESCRIPTION
This file gives instructions for building Perl 5.7 and above, and also Perl modules for NetWare. Before you start, you may want to read the README file found in the top level directory into which the Perl source code distribution was extracted. Make sure you read and understand the terms under which the software is being distributed. BUILD
This section describes the steps to be performed to build a Perl NLM and other associated NLMs. Tools & SDK The build requires CodeWarrior compiler and linker. In addition, the "NetWare SDK", "NLM & NetWare Libraries for C" and "NetWare Server Protocol Libraries for C", all available at <http://developer.novell.com/wiki/index.php/Category:Novell_Developer_Kit>, are required. Microsoft Visual C++ version 4.2 or later is also required. Setup The build process is dependent on the location of the NetWare SDK. Once the Tools & SDK are installed, the build environment has to be setup. The following batch files setup the environment. SetNWBld.bat The Execution of this file takes 2 parameters as input. The first being the NetWare SDK path, second being the path for CodeWarrior Compiler & tools. Execution of this file sets these paths and also sets the build type to Release by default. Buildtype.bat This is used to set the build type to debug or release. Change the build type only after executing SetNWBld.bat * Example: 1. Typing "buildtype d on" at the command prompt causes the buildtype to be set to Debug type with D2 flag set. 2. Typing "buildtype d off" or "buildtype d" at the command prompt causes the buildtype to be set to Debug type with D1 flag set. 2. Typing "buildtype r" at the command prompt sets it to Release Build type. Make The make process runs only under WinNT shell. The NetWare makefile is located under the NetWare folder. This makes use of miniperl.exe to run some of the Perl scripts. To create miniperl.exe, first set the required paths for Visual c++ compilier (specify vcvars32 location) at the command prompt. Then run nmake from win32 folder through WinNT command prompt. The build process can be stopped after miniperl.exe is created. Then run nmake from NetWare folder through WinNT command prompt. Currently the following two build types are tested on NetWare: o USE_MULTI, USE_ITHREADS & USE_IMP_SYS defined o USE_MULTI & USE_IMP_SYS defined and USE_ITHREADS not defined Interpreter Once miniperl.exe creation is over, run nmake from the NetWare folder. This will build the Perl interpreter for NetWare as perl.nlm. This is copied under the Release folder if you are doing a release build, else will be copied under Debug folder for debug builds. Extensions The make process also creates the Perl extensions as <Extension.nlm> INSTALL
To install NetWare Perl onto a NetWare server, first map the Sys volume of a NetWare server to i:. This is because the makefile by default sets the drive letter to i:. Type nmake nwinstall from NetWare folder on a WinNT command prompt. This will copy the binaries and module files onto the NetWare server under sys:Perl folder. The Perl interpreter, perl.nlm, is copied under sys:perlsystem folder. Copy this to sys:system folder. Example: At the command prompt Type "nmake nwinstall". This will install NetWare Perl on the NetWare Server. Similiarly if you type "nmake install", This will cause the binaries to be installed on the local machine. (Typically under the c:perl folder) BUILD NEW EXTENSIONS
To build extensions other than standard extensions, NetWare Perl has to be installed on Windows along with Windows Perl. The Perl for Windows can be either downloaded from the CPAN site and built using the sources, or the binaries can be directly downloaded from the ActiveState site. Installation can be done by invoking nmake install from the NetWare folder on a WinNT command prompt after building NetWare Perl by following steps given above. This will copy all the *.pm files and other required files. Documentation files are not copied. Thus one must first install Windows Perl, Then install NetWare Perl. Once this is done, do the following to build any extension: o Change to the extension directory where its source files are present. o Run the following command at the command prompt: perl -II<path to NetWare lib dir> -II<path to lib> Makefile.pl Example: perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:perl5.6.1lib MakeFile.pl or perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:perl5.8.0lib MakeFile.pl o nmake o nmake install Install will copy the files into the Windows machine where NetWare Perl is installed and these files may have to be copied to the NetWare server manually. Alternatively, pass INSTALLSITELIB=i:perllib as an input to makefile.pl above. Here i: is the mapped drive to the sys: volume of the server where Perl on NetWare is installed. Now typing nmake install, will copy the files onto the NetWare server. Example: You can execute the following on the command prompt. perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:perl5.6.1lib MakeFile.pl INSTALLSITELIB=i:perllib or perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:perl5.8.0lib MakeFile.pl INSTALLSITELIB=i:perllib o Note: Some modules downloaded from CPAN may require NetWare related API in order to build on NetWare. Other modules may however build smoothly with or without minor changes depending on the type of module. ACKNOWLEDGEMENTS
The makefile for Win32 is used as a reference to create the makefile for NetWare. Also, the make process for NetWare port uses miniperl.exe to run scripts during the make and installation process. AUTHORS
Anantha Kesari H Y (hyanantha@novell.com) Aditya C (caditya@novell.com) DATE
o Created - 18 Jan 2001 o Modified - 25 June 2001 o Modified - 13 July 2001 o Modified - 28 May 2002 perl v5.12.1 2010-04-26 PERLNETWARE(1)
All times are GMT -4. The time now is 06:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy