General discussion

  • Creator
    Topic
  • #2189114

    wanted more support in this How much more code would it take ?

    Locked

    by lawrephord ·

    to make 4000 characters filename support ???????

    .\” $NetBSD: mount_msdos.8,v 1.31 2005/01/31 05:19:19 erh Exp $
    .\”
    .\” Copyright (c) 1993, 1994 Christopher G. Demetriou
    .\” All rights reserved.
    .\”
    .\” 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 for the
    .\” NetBSD Project. See http://www.NetBSD.org/ for
    .\” information about NetBSD.
    .\” 4. The name of the author may not be used to endorse or promote products
    .\” derived from this software without specific prior written permission.
    .\”
    .\” THIS SOFTWARE IS PROVIDED BY THE AUTHOR “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 AUTHOR 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.
    .\”
    .\” <>
    .\”
    .Dd September 7, 2003
    .Dt MOUNT_MSDOS 8
    .Os
    .Sh NAME
    .Nm mount_msdos
    .Nd mount an MS-DOS file system
    .Sh SYNOPSIS
    .Nm
    .Op Fl 9Gls
    .Op Fl g Ar gid
    .Op Fl M Ar mask
    .Op Fl m Ar mask
    .Op Fl o Ar options
    .Op Fl t Ar gmtoff
    .Op Fl u Ar uid
    .Pa special
    .Pa node
    .Sh DESCRIPTION
    The
    .Nm
    command attaches the MS-DOS filesystem residing on
    the device
    .Pa special
    to the global filesystem namespace at the location
    indicated by
    .Pa node .
    Both
    .Ar special
    and
    .Ar node
    are converted to absolute paths before use.
    This command is normally executed by
    .Xr mount 8
    at boot time, but can be used by any user to mount an
    MS-DOS file system on any directory that they own (provided,
    of course, that they have appropriate access to the device that
    contains the file system).
    .Pp
    Support for FAT16 and VFAT32 as well as long file names is available.
    .Pp
    The options are as follows:
    .Bl -tag -width XoXoptionsXX
    .It Fl 9
    Ignore the special Win’95 directory entries even
    if deleting or renaming a file.
    This forces
    .Fl s .
    .It Fl G
    This option causes the filesystem to be interpreted as an Atari-Gemdos
    filesystem.
    The differences to the MSDOS filesystem are minimal and
    limited to the boot block.
    This option enforces
    .Fl s .
    .It Fl g Ar gid
    Set the group of the files in the file system to
    .Ar gid .
    The default group is the group of the directory
    on which the file system is being mounted.
    .It Fl l
    Force listing and generation of
    Win’95 long filenames
    and separate creation/modification/access dates.
    .Pp
    If neither
    .Fl s
    nor
    .Fl l
    are given,
    .Nm
    searches the root directory of the filesystem to
    be mounted for any existing Win’95 long filenames.
    If no such entries are found,
    .Fl s
    is the default.
    Otherwise
    .Fl l
    is assumed.
    .It Fl M Ar mask
    Specify the maximum file permissions for directories
    in the file system. The value of
    .Fl m
    is used if it is supplied and
    .Fl M
    is omitted.
    .It Fl m Ar mask
    Specify the maximum file permissions for files
    in the file system.
    (For example, a mask of
    .Li 755
    specifies that, by default, the owner should have
    read, write, and execute permissions for files, but
    others should only have read and execute permissions.
    See
    .Xr chmod 1
    for more information about octal file modes.)
    Only the nine low-order bits of
    .Ar mask
    are used. The value of
    .Fl M
    is used if it is supplied and
    .Fl m
    is omitted.
    The default mask is taken from the
    directory on which the file system is being mounted.
    .It Fl o Ar options
    Use the specified mount
    .Ar options ,
    as described in
    .Xr mount 8 .
    .It Fl s
    Force behaviour to
    ignore and not generate Win’95 long filenames.
    See also
    .Fl l .
    .It Fl t Ar gmtoff
    Set the time zone offset (in seconds) from UTC to
    .Ar gmtoff ,
    with positive values indicating east of the Prime Meridian.
    If not set, the user’s current time zone will be used.
    .It Fl u Ar uid
    Set the owner of the files in the file system to
    .Ar uid .
    The default owner is the owner of the directory
    on which the file system is being mounted.
    .El
    .Sh EXAMPLES
    To remove the ‘execute’ permission bit for all files, but still keep
    directories searchable, use:
    .Bl -item -offset indent
    .It
    mount_msdos -m 0644 -M 0755 /dev/wd0e /msdos
    .El
    .Sh SEE ALSO
    .Xr mount 2 ,
    .Xr unmount 2 ,
    .Xr fstab 5 ,
    .Xr mount 8
    .Sh HISTORY
    The
    .Nm
    utility first appeared in
    .Nx 0.9 .
    Its predecessor, the
    .Ic mount_pcfs
    utility appeared in
    .Nx 0.8 ,
    and was abandoned in favor
    of the more aptly-named
    .Nm .
    .Sh BUGS
    Compressed partitions are not supported.
    .Pp
    The use of the
    .Fl 9
    flag could result in damaged filesystems,
    albeit the damage is in part taken care of by
    procedures similar to the ones used in Win’95.
    .Pp
    The default handling for
    .Fl s
    and
    .Fl l
    will result in empty filesystems to be populated
    with short filenames only.
    To generate long filenames
    on empty DOS filesystems use
    .Fl l .

All Comments

  • Author
    Replies
    • #3053613

      to begin

      by jaqui ·

      In reply to wanted more support in this How much more code would it take ?

      you have to use a filesystem that allows long filenames.
      dos doesn’t
      fat16 and fat32 have that antique 8.3 limit.

      windows itself stores longer filenames in a file, not on the filesystem. the longer the name, you get the folder / filenames with the ~1 ending.

Viewing 0 reply threads