PuppyThis forum is for the discussion of Puppy Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not really familiar with Puppy. Having a look it appears to be run from a live CD in which case it seems you'd have to burn a CD with ksh on it to do this.
You may not need ksh however. Linux uses bash rather than ksh by default and they have a lot of the same capabilities. If you're running scripts that have something like "#!/bin/ksh" as the first line (called the interpreter line) you can likely fake it out simply by creating a symbolic link from bash to ksh:
ln -s /bin/bash /bin/ksh
Anything that had /bin/ksh for interpreter would actually run /bin/bash instead. There are some differences between the shells but for most purposes they are very similar. I haven't run across any ksh scripts yet that failed to work in bash.
My main reluctance to using bash was the way it does history scrolling since I was used to the way ksh did it. However you can make bash do it the way ksh does it by simply typing "set -o vi" (adding this to your .profile or .bashrc keeps from having to do it every time you login).
Not really familiar with Puppy. Having a look it appears to be run from a live CD in which case it seems you'd have to burn a CD with ksh on it to do this.
You may not need ksh however. Linux uses bash rather than ksh by default and they have a lot of the same capabilities. If you're running scripts that have something like "#!/bin/ksh" as the first line (called the interpreter line) you can likely fake it out simply by creating a symbolic link from bash to ksh:
ln -s /bin/bash /bin/ksh
Anything that had /bin/ksh for interpreter would actually run /bin/bash instead. There are some differences between the shells but for most purposes they are very similar. I haven't run across any ksh scripts yet that failed to work in bash.
My main reluctance to using bash was the way it does history scrolling since I was used to the way ksh did it. However you can make bash do it the way ksh does it by simply typing "set -o vi" (adding this to your .profile or .bashrc keeps from having to do it every time you login).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.