Swap, swap, swap, and bad places to work

Re:Swap, swap, swap, and bad places to work by aardvarklegend on Friday August 09, 2019 @10:36AM (#20654730)

Sorry, but that’s not enough. You need more ram to actually make the ssh connection useful. You can lock sshd and then be blocked from running your shell or any commands in that shell. You really do need reserved unused memory.

[ Parent | on HN ]

Re:Swap, swap, swap, and bad places to work by Godel_unicode on Friday August 09, 2019 @11:04AM (#20655006)

This approaches understanding why this isn't done; it's not just reserved memory for SSH, it's reserved memory for SSH plus bash plus the vim, top, grep, kill, etc commands you'll be running once you SSH. How much RAM does top need? What about vim? Now realize you're imposing this penalty on every embedded, low-memory Linux device which might not ever have this problem.

[ Parent | on HN ]

Re:Swap, swap, swap, and bad places to work by kevin_thibedeau on Friday August 09, 2019 @02:50PM (#20657251)

Linux was quite usable in 4MiB 25 years ago. Just give yourself a minimal busybox environment for rescue activities.

[ Parent | on HN ]

Re:Swap, swap, swap, and bad places to work by pixl97 on Friday August 09, 2019 @01:57PM (#20656783)

Why would you be imposing this on every device when I would assume it would be controlled by a settings file in /etc

[ Parent | on HN ]

Re:Swap, swap, swap, and bad places to work by Dylan16807 on Friday August 09, 2019 @12:43PM (#20656004)

But for the actual goal you don't have to reserve it as empty, you just have to prioritize it.

[ Parent | on HN ]