I run Slackware on machines with 800 to 900 MB, and speeds of 1.3 to 1.6 GHz. Unless you are going to start gaming, any thing bigger or faster should work on any Linux.
There is no way to predict how much the update process is going to be fathomable to any given person.
Slackware invites package by package installation. I compile many packages. You can install anything where source code can be found. For some people that is no worse than figuring out which binary to install and where to get it.
Some people just say install the whole thing, but I don't like that method as it also installs packages the user does not need, want, or cannot use.
If the person is used to updating from a central binary server (like windows updates) then something more akin to that will serve them better.
What I am saying is that you may need to have the user participate in choosing a distribution. I have tried this before and it is a real pain, as many users don't want to face such questions and just want it to work. If that is the case, they are not going to be able to update or service it either.
Better then to have a logbook of how it was installed for whoever is going to get called to do the servicing. Write everything down. My logbooks for the several computers I maintain can cover 4 to 6 pages of notes for each Linux install.
Saving notes and config files in /root also helps. Give the notes prominent understandable names.
Last edited by selfprogrammed; 03-01-2014 at 12:09 AM.