Re: Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2. 6.14.x)

2005-12-01 Thread Matt Darcy
Mark Rosenstand wrote: On Wed, 2005-11-30 at 07:46 -0800, Dan Nicholson wrote: On 11/30/05, Feldmeier Bernd [EMAIL PROTECTED] wrote: Hello guys, I created a LFS 6.1.1 test system. But is there a problem if I use the latest kernel version ? Because Using Linux-Libc-Headers version and

Re: Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2. 6.14.x)

2005-12-01 Thread Matt Darcy
Mark Rosenstand wrote: Matt Darcy wrote: Mark Rosenstand wrote: And I run a dovecot IMAP server without inotify-support on a inotify-enabled Linux 2.6.14 machine because it couldn't find linux/inotify.h And what is your experience with this ? Do you find that inotify works/is picked up by

FC4 as a host [Was: Re: file format not recognized from ld right from the start????]

2005-12-01 Thread Jeremy Huntwork
Andrew Benton wrote: Bing. You hit the nail on the head there. As Richard said, Fedora Core 4 isn't a suitable distro to build the stable version of the book. It should work OK for the development version but that may not be suitable if it's your first attempt at LFS. I've had good results

Re: FC4 as a host [Was: Re: file format not recognized from ld right from the start????]

2005-12-01 Thread Richard A Downing
On Thu, 01 Dec 2005 10:04:50 -0500 Jeremy Huntwork [EMAIL PROTECTED] wrote: Andrew Benton wrote: Bing. You hit the nail on the head there. As Richard said, Fedora Core 4 isn't a suitable distro to build the stable version of the book. It should work OK for the development version but

Re: Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2. 6.14.x)

2005-12-01 Thread Dan Nicholson
On 12/1/05, Mark Rosenstand [EMAIL PROTECTED] wrote: I would like it to use inotify, but it doesn't because the headers are too old. I never really understood why most (all?) distributors choose to use kernel headers that doesn't match the running kernel. It's up to the userspace package

Re: Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2. 6.14.x)

2005-12-01 Thread Dan Nicholson
On 12/1/05, Dan Nicholson [EMAIL PROTECTED] wrote: On 12/1/05, Mark Rosenstand [EMAIL PROTECTED] wrote: I would like it to use inotify, but it doesn't because the headers are too old. I never really understood why most (all?) distributors choose to use kernel headers that doesn't match the

Re: Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2. 6.14.x)

2005-12-01 Thread Matthew Burgess
Dan Nicholson wrote: As a follow up to this comment, beagle also uses inotify. I built it with l-l-h-2.6.12.0, and it works fine now that I've upgraded my kernel to 2.6.14. How? beagle (appropriately) includes inotify.h in it's source tree. Just as a point of interest, what happens if one

Re: Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2. 6.14.x)

2005-12-01 Thread Dan Nicholson
On 12/1/05, Matthew Burgess [EMAIL PROTECTED] wrote: Dan Nicholson wrote: As a follow up to this comment, beagle also uses inotify. I built it with l-l-h-2.6.12.0, and it works fine now that I've upgraded my kernel to 2.6.14. How? beagle (appropriately) includes inotify.h in it's

clarify __ Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2.6.14.x)

2005-12-01 Thread Bernd Feldmeier
Hi guys, nice discussion about that very important stuff. I began this discussion earlier ... So maybe someone could clarify this stuff clearly ... a) dependency of kernel version and linux-libc-header version b) problems occuring c) real meaning of sanatized headers (why ...) d) creating our

LFS 6.1 and 6.1.1, chapter 3: man-pages-2.01 download location

2005-12-01 Thread Nico R.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! Chapter 3.2 of LFS 6.1.1 URL:http://www.linuxfromscratch.org/lfs/view/6.1.1/chapter03/packages.html lists URL:http://www.kernel.org/pub/linux/docs/manpages/ as download location for man-pages-2.01. This package is not/no longer available from

Re: LFS 6.1 and 6.1.1, chapter 3: man-pages-2.01 download location

2005-12-01 Thread Justin R. Knierim
Nico R. wrote: I suggest finding a mirror which still has version 2.01 of man-pages and including the correct URIs in the LFS 6.1 and 6.1.1 errata. LFS has its own package mirrors. On it are the packages for LFS version 6.0 to Development. There is no sense in adding download locations to

Re: clarify __ Using Linux-Libc-Headers-2.6.x.y + latest kernel version (e.g. 2.6.14.x)

2005-12-01 Thread Bryan Kadzban
Bernd Feldmeier wrote: a) dependency of kernel version and linux-libc-header version None whatsoever. These are two different packages, with two different reasons for existing. l-l-h is based on the kernel headers, but you can use any version of either of them (well, no, that isn't quite

ANNOUNCE: jhalfs 0.2 Released

2005-12-01 Thread Jeremy Huntwork
As you may be aware, there is a new implementation of ALFS available, called jhalfs. The main purpose of jhalfs is to provide a pure reference build of LFS by extracting the commands to run directly from the LFS book. This has the added benefit of reducing maintenance as there are no profiles

Re: qt

2005-12-01 Thread Bruce Dubbs
Bruce Dubbs wrote: I'm working with qt on a fresh lfs-dev system. The latest suitable for KDE is version 3.3.5. I've built about all the dependencies and am trying to get qt validated. My access is via a chroot from an LFS 6.1 system. During the make, I am getting a segfault from the

[Announce] LFS LiveCD 6.1.1-1 Released

2005-12-01 Thread Justin R. Knierim
The LFS LiveCD Team is proud to announce the release of the x86-6.1.1-1 version of the LFS LiveCD. This version is built using LFS 6.1.1 and BLFS packages from the svn branch. Packages for LFS 6.1.1 are included on the LiveCD. Other new features: * XFCE Terminal with helpful menus,

Re: [Announce] LFS LiveCD 6.1.1-1 Released

2005-12-01 Thread Mukesh Kaushal
Congrats to all of the members of the LFS team. This is really a great achievement for us. Gossip is like a photograph. It starts with a negative, then is developed and enlarged --- Regards Mukesh Kaushal - Original Message - From: Justin R. Knierim [EMAIL PROTECTED] To: Development