> Date: Fri, 29 Mar 2013 15:56:24 -0400
> From: "Cliff McDiarmid" <[email protected]>
> To: "akhiezer" <[email protected]>,
> "BLFS Support List"
> <[email protected]>
> Subject: Re: [blfs-support] Autofs problem on LFS7.2
>
.
.
> > > > > > > > > Right. I've recompiled autofs(had to include MIT
> > > > > > > > > Kerberos)and the results were intially promising.
> > > > .
> > > > .
> > > > > > > You may be right about Kerbos, I seem to remember getting round
> > > > > > > that originally and not compiling against it.
> > > >
> > > >
> > > > Might come back to: why 'had to include MIT Kerberos' for that second
> > > > compile,
> > > > yet not for the first one; and for the first compile what did 'getting
> > > > round'
> > > > (ie avoiding) compiling kerberos entail.
> > > >
The reason for making a note about this, is that for debugging you often
ideally
want to be changing only one parameter at a time (one type of exception may be
when 'bisecting' a problem). Introducing a structure like kerberos into the
picture, can make the debugging a bit like trying to sort out a networking
problem
in the presence of a non-trivial active firewall, compared to when the firewall
is
completely deactivated.
> >
.
.
> > I'd do (and verify):
> > $ chmod 644 /etc/auto.testautomount
> >
.
.
> > > /testautomount /etc/auto.testautomount$
> >
> > Change this to:
> > /testautomount file:/etc/auto.testautomount
>
> Got it! After starting autofs with 'automount -v -f -d /etc/auto.master',
> plugging the usbstick and issuing
> 'ls -laF /testautomount/sandisk' we get:
>
:) That's good that it's started working.
The chmod-0644 should have been enough by itself: did you test after just that
change, and before going on to the 'file:' change? Sorry if/that maybe wasn't
clear(er) on that.
> > > > ----
> > > > (1) Go back to the original src - i.e. where that 'LIBTIRPC' block is
> > > > _NOT_
> > > > commented out - and compile as in the book, but for the configure
> > > > stage, do:
> > > >
> > > > ./configure --prefix=/ --mandir=/usr/share/man \
> > > > --without-systemd --without-libtirpc --without-hesiod \
> > > > --without-openldap --without-sasl
> > > >
> > > > (The sasl, ldap, hesiod, &c stuff can be added back in later once we
> > > > have got
> > > > a working autofs from a basic config).
> > > > Then test and see if it goes OK.
> > > > Post the output from 'automount -v -f -d /etc/auto.master' , incl
> > > > showing what
> > > > happens when you plug a stick in: just copy'n'paste the full session,
> > > > please.
> > > > --
> > > > (2) If still no-go after '(1)', then do the same as '(1)' but with the
> > > > 'patch-reverted' src - i.e. with that 'LIBTIRPC' block commented out -
> > > > and
> > > > use the same 'configure ...' line as in '(1)' .
> > > > ----
Tidy-up of the 'LIBTIRPC' stuff: although that block of 'libtirpc' code was
committed upstream as a single contained patch, and we reverted it as a single
contained patch, it's still not always a good idea to be 'lopping off' chunks
of code - without a full understanding of how it sits in relation to the other
code - to get around an immediate issue, as we have basically done here; as
there can be unintended consequences (recall e.g. the valgrind/debian/openssl
mess-up from a few years back).
So, I'd suggest trying '(1)', above, so that you are (at least in theory)
bypassing 'libtirpc' code in a 'more-proper' manner. I know that there's often
the tendency to just want push on from here with the setup as-is, now that it's
working better, and get it all setup, and catch-up with other things that have
become queued, rather than spending more time on the present stage of the
development: but it's also a good idea to have the 'foundations' in as good a
shape as possible.
rgds,
akh
--
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
