On 17.08.2014 17:57, Marcos Menendez wrote:
>>> This may sound rather harsh, but it needs to be said. When we put the
>>> books together the packages and all the information required to get both
>>> the base LFS and BLFS systems up and running.
>>>
>>> It is stated in a number of places in the LFS book that you need to
>>> actually follow things through and not just jump ahead to what YOU think
>>> should be done.
>
>>> You are obviously not following the instructions, because if you were,
>>> then you would not be posting on the list.
>>>
>>> These lists are for genuine issues with regards to the published
>>> instructions, and not for us to teach you how to follow printed
>>> instructions.
>>>
>>> A number of us have spent many hours putting together this material.
>>>
>>> Some have been with linux from scratch for a number of years.
>>>
>>> Christopher.
>>>
>
> Well, Christopher..., nice to meet you too.
>
> I don't see the point in all the previous 'speech', really. I must recognize
> that your answer surprised me quite a lot, showing such an aggressive
> attitude, since I'm convinced that nothing justifies it (not in my case at
> least). You give the impression that you were just waiting, hiding in the
> corner, for the first person in this list to ask something that triggers your
> 'alarm sensor' to dump all your stored complains on him/her (for a man that
> claims he has 'spent many hours putting together this material',...man...,
> you should have think more before answering).
>
>
> I think Akh below, clarifies why your answer was unfair and unjustifiable.
>
>>
>> Hmmm. Is that possibly being a bit unfair?
>>
>> *IF* /etc/profile.d/ is created in LFS, then fair enough. I've just grepped
>> through lfs 7.5 incl bootscripts, and no mention of 'profile.d' .
>>
>> But *IF* it's only created in BLFS, then perhaps arguably much less so.
>>
>> For, of course, LFS is intended to be followed in a linear
>> fashion, doing basically all items en route: whereas of
>> course BLFS is well-known and openly acknowledged to be
>> non-linear; even e.g. BLFS "Which Sections of the Book Do I Want?"
>> ('http://www.linuxfromscratch.org/blfs/view/svn/introduction/which.html')
>> doesn't give anywhere-near-direct instructions _to_ create /etc/profile.d/ .
>>
>
> Thanks for your answer Akh.
>
> Yes, as you very well mentioned, in the introduction of BLFS states exactly
> that, giving the new user the idea that you can directly jump , or at least I
> understand it that way, to the package you need and compile/install it right
> away, leaving the linear way used for the LFS, since you already have a
> working LFS system.
> That's why I started directly from X Windows. I think (maybe) that it should
> be made more clear in that intro that, despite of that non-linear way of
> adding things from BLFS, you still need to read chapter 3 and do what it is
> stated there (thanks to David Brodie for pointing me to it).
>
> Marcos
> In think it would be nice to link to "Bash Startup Files" page from the first page in Xorg section as well as any other that creates/modifies files in /etc/profile.d to ensure that /etc/profile and /etc/profile.d/* scripts exist before trying to create new and modify existing files. CC'ing -dev. -- Note: My last name is not Krejzi.
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
