Jeremy Fitzhardinge wrote: > > On Mon, 2002-11-04 at 04:23, Steffen Grunewald wrote: > Before I start my own modifications, Ii'd like to ask: Are there > patches available to fix this behaviour cleanly? Or should I start > a sourceforge project (Jeremy won't like that...)? > > Well, I was actually thinking of kicking autofs-4 onto SourceForge, just > so that it isn't some code sitting here being somewhat ignored.
It's not only being ignored, but patches show up here and there and nobody checks/unifies them. I counted 38 patches for Debian's autofs-4 release, some of whose shouldn't be in a general release, while some others (most) should, with some minor modifications. (Some of them, or very similar ones, are in PLD.) In > particular, I'd like to get some sanity in the realm of startup scripts > for various distributions, since the current stuff doesn't scale well. Well, there's Redhat's style, and there is Debian style. Most of the major distros seem to follow what RedHat does. Even SuSE. It would make sense to put all the good general patches together and release a source RPM at least. I'd be willing to do this as a starting point (I'm perhaps not a geek who understands all the patches - the debian people already did. I'd check whether they apply cleanly and put together a SPEC file) --- where to put it? Should I attach it to a mail to the list? > As far as YP and nsswitch.conf goes, I don't really have an opinion > (though HPA might have an opinion at you, depending on what you're > thinking about). Debian solved this in a rather pragmatic way: if there's a auto.master file, they don't look for a NIS map. If there's not, they do. So this is somewhat resembling "files nis" order without looking into nsswitch.conf. It's a bit ugly, but at least it does what you'd expect. Steffen _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
