From: "szonyi calin" <caszonyi@yahoo.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.8-rc3
Date: Fri, 6 Aug 2004 00:19:52 +0200 (CEST) [thread overview]
Message-ID: <20040805221952.31315.qmail@web52902.mail.yahoo.com> (raw)
In-Reply-To: <87657xtyd3.fsf@devron.myhome.or.jp>
--- OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> a écrit :
> Erik Mouw <erik@harddisk-recovery.com> writes:
>
> > > iocharset=value
> > > Character set to use for converting between
> 8 bit characters and
> > > 16 bit Unicode characters. The default is
> iso8859-1. Long file-
> > > names are stored on disk in Unicode format.
> > >
> > > the default is iso8859-1. Has this default gone haywire
> somewhere?
> >
> > Yes, it's in the hidden in the ChangeLog. You can find it if
> you know
> > iocharset is the same as nls:
> >
> > Hirofumi Ogawa:
> > o FAT: kill nls default
>
> Or Documentation/filesystems/vfat.txt
kernel says
FAT: codepage or iocharset option didn't specified
File name can not access proper (mounted as read-only)
codepage *is* specified:
my fstab line for mounting the vfat filesystem is:
/dev/hda1 /mnt/dosc vfat
defaults,user,uid=100,gid=100,codepage=437 1 0
So the message is not correct ;-)
specifying iocharset works.
Bye
Calin
--
Yesterday it worked
today isn't working
windows is like that
Vous manquez despace pour stocker vos mails ?
Yahoo! Mail vous offre GRATUITEMENT 100 Mo !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com
next prev parent reply other threads:[~2004-08-05 22:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 22:09 Linux 2.6.8-rc3 Linus Torvalds
2004-08-04 12:07 ` Jan De Luyck
2004-08-04 12:13 ` Karol Kozimor
2004-08-04 12:40 ` Erik Mouw
2004-08-05 15:10 ` OGAWA Hirofumi
2004-08-05 22:19 ` szonyi calin [this message]
2004-08-04 12:57 ` Gene Heskett
2004-08-04 12:44 ` Juergen Stuber
2004-08-04 13:37 ` Geert Uytterhoeven
2004-08-04 15:04 ` Jari Ruusu
2004-08-04 16:00 ` James Morris
2004-08-04 16:10 ` J. Bruce Fields
2004-08-04 16:27 ` Arjan van de Ven
2004-08-04 18:19 ` Patrick McFarland
2004-08-04 18:45 ` Linus Torvalds
2004-08-05 13:54 ` Patrick McFarland
2004-08-04 21:27 ` H. Peter Anvin
2004-08-04 18:37 ` Linux 2.6.8-rc3 - BSD licensing Fruhwirth Clemens
2004-08-04 18:51 ` Linus Torvalds
2004-08-04 19:26 ` Fruhwirth Clemens
2004-08-04 19:56 ` Linus Torvalds
2004-08-05 12:33 ` Jari Ruusu
2004-08-05 16:50 ` Linus Torvalds
2004-08-05 17:45 ` Måns Rullgård
2004-08-05 20:21 ` Alan Cox
2004-08-05 21:37 ` Måns Rullgård
2004-08-05 21:08 ` Alan Cox
2004-08-06 9:47 ` Jari Ruusu
2004-08-06 16:39 ` Linus Torvalds
2004-08-07 10:19 ` Jari Ruusu
2004-08-07 10:38 ` Patrick McFarland
2004-08-07 17:27 ` Linus Torvalds
2004-08-05 12:32 ` Linux 2.6.8-rc3 Jari Ruusu
2004-08-04 16:23 ` Linus Torvalds
2004-08-05 15:04 ` [PATCH] Drop asm i586 AES code James Morris
2004-08-04 15:08 ` Linux 2.6.8-rc3 (compile stats) John Cherry
2004-08-04 18:52 ` [patch] 2.6.8-rc3: fix modular kernel with gcc 2.95 Adrian Bunk
2004-08-06 19:57 ` 2.6.8-rc3: MPT Fusion compile error with PROC_FS=n Adrian Bunk
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=20040805221952.31315.qmail@web52902.mail.yahoo.com \
--to=caszonyi@yahoo.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@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.