On Friday 03 April 2009 23:13:19 Chris Staub wrote:
> Jason Erickson wrote:
> > I've been using this for the past week learning about linux and
> > the installs and it has been a great tool. I want to first
> > thank you for offering this book and helping others learn how
> > to build linux from s
Yep...didnt see that page.
Thanks
Jason
On Fri, Apr 3, 2009 at 8:13 PM, Chris Staub wrote:
> Jason Erickson wrote:
>> I've been using this for the past week learning about linux and the
>> installs and it has been a great tool. I want to first thank you for
>> offering this book and helping oth
Jason Erickson wrote:
> I've been using this for the past week learning about linux and the
> installs and it has been a great tool. I want to first thank you for
> offering this book and helping others learn how to build linux from
> scratch to make our own custom installs.
>
> I did notice a fe
Tushar Teredesai wrote:
>
> If you want, you can install the package manager as a package
> controlled by the package manager. Since the package manager in the
> package user's approach does not have any build dependencies (only
> run-time dependencies) it can be the first package to be installed
On Thu, Apr 2, 2009 at 2:01 PM, Mike McCarty wrote:
>
> One slightly confusing point, though, is why the package management
> tools don't get installed using the package user philosophy. Why
> aren't the tools themselves installed into the chroot environment
> using the temporary tools in /tools?
Tomas Klacko wrote:
>> You need to compile everything with
>> lib-path as /usr/lib etc so that we can compile gcc-pass1
>> against these binutils, (if I understand correctly this part
>> does not need -B).
>>
>
> Do you have any pointers on where to find out more about the lib-path?
> My curre
Support wrote:
> Mike McCarty wrote:
>> That's what I mentioned in the first message, which I didn't make
>> clear, I guess. In between Chapters 5 and 6, one would
>> build & install in /tools a temporary copy of the manager. Then, after
>> the initial setup in Chapter 6, the first package built &
On Friday 03 April 2009 14:03:28 Jason Erickson wrote:
> For section 5.21 Gawk-3.1.6 There seems to be a formatting
> issuehere is what the book says:
> Compilation is now complete. As discussed earlier, running the
> test suite is not mandatory for the temporary tools
> here in this chapter. T
I've been using this for the past week learning about linux and the
installs and it has been a great tool. I want to first thank you for
offering this book and helping others learn how to build linux from
scratch to make our own custom installs.
I did notice a few things going through it that I t
Mike McCarty wrote:
> That's what I mentioned in the first message, which I didn't make
> clear, I guess. In between Chapters 5 and 6, one would
> build & install in /tools a temporary copy of the manager. Then, after
> the initial setup in Chapter 6, the first package built & intalled
> would be t
Hey,
I've run into a problem with HAL and Xorg. I've built Xorg with HAL support,
and it expects that HAL has a mouse listed with `hal-device`. But it
doesn't, which means that with the default configuration(AllowEmptyInput on)
I don't have any mouse and keyboard. If I override that option to off,
Support wrote:
> Mike McCarty wrote:
>> That's what I'm asking about. I guess I wasn't clear. I don't understand
>> why the first package installed in Chapter 6, per the Hint, is
>> libc-headers instead of the package manager. ISTM that the first
>> package installed in the "real" system, that is t
Mike McCarty wrote:
> That's what I'm asking about. I guess I wasn't clear. I don't understand
> why the first package installed in Chapter 6, per the Hint, is
> libc-headers instead of the package manager. ISTM that the first
> package installed in the "real" system, that is the chroot environment
13 matches
Mail list logo
