On Fri, Dec 28, 2007 at 10:32:03PM +, Ken Moffat wrote:
>
> For the kernel, you should keep the built directory around if you
> are going to need to build external modules against it, or to look
> at what is in the .config if it fails to build (normally,
> /proc/config.gz is an easier way to
On Fri, Dec 28, 2007 at 04:15:20PM -0600, Clyde Forrester wrote:
> Thank you.
> Am I still expected to rm the directories at the end of each section? Or
> are those directories expected to live there now? Or do I just clean 'em
> up whenever I'm short on space. I'm used to the paranoid environmen
Ken Moffat wrote:
> On Fri, Dec 28, 2007 at 02:08:28PM -0600, Clyde Forrester wrote:
>
>> In Chapter 5, we were cautioned to unpack the packages as user lfs and
>> so on.
>>
>> In Chapter 6 (6.7., and 6.8. for example) are we expected to unpack the
>> package and step into the directory as we
On Fri, Dec 28, 2007 at 01:35:12PM -0700, Shawn wrote:
> Assuming ext3fs, what is the output from "/sbin/dumpe2fs -h /dev/hda?" for
> your host filesystem?
> In particular, what does Reserved block count, Free blocks and Free inodes
> report? What is the "Filesystem state"? We can eliminate a fs
On Fri, Dec 28, 2007 at 02:08:28PM -0600, Clyde Forrester wrote:
> In Chapter 5, we were cautioned to unpack the packages as user lfs and
> so on.
>
> In Chapter 6 (6.7., and 6.8. for example) are we expected to unpack the
> package and step into the directory as we did in Chapter 5? Obviously w
On December 28, 2007 10:03:32 Ken Moffat wrote:
> OK, I admit it, I've failed the latest module in "administering
> your own systems", but I'm out of ideas about how to track down what
> is wrong.
>
> I was using an existing system, with gdm, to build a new clfs system
> in an xterm. Unfortunate
In Chapter 5, we were cautioned to unpack the packages as user lfs and
so on.
In Chapter 6 (6.7., and 6.8. for example) are we expected to unpack the
package and step into the directory as we did in Chapter 5? Obviously we
wouldn't unpack them as the lfs user as there is no such thing. Once
ag
OK, I admit it, I've failed the latest module in "administering
your own systems", but I'm out of ideas about how to track down what
is wrong.
I was using an existing system, with gdm, to build a new clfs system
in an xterm. Unfortunately, the new system didn't boot so I went
back to the host s
hi everybody!
i got stuck here, but i got no idea why the linker is missing,
the earlier two commands in 6.10 of the stable lfs-book all
worked:
> mv -v /tools/bin/{ld,ld-old}
> mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
but it seems as i do not have a ld-new to be moved to ld..
where cou
