On 08/31/2015 07:37 PM, Bruce Dubbs wrote:
Simon Kitching wrote:

I started writing such a document as a hint, but it feels to me a little
too large for that format. I've therefore put the completed document up
on my website. If you think it is of any use, then you are welcome to
take that and host it on the LFS site if you wish, and welcome to make
any changes you feel necessary. The document is currently licenced under
cc-by-sa, but I'm happy to dual-licence it to the gnu licence if you
wish. Or you could link to the original, but I presume you'll want to
make changes.

It is written in markdown format, so converting to "hint" format would
be easy if desired.

html form: http://moi.vonos.net/linux/beginners-installing-from-source/
markdown form:
http://moi.vonos.net/downloads/markdown/beginners-installing-from-source.md.raw


I hope it's helpful. I can't imagine too many people interested in LFS
who would learn much from that page, but it is certainly less
out-of-date than the TDLP document that the LFS book currently refers to!

Overall the link is very helpful. One comment about the link above is the width of the page. On my browser, which I normally keep about the size of a 8.5 x 11 sheet of paper, I have to scroll horizontally quite a bit.

That may be because the code lines in the section with at tar --extract ... are too long. Try just putting the comments in that section on separate lines and keeping the comments to 80 characters or less:
Yes, I think you're right. I have split the examples into shorter lines as you suggested.

The section on make could use an example.
Not sure what you meant here. There is an example showing untar/configure/make/install. Can you suggest what would be useful here?

In the code examples, "less is more", e.g, s/more/less/

Ok, done and pushed.

Will the site be permanent?

Yes, that URL is stable, unless I get run over by a bus :-)

Regards, Simon
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to