All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Deragon <hans@deragon.biz>
Cc: autofs@linux.kernel.org
Subject: Re: backfstype patch.
Date: Wed, 30 Jun 2004 11:11:30 -0400	[thread overview]
Message-ID: <40E2D822.7020609@deragon.biz> (raw)
In-Reply-To: <40E2CC43.1060001@sun.com>

Mike Waychison wrote:
>>Michael.Waychison> Why do this in the parser when it can easily be done in
>>Michael.Waychison> a mount module?
>>
>>Care to expound a bit?  I'm not sure what people use backfstype for,
> 
> but if
> 
>>it is generic, then you wouldn't want to handle every case in every mount
>>module.  But I think I'm missing your point.
>>
>>It makes some sense to me to handle this above the mount module, simply
>>because you could call into two different modules.
>>
>>So, care to set me straight?  ;)
>>
>>-Jeff
> 
> 
> I'm CC'ing David as he may have a better view of what the cachefs status is.
> 
> Backfstype is a fstype=cachefs specific mount option.  Specifically:
> 
>  - add cachefs to the not_generic array in daemon/mount.c
>  - create a new mount module, modules/mount_cachefs.c.  This module
> would check for cachefs support available and use it if available.
> Otherwise it would rewrite the fstype with the backfstype mount option
> and call do_mount again.
> 
> - --
> Mike Waychison
> Sun Microsystems, Inc.
> 1 (650) 352-5299 voice
> 1 (416) 202-8336 voice
> http://www.sun.com

Great.


   Is this issue in someone's else hands?  The reason I coded the solution in 
parse_sun.c is simply because I know nada about automount and I wanted a quick 
solution.  I did not take the time to study automount's architecture to 
understand the big picture, and I won't have the time to do this either. :( 
Worse, I do not know much about C coding and particularly the available API for 
Linux system calls.  However, I would like to see some solution taking care of 
backfstype being implemented in the next release.  Can someone please take the 
initiative?  You guys seam to understand the issue much better than I.


Best regards,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc.     Open source:
http://www.deragon.biz        http://facil.qc.ca (Promotion du libre)
mailto://hans@deragon.biz     http://autopoweroff.sourceforge.net (Logiciel)

  parent reply	other threads:[~2004-06-30 15:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 20:10 backfstype patch Hans Deragon
2004-06-30 13:26 ` Jeff Moyer
2004-06-30 14:00   ` raven
2004-06-30 15:01   ` Hans Deragon
2004-06-30 13:31 ` Mike Waychison
2004-06-30 13:51   ` Jeff Moyer
2004-06-30 14:20     ` Mike Waychison
2004-06-30 14:22       ` Jeff Moyer
2004-06-30 15:11       ` Hans Deragon [this message]
2004-06-30 14:28     ` Mike Waychison
  -- strict thread matches above, loose matches on Subject: below --
2004-07-16 18:45 Hans Deragon
2004-07-16 19:01 ` Jeff Moyer
2005-03-02 21:03   ` Greg Bradner
2005-03-03  2:15     ` Ian Kent
2004-07-17  4:16 ` raven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40E2D822.7020609@deragon.biz \
    --to=hans@deragon.biz \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.