What's it doing? Lemmy-Easy-Deploy

Soullioness@lemmy.world to Selfhosted@lemmy.world – 4 points –
lemmy.world

It's been sitting here frozen like this for a really long time, hours actually. I'm trying to install Lemmy on my raspberry pi. The terminal hasn't moved at all in hours, but the mouse will nudge a little after like a minute of lag. Is it frozen in a broken way? Or should I just try and leave it for the night?

11

I think you're probably swapping like mad, and likely to eventually bomb... I could be wrong but I can't see compiling a real Rust project on a Pi 3 coming to a successful conclusion. Like one other poster mentioned I think it might actually even damage the hardware from overheating. I think for my system I had to up the hosting to 2GB RAM, and still had to activate swap for some parts of the compilation, before it succeeded. Is it possible for you to cross-compile it or something?

I doubt it'll overheat, Pi's do thermal throttle when hot and from memory the Pi 3 runs fairly under clocked to begin with. If it's swapping you're more likely to burn out the SD card.

I have no idea what cross compiling is but I'm open to trying it.

Cross compiling is building software on one platform that's designed to run on a different platform -- e.g. you can build a Rust package on your PC that's designed to run on your Pi. It's not very well-supported in general (i.e. I have no idea if it's even feasible for this scenario) but in cases where it works it can be pretty useful.

Cool. I was just looking it up. Very neat. I don't have the first clue how to go about it but I'll let the little raspberry try overnight. We'll see what happens.

Can you open another terminal and do a top? My guess is that it's compiling and you're on slow hardware but Idk.

Top will show you what your system is doing.

I wish I could. The whole computer is completely frozen! Just the mouse will nudge a little very very slowly. I don't think I can get another terminal open. And yes it's very slow hardware. It's a raspberry pi 3.

Well, you can either let it ride or quit. Us old guys used to spend 24 hours compiling every few weeks to keep our systems up to date. I'd just be patient and wait.

I still remember when Debian had the problem that the mips builders couldn't build packages fast enough to get through the queue before more packages came in, so there was an ever-growing backlog whatever they did. 😃

I'm thinking that I should probably let it ride. Maybe it'll work. It's not like I've got better plans for that little computer.