From: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Status of loopback
Date: Wed, 07 Feb 2001 13:52:28 -0500 [thread overview]
Message-ID: <3A81996C.3060600@lycosmail.com> (raw)
I'm curious if the loopback block driver is stable enough yet to, say
put a loopback file on a vfat partition.
I have 2 HDs, one windoze, one linux. I can't be sure I won't need to
keep the vfat partition, so I can't just wipe it out. However, it
currently has more space on it than my ext2 disc. (200 vs 500 MB)
The question therefore is, is it safe to do this yet?? I want to move
some stuff to the other disc, but don't want the troubles of
permissions. (BTW, IIRC umsdos doesn't to Win9x LFNs, right. Otherwise I
could remount umsdos [assuming that it works again. It was broken
sometime around 2.3.20]).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-07 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 18:52 Adam Schrotenboer [this message]
2001-02-08 11:44 ` Status of loopback Marc Mutz
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=3A81996C.3060600@lycosmail.com \
--to=ajschrotenboer@lycosmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox