From: Geoff Levand <geoffrey.levand@am.sony.com>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>,
Hiroyuki Machida <machida@sm.sony.co.jp>
Subject: Re: does the linux support rootfs on vfat?
Date: Mon, 06 Mar 2006 08:41:28 -0800 [thread overview]
Message-ID: <440C6638.7000909@am.sony.com> (raw)
In-Reply-To: <50c9a2250603042217l475e84pc9ab7ce87c40eb76@mail.gmail.com>
zhuzhenhua wrote:
> if in my product based ide disk, i want to it to support the
> u-disk(with vfat fs), and can i set the root fs as vfat too?
> if use vfat as rootfs, what's disadvantage of the selection?
>
See these threads, 'Posix file attribute support on VFAT', which
disscusses using VFAT for a root fs:
http://lkml.org/lkml/2005/8/8/76
http://lkml.org/lkml/2005/8/8/326
-Geoff
prev parent reply other threads:[~2006-03-06 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 6:17 does the linux support rootfs on vfat? zhuzhenhua
2006-03-05 8:09 ` Jan-Benedict Glaw
2006-03-05 11:22 ` Ralf Baechle
2006-03-06 16:49 ` Geoff Levand
2006-03-06 17:08 ` P. Christeas
2006-03-06 12:36 ` Stuart Longland
2006-03-06 16:41 ` Geoff Levand [this message]
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=440C6638.7000909@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=linux-mips@linux-mips.org \
--cc=machida@sm.sony.co.jp \
--cc=zzh.hust@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox