All of lore.kernel.org
 help / color / mirror / Atom feed
* fstab
@ 2009-05-03 16:14 Peter
  2009-05-05 13:54 ` fstab Leonardo Chiquitto
  0 siblings, 1 reply; 4+ messages in thread
From: Peter @ 2009-05-03 16:14 UTC (permalink / raw)
  To: autofs


I can't find any reference to a network share (nfs) can or can not be present in fstab. My problem is SLOCATE doesn't like Autofs and ignores my nfs share when I run updatedb. Using nfs in a "normal" fashion from fstab slocate works. Looks like Autofs ignore has been hardcoded because removing autofs from updatedb.conf makes no difference. I keep my file storage server down and bring it up when needed. Autofs works like a charm, nfs via fstab doesn't. If I put in a line in fstab noauto with the nfs share will KDE or AUTOFS have problems? I am on Gentoo.
thanks
regards
peter

-- 
Peter <Sheldon>

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: fstab
  2009-05-03 16:14 fstab Peter
@ 2009-05-05 13:54 ` Leonardo Chiquitto
  0 siblings, 0 replies; 4+ messages in thread
From: Leonardo Chiquitto @ 2009-05-05 13:54 UTC (permalink / raw)
  To: Peter; +Cc: autofs

> I can't find any reference to a network share (nfs) can or can
>  not be present in fstab. My problem is SLOCATE doesn't
> like Autofs and ignores my nfs share when I run updatedb.

I found that when using AutoFS 5, setting DEFAULT_BROWSE_MODE
to "yes" (it's the default, but perhaps your distribution tweaks it by
default) in /etc/sysconfig/autofs can influence updatedb behavior.

Also, if you want updatedb to search down the AutoFS paths, make
sure it is configured to allow NFS, CIFS and whatever other file
systems you are mounting with AutoFS.

Regards,
Leonardo

^ permalink raw reply	[flat|nested] 4+ messages in thread
* fstab
@ 2012-09-12 11:48 Jaap de Jong
  2012-09-12 11:52 ` fstab Jaap de Jong
  0 siblings, 1 reply; 4+ messages in thread
From: Jaap de Jong @ 2012-09-12 11:48 UTC (permalink / raw)
  To: openembedded-core@lists.openembedded.org

Hi All,

I've created my own /etc/fstab which is perfectly included in 
base-files_*.ipk as expected.
It also shows up in 
build/tmp-angstrom_v2012_05-eglibc/work/mymachine/myimage*/rootfs/etc
But I find a different version of /etc/fstab under 
build/tmp-angstrom_v2012_05-eglibc/deploy/images/mymachine/myimage*.rootfs.tar.bz2
I can't figure out why!
Any ideas or hints?

Thanks!
Jaap



^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: fstab
  2012-09-12 11:48 fstab Jaap de Jong
@ 2012-09-12 11:52 ` Jaap de Jong
  0 siblings, 0 replies; 4+ messages in thread
From: Jaap de Jong @ 2012-09-12 11:52 UTC (permalink / raw)
  To: openembedded-core

Sorry !!!!
Already solved.
My bad !!!

On 09/12/2012 01:48 PM, Jaap de Jong wrote:
> Hi All,
>
> I've created my own /etc/fstab which is perfectly included in
> base-files_*.ipk as expected.
> It also shows up in
> build/tmp-angstrom_v2012_05-eglibc/work/mymachine/myimage*/rootfs/etc
> But I find a different version of /etc/fstab under
> build/tmp-angstrom_v2012_05-eglibc/deploy/images/mymachine/myimage*.rootfs.tar.bz2
> I can't figure out why!
> Any ideas or hints?
>
> Thanks!
> Jaap
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>




^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-09-12 12:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-12 11:48 fstab Jaap de Jong
2012-09-12 11:52 ` fstab Jaap de Jong
  -- strict thread matches above, loose matches on Subject: below --
2009-05-03 16:14 fstab Peter
2009-05-05 13:54 ` fstab Leonardo Chiquitto

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.