On 21/11/2007, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Kevin Buckley wrote these words on 11/21/07 10:58 CST:
Thanks (I think !?) for responding in such detail to my thoughts, although I reckon that some of the questions you raise at the start of the reply were actually answered later on in the "posting as a whole" - one of the perils of replying piece by piece. I'll try and summarise to avoid doing the same. I appreciate that one of your points was that there'd then be hundreds of LFS/BLFS books and that only a few folk have editing rights to the official book but that wasn't where quite I was going. The thrust of my posting was that Users/Individuals who have created an LFS/BLFS installation should be encouraged to place thier own LFS/BLFS book, "out there on the Internet" for all to see/find. Some folk on here may recall that I attempted to do something similar a good while back now so as to highlight the differences that one might need to follow so as to achieve an LFS installtion that used the one of the package-manager Hints you allude to (the "package user" one). [Of course, that effort on my part has since stagnated somewhat] I seem to recall that someone decried my efforts by pointing out that all that I had done was to add a block of commands describing the creation of the "package user" (actually there were a few other subtle changes to the LFS commands as anyone who has tried to follow that Hint will I am sure be aware of, eg, in the resolution of clashes of ownership of directories and the like, but that's by the by) but that missed the bigger point that at least I had documented what I had done. The fact is that anyone who found the "Book" detailing my efforts in trying to use that package management style would have a resource against which to compare a current LFS/BLFS vanilla, albeit allowing for updates in the official Book since the one I used as a base was made available (5.1 if memory serves - so well old). I would suggest that the "Your Distro, Your Rules" theme underpinning LFS would imply that if everyone who has ever done anything differently in arriving at an LFS/BLFS-based system were to add their differences into a Wiki, the Wiki would become too big to be of much use someone looking for a solution to installing a given package not covered by BLFS, unless of course they had checked the Wiki first to see if they were actually treading new ground or not. Certainly there'd be little to gain from starting at the Wiki when looking for non-core LFS info, compared to a general search of the internet. My suggestion as to where to put stuff "if not in the Wiki" was, therefore, up on the internet as a User Linux From Scratch, or Individual Linux From Scratch, book. In respect of "coddling the HTML" I found that I was able to take the Official book that I used as a base for my needs and easily create a couple of environments that made my additions/deletion to the command listings appear with a Red or Royal Blue background, as opposed to Grey-Blue or whatever the current book uses., so as to make then stand out. (Of course that operation may have changed in terms of complexity now too) As to the generic nature of the official LFS/BLFS commands yes, yes, yes, I even made mention of this and again was why I was suggesting User/Individual books. I guess some of the thrust of my intention was lost along the way but I see that you did pick up on the idea of encouraging folk to document their experiences with the LFS/BLFS "process". I think the "following somone else's recipe" charge you lay at my door is also a little off the beam. It was my intetnion that the User/Individual books that might appear if encouraged, would serve to highlight differences from the official books. All the official book's content would be there but an individual would be able to see what was done differently and, asuming they have brought into the "LFS is about learning as well as doing", would then look to see why. Maybe it would be just information overload by proxy (no pun intended) from the internet as opposed to information overload in the Wiki but it just struck me that a full documentation of how everyone went about creating their LFS/BLFS installtion would be of greater benefit that a myriad instances of a couple of lines external to the official books (in the Wiki) detailing changes to one package. That view is probably very much a personal thing though. Again, from a personal way of working, what I would envisage is that as more books appeared which included details of how folk got a package not covered by BLFS to work within the base environment, there would be a distillation of the knowledge from all of them into what I, rather grandiously termed "a consensus on experience or fact" that would be placed in the Wiki. But maybe I have missed the point of a Wiki ? I'll certainly have a think about documenting how I "coddled the HTML" though as it was my intention that at some point I would just do a diff between "my Book" and the original and then use the diffs as a base to create my next LFS installation book for my own use. (But no, that never happened!) With the usual thanks for LFS/BLFS and hoping to have added something, Kevin -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
