Bug 172820 - setup - "unknown" file system hfsplus
Summary: setup - "unknown" file system hfsplus
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: setup
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: FC5Target
TreeView+ depends on / blocked
 
Reported: 2005-11-10 01:30 UTC by Michal Jaegermann
Modified: 2015-03-05 01:15 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-01-24 19:08:45 UTC


Attachments (Terms of Use)

Description Michal Jaegermann 2005-11-10 01:30:52 UTC
Description of problem:

I happen to have here a CD written in a default format on a Mac OSX machine.
Dropping it into a drive does not result, contrary to expectations, in
an automatic mount.  A bit of digging in a mount manpage how an 'auto' file
type really works (not 'autofs'!!) reveals that mount tries filesystems listed
in '/etc/filesystems' and a content of this file currently looks like this:

ext3
ext2
nodev proc
nodev devpts
iso9660
vfat
hfs

The required filesystem happens to be 'hfsplus' and adding it at the bottom
of this list does result in an automatic mount on an insertion of CD and
after that 'hfsplus' shows up, not that surprisingly, in an output of
'cat /proc/filesystems' too.  Currently this does not mean that nautilus is
noticing a new mount but this looks like an unrelated breakage.

I would suggest that 'hfsplus' should be in '/etc/filesystems' list from
the very beginning (especially that 'man mount' fails to mention it, see
bug #172817).

BTW - 'man mount' claims that '/etc/filesystems' entries marked 'nodev' are
ignored so why they are there is not clear.  Something else looks at this file?

Version-Release number of selected component (if applicable):
setup-2.5.47-1.1
but this actually applies equally well to FC3 and FC4.

Comment 1 Phil Knirsch 2006-01-24 19:08:45 UTC
Added in CVS, will be in next build.

Read ya, Phil


Note You need to log in before you can comment on or make changes to this bug.