5 Commits

Author	SHA1	Message	Date
Micah Abbott	d451b87fbe	docs: fix swapped link syntax ... A few links in the docs had the Markdown syntax swapped like: (link title)[link url] Just cleaned up those. Verified via `mkdocs serve` Closes: #297 Approved by: cgwalters	2016-05-12 21:01:54 +00:00
Krzesimir Nowak	826c2149b8	manual: Fix a bunch of typos and docbookisms ... Closes: #238 Approved by: cgwalters	2016-04-04 14:09:00 +00:00
Colin Walters	8894bb3949	deploy: Handle a read-only /boot ... I'd like to encourage people to make OSTree-managed systems more strictly read-only in multiple places. Ideally everywhere is read-only normally besides `/var/`, `/tmp/`, and `/run`. `/boot` is a good example of something to make readonly. Particularly now that there's work on the `admin unlock` verb, we need to protect the system better against things like `rpm -Uvh kernel.rpm` because the RPM-packaged kernel won't understand how to do OSTree right. In order to make this work of course, we *do* need to remount `/boot` as writable when we're doing an upgrade that changes the kernel configuration. So the strategy is to detect whether it's read-only, and if so, temporarily mount read-write, then remount read-only when the upgrade is done. We can generalize this in the future to also do `/etc` (and possibly `/sysroot/ostree/` although that gets tricky). One detail: In order to detect "is this path a mountpoint" is nontrivial - I looked at copying the systemd code, but the right place is to use `libmount` anyways.	2016-03-21 12:49:05 -04:00
Micah Abbott	0b068c668a	docs: Cleanup Markdown ... I was going through the new version of the docs and noticed a few problems. Mostly URLs that aren't linked, extra whitespace, and a few mis-spellings. I ran the files through `aspell check` and made some manual changes myself. These changes were tested locally with `mkdocs serve`	2016-03-16 15:02:18 -04:00
Colin Walters	64ebe2b82a	Rewrite manual in mkdocs ... I don't much like Docbook (and am considering converting the man pages too), but let's start with the manual. I looked at various documentation generators (there are a lot), and I had a few requirements: - Markdown - Packaged in Fedora - Suitable for upload to a static webserver `mkdocs` seems to fit the bill.	2016-01-28 09:31:37 -05:00