From: Florian Iragne <florian.iragne@labri.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: add/remove actions for usb devices
Date: Mon, 29 Mar 2004 16:36:49 +0000 [thread overview]
Message-ID: <406850A1.2020105@labri.fr> (raw)
In-Reply-To: <40648838.2040703@labri.fr>
jjluza wrote:
>Le dimanche 28 Mars 2004 18:56, vous avez écrit :
>
>
>>jjluza wrote:
>>
>>
>>>Now, I have still a problem, I just notice (as it is said in the manpage
>>>of mount) that I can't use "-o sync" with "-t vfat". I get no error, but
>>>the behaviour is like it is not mounted with sync option (I even got a
>>>awfull kernel oops).
>>>Is there a workaround since usb stick need to use vfat and only vfat fs ?
>>>I would like to stop using supermount with my usb stick, if it's
>>>possible. Sorry if it's not udev related, maybe you know someone I can
>>>ask about that ?
>>>
>>>
>>correct me if i'm wrong, but supermount do mount devices in sync mode,
>>so it has the same behaviour as mounting devices with sync option and
>>umount them after removal.
>>
>>my 2 cents
>>
>>Florian
>>
>>
>
>
>That's what I thought but it seems that it's not what it does.
>Look at the manpage of mount, you'll see that sync works only with ext2, ext3
>et ufs.
>I think supermount does more thing than only mounts devices in sync mode.
>
>
well, where do you see any mention of the limitation of the sync mode to
ext*/ufs? i've read the manpage of mount several times, but did not find
anything like the info you mentioned.
Florian
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-03-29 16:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 19:44 add/remove actions for usb devices Florian Iragne
2004-03-26 19:51 ` Greg KH
2004-03-26 21:13 ` Florian Iragne
2004-03-26 21:22 ` Florian Iragne
2004-03-26 22:59 ` Greg KH
2004-03-28 12:05 ` Florian Iragne
2004-03-28 13:45 ` Florian Iragne
2004-03-28 13:52 ` Kay Sievers
2004-03-28 14:08 ` Martin Lohmeier
2004-03-28 14:35 ` jjluza
2004-03-28 14:58 ` Kay Sievers
2004-03-28 16:16 ` jjluza
2004-03-28 18:02 ` Florian Iragne
2004-03-28 18:19 ` Kay Sievers
2004-03-29 16:21 ` Florian Iragne
2004-03-29 16:36 ` Florian Iragne [this message]
2004-03-29 18:51 ` Patrick Mansfield
2004-03-29 19:11 ` Martin Lohmeier
2004-03-29 23:26 ` jjluza
2004-03-30 7:22 ` Florian Iragne
2004-03-30 7:25 ` Florian Iragne
2004-03-30 8:35 ` jjluza
2004-03-30 8:49 ` Florian Iragne
2004-03-30 9:48 ` jjluza
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=406850A1.2020105@labri.fr \
--to=florian.iragne@labri.fr \
--cc=linux-hotplug@vger.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.