Pretty much everything here is useful only on Unix-style systems.
These are licensed under the GPL, but that doesn't mean it's necessarily a good idea for you to distribute modified versions. I'd like to know if you plan to do that.
Together, these three sections define almost all of the organization of my systems.
/fshierarchy: how I organize my filesystems
svscanas process 1: how I manage booting and shutdown
shinterpreter that optionally warns about suspicious or nonportable constructs. For now, it's a list of constructs that would be warned about.
The following mailing lists are open to the public. So information posted to them is not kept secret - X-No-Archive header fields are ignored, email addresses in message headers are revealed, etc. Currently, you can access them in two ways:
firstname.lastname@example.org, substituting the appropriate list name. For help, send a message to
multivac.cwru.edu, use the list name as your username, use any password, and tell your POP client to leave messages on the server.
In the future, I plan to add IMAP (and possibly HTTP) access, and eventually remove ezmlm. The lists are:
prjware-announce(announcement-only): for announcements of new releases of my software, etc.
prjware(unmoderated): for general discussion of my software, configurations, etc., not covered by more specific lists. Announcements are not copied here; read the
prjware-announcelist if you want them.
spf(unmoderated): for discussion of the slashpackage-foreign project.
mkmed(unmoderated): for discussion of the mkmed build system.
I've described some of my experiences with computer hardware.
The source is the documentation. You get what you pay for.
If I've helped you, and if you're feeling generous, you can: