Import 4.4BSD-Lite2 onto the vendor branch, note that in the kernel, all

files are off the vendor branch, so this should not change anything.

A "U" marker generally means that the file was not changed in between
the 4.4Lite and Lite-2 releases, and does not need a merge.  "C" generally
means that there was a change.
[note, new file: cd9660_mount.h]
This commit is contained in:
Peter Wemm 1996-03-11 19:20:10 +00:00
parent 82f8a29f23
commit 186242c540
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=14553
2 changed files with 54 additions and 11 deletions

View file

@ -3,20 +3,12 @@
them back. It looks like a seperate (but very similar) lookup routine them back. It looks like a seperate (but very similar) lookup routine
will be needed due to the associated file stuff. will be needed due to the associated file stuff.
2. Make filesystem exportable. This comes for free if stacked with UFS. 2. It would be nice to be able to use the vfs_cluster code.
Otherwise, the ufs_export routines need to be elevated to vfs_* routines.
[ DONE - hibler ]
3. If it can't be merged with UFS, at least get them in sync. For example,
it could use the same style hashing routines as in ufs/ufs_ihash.c
4. It would be nice to be able to use the vfs_cluster code.
Unfortunately, if the logical block size is smaller than the page size, Unfortunately, if the logical block size is smaller than the page size,
it won't work. Also, if throughtput is relatively constant for any it won't work. Also, if throughtput is relatively constant for any
block size (as it is for the HP drive--150kbs) then clustering may not block size (as it is for the HP drive--150kbs) then clustering may not
buy much (or may even hurt when vfs_cluster comes up with a large sync buy much (or may even hurt when vfs_cluster comes up with a large sync
cluster). cluster).
5. Seems like there should be a "notrans" or some such mount option to show 3. Seems like there should be a "notrans" or some such mount option to show
filenames as they really are without lower-casing, stripping of version filenames as they really are without lower-casing. Does this make sense?
numbers, etc. Does this make sense?

View file

@ -0,0 +1,51 @@
/*
* Copyright (c) 1995
* The Regents of the University of California. All rights reserved.
*
* This code is derived from software contributed to Berkeley
* by Pace Willisson (pace@blitz.com). The Rock Ridge Extension
* Support code is derived from software contributed to Berkeley
* by Atsushi Murai (amurai@spec.co.jp).
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This product includes software developed by the University of
* California, Berkeley and its contributors.
* 4. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* @(#)cd9660_mount.h 8.1 (Berkeley) 5/24/95
*/
/*
* Arguments to mount ISO 9660 filesystems.
*/
struct iso_args {
char *fspec; /* block special device to mount */
struct export_args export; /* network export info */
int flags; /* mounting flags, see below */
};
#define ISOFSMNT_NORRIP 0x00000001 /* disable Rock Ridge Ext.*/
#define ISOFSMNT_GENS 0x00000002 /* enable generation numbers */
#define ISOFSMNT_EXTATT 0x00000004 /* enable extended attributes */