News for hackers. Stuff that matters.
Re:The tragedy of running an old Node project by getcrunk on Monday November 18, 2024 @01:48PM (#42175562)
How exactly does one do that. Sounds exciting!
Re:The tragedy of running an old Node project by kaptainscarlet on Monday November 18, 2024 @01:56PM (#42175654)
I think you copy the library file and add it to you load path
Re:The tragedy of running an old Node project by exe34 on Monday November 18, 2024 @02:16PM (#42175851)
patchelf
Re:The tragedy of running an old Node project by ian-g on Monday November 18, 2024 @02:38PM (#42176075)
but don't forget to make sure your new path is fewer characters than the original one so you don't overwrite any of the library
Re:The tragedy of running an old Node project by pavel_lishin on Monday November 18, 2024 @04:44PM (#42177438)
A sewing needle, a spare magnet, and a very steady hand.
Re:The tragedy of running an old Node project by wink on Tuesday November 19, 2024 @07:00AM (#42182495)
Not the OP but what sometimes works is as easy as:

``` ldd your-binary ``` on the old host and then copy all the thing that is referenced, put into ./foo and then start like so on new host: `LD_LIBRARY_PATH=./foo ./your-binary`. (may include typos, from memory)

A great tool for this used to be https://github.com/intoli/exodus - not sure if it still works.

Disclaimer: Also please don't do this with network-facing services, security applies, etc.pp. but it's a good trick to know.

Re:The tragedy of running an old Node project by Izkata on Tuesday November 19, 2024 @11:20AM (#42185145)
I used it for something early this year, it was working then.