| 1 |
On Fri, Dec 28, 2012 at 9:10 AM, Kevin Chadwick <ma1l1ists@××××××××.uk> wrote: |
| 2 |
>> > Should perl be in / or /usr? |
| 3 |
>> |
| 4 |
>> Now that is a good question, if only because Perl traditionally _loathes_ |
| 5 |
>> being in /bin, for its own philosophical reasons. |
| 6 |
>> |
| 7 |
> |
| 8 |
> |
| 9 |
>> Now, as a practical matter? WTF are the scripts written in Perl? Or in |
| 10 |
>> anything other than sh? If they're intended for emergency use, they've got |
| 11 |
>> some pretty fat dependencies, and should probably be launched from a full |
| 12 |
>> rescue environment instead. Or the log files should be copied to some place |
| 13 |
>> with more featureful tools available. |
| 14 |
> |
| 15 |
> |
| 16 |
> Can perl be built statically and moved to / by the admin for this |
| 17 |
> corner case? |
| 18 |
|
| 19 |
Certainly, but you still have modules to consider...but those can of |
| 20 |
course be bundled. |
| 21 |
|
| 22 |
> |
| 23 |
> If not you should have all the tools to fix /usr in root and then if |
| 24 |
> anything needs fixing via perl then you should be able to mount /usr or |
| 25 |
> mount -a and have a fully working single user system to run perl from. |
| 26 |
|
| 27 |
Indeed. The only reason I can imagine this to not be the case is if |
| 28 |
the mount for /usr fails. Most of the reasons imaginable also apply |
| 29 |
equally strongly to initramfs+root-on-special-mount and |
| 30 |
everything-in-/usr. |
| 31 |
|
| 32 |
-- |
| 33 |
:wq |
Archives