Daniel Robbins wrote: > Yes, that was my request and I was told that this was the plan of > attack, but the end result looked nothing like this. > > Just to be clear, I think the *official* documentation should be > simple, with a linear path and non-intrusive links for non-standard > stuff, and should fit on a single (Web) page. > > I don't think that a quick install guide solves the problem. (I know > *you're* not saying it does, just pointing it out...) The official > documentation should be incredibly efficient to use, eliminating the > need for a quick install guide.
I wholy agree on this point, yet I see a tiny problem. If you scrap all the different paths in the handbook by keeping only one "standard" path, I'd say about 50% of the whole thing is arch dependant : - partitioning (i've never used anything other than x86/amd64) - kernel setup - bootloader Common stuff: - stage setup - rsync, emerge system/world - network setup - additional utilities (such as cron, syslog) Although I really would like to see a shorter guide, I think there are a few issues (like these, but maybe others?) to layout first. Ideas, comments ? Rémi PS, my 50% figure may not be very accurate :) don't feel offended if i'm way off -- [email protected] mailing list
