| 1 |
My practice for many years has been to have a root terminal running, |
| 2 |
which I start via 'konsole' + 'su'. After a system update + reboot, |
| 3 |
I am confronted with : |
| 4 |
|
| 5 |
Warning: Could not find 'su', starting '/bin/bash' instead. |
| 6 |
Please check your profile settings. |
| 7 |
|
| 8 |
499: ~> su |
| 9 |
bash: su: command not found |
| 10 |
|
| 11 |
I always start from a raw terminal & use 'startx', |
| 12 |
so hopefully I can still login as root & do system things that way, |
| 13 |
but can anyone suggest what might have caused this problem ? |
| 14 |
-- one pkg which was updated was 'shadow' : might that be the cause ? |
| 15 |
|
| 16 |
BTW no-one else has physical access to this machine, |
| 17 |
so leaving a root terminal running does not endanger security. |
| 18 |
|
| 19 |
-- |
| 20 |
========================,,============================================ |
| 21 |
SUPPORT ___________//___, Philip Webb |
| 22 |
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
| 23 |
TRANSIT `-O----------O---' purslowatcadotinterdotnet |
Archives