Print this page
11622 clean up rarer mandoc lint warnings
   1 '\" te
   2 .\" Copyright (c) 2007 Sun Microsystems, Inc. All Rights Reserved.
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH PCFS 7FS "Nov 6, 2007"
   7 .SH NAME
   8 pcfs \- FAT formatted file system
   9 .SH SYNOPSIS
  10 .LP
  11 .nf
  12 #include <sys/param.h>
  13 #include <sys/mount.h>
  14 #include <sys/fs/pc_fs.h>
  15 
  16 \fBint\fR \fBmount\fR(\fBconst char *\fR\fIspec\fR,
  17      \fBconst char *\fR \fIdir\fR, \fBint\fR  \fImflag\fR,
  18      \fB"pcfs", NULL, 0,\fR \fBchar *\fR\fIoptptr\fR,
  19      \fBint\fR \fIoptlen\fR);
  20 .fi
  21 
  22 .SH DESCRIPTION
  23 .sp
  24 .LP
  25 \fBpcfs\fR is a file system type that enables direct access to files on
  26 \fBFAT\fR formatted disks from within the SunOS operating system.
  27 .sp
  28 .LP
  29 Once mounted, \fBpcfs\fR provides standard SunOS file operations and semantics.
  30 Using \fBpcfs\fR, you can create, delete, read, and write files on a \fBFAT\fR
  31 formatted disk. You can also create and delete directories and list files in a
  32 directory.
  33 .sp
  34 .LP
  35 \fBpcfs\fR supports FAT12 (floppies) and FAT16 and FAT32 file systems.
  36 .sp
  37 .LP
  38 \fBpcfs\fR file systems can be force umounted using the \fB-f\fR argument to
  39 \fBumount\fR(1M).
  40 .sp
  41 .LP
  42 The \fBpcfs\fR file system contained on the block special file identified by
  43 \fIspec\fR is mounted on the directory identified by \fIdir\fR. \fIspec\fR and
  44 \fIdir\fR are pointers to pathnames. \fImflag\fR specifies the \fBmount\fR


  59 option, as described in \fBmount_pcfs\fR(1M).
  60 .sp
  61 .LP
  62 Timestamps on FAT formatted media are recorded in local time. If the recording
  63 and  receiving systems use different timezones, the representation of
  64 timestamps shown on the two systems for the same medium might vary. To correct
  65 this,  \fBpcfs\fR  provides a  timezone mount option to force  interpretation
  66 of timestamps as read from a FAT formatted medium in a given  timezone (that of
  67 the recorder). By default, the local timezone of the  receiver is used. See
  68 \fBmount_pcfs\fR(1M) for details.
  69 .sp
  70 .LP
  71 The root directory of a FAT formatted medium has no timestamps and \fBpcfs\fR
  72 returns the time when the mount was done as timestamp  for the root of the
  73 filesystem.
  74 .sp
  75 .LP
  76 The FAT filesystem doesn't support multiple links. As a result, the link count
  77 for all files and directories in \fBpcfs\fR is hard-coded as "1."
  78 .SS "Mounting File Systems"
  79 .sp
  80 .LP
  81 Use the following command to mount \fBpcfs\fR from diskette:
  82 .sp
  83 .in +2
  84 .nf
  85 mount \fB-F\fR pcfs \fIdevice-special\fR \fIdirectory-name\fR
  86 .fi
  87 .in -2
  88 .sp
  89 
  90 .sp
  91 .LP
  92 You can use:
  93 .sp
  94 .in +2
  95 .nf
  96 mount \fIdirectory-name\fR
  97 .fi
  98 .in -2
  99 .sp
 100 


 195 .in -2
 196 .sp
 197 
 198 .sp
 199 .LP
 200 If Volume Management is running, run \fBvolcheck\fR(1) to automatically mount
 201 the floppy and some removable disks.
 202 .sp
 203 .LP
 204 To mount a \fBPCMCIA\fR pseudo-floppy memory card, with Volume Management not
 205 running (or not managing the \fBPCMCIA\fR media), use:
 206 .sp
 207 .in +2
 208 .nf
 209 mount \fB-F\fR pcfs /dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRs\fIN\fR /pcfs
 210 .fi
 211 .in -2
 212 .sp
 213 
 214 .SS "Conventions"
 215 .sp
 216 .LP
 217 Files and directories created through \fBpcfs\fR must comply with either the
 218 \fBFAT\fR short file name convention or the long file name convention
 219 introduced with Windows 95. The \fBFAT\fR short file name convention is of the
 220 form \fIfilename\fR[.\fIext\fR], where \fIfilename\fR generally consists of
 221 from one to eight upper-case characters, while the optional \fIext\fR consists
 222 of from one to three upper-case characters.
 223 .sp
 224 .LP
 225 The long file name convention is much closer to Solaris file names. A long file
 226 name can consist of any characters valid in a short file name, lowercase
 227 letters, non-leading spaces, the characters \fB+,;=[]\fR, any number of
 228 periods, and can be up to 255 characters long. Long file names have an
 229 associated short file name for systems that do not support long file names
 230 (including earlier releases of Solaris). The short file name is not visible if
 231 the system recognizes long file names. \fBpcfs\fR generates a unique short name
 232 automatically when creating a long file name.
 233 .sp
 234 .LP
 235 Given a long file name such as \fBThis is a really long filename.TXT\fR, the
 236 short file name will generally be of the form \fBTHISIS~\fR\fIN\fR\fB\&.TXT\fR,


 243 .LP
 244 When creating a file name, \fBpcfs\fR creates a short file name if it fits the
 245 \fBFAT\fR short file name format, otherwise it creates a long file name. This
 246 is because long file names take more directory space. Because the root
 247 directory of a \fBpcfs\fR file system is fixed size, long file names in the
 248 root directory should be avoided if possible.
 249 .sp
 250 .LP
 251 When displaying file names, \fBpcfs\fR shows them exactly as they are on the
 252 media. This means that short names are displayed as uppercase and long file
 253 names retain their case. Earlier versions of \fBpcfs\fR folded all names to
 254 lowercase, which can be forced with the \fBPCFS_MNT_FOLDCASE\fR mount option.
 255 All file name searches within \fBpcfs\fR, however, are treated as if they were
 256 uppercase, so \fBreadme.txt\fR and \fBReAdMe.TxT\fR refer to the same file.
 257 .sp
 258 .LP
 259 To format a diskette or a \fBPCMCIA\fR pseudo-floppy memory card in \fBFAT\fR
 260 format in the SunOS system, use either the \fBfdformat\fR \fB-d\fR or the
 261 \fBDOS\fR \fBFORMAT\fR command.
 262 .SS "Boot Partitions"
 263 .sp
 264 .LP
 265 On x86 systems, hard drives may contain an \fBfdisk\fR partition reserved for
 266 the Solaris boot utilities. These partitions are special instances of
 267 \fBpcfs\fR. You can mount an x86 boot partition with the command:
 268 .sp
 269 .in +2
 270 .nf
 271 mount \fB-F\fR pcfs \fIdevice-special\fR:boot \fIdirectory-name\fR
 272 .fi
 273 .in -2
 274 .sp
 275 
 276 .sp
 277 .LP
 278 or you can use:
 279 .sp
 280 .in +2
 281 .nf
 282 \fBmount \fIdirectory-name\fR\fR
 283 .fi
 284 .in -2


 290 .sp
 291 .in +2
 292 .nf
 293 \fIdevice-special\fR:boot \(mi \fIdirectory-name\fR pcfs \(mi no rw
 294 .fi
 295 .in -2
 296 .sp
 297 
 298 .sp
 299 .LP
 300 \fIdevice-special\fR specifies the special block device file for the entire
 301 hard disk (\fB/dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRp0\fR)
 302 .sp
 303 .LP
 304 \fIdirectory-name\fR specifies the location where the file system is mounted.
 305 .sp
 306 .LP
 307 All files on a boot partition are owned by super-user. Only the super-user may
 308 create, delete, or modify files on a boot partition.
 309 .SH EXAMPLES
 310 .LP
 311 \fBExample 1 \fRSample Displays of File Names
 312 .sp
 313 .LP
 314 If you copy a file \fBfinancial.data\fR from a UNIX file system to \fBpcfs\fR,
 315 it displays as \fBfinancial.data\fR in \fBpcfs\fR, but may show up as
 316 \fBFINANC~1.DAT\fR in systems that do not support long file names.
 317 
 318 .sp
 319 .LP
 320 The following are legal long file names. They are also \fBillegal\fR short file
 321 names:
 322 
 323 .br
 324 .in +2
 325 \fBtest.sh.orig\fR
 326 .in -2
 327 .br
 328 .in +2
 329 \fBdata+\fR
 330 .in -2
 331 .br
 332 .in +2
 333 \fB\&.login\fR
 334 .in -2
 335 .sp
 336 .LP
 337 Other systems that do not support long file names may see:
 338 
 339 .br
 340 .in +2
 341 \fBTESTSH~1.ORI\fR
 342 .in -2
 343 .br
 344 .in +2
 345 \fBDATA~1\fR
 346 .in -2
 347 .br
 348 .in +2
 349 \fBLOGIN~1\fR
 350 .in -2
 351 .sp
 352 .LP
 353 The short file name is generated from the initial characters of the long file
 354 name, so differentiate names in the first few characters. For example, these
 355 names:
 356 
 357 .br
 358 .in +2
 359 \fBWorkReport.January.Data\fR
 360 .in -2
 361 .br
 362 .in +2
 363 \fBWorkReport.February.Data\fR
 364 .in -2
 365 .br
 366 .in +2
 367 \fBWorkReport.March.Data\fR
 368 .in -2
 369 .sp
 370 .LP
 371 result in these short names, which are not distinguishable:
 372 
 373 .br
 374 .in +2
 375 \fBWORKRE~1.DAT\fR
 376 .in -2
 377 .br
 378 .in +2
 379 \fBWORKRE~2.DAT\fR
 380 .in -2
 381 .br
 382 .in +2
 383 \fBWORKRE~13.DAT\fR
 384 .in -2
 385 .sp
 386 .LP
 387 These names, however:
 388 
 389 .br
 390 .in +2
 391 \fBJanuary.WorkReport.Data\fR
 392 .in -2
 393 .br
 394 .in +2
 395 \fBFebruary.WorkReport.Data\fR
 396 .in -2
 397 .br
 398 .in +2
 399 \fBMarch.WorkReport.Data\fR
 400 .in -2
 401 .sp
 402 .LP
 403 result in the more descriptive short names:
 404 
 405 .br
 406 .in +2
 407 \fBJANUAR~1.DAT\fR
 408 .in -2
 409 .br
 410 .in +2
 411 \fBFEBRUA~1.DAT\fR
 412 .in -2
 413 .br
 414 .in +2
 415 \fBMARCHW~1.DAT\fR
 416 .in -2
 417 .SH FILES
 418 .sp
 419 .ne 2
 420 .na
 421 \fB\fB/usr/lib/fs/pcfs/mount\fR\fR
 422 .ad
 423 .RS 26n
 424 \fBpcfs\fR \fBmount\fR command
 425 .RE
 426 
 427 .sp
 428 .ne 2
 429 .na
 430 \fB\fB/usr/kernel/fs/pcfs\fR\fR
 431 .ad
 432 .RS 26n
 433 32-bit kernel module
 434 .RE
 435 
 436 .SH ENVIRONMENT VARIABLES
 437 .sp
 438 .LP
 439 See \fBenviron\fR(5) for descriptions of the following environment variables
 440 for the current locale setting: LANG, LC_ALL, LC_CTYPE, and LC_COLLATE.
 441 .SH SEE ALSO
 442 .sp
 443 .LP
 444 \fBchgrp\fR(1), \fBchown\fR(1), \fBdos2unix\fR(1), \fBeject\fR(1),
 445 \fBfdformat\fR(1), \fBunix2dos\fR(1), \fBvolcheck\fR(1), \fBmount\fR(1M),
 446 \fBmount_pcfs\fR(1M), \fBumount\fR(1M), \fBctime\fR(3C), \fBvfstab\fR(4),
 447 \fBenviron\fR(5), \fBpcmem\fR(7D)
 448 .SH WARNINGS
 449 .sp
 450 .LP
 451 Do not physically eject a \fBFAT\fR floppy while the device is mounted as
 452 \fBpcfs\fR. If Volume Management is managing a device, use the \fBeject\fR(1)
 453 command before physically removing media.
 454 .sp
 455 .LP
 456 When mounting \fBpcfs\fR on a hard disk, make sure the first block on that
 457 device contains a valid \fBfdisk\fR partition table.
 458 .sp
 459 .LP
 460 Because \fBpcfs\fR has no provision for handling owner-IDs or group-IDs on
 461 files, \fBchown\fR(1) or \fBchgrp\fR(1) may generate various errors. This is a
 462 limitation of \fBpcfs\fR, but it should not cause problems other than error
 463 messages.
 464 .SH NOTES
 465 .sp
 466 .LP
 467 Only the following characters are allowed in \fBpcfs\fR short file names and
 468 extensions:
 469 .br
 470 .in +2
 471 \fB0-9\fR
 472 .in -2
 473 .br
 474 .in +2
 475 \fBA-Z\fR
 476 .in -2
 477 .br
 478 .in +2
 479 \fB$#&@!%()-{}<>`_^~|'\fR
 480 .in -2
 481 .sp
 482 .LP
 483 SunOS and \fBFAT\fR use different character sets and have different
 484 requirements for the text file format. Use the \fBdos2unix\fR(1) and
 485 \fBunix2dos\fR(1) commands to convert files between them.
 486 .sp


 491 should not be used as the format for a regular local storage. Instead, use
 492 \fBufs\fR for local storage within the SunOS system.
 493 .sp
 494 .LP
 495 Although long file names can contain spaces (just as in UNIX file names), some
 496 utilities may be confused by them.
 497 .sp
 498 .LP
 499 This implementation of \fBpcfs\fR conforms to the behavior exhibited by Windows
 500 95 version 4.00.950.
 501 .sp
 502 .LP
 503 When \fBpcfs\fR encounters long file names with non-ASCII characters, it
 504 converts such long file names in Unicode scalar values into UTF-8 encoded
 505 filenames so that they are legible and usable with any of Solaris UTF-8
 506 locales. In the same context, when new file names with non-ASCII characters are
 507 created, \fBpcfs\fR expects that such file names are in UTF-8. This feature
 508 increases the interoperability of \fBpcfs\fR on Solaris with other operating
 509 systems.
 510 .SH BUGS
 511 .sp
 512 .LP
 513 \fBpcfs\fR should handle the disk change condition in the same way that
 514 \fBDOS\fR does, so you do not need to unmount the file system to change
 515 floppies.
   1 '\" te
   2 .\" Copyright (c) 2007 Sun Microsystems, Inc. All Rights Reserved.
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH PCFS 7FS "Nov 6, 2007"
   7 .SH NAME
   8 pcfs \- FAT formatted file system
   9 .SH SYNOPSIS

  10 .nf
  11 #include <sys/param.h>
  12 #include <sys/mount.h>
  13 #include <sys/fs/pc_fs.h>
  14 
  15 \fBint\fR \fBmount\fR(\fBconst char *\fR\fIspec\fR,
  16      \fBconst char *\fR \fIdir\fR, \fBint\fR  \fImflag\fR,
  17      \fB"pcfs", NULL, 0,\fR \fBchar *\fR\fIoptptr\fR,
  18      \fBint\fR \fIoptlen\fR);
  19 .fi
  20 
  21 .SH DESCRIPTION


  22 \fBpcfs\fR is a file system type that enables direct access to files on
  23 \fBFAT\fR formatted disks from within the SunOS operating system.
  24 .sp
  25 .LP
  26 Once mounted, \fBpcfs\fR provides standard SunOS file operations and semantics.
  27 Using \fBpcfs\fR, you can create, delete, read, and write files on a \fBFAT\fR
  28 formatted disk. You can also create and delete directories and list files in a
  29 directory.
  30 .sp
  31 .LP
  32 \fBpcfs\fR supports FAT12 (floppies) and FAT16 and FAT32 file systems.
  33 .sp
  34 .LP
  35 \fBpcfs\fR file systems can be force umounted using the \fB-f\fR argument to
  36 \fBumount\fR(1M).
  37 .sp
  38 .LP
  39 The \fBpcfs\fR file system contained on the block special file identified by
  40 \fIspec\fR is mounted on the directory identified by \fIdir\fR. \fIspec\fR and
  41 \fIdir\fR are pointers to pathnames. \fImflag\fR specifies the \fBmount\fR


  56 option, as described in \fBmount_pcfs\fR(1M).
  57 .sp
  58 .LP
  59 Timestamps on FAT formatted media are recorded in local time. If the recording
  60 and  receiving systems use different timezones, the representation of
  61 timestamps shown on the two systems for the same medium might vary. To correct
  62 this,  \fBpcfs\fR  provides a  timezone mount option to force  interpretation
  63 of timestamps as read from a FAT formatted medium in a given  timezone (that of
  64 the recorder). By default, the local timezone of the  receiver is used. See
  65 \fBmount_pcfs\fR(1M) for details.
  66 .sp
  67 .LP
  68 The root directory of a FAT formatted medium has no timestamps and \fBpcfs\fR
  69 returns the time when the mount was done as timestamp  for the root of the
  70 filesystem.
  71 .sp
  72 .LP
  73 The FAT filesystem doesn't support multiple links. As a result, the link count
  74 for all files and directories in \fBpcfs\fR is hard-coded as "1."
  75 .SS "Mounting File Systems"


  76 Use the following command to mount \fBpcfs\fR from diskette:
  77 .sp
  78 .in +2
  79 .nf
  80 mount \fB-F\fR pcfs \fIdevice-special\fR \fIdirectory-name\fR
  81 .fi
  82 .in -2
  83 .sp
  84 
  85 .sp
  86 .LP
  87 You can use:
  88 .sp
  89 .in +2
  90 .nf
  91 mount \fIdirectory-name\fR
  92 .fi
  93 .in -2
  94 .sp
  95 


 190 .in -2
 191 .sp
 192 
 193 .sp
 194 .LP
 195 If Volume Management is running, run \fBvolcheck\fR(1) to automatically mount
 196 the floppy and some removable disks.
 197 .sp
 198 .LP
 199 To mount a \fBPCMCIA\fR pseudo-floppy memory card, with Volume Management not
 200 running (or not managing the \fBPCMCIA\fR media), use:
 201 .sp
 202 .in +2
 203 .nf
 204 mount \fB-F\fR pcfs /dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRs\fIN\fR /pcfs
 205 .fi
 206 .in -2
 207 .sp
 208 
 209 .SS "Conventions"


 210 Files and directories created through \fBpcfs\fR must comply with either the
 211 \fBFAT\fR short file name convention or the long file name convention
 212 introduced with Windows 95. The \fBFAT\fR short file name convention is of the
 213 form \fIfilename\fR[.\fIext\fR], where \fIfilename\fR generally consists of
 214 from one to eight upper-case characters, while the optional \fIext\fR consists
 215 of from one to three upper-case characters.
 216 .sp
 217 .LP
 218 The long file name convention is much closer to Solaris file names. A long file
 219 name can consist of any characters valid in a short file name, lowercase
 220 letters, non-leading spaces, the characters \fB+,;=[]\fR, any number of
 221 periods, and can be up to 255 characters long. Long file names have an
 222 associated short file name for systems that do not support long file names
 223 (including earlier releases of Solaris). The short file name is not visible if
 224 the system recognizes long file names. \fBpcfs\fR generates a unique short name
 225 automatically when creating a long file name.
 226 .sp
 227 .LP
 228 Given a long file name such as \fBThis is a really long filename.TXT\fR, the
 229 short file name will generally be of the form \fBTHISIS~\fR\fIN\fR\fB\&.TXT\fR,


 236 .LP
 237 When creating a file name, \fBpcfs\fR creates a short file name if it fits the
 238 \fBFAT\fR short file name format, otherwise it creates a long file name. This
 239 is because long file names take more directory space. Because the root
 240 directory of a \fBpcfs\fR file system is fixed size, long file names in the
 241 root directory should be avoided if possible.
 242 .sp
 243 .LP
 244 When displaying file names, \fBpcfs\fR shows them exactly as they are on the
 245 media. This means that short names are displayed as uppercase and long file
 246 names retain their case. Earlier versions of \fBpcfs\fR folded all names to
 247 lowercase, which can be forced with the \fBPCFS_MNT_FOLDCASE\fR mount option.
 248 All file name searches within \fBpcfs\fR, however, are treated as if they were
 249 uppercase, so \fBreadme.txt\fR and \fBReAdMe.TxT\fR refer to the same file.
 250 .sp
 251 .LP
 252 To format a diskette or a \fBPCMCIA\fR pseudo-floppy memory card in \fBFAT\fR
 253 format in the SunOS system, use either the \fBfdformat\fR \fB-d\fR or the
 254 \fBDOS\fR \fBFORMAT\fR command.
 255 .SS "Boot Partitions"


 256 On x86 systems, hard drives may contain an \fBfdisk\fR partition reserved for
 257 the Solaris boot utilities. These partitions are special instances of
 258 \fBpcfs\fR. You can mount an x86 boot partition with the command:
 259 .sp
 260 .in +2
 261 .nf
 262 mount \fB-F\fR pcfs \fIdevice-special\fR:boot \fIdirectory-name\fR
 263 .fi
 264 .in -2
 265 .sp
 266 
 267 .sp
 268 .LP
 269 or you can use:
 270 .sp
 271 .in +2
 272 .nf
 273 \fBmount \fIdirectory-name\fR\fR
 274 .fi
 275 .in -2


 281 .sp
 282 .in +2
 283 .nf
 284 \fIdevice-special\fR:boot \(mi \fIdirectory-name\fR pcfs \(mi no rw
 285 .fi
 286 .in -2
 287 .sp
 288 
 289 .sp
 290 .LP
 291 \fIdevice-special\fR specifies the special block device file for the entire
 292 hard disk (\fB/dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRp0\fR)
 293 .sp
 294 .LP
 295 \fIdirectory-name\fR specifies the location where the file system is mounted.
 296 .sp
 297 .LP
 298 All files on a boot partition are owned by super-user. Only the super-user may
 299 create, delete, or modify files on a boot partition.
 300 .SH EXAMPLES

 301 \fBExample 1 \fRSample Displays of File Names
 302 .sp
 303 .LP
 304 If you copy a file \fBfinancial.data\fR from a UNIX file system to \fBpcfs\fR,
 305 it displays as \fBfinancial.data\fR in \fBpcfs\fR, but may show up as
 306 \fBFINANC~1.DAT\fR in systems that do not support long file names.
 307 
 308 .sp
 309 .LP
 310 The following are legal long file names. They are also \fBillegal\fR short file
 311 names:
 312 

 313 .in +2
 314 \fBtest.sh.orig\fR
 315 .in -2
 316 .br
 317 .in +2
 318 \fBdata+\fR
 319 .in -2
 320 .br
 321 .in +2
 322 \fB\&.login\fR
 323 .in -2
 324 .sp
 325 .LP
 326 Other systems that do not support long file names may see:
 327 

 328 .in +2
 329 \fBTESTSH~1.ORI\fR
 330 .in -2
 331 .br
 332 .in +2
 333 \fBDATA~1\fR
 334 .in -2
 335 .br
 336 .in +2
 337 \fBLOGIN~1\fR
 338 .in -2
 339 .sp
 340 .LP
 341 The short file name is generated from the initial characters of the long file
 342 name, so differentiate names in the first few characters. For example, these
 343 names:
 344 

 345 .in +2
 346 \fBWorkReport.January.Data\fR
 347 .in -2
 348 .br
 349 .in +2
 350 \fBWorkReport.February.Data\fR
 351 .in -2
 352 .br
 353 .in +2
 354 \fBWorkReport.March.Data\fR
 355 .in -2
 356 .sp
 357 .LP
 358 result in these short names, which are not distinguishable:
 359 

 360 .in +2
 361 \fBWORKRE~1.DAT\fR
 362 .in -2
 363 .br
 364 .in +2
 365 \fBWORKRE~2.DAT\fR
 366 .in -2
 367 .br
 368 .in +2
 369 \fBWORKRE~13.DAT\fR
 370 .in -2
 371 .sp
 372 .LP
 373 These names, however:
 374 

 375 .in +2
 376 \fBJanuary.WorkReport.Data\fR
 377 .in -2
 378 .br
 379 .in +2
 380 \fBFebruary.WorkReport.Data\fR
 381 .in -2
 382 .br
 383 .in +2
 384 \fBMarch.WorkReport.Data\fR
 385 .in -2
 386 .sp
 387 .LP
 388 result in the more descriptive short names:
 389 

 390 .in +2
 391 \fBJANUAR~1.DAT\fR
 392 .in -2
 393 .br
 394 .in +2
 395 \fBFEBRUA~1.DAT\fR
 396 .in -2
 397 .br
 398 .in +2
 399 \fBMARCHW~1.DAT\fR
 400 .in -2
 401 .SH FILES

 402 .ne 2
 403 .na
 404 \fB\fB/usr/lib/fs/pcfs/mount\fR\fR
 405 .ad
 406 .RS 26n
 407 \fBpcfs\fR \fBmount\fR command
 408 .RE
 409 
 410 .sp
 411 .ne 2
 412 .na
 413 \fB\fB/usr/kernel/fs/pcfs\fR\fR
 414 .ad
 415 .RS 26n
 416 32-bit kernel module
 417 .RE
 418 
 419 .SH ENVIRONMENT VARIABLES


 420 See \fBenviron\fR(5) for descriptions of the following environment variables
 421 for the current locale setting: LANG, LC_ALL, LC_CTYPE, and LC_COLLATE.
 422 .SH SEE ALSO


 423 \fBchgrp\fR(1), \fBchown\fR(1), \fBdos2unix\fR(1), \fBeject\fR(1),
 424 \fBfdformat\fR(1), \fBunix2dos\fR(1), \fBvolcheck\fR(1), \fBmount\fR(1M),
 425 \fBmount_pcfs\fR(1M), \fBumount\fR(1M), \fBctime\fR(3C), \fBvfstab\fR(4),
 426 \fBenviron\fR(5), \fBpcmem\fR(7D)
 427 .SH WARNINGS


 428 Do not physically eject a \fBFAT\fR floppy while the device is mounted as
 429 \fBpcfs\fR. If Volume Management is managing a device, use the \fBeject\fR(1)
 430 command before physically removing media.
 431 .sp
 432 .LP
 433 When mounting \fBpcfs\fR on a hard disk, make sure the first block on that
 434 device contains a valid \fBfdisk\fR partition table.
 435 .sp
 436 .LP
 437 Because \fBpcfs\fR has no provision for handling owner-IDs or group-IDs on
 438 files, \fBchown\fR(1) or \fBchgrp\fR(1) may generate various errors. This is a
 439 limitation of \fBpcfs\fR, but it should not cause problems other than error
 440 messages.
 441 .SH NOTES


 442 Only the following characters are allowed in \fBpcfs\fR short file names and
 443 extensions:
 444 .br
 445 .in +2
 446 \fB0-9\fR
 447 .in -2
 448 .br
 449 .in +2
 450 \fBA-Z\fR
 451 .in -2
 452 .br
 453 .in +2
 454 \fB$#&@!%()-{}<>`_^~|'\fR
 455 .in -2
 456 .sp
 457 .LP
 458 SunOS and \fBFAT\fR use different character sets and have different
 459 requirements for the text file format. Use the \fBdos2unix\fR(1) and
 460 \fBunix2dos\fR(1) commands to convert files between them.
 461 .sp


 466 should not be used as the format for a regular local storage. Instead, use
 467 \fBufs\fR for local storage within the SunOS system.
 468 .sp
 469 .LP
 470 Although long file names can contain spaces (just as in UNIX file names), some
 471 utilities may be confused by them.
 472 .sp
 473 .LP
 474 This implementation of \fBpcfs\fR conforms to the behavior exhibited by Windows
 475 95 version 4.00.950.
 476 .sp
 477 .LP
 478 When \fBpcfs\fR encounters long file names with non-ASCII characters, it
 479 converts such long file names in Unicode scalar values into UTF-8 encoded
 480 filenames so that they are legible and usable with any of Solaris UTF-8
 481 locales. In the same context, when new file names with non-ASCII characters are
 482 created, \fBpcfs\fR expects that such file names are in UTF-8. This feature
 483 increases the interoperability of \fBpcfs\fR on Solaris with other operating
 484 systems.
 485 .SH BUGS


 486 \fBpcfs\fR should handle the disk change condition in the same way that
 487 \fBDOS\fR does, so you do not need to unmount the file system to change
 488 floppies.