From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: long file names
Date: Wed, 12 Jun 2002 11:32:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0206121131380.239-100000@igueths> (raw)
In-Reply-To: <20020612025616.WBBG26462.priv-edtnes28.telusplanet.net@a7a42593>
Raul,
What kernel are you running? I'm just asking because the fat/vfat
modules are broken under 2.4.18.
Explorer has caused a general protection fault in module kernel32.dll. I'm sick of Winblows!
On Tue, 11 Jun 2002, Tyler Spivey wrote:
> try mounting it with -t vfat.
> i haven't tried, and hope i never will try to mount a widnows partition.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Spivey
` Igor Gueths [this message]
` Gregory Nowak
` Raul A. Gallegos
` jwantz
` Igor Gueths
` jwantz
` cd burning randy turner
` Gregory Nowak
` randy turner
` Igor Gueths
` Igor Gueths
` randy turner
` Igor Gueths
` randy turner
` Igor Gueths
` long file names Steve Holmes
` Janina Sajka
` Toby Fisher
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=Pine.LNX.4.44.0206121131380.239-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).