diff options
author | Loui Chang <louipc.ist@gmail.com> | 2009-01-25 20:37:25 -0500 |
---|---|---|
committer | Aaron Griffin <aaronmgriffin@gmail.com> | 2009-01-26 22:10:09 -0600 |
commit | 7a98a216dec70340a3627dd38f6862d1a4cfca82 (patch) | |
tree | 0ad47099e41f7bd58453c4741c17c4c93c349c06 /README | |
parent | 7ab1ae57c7158ce8df40c05f39658c2f781ac943 (diff) | |
download | archiso32-7a98a216dec70340a3627dd38f6862d1a4cfca82.tar.xz |
Fix typos, formatting, and vague language where possible.
Signed-off-by: Loui Chang <louipc.ist@gmail.com>
[Fixed menu.lst: LiveCD -> Live CD -aaron]
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
Diffstat (limited to 'README')
-rw-r--r-- | README | 20 |
1 files changed, 10 insertions, 10 deletions
@@ -2,16 +2,16 @@ Archiso For Dummies Like Me and You ------------------------------------- --What the hell is Archiso? +- What the hell is Archiso? Archiso is a small set of bash scripts that is capable of building fully -functional ArchLinux-based liveCDs. It is a very generic tool, so it +functional Arch Linux based live CDs. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, -to install disks, to special interest liveCD systems, and who knows what +to install disks, to special interest live CD systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it. --Alright, so how does one install it? +- Alright, so how does one install it? First off, Archiso has some dependencies: - mkinitcpio @@ -22,7 +22,7 @@ Archiso itself can be installed with the handy dandy included Makefile, and the incantation 'make install'. --Great, so how do you use this thing? +- Great, so how do you use this thing? The heart and soul of Archiso is mkarchiso. All of its options are documented in its usage output, so we won't go into detail here. @@ -44,13 +44,13 @@ initcpio really belong here, fancier stuff can be done on the booted system anyway. You'll also want to create a list of packages you want installed on your -liveCD system. A file full of package names, one-per-line, is the format +live CD system. A file full of package names, one-per-line, is the format for this. Typically you'll want BASE and a kernel as a bare minimum, but -you're free to install whatever else you want (this is *great* for -special interest liveCDs, just specify packages you want and gogogo). +you're free to install whatever else you want. This is *great* for +special interest live CDs, just specify packages you want and gogogo. The last item of importance is what are called addons. Basically this -means any other crap you might want to include on your liveCD, including +means any other crap you might want to include on your live CD, including binary package repos, special configurations, random files, we don't know, be creative. mkarchiso expects them all to be put in a single directory, with an fstab-like config file. Currently two types of addons @@ -79,7 +79,7 @@ If you want to add plain directories to bind mount: core /packages bind where the first component is the path to the directory relative to your addons directory, the second component is where you'd like it - bind-mounted relative to the liveCD's root filesystem, and the last + bind-mounted relative to the live CD's root filesystem, and the last component is the type. vim: textwidth=72 |