Humm... As a side issue I'll be returning to school for Software Engineering & Embedded systems. Hoping to have some of my student loans forgiven I was thinking of setting up something where we take given-away computers and install a variant of Linux education for poor Montessori programs, charter schools, etc. that can afford nothing but free software. But then what? Even if I write scripts to auto update, remove extra kernels, etc. after a few years the systems would need work. I was thinking of writing a simply, lay flat, laminated, binder book with simple flow charts. E.g. "If this happens try these three things following the chart.." But again that would be at least 2 years away.
Blessings, Paul W. On Mon, Aug 28, 2017 at 12:34 PM, Brian P. Martin < [email protected]> wrote: > > > We are considering a project over the next year: > > writing a "Linux Widow's Guide". Perhaps that title > > is sexist; I have met many competent women Linux > > adepts, but none with a non-techy husband depending > > on Linux systems that she exclusively maintains. > > "Linux Widow(er)s Guide" seems clunky and harder for > > a librarian to catalog, but might actually sell better. > Yes, in my opinion, "Linux Widow's Guide" is sexist. Also, it's > unnecessarily narrow. Besides widows and widowers, what about new > divorcées, or families whose in-house tech-support's reserve unit got > called up for a free trip to Afghanistan. How about "Caring for your > Linux system", possibly followed by "(when your tech-support person is > gone)"? > > I'm actively not looking for projects right now. Check back with me in > six months and we'll see. > > -B > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
