Re: CDs which hang kernel
On Mon, 11 Jul 2005 23:10:37 +0300 Nerijus Baliunas <[EMAIL PROTECTED]> wrote: > I have 2 cdroms which hang PC - one when trying to mount, another when > inserted. Kernel 2.6.12-1.1390_FC4, Lite-On SOHW-1673S, > hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) > I can send them by mail if anyone wants. Actually it hangs with first one, when trying to mount, with second I get oops. Regards, Nerijus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
CDs which hang kernel
Hello, I have 2 cdroms which hang PC - one when trying to mount, another when inserted. Kernel 2.6.12-1.1390_FC4, Lite-On SOHW-1673S, hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) I can send them by mail if anyone wants. Regards, Nerijus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [Emu10k1-devel] Re: Buggy emu10k1 drivers.
> Can you give the CVS driver a try? Snapshots are available here: > http://opensource.creative.com/snapshot.html > > The driver in the kernel is based on a CVS snapshot from last summer, the > problem may be fixed in CVS. So why noone sends updated driver to Alan? Regards, Nerijus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH] support for Cobalt Networks (x86 only) systems
> Aattached is a (large, but self contained) patch for Cobalt Networks suport Is not? ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH] fix more typos in Configure.help and fs/nls/Config.in
> > Official country name: Belarus > > Language/Nationality: Belarusian > > > > Standard has taken things right as we pronounce them. > > > > Please apply the patch. > > Done. Thanks for confirming it is correct You forgot to apply the second part: --- Config.in.orig Wed May 30 00:27:45 2001 +++ Config.in Mon May 28 19:32:25 2001 @@ -29,7 +29,7 @@ tristate 'Codepage 852 (Central/Eastern Europe)' CONFIG_NLS_CODEPAGE_852 tristate 'Codepage 855 (Cyrillic)' CONFIG_NLS_CODEPAGE_855 tristate 'Codepage 857 (Turkish)'CONFIG_NLS_CODEPAGE_857 - tristate 'Codepage 860 (Portugese)' CONFIG_NLS_CODEPAGE_860 + tristate 'Codepage 860 (Portuguese)' CONFIG_NLS_CODEPAGE_860 tristate 'Codepage 861 (Icelandic)' CONFIG_NLS_CODEPAGE_861 tristate 'Codepage 862 (Hebrew)' CONFIG_NLS_CODEPAGE_862 tristate 'Codepage 863 (Canadian French)'CONFIG_NLS_CODEPAGE_863 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH] fix more typos in Configure.help and fs/nls/Config.in
> > The ISO639 registrars call it "Belarusian". See > > http://lcweb.loc.gov/standards/iso639-2/langhome.html > > under "English Name of Language". > > Which is a typo in the standard for sure, since belarussian is > meaning "White Russians". No. They changed their country name to "Belarus", since "Belarusian". Regards, Nerijus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] fix more typos in Configure.help and fs/nls/Config.in
The ISO639 registrars call it "Belarusian". See http://lcweb.loc.gov/standards/iso639-2/langhome.html under "English Name of Language". Against 2.4.5-ac2: --- Configure.help.orig Mon May 28 19:23:18 2001 +++ Configure.help Mon May 28 19:31:50 2001 @@ -12838,7 +12838,7 @@ only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Thai. -Windows CP1251 (Bulgarian, Belarussian) +Windows CP1251 (Bulgarian, Belarusian) CONFIG_NLS_CODEPAGE_1251 The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in @@ -12847,7 +12847,7 @@ DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Russian and - Bulgarian and Belarussian. + Bulgarian and Belarusian. Japanese charsets (Shift-JIS, EUC-JP) CONFIG_NLS_CODEPAGE_932 @@ -12938,7 +12938,7 @@ from the Microsoft FAT file system family or from JOLIET CDROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for ISO8859-5, a Cyrillic - character set with which you can type Bulgarian, Byelorussian, + character set with which you can type Bulgarian, Belarusian, Macedonian, Russian, Serbian, and Ukrainian. Note that the charset KOI8-R is preferred in Russia. @@ -13027,13 +13027,13 @@ input/output character sets. Say Y here for the preferred Russian character set. -NLS KOI8-U/RU (Ukrainian, Belarussian) +NLS KOI8-U/RU (Ukrainian, Belarusian) CONFIG_NLS_KOI8_U If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the preferred Ukrainian - (koi8-u) and Belarussian (koi8-ru) character sets. + (koi8-u) and Belarusian (koi8-ru) character sets. NLS UTF8 CONFIG_NLS_UTF8 @@ -19014,7 +19014,7 @@ # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ -# LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt +# LocalWords: Valencian Slovene Esperanto Estonian Latvian Belarusian KOI mt # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb --- Config.in.orig Sun May 27 00:10:50 2001 +++ Config.in Mon May 28 19:32:25 2001 @@ -29,7 +29,7 @@ tristate 'Codepage 852 (Central/Eastern Europe)' CONFIG_NLS_CODEPAGE_852 tristate 'Codepage 855 (Cyrillic)' CONFIG_NLS_CODEPAGE_855 tristate 'Codepage 857 (Turkish)'CONFIG_NLS_CODEPAGE_857 - tristate 'Codepage 860 (Portugese)' CONFIG_NLS_CODEPAGE_860 + tristate 'Codepage 860 (Portuguese)' CONFIG_NLS_CODEPAGE_860 tristate 'Codepage 861 (Icelandic)' CONFIG_NLS_CODEPAGE_861 tristate 'Codepage 862 (Hebrew)' CONFIG_NLS_CODEPAGE_862 tristate 'Codepage 863 (Canadian French)'CONFIG_NLS_CODEPAGE_863 @@ -43,7 +43,7 @@ tristate 'Korean charset (CP949, EUC-KR)'CONFIG_NLS_CODEPAGE_949 tristate 'Thai charset (CP874, TIS-620)' CONFIG_NLS_CODEPAGE_874 tristate 'Hebrew charsets (ISO-8859-8, CP1255)' CONFIG_NLS_ISO8859_8 - tristate 'Windows CP1251 (Bulgarian, Belarussian)' CONFIG_NLS_CODEPAGE_1251 + tristate 'Windows CP1251 (Bulgarian, Belarusian)' CONFIG_NLS_CODEPAGE_1251 tristate 'NLS ISO 8859-1 (Latin 1; Western European Languages)' CONFIG_NLS_ISO8859_1 tristate 'NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages)' CONFIG_NLS_ISO8859_2 tristate 'NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish)' CONFIG_NLS_ISO8859_3 @@ -56,7 +56,7 @@ tristate 'NLS ISO 8859-14 (Latin 8; Celtic)' CONFIG_NLS_ISO8859_14 tristate 'NLS ISO 8859-15 (Latin 9; Western European Languages with Euro)' CONFIG_NLS_ISO8859_15 tristate 'NLS KOI8-R (Russian)' CONFIG_NLS_KOI8_R - tristate 'NLS KOI8-U/RU (Ukrainian, Belarussian)' CONFIG_NLS_KOI8_U + tristate 'NLS KOI8-U/RU (Ukrainian, Belarusian)' CONFIG_NLS_KOI8_U tristate 'NLS UTF8' CONFIG_NLS_UTF8 endmenu fi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] (updated) for iso8859-13
On Fri, 11 May 2001 08:24:46 +0200 Andrzej Krzysztofowicz <[EMAIL PROTECTED]> wrote: > "Nerijus Baliunas wrote:" > > -NLS ISO 8859-1 (Latin 1; Western European Languages) > > +NLS ISO 8859-1 (Latin 1; Western European Languages) > > Should'n it be consistent with Config.in ? Probably. Updated patch: --- Configure.helpFri May 11 01:52:15 2001 +++ Configure.help.newFri May 11 14:03:45 2001 @@ -12567,8 +12567,8 @@ cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936, cp949, cp950, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7, - iso8859-8, iso8859-9, iso8859-14, iso8859-15, koi8-r, koi8-ru, - koi8-u, sjis, tis-620, utf8. + iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15, + koi8-r, koi8-ru, koi8-u, sjis, tis-620, utf8. If you specify a wrong value, it will use the built-in NLS; compatible with iso8859-1. @@ -12605,7 +12605,8 @@ DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage that is used - for the Baltic Rim Languages. If unsure, say N. + for the Baltic Rim Languages (Latvian and Lithuanian). If unsure, + say N. Codepage 850 (Europe) CONFIG_NLS_CODEPAGE_850 @@ -12841,7 +12842,7 @@ correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 4 character set which introduces letters for Estonian, Latvian, and - Lithuanian. It is an incomplete predecessor of Latin 6. + Lithuanian. It is an incomplete predecessor of Latin 7. NLS ISO 8859-5 (Cyrillic) CONFIG_NLS_ISO8859_5 @@ -12886,7 +12887,7 @@ set, and it replaces the rarely needed Icelandic letters in Latin 1 with the Turkish ones. Useful in Turkey. -nls iso8859-10 +NLS ISO 8859-10 (Latin 6; Nordic) CONFIG_NLS_ISO8859_10 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12902,7 +12903,8 @@ from the Microsoft FAT file system family or from JOLIET CDROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 7 character - set, which supports modern Baltic languages including Latvian. + set, which supports modern Baltic languages including Latvian + and Lithuanian. NLS ISO 8859-14 (Latin 8; Celtic) CONFIG_NLS_ISO8859_14 @@ -12926,8 +12928,8 @@ Portuguese, Spanish, and Swedish. Latin 9 is an update to Latin 1 (ISO 8859-1) that removes a handful of rarely used characters and instead adds support for Estonian, corrects the - support for French and Finnish, and adds the new Euro character. If - unsure, say Y. + support for French and Finnish, and adds the new Euro character. + If unsure, say Y. NLS KOI8-R (Russian) CONFIG_NLS_KOI8_R - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] for iso8859-13
Patch for Documentation/Configure.help in 2.4.4-ac6. Adds missing iso8859-13 to CONFIG_NLS_DEFAULT and corrects some texts. --- Configure.helpFri May 11 01:52:15 2001 +++ Configure.help.newFri May 11 02:02:53 2001 @@ -12567,8 +12567,8 @@ cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936, cp949, cp950, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7, - iso8859-8, iso8859-9, iso8859-14, iso8859-15, koi8-r, koi8-ru, - koi8-u, sjis, tis-620, utf8. + iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15, + koi8-r, koi8-ru, koi8-u, sjis, tis-620, utf8. If you specify a wrong value, it will use the built-in NLS; compatible with iso8859-1. @@ -12605,7 +12605,8 @@ DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage that is used - for the Baltic Rim Languages. If unsure, say N. + for the Baltic Rim Languages (Latvian and Lithuanian). If unsure, + say N. Codepage 850 (Europe) CONFIG_NLS_CODEPAGE_850 @@ -12804,7 +12805,7 @@ say Y here if you want to include the DOS codepage for Traditional Chinese(Big5). -NLS ISO 8859-1 (Latin 1; Western European Languages) +NLS ISO 8859-1 (Latin 1; Western European Languages) CONFIG_NLS_ISO8859_1 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12815,7 +12816,7 @@ Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, and Swedish. It is also the default for the US. If unsure, say Y. -NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages) +NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages) CONFIG_NLS_ISO8859_2 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12825,7 +12826,7 @@ languages: Czech, German, Hungarian, Polish, Rumanian, Croatian, Slovak, Slovene. -NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish) +NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish) CONFIG_NLS_ISO8859_3 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12834,16 +12835,16 @@ set, which is popular with authors of Esperanto, Galician, Maltese, and Turkish. -NLS ISO 8859-4 (Latin 4; old Baltic charset) +NLS ISO 8859-4 (Latin 4; old Baltic charset) CONFIG_NLS_ISO8859_4 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 4 character set which introduces letters for Estonian, Latvian, and - Lithuanian. It is an incomplete predecessor of Latin 6. + Lithuanian. It is an incomplete predecessor of Latin 7. -NLS ISO 8859-5 (Cyrillic) +NLS ISO 8859-5 (Cyrillic) CONFIG_NLS_ISO8859_5 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12853,7 +12854,7 @@ Macedonian, Russian, Serbian, and Ukrainian. Note that the charset KOI8-R is preferred in Russia. -NLS ISO 8859-6 (Arabic) +NLS ISO 8859-6 (Arabic) CONFIG_NLS_ISO8859_6 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12861,7 +12862,7 @@ input/output character sets. Say Y here for ISO8859-6, the Arabic character set. -NLS ISO 8859-7 (Modern Greek) +NLS ISO 8859-7 (Modern Greek) CONFIG_NLS_ISO8859_7 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12877,7 +12878,7 @@ input/output character sets. Say Y here for ISO8859-8, the Hebrew character set. -NLS ISO 8859-9 (Latin 5; Turkish) +NLS ISO 8859-9 (Latin 5; Turkish) CONFIG_NLS_ISO8859_9 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12886,7 +12887,7 @@ set, and it replaces the rarely needed Icelandic letters in Latin 1 with the Turkish ones. Useful in Turkey. -nls iso8859-10 +NLS ISO 8859-10 (Latin 6; Nordic) CONFIG_NLS_ISO8859_10 If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs @@ -12902,7 +12903,8 @@ from the Microsoft FAT file system family or from JOLIET CDROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 7 character - set, which supports modern Baltic languages including Latvian. + set, which supports modern Baltic languages including
{ DriveReady SeekComplete }
Hello,
Just got a message:
hda: status error: status=0x50 { DriveReady SeekComplete }
hda: no DRQ after issuing MULTWRITE
hda is: QUANTUM FIREBALL CX10.2A, 9787MB w/418kB Cache, CHS=19885/16/63, UDMA(33)
Promise Ultra100 controller.
# hdparm /dev/hda
/dev/hda:
multcount= 8 (on)
I/O support = 3 (32-bit w/sync)
unmaskirq= 1 (on)
using_dma= 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead= 8 (on)
geometry = 1247/255/63, sectors = 20044080, start = 0
# hdparm -i /dev/hda
/dev/hda:
Model=QUANTUM FIREBALL CX10.2A, FwRev=A3F.0B00, SerialNo=133918662657
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
BuffType=DualPortCache, BuffSize=418kB, MaxMultSect=16, MultSect=8
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=20044080
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
AdvancedPM=no
Drive Supports : ATA/ATAPI-4 T13 1153D revision 15 : ATA-1 ATA-2 ATA-3 ATA-4
2.2.19 with ide.2.2.19.03252001.patch.
Is something wrong with disk?
Regards,
Nerijus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
RE: Promise 20267 "working" but no UDMA
> > PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode. How does MASTER mode differ from PCI? I have: PDC20267: IDE controller on PCI bus 00 dev 50 PDC20267: chipset revision 2 PDC20267: not 100% native mode: will probe irqs later PDC20267: ROM enabled at 0xe800 PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. Another question - I have Promise Ultra100 and 2 disks: hda: QUANTUM FIREBALL CX10.2A, 9787MB w/418kB Cache, CHS=19885/16/63, UDMA(33) hdc: IBM-DTLA-305030, 29314MB w/380kB Cache, CHS=59560/16/63, UDMA(100) Why Quantum is shown as UDMA 33 when Promise BIOS shows it as UDMA 66? Why DMA Mode: UDMA 4 in /proc/ide/pdc202xx for IBM disk? Shouldn't it be UDMA 5? Regards, Nerijus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: Need for more ISO8859 codepages?
> About 18 months ago I patched fs/nls/ to include support for the > Celtic character set, ISO8859-14. I notice that there are still gaps > in nls, specifically in ISO8859 codepages 10 to 13. > > The missing codepages are for Nordic/Icelandic (ISO8859-10), Thai > (ISO8859-11), and Baltic Rim (ISO8859-13) languages. I'm still trying > to determine the status of ISO8859-12 at the moment. > > Two questions, really. The general one is whether anyone would find > these codepages useful. If they would, I'm willing to provide the > patches in due course. More specifically, can anyone tell me why > ISO8859-10 (Icelandic etc.) is mentioned in Documentation/Configure.help > whilst nls_iso8859-10.c is missing from the fs/nls directory? Hello, ISO8859-13 is used in Latvia and Lithuania, so it would be useful. I don't think ISO8859-12 is really used, it is reserved for Devanagari (Indian), but I think they will use unicode eventually... So it would be nice to add support for ISO8859-10 and ISO8859-13 at least. Regards, Nerijus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: bread in fat_access failed
> Nov 28 01:00:28 sargis kernel: bread in fat_access failed > Nov 28 01:00:28 sargis kernel: attempt to access beyond end of device > Nov 28 01:00:28 sargis kernel: 02:00: rw=0, want=5, limit=4 > Nov 28 01:00:28 sargis kernel: dev 02:00 blksize=512 blocknr=9 > sector=9 size=512 > count=1 > > What do they mean? Problems with hdd? Sorry, it seems floppy was removed when still mounted. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
bread in fat_access failed
Hello, I get a lot of such messages: Nov 28 01:00:28 sargis kernel: bread in fat_access failed Nov 28 01:00:28 sargis kernel: attempt to access beyond end of device Nov 28 01:00:28 sargis kernel: 02:00: rw=0, want=5, limit=4 Nov 28 01:00:28 sargis kernel: dev 02:00 blksize=512 blocknr=9 sector=9 size=512 count=1 What do they mean? Problems with hdd? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: VFAT problem
> > I have discovered a problem with the Linux 2.4.0 VFAT filesystem. Short > > names that have mixed case do not retain their case on the VFAT > > filesystem. This has mostly worked in the past on 2.1.x, 2.2.x, 2.3.x > > Is it supposed to? My MS-DOS file system(s) always have shown files > with their names mapped to lower case. The MS-DOS files all have > upper case file-names and always will. It's only Windows file-systems, > starting with FAT-32, then NT-FS that have upper/lower case file-names, > and container-files for "Very Long File Names with spaces and a letter to > the president" Read the subject - it is VFAT, not MSDOS. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
