| 1 |
> > Should perl be in / or /usr? |
| 2 |
> |
| 3 |
> Now that is a good question, if only because Perl traditionally _loathes_ |
| 4 |
> being in /bin, for its own philosophical reasons. |
| 5 |
> |
| 6 |
|
| 7 |
|
| 8 |
> Now, as a practical matter? WTF are the scripts written in Perl? Or in |
| 9 |
> anything other than sh? If they're intended for emergency use, they've got |
| 10 |
> some pretty fat dependencies, and should probably be launched from a full |
| 11 |
> rescue environment instead. Or the log files should be copied to some place |
| 12 |
> with more featureful tools available. |
| 13 |
|
| 14 |
|
| 15 |
Can perl be built statically and moved to / by the admin for this |
| 16 |
corner case? |
| 17 |
|
| 18 |
If not you should have all the tools to fix /usr in root and then if |
| 19 |
anything needs fixing via perl then you should be able to mount /usr or |
| 20 |
mount -a and have a fully working single user system to run perl from. |
| 21 |
|
| 22 |
-- |
| 23 |
_______________________________________________________________________ |
| 24 |
|
| 25 |
'Write programs that do one thing and do it well. Write programs to work |
| 26 |
together. Write programs to handle text streams, because that is a |
| 27 |
universal interface' |
| 28 |
|
| 29 |
(Doug McIlroy) |
| 30 |
_______________________________________________________________________ |
Archives