-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KornShell no longer in Amazon Linux 2 #1468
Comments
that move seems hardly related to the ksh2020 situation and the ongoing readjustments of this project I presume. so it seems a "random coincidence" that it happens right now. if it is not random, I would say it is another indication that the reset of this repo to 93u+ and the planned "community fork" are the right way to proceed. I have no idea how to rectify the situation, assuming that you writing to their support service and requesting to reinstate /bin/ksh will not have any effect whatsoever.... |
@marcastel is it not possible to just install it with |
@dannyweldon Obviously yes. But this only does the job for manual installations. I use cloud-init for my on premises and in the cloud virtual machines. Not having KornShell as a primary shell means that a) I cannot automatically create my users, and b) all my shell scripts cannot be run... or at the cost of a lot of (dirty) tweaking. Not having KornShell as a primary shell is sort of going back three decades ago in the System V, Xenix and SCO quarrels. Then came POSIX. Then came Linux, which is not POSIX. And we are in for the same quarrels. You can lead a donkey to water, but you can't make it drink. |
Since prior version is end of life, I have been looking into Amazon Linux 2 for my AWS instances.
This is catastrophic. We need (want) our POSIX Shell back.
Any ideas as how to get this corrected ? That is, a ksh93u-compatible KornShell named
ksh
, located in/bin
and listed in/etc/shells
.I can provide a helping hand provided I have directives and some visibility on where we are going.
The text was updated successfully, but these errors were encountered: