Alexander E. Patrakov wrote:
>
> Since the proposal to add translated messages to the bootscripts failed,
> wc should work fine (all strings it operated upon are ASCII-only) and the sed
> s/././g command is not needed.
>
> Or should we keep that just in case so that the proposal can be easily
>
Andrew Benton wrote:
Sorry if this has been covered already, but I'm just looking at the page
7.4. Device and Module Handling on an LFS System in Linux From Scratch -
Version 6.1-testing-20050401 Chapter 7. Setting Up System Bootscripts
It has a section 7.4.3. Handling Hotpluggable/Dynamic Device
Puvi wrote:
configure: error: forced unwind support is required
See this thread:
http://archives.linuxfromscratch.org/mail-archives/lfs-hackers/2004-July/001835.html
The problem seems to lie in the way your host system is set up, though
after reading through that thread, I'm not sure if the exact
hi
Iam using linux Redhat linux 9 (with out an upgradded packages ) i
sarted compiling LFS version 6 as stated in the pdf while compailing
glibc i got the error "configure: error: forced unwind support is
required" i have not worked on such projet can an body give me a
solution to solve this probl
DJ Lucas wrote:
> Matthias Berndt wrote:
>> Greetings,
>>
>> wouldn't it make sense to move 'wc' from '/usr/bin' to '/bin' like
>> other tools in the coreutils-package to prevent some more or less
>> cryptic constructions in '/etc/rc.d/init.d/functions'? FHS don't tell me
>> anything against this
On Saturday 09 April 2005 09:29, Allard Welter wrote:
> It's been a while since building lfs. All going swimmingly thanks.
> The coreutils-5.2.1-suppress_hostname_uptime_kill_su-1.patch also
> suppresses the building of hostname, however the mv command after the
> install in ch6 still attempts to m
