Ticket #3 (closed enhancement: fixed)

Opened 12 years ago

Last modified 7 years ago

Proof Reading Text

Reported by: jim Owned by: chris@…
Priority: major Milestone: CLFS Standard 1.0.0
Component: BOOK Version: CLFS Standard 1.0.0
Keywords: Cc:

Description

All Pages need to be reviewed before the First Release.

Change History

comment:1 Changed 12 years ago by jim

We need everyone to get on this after Chris makes his dependency update. We only have a few tickets left to resolve to get the first release out. Let's work on getting a release by June 1st.

comment:2 Changed 12 years ago by chris@…

Going through the book looking for text that needs to be changed. Here are a few things in particular I am wondering about...

Section 1.2 - "How to build a CLFS system" - is the text on this page good enough, or is there something that needs to be changed/clarified?

Section 1.2 also mentions that "a full technical explanation is provided at the beginning of <temp-system>", however there really is any technical explanation there. In LFS, that link points to "toolchain technical notes" -  http://www.linuxfromscratch.org/lfs/view/development/chapter05/toolchaintechnotes.html - that describes how the compiler and linker are installed and work together, how the toolchain is changed to only look at /tools, etc. Can this text be copied from LFS and modified to fit CLFS (one thing of course is to remove sentences like "the process is similar to cross-compiling..." because obviously this *is* cross-compiling), or would it need something completely different?

Section 1.5 (Resources) mentions LFS mirrors - are there any mirrors for trac.cross-lfs.org? Also, I think we should keep the link to LFS mirrors there, since this is still part of the LFS project.

Section 1.6 (Help) - I think the 1st two paragraphs are redundant and can be removed. The FAQ and mailing list search are already mentioned in the previous section.

Chapter 2 (Creating a new partition) - this could mention that all of this is optional if you're building for a different physical machine. No need to create a new partition if all you're going to do is tar up the temp. system and move it to another machine (you could just create a /mnt/lfs dir and go from there...). Not really essential, but I just like to avoid unnecessary additional work.

Section 4.5 has a paragraph (about the LC_ALL var.) that's marked "TO BE REWRITTEN". What exactly needs to be changed here?

Will continue looking for more...

comment:3 Changed 12 years ago by manuel@…

Section 4.5 has a paragraph (about the LC_ALL var.) that's marked "TO BE REWRITTEN". What exactly needs to be changed here?

In that paragraph there this sentence:

"If the host system uses a version of Glibc older than 2.2.4, having LC_ALL set to something other than “POSIX” or “C” (during this chapter) may cause issues if you exit the chroot environment and wish to return later."

That phrase is applicable only for chroot method (if not already obsolete), not for boot method.

comment:4 Changed 12 years ago by justin

Section 1.5 (Resources) mentions LFS mirrors - are there any mirrors for
trac.cross-lfs.org? Also, I think we should keep the link to LFS mirrors
there, since this is still part of the LFS project.

There are 2 http mirrors, trac.cross-lfs.org and clfs.be-linux.org. Listed here:
 http://trac.cross-lfs.org/wiki/mirrors

As for FTP mirrirs, we still have our files on the LFS mirrors in the standard location. We can create a separate FTP repo and offer this if this is so wished. Otherwise, all LFS FTP mirrors are also CLFS mirrors at this time:
 http://trac.cross-lfs.org/wiki/download

comment:5 Changed 12 years ago by chris@…

Another question - on multilib builds, in 64-bit glibc, it says 'Now we make sure the Glibc goes into /tools/lib64: echo "slibdir=/lib64" >> configparms'

This is not very clear. The glibc what?

comment:6 Changed 12 years ago by jim

  • Owner changed from clfs-commits@… to chris@…

Assigned chris to be the keeper of this ticket. Chris has done a lot of work to get this resolved quickly.

comment:7 Changed 11 years ago by chris@…

  • Status changed from new to assigned
  • Owner changed from chris@… to chris@…

comment:8 Changed 11 years ago by jim

  • Version changed from unstable to 1.0

comment:9 Changed 11 years ago by chris@…

One thing that needs to be addressed is the explanatory text about udev/hotplug. For one thing, it needs to be changed to reflect the fact that hotplug no longer exists. I don't know much about the technical details of how udev works - would it be as simple as replacing occurences of "udev and hotplug" with just "udev", or would it be more than that? Of course there is a little more than that, for example the descriptions of the udev helper scripts, many of which just say "To be written" (though those could probably just be copied from LFS, assuming that LFS descriptions of them are accurate).

comment:10 Changed 11 years ago by jim

  • Version changed from 1.0 to 1.0.0

comment:11 Changed 11 years ago by chris@…

Do we need the text about compiling the keymap into the kernel in the "boot" section? That text assumes that the host system has kbd installed, and has keymaps in a specific place. It would probably be easiest just to remove that text.

comment:12 Changed 11 years ago by chris@…

The udev-rules installation page needs descriptions for each of the udev rules. We need someone familiar with the udev rules to help provide descriptions.

comment:13 Changed 11 years ago by jim

Ok Here are the udev rules

05-udev-early.rules - Early system rules. Rules to make sure the system is able to do hotplug events and network connectivty. Makes sure sysfs is ready before any rules are run.

35-helper.rules - Any rule that utilizies a helper program.

40-modprobe.rules - Rules that get modules loaded via modprobe

50-udev.rules - Basic system device and permissions

60-persistent-disk.rules - Allows persistent naming of disk drives

61-persistent-input.rules - Allows persistent naming of input devices

90-user.rules - Rules defined the user of the system

95-debug.rules - Rules for debugging udev/hotplug

comment:14 Changed 11 years ago by chris@…

Looks like LFS has already rewritten the text about udev/hotplug to update for the latest udev version. Perhaps we should just copy the text from LFS?

comment:15 Changed 11 years ago by ken

Another proffreading item: in boot/kernel.html

If you wish to do this, run the following command (replace [path to keymap] with the keymap location on the host - a common location is in /usr/share/kbd): (ok so far)

and then after the command:

For example, if using a Dutch keyboard, use /lib/kbd/keymaps/i386/qwerty/nl.map.gz.

I think we've painted ourselves into this one! Probably, the Dutch example needs to revert to /usr/share for boot, unlike whatever happens for the final system.

comment:16 Changed 11 years ago by chris@…

I don't really like that note in cross-tools/temp-system gcc pages that says "The above patches and sed's are critical...". For one thing, it's annoying seeing the same thing 3 times. Also, I don't see why this note is only in gcc since the same could be said of the modifications in the glibc installation. I think that note should be removed entirely (from every gcc page).

comment:17 Changed 11 years ago by chris@…

Seems most of the stuff mentioned here has been addressed. Here's a list of outstanding issues...

There's still an issue in the "How to build a CLFS system" page - it says "This effort to isolate the new system from the host distribution may seem excessive, but a full technical explanation is provided at the beginning of Constructing a Temporary System." There really isn't any technical explanation at the beginning of the temp-system section.

I never really liked the Texinfo instructions that tell you how to optionally install files for a TeX installation but never say why you might want that, or even specify exactly *what* is installed (ie, do you still need to install the TeX package?) That part of the Texinfo instructions should either be clarified or removed.

comment:18 Changed 11 years ago by alexander@…

Big question about Texinfo: does it really install files newer than those in teTeX-3.0? Even if so, does teTeX preserve or overwrite them?

comment:19 Changed 11 years ago by jim

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:20 Changed 9 years ago by sunrise

This works ok for me.. but It probably needs feedback. adidas nike shoes

comment:22 Changed 7 years ago by david20111

This works ok for me.. but It probably needs feedback. air jordan
Note: See TracTickets for help on using tickets.