From: Jeremy White <jwhite@codeweavers.com>
To: linux-kernel@vger.kernel.org
Subject: isofs unhide option: troubles with Wine
Date: 24 May 2002 23:30:29 -0500 [thread overview]
Message-ID: <1022301029.2443.28.camel@jwhiteh> (raw)
Greetings,
When installing Microsoft Office with Wine, we find that some
MS CDs have certain files marked as hidden on the CD.
With the default isofs mount options, these files are
completely inaccessible. (Relevant code is in
fs/isofs/namei.c, and dir.c; search for unhide).
You're forced to remount the CD with the -unhide option
to make these files visible.
Now, forgive me if I've overlooked TFM, but I did not
find any discussion of the unhide option in the archives
I could search.
Further, imho, the unhide code is incorrectly implemented
in Linux.
The use of the 'hide' bit in Windows has no good parallel in
Linux. The current implementation treats a hidden file
as if it didn't exist at all, there is no possible way
a user space program can see that file. In Windows, the
file just is hidden from 'normal' programs, you can still
get to the file if you work hard enough.
Further, I hypothesize (perhaps wrongly) that the only use
of this hidden bit is on Windows CDs, and largely on MS
Office CDs, and so I think it is reasonable for me to
call for a change. (Understand, I'm trying to help
very basic users to use MS Office; for them to have to
su to root, umount, and then mount -o unhide, is a pretty tough thing
to ask. See the following article to see why I'm so upset about this:
http://biz.yahoo.com/fo/020523/linux_gets_friendlier_1.html)
Unfortunately, I don't have a strong feeling for what the
'right' solution is. I see several options:
1. Invert the logic of the option, make it 'hide' instead
of unhide, and so unhide is the default.
2. Make it possible to set this mount option from user
space (I don't like this, but it would get me around
the problem).
3. Make it so that isofs/dir.c still strips out hidden
files, but enable isofs/namei.c to return a hidden file that
is opened directly by name.
I am willing to submit a patch to implement the appropriate solution.
Comments and opinions are greatly appreciated; please copy me directly
though, as I am not subscribed.
Thanks,
Jeremy
next reply other threads:[~2002-05-25 4:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 4:30 Jeremy White [this message]
2002-05-25 13:46 ` isofs unhide option: troubles with Wine Olaf Dietsche
2002-05-25 13:49 ` Jeremy White
2002-05-25 14:01 ` Joseph Mathewson
2002-05-25 14:23 ` Jeremy White
2002-06-10 3:12 ` Francois Gouget
2002-06-10 11:52 ` Thunder from the hill
2002-06-10 12:38 ` Guest section DW
2002-05-25 15:50 ` Alan Cox
2002-06-03 17:05 ` Jeremy White
2002-06-03 18:06 ` Thunder from the hill
2002-06-03 18:40 ` H. Peter Anvin
2002-06-03 19:40 ` Thunder from the hill
2002-06-03 19:43 ` H. Peter Anvin
2002-06-04 0:23 ` Alan Cox
2002-06-19 2:36 ` Jeremy White
2002-05-25 14:18 ` Ruth Ivimey-Cook
2002-05-25 14:25 ` Jeremy White
2002-05-25 19:31 ` H. Peter Anvin
2002-05-25 19:40 ` Linus Torvalds
2002-05-25 20:31 ` H. Peter Anvin
2002-05-25 21:20 ` Lionel Bouton
2002-05-25 21:51 ` H. Peter Anvin
2002-05-25 21:07 ` Lionel Bouton
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 17:04 Andries.Brouwer
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=1022301029.2443.28.camel@jwhiteh \
--to=jwhite@codeweavers.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