All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: zhuzhenhua <zzh.hust@gmail.com>, linux-mips <linux-mips@linux-mips.org>
Subject: Re: does the linux support rootfs on vfat?
Date: Mon, 06 Mar 2006 08:49:24 -0800	[thread overview]
Message-ID: <440C6814.4020204@am.sony.com> (raw)
In-Reply-To: <20060305112247.GA4243@linux-mips.org>

Ralf Baechle wrote:
> On Sun, Mar 05, 2006 at 09:09:58AM +0100, Jan-Benedict Glaw wrote:
> 
>> On Sun, 2006-03-05 14:17:56 +0800, zhuzhenhua <zzh.hust@gmail.com> 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?
>> 
>> Well, most notably you won't have device nodes. Maybe a ram-backed
>> filesystem mounted to /dev/ could solve that, but you'd probably need
>> an initrd for that to do.
> 
> It's anso case-insensitive which may cause some further troubles.  It's
> doesn't have proper inodes, no UNIX file modes, no UID / GID support (These
> two can be kludges in awfully insufficient way through mount options), not
> only lacks device special files but also no FIFO, no UNIX domain sockets,
> no hard or soft links.  It's simply a sorry excuse for a useful filesystem.

It's attractive for a limited resource device that needs to have FAT support
for a removable flash memory card (for Windows PC interoperability).  If you
can use FAT for the root fs, that reduces the system resource needs.

It doesn't make sense if his ide disk is non-removable though.

-Geoff

  reply	other threads:[~2006-03-06 16:41 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 [this message]
2006-03-06 17:08       ` P. Christeas
2006-03-06 12:36 ` Stuart Longland
2006-03-06 16:41 ` Geoff Levand

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=440C6814.4020204@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --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 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.