Re: [lfs-support] Proposed Changes to LFS Book
On 16 January 2014 00:59, Ken Moffat zarniwh...@ntlworld.com wrote: On Wed, Jan 15, 2014 at 04:51:23PM +, Ken Moffat wrote: On Tue, Jan 14, 2014 at 03:50:47PM -0500, alex lupu wrote: I would like to submit for your consideration the following changes to the Section III. 6.7. Linux-3.12.6 API Headers of the Linux From Scratch - Version SVN-20140102 book. 1. After the paragraph ..: This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball., I would insert: Note: For the meaning of the action sanitizing (in this context), run command sh scripts/headers_install.sh | sed s/echo// and in the output read the section between Prepares and keywords. (output, lines 3-6). I don't find that helpful. At all. Please note that I'm not intending to shut you off here - _I_ know what is meant by sanitizing the headers (or, I think I do), but the book doesn't go into any detail. Maybe we ought to change the chapter 5 reference to 'sanitizing' (5.6) - that is where we first mention it. At the moment we say I have returned to LFS a number of times, I use the whole experience as a learning resource and yes, it still is too advanced for me, but I would appreciate the additional slightly more wordy text, because it aids my understanding of the process of sanitizing. This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball. perhaps change to ... source tarball (to make them fit for use by userspace applications). Ditto here, this increases my ability to Google something meaningful. But I've been doing this stuff for years, back to the days of linux-libc-headers and clfs's own attempt. Not sure if my wording would add anything useful for new readers, or if it would just sow confusion. And anyway, I'm too busy to do any development at the moment. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Proposed Changes to LFS Book
On Tue, Jan 14, 2014 at 03:50:47PM -0500, alex lupu wrote: Dear Development LFS Book Administrators: For development, you ought to post to lfs-dev, but you'll need to subscribe before you do that. The devs (primarily Bruce and Matt) might read this here, I'm not sure. I would like to submit for your consideration the following changes to the Section III. 6.7. Linux-3.12.6 API Headers of the Linux From Scratch - Version SVN-20140102 book. 1. After the paragraph ..: This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball., I would insert: Note: For the meaning of the action sanitizing (in this context), run command sh scripts/headers_install.sh | sed s/echo// and in the output read the section between Prepares and keywords. (output, lines 3-6). I don't find that helpful. At all. 2. After section They are placed in an intermediate local , I would insert: subdirectory (named by us, 'dest', in the command below) If the user does not understand that we are creating a directory called 'dest' then LFS is probably too hard for them. In everything, a balance is needed between explaining and teaching your grandmother to suck eggs. 3. After copied to the needed location, I would change to copied to the intended user-space standard location, '/usr/include/...' Again, that should be obvious from the command. 4. I would change the command cp -rv dest/include/* /usr/include to cp -prv dest/include/* /usr/include That would synchronize the file times in the '/usr/inlude/' tree to the times of the files created in the kernel directory on running the command 'make headers_install', and not assign them an arbitrary time when I get around to run the copy after taking out the garbage and then getting a well deserved rest before being finally able to complete the procedure :) So, you think that the time(s) when the files were initially created in dest/ are more important than the times when they were finally installed to /usr ? Why ? ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Proposed Changes to LFS Book
Ken Moffat wrote: On Tue, Jan 14, 2014 at 03:50:47PM -0500, alex lupu wrote: Dear Development LFS Book Administrators: For development, you ought to post to lfs-dev, but you'll need to subscribe before you do that. The devs (primarily Bruce and Matt) might read this here, I'm not sure. Yes. I read everything here. I respond as time permits. I agree with everything Ken says. My reaction was generally, If a user doesn't see that, then LFS is too advanced for them. -- Bruce I would like to submit for your consideration the following changes to the Section III. 6.7. Linux-3.12.6 API Headers of the Linux From Scratch - Version SVN-20140102 book. 1. After the paragraph ..: This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball., I would insert: Note: For the meaning of the action sanitizing (in this context), run command sh scripts/headers_install.sh | sed s/echo// and in the output read the section between Prepares and keywords. (output, lines 3-6). I don't find that helpful. At all. 2. After section They are placed in an intermediate local , I would insert: subdirectory (named by us, 'dest', in the command below) If the user does not understand that we are creating a directory called 'dest' then LFS is probably too hard for them. In everything, a balance is needed between explaining and teaching your grandmother to suck eggs. 3. After copied to the needed location, I would change to copied to the intended user-space standard location, '/usr/include/...' Again, that should be obvious from the command. 4. I would change the command cp -rv dest/include/* /usr/include to cp -prv dest/include/* /usr/include That would synchronize the file times in the '/usr/inlude/' tree to the times of the files created in the kernel directory on running the command 'make headers_install', and not assign them an arbitrary time when I get around to run the copy after taking out the garbage and then getting a well deserved rest before being finally able to complete the procedure :) So, you think that the time(s) when the files were initially created in dest/ are more important than the times when they were finally installed to /usr ? Why ? ĸen -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Proposed Changes to LFS Book
On Wed, Jan 15, 2014 at 04:51:23PM +, Ken Moffat wrote: On Tue, Jan 14, 2014 at 03:50:47PM -0500, alex lupu wrote: I would like to submit for your consideration the following changes to the Section III. 6.7. Linux-3.12.6 API Headers of the Linux From Scratch - Version SVN-20140102 book. 1. After the paragraph ..: This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball., I would insert: Note: For the meaning of the action sanitizing (in this context), run command sh scripts/headers_install.sh | sed s/echo// and in the output read the section between Prepares and keywords. (output, lines 3-6). I don't find that helpful. At all. Please note that I'm not intending to shut you off here - _I_ know what is meant by sanitizing the headers (or, I think I do), but the book doesn't go into any detail. Maybe we ought to change the chapter 5 reference to 'sanitizing' (5.6) - that is where we first mention it. At the moment we say This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball. perhaps change to ... source tarball (to make them fit for use by userspace applications). But I've been doing this stuff for years, back to the days of linux-libc-headers and clfs's own attempt. Not sure if my wording would add anything useful for new readers, or if it would just sow confusion. And anyway, I'm too busy to do any development at the moment. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Proposed Changes to LFS Book
Dear Development LFS Book Administrators: I would like to submit for your consideration the following changes to the Section III. 6.7. Linux-3.12.6 API Headers of the Linux From Scratch - Version SVN-20140102 book. 1. After the paragraph ..: This is done by way of sanitizing various C header files that are shipped in the Linux kernel source tarball., I would insert: Note: For the meaning of the action sanitizing (in this context), run command sh scripts/headers_install.sh | sed s/echo// and in the output read the section between Prepares and keywords. (output, lines 3-6). 2. After section They are placed in an intermediate local , I would insert: subdirectory (named by us, 'dest', in the command below) 3. After copied to the needed location, I would change to copied to the intended user-space standard location, '/usr/include/...' 4. I would change the command cp -rv dest/include/* /usr/include to cp -prv dest/include/* /usr/include That would synchronize the file times in the '/usr/inlude/' tree to the times of the files created in the kernel directory on running the command 'make headers_install', and not assign them an arbitrary time when I get around to run the copy after taking out the garbage and then getting a well deserved rest before being finally able to complete the procedure :) Thanks, -- Alex -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
