Announce: modutils 2.4.3 is available

Announce: modutils 2.4.3 is available

[Keith Owens]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Just a small collection of bug fixes.  No new facilities.

ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/modutils/v2.4

modutils-2.4.3.tar.gz           Source tarball, includes RPM spec file
modutils-2.4.3-1.src.rpm        As above, in SRPM format
modutils-2.4.3-1.i386.rpm       Compiled with egcs-2.91.66, glibc 2.1.2
modutils-2.4.3-1.sparc64.rpm    Combined sparc 32/64.
modutils-2.4.3-1.ia64.rpm       Compiled with gcc 2.96-ia64-000717 snap 001117,
				libc-2.2.1.
patch-modutils-2.4.3.gz         Patch from modutils 2.4.2 to 2.4.3.

Related kernel patches.

patch-2.4.2-persistent.gz       Adds persistent data and generic string
				support to kernel 2.4.2.  Optional.

Changelog extract

	* putenv() strings must be copied first.
	* Not everybody has Elf64_Xword.
	* Add stdlib.h to some files for glibc 2.2.
	* Redhat modutils-2.4.0-alias.patch.
	* Out by one error in alloca.  Spotted by Yann Droneaud.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE6md8Vi4UHNye0ZOoRAre4AJ9DqRQamIQnyrC/SogQtnEOdYmAsgCffV8a
ga0aQX649OmmvwYAdXA/l0c=
=4sk2
-----END PGP SIGNATURE-----

Re: Announce: modutils 2.4.3 is available

[Stefan Smietanowski]

Hi.

> modutils-2.4.3.tar.gz           Source tarball, includes RPM spec file
> modutils-2.4.3-1.src.rpm        As above, in SRPM format
> modutils-2.4.3-1.i386.rpm       Compiled with egcs-2.91.66, glibc 2.1.2
> modutils-2.4.3-1.sparc64.rpm    Combined sparc 32/64.
> modutils-2.4.3-1.ia64.rpm       Compiled with gcc 2.96-ia64-000717 snap 001117,

IIRC 2.4.2 was 2.4 only, and was released under protest, is it the same
for 2.4.3?

// Stefan

Re: Announce: modutils 2.4.3 is available

[Keith Owens]

On Mon, 26 Feb 2001 11:08:59 +0100, 
Stefan Smietanowski <stefan@hanse.com> wrote:
>Keith Owens wrote
>> modutils-2.4.3.tar.gz           Source tarball, includes RPM spec file
>
>IIRC 2.4.2 was 2.4 only, and was released under protest, is it the same
>for 2.4.3?

modutils 2.4 will work on kernel 2.0 and libc 5, one of the changes in
2.4.3 is for libc5 support.  The protest period has expired.

Re: Announce: modutils 2.4.3 is available

[Kurt Garloff]

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

On Tue, Feb 27, 2001 at 09:41:26AM +1100, Keith Owens wrote:
> On Mon, 26 Feb 2001 11:08:59 +0100, 
> Stefan Smietanowski <stefan@hanse.com> wrote:
> >Keith Owens wrote
> >> modutils-2.4.3.tar.gz           Source tarball, includes RPM spec file
> >
> >IIRC 2.4.2 was 2.4 only, and was released under protest, is it the same
> >for 2.4.3?
> 
> modutils 2.4 will work on kernel 2.0 and libc 5, one of the changes in
> 2.4.3 is for libc5 support.  The protest period has expired.

To clearify: The incompatibility only affects the hotplug kernel device
tables ... 
As there was no support amongst USB crowds for adding a version info for the
table formats, the modutils-2.4.2 could not provide support for per 2.4.0
kernel hotplug device tables. Nor can 2.4.3. The rest of the functionality
is unaffected.
Keith, correct me if I misunderstood ...

Regards,
-- 
Kurt Garloff  <garloff@suse.de>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE GmbH, Nuernberg, FRG                               SCSI, Security

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Building autofs

[Rainer Mager]

Hi all,

	I'm trying to use autofs for the first time and am running into some
problems. First,  the documentation seems quite weak, that is, I'm not sure
if what I have is what I should have. I managed to find an autofs version 4
pre 9 tarball on the kernel mirrors. This seem the latest but is still a bit
old and the referenced home page doesn't seem any newer. My real problem,
however, is that when I try to build it I get this error:

lookup_program.c:147: `OPEN_MAX' undeclared (first use in this function)

My understanding is that OPEN_MAX is defined in linux/limits.h but I
hesitate to change the code since I would expect this to build out of the
box.


	Cas someone who is using autofs give me some pointers? Am I on the right
track?

Thanks,

--Rainer

Re: Building autofs

[Urban Widmark]

On Wed, 28 Feb 2001, Rainer Mager wrote:

> Hi all,
> 
> 	I'm trying to use autofs for the first time and am running into some
> problems. First,  the documentation seems quite weak, that is, I'm not sure

I am sure the maintainer would appreciate if you wrote down what you found
difficult/missing from the docs (in the form of a patch to the existing
docs perhaps).

> if what I have is what I should have. I managed to find an autofs version 4
> pre 9 tarball on the kernel mirrors. This seem the latest but is still a bit
> old and the referenced home page doesn't seem any newer. My real problem,
> however, is that when I try to build it I get this error:
> 
> lookup_program.c:147: `OPEN_MAX' undeclared (first use in this function)

#include <linux/limits.h> gives:
#define OPEN_MAX         256    /* # open files a process may have */

But autofs is well behaved and doesn't use kernel headers but that makes
it fails on newer glibcs (at least I think that was it).

Just define it. If autofs4 is doing the same as autofs3 then it is only
used for program lookups (where a program generates the map to use) and
unless you are going to use those it won't matter at all.


There is also some info here, including how to find the autofs
mailinglist.
http://www.linux-consulting.com/Amd_AutoFS/autofs.html

Or google for "autofs OPEN_MAX", "autofs mailinglist archive", ...
There appears to be a autofs-open_max.patch somewhere.

/Urban