Print this page
11622 clean up rarer mandoc lint warnings
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man7fs/pcfs.7fs
+++ new/usr/src/man/man7fs/pcfs.7fs
1 1 '\" te
2 2 .\" Copyright (c) 2007 Sun Microsystems, Inc. All Rights Reserved.
3 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 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 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 6 .TH PCFS 7FS "Nov 6, 2007"
7 7 .SH NAME
8 8 pcfs \- FAT formatted file system
9 9 .SH SYNOPSIS
10 -.LP
11 10 .nf
12 11 #include <sys/param.h>
13 12 #include <sys/mount.h>
14 13 #include <sys/fs/pc_fs.h>
15 14
16 15 \fBint\fR \fBmount\fR(\fBconst char *\fR\fIspec\fR,
17 16 \fBconst char *\fR \fIdir\fR, \fBint\fR \fImflag\fR,
18 17 \fB"pcfs", NULL, 0,\fR \fBchar *\fR\fIoptptr\fR,
19 18 \fBint\fR \fIoptlen\fR);
20 19 .fi
21 20
22 21 .SH DESCRIPTION
23 -.sp
24 -.LP
25 22 \fBpcfs\fR is a file system type that enables direct access to files on
26 23 \fBFAT\fR formatted disks from within the SunOS operating system.
27 24 .sp
28 25 .LP
29 26 Once mounted, \fBpcfs\fR provides standard SunOS file operations and semantics.
30 27 Using \fBpcfs\fR, you can create, delete, read, and write files on a \fBFAT\fR
31 28 formatted disk. You can also create and delete directories and list files in a
32 29 directory.
33 30 .sp
34 31 .LP
35 32 \fBpcfs\fR supports FAT12 (floppies) and FAT16 and FAT32 file systems.
36 33 .sp
37 34 .LP
38 35 \fBpcfs\fR file systems can be force umounted using the \fB-f\fR argument to
39 36 \fBumount\fR(1M).
40 37 .sp
41 38 .LP
42 39 The \fBpcfs\fR file system contained on the block special file identified by
43 40 \fIspec\fR is mounted on the directory identified by \fIdir\fR. \fIspec\fR and
44 41 \fIdir\fR are pointers to pathnames. \fImflag\fR specifies the \fBmount\fR
45 42 options. The \fBMS_DATA\fR bit in \fImflag\fR must be set. Mount options can be
46 43 passed to \fBpcfs\fR using the optptr and optlen arguments. See
47 44 \fBmount_pcfs\fR(1M) for a list of mount options supported by \fBpcfs\fR.
48 45 .sp
49 46 .LP
50 47 Because FAT formatted media can record file timestamps between January 1st 1980
51 48 and December 31st 2127, it's not possible to fully represent UNIX \fBtime_t\fR
52 49 in \fBpcfs\fR for 32 bit or 64 bit programs. In particular, if post-2038
53 50 timestamps are present on a FAT formatted medium and \fBpcfs\fR returns these,
54 51 32bit applications may unexpectedly fail with \fBEOVERFLOW\fR errors. To
55 52 prevent this, the default behaviour of \fBpcfs\fR has been modified to clamp
56 53 post-2038 timestamps to the latest possible value for a 32bit \fBtime_t\fR,
57 54 which is January 19th 2038, 03:14:06 UTC when setting and retrieving file
58 55 timestamps. You can override this behavior using the \fBnoclamptime\fR mount
59 56 option, as described in \fBmount_pcfs\fR(1M).
60 57 .sp
61 58 .LP
62 59 Timestamps on FAT formatted media are recorded in local time. If the recording
63 60 and receiving systems use different timezones, the representation of
64 61 timestamps shown on the two systems for the same medium might vary. To correct
65 62 this, \fBpcfs\fR provides a timezone mount option to force interpretation
66 63 of timestamps as read from a FAT formatted medium in a given timezone (that of
67 64 the recorder). By default, the local timezone of the receiver is used. See
68 65 \fBmount_pcfs\fR(1M) for details.
|
↓ open down ↓ |
34 lines elided |
↑ open up ↑ |
69 66 .sp
70 67 .LP
71 68 The root directory of a FAT formatted medium has no timestamps and \fBpcfs\fR
72 69 returns the time when the mount was done as timestamp for the root of the
73 70 filesystem.
74 71 .sp
75 72 .LP
76 73 The FAT filesystem doesn't support multiple links. As a result, the link count
77 74 for all files and directories in \fBpcfs\fR is hard-coded as "1."
78 75 .SS "Mounting File Systems"
79 -.sp
80 -.LP
81 76 Use the following command to mount \fBpcfs\fR from diskette:
82 77 .sp
83 78 .in +2
84 79 .nf
85 80 mount \fB-F\fR pcfs \fIdevice-special\fR \fIdirectory-name\fR
86 81 .fi
87 82 .in -2
88 83 .sp
89 84
90 85 .sp
91 86 .LP
92 87 You can use:
93 88 .sp
94 89 .in +2
95 90 .nf
96 91 mount \fIdirectory-name\fR
97 92 .fi
98 93 .in -2
99 94 .sp
100 95
101 96 .sp
102 97 .LP
103 98 if the following line is in your \fB/etc/vfstab\fR file:
104 99 .sp
105 100 .in +2
106 101 .nf
107 102 \fIdevice-special\fR - \fIdirectory-name\fRpcfs \(mi no rw
108 103 .fi
109 104 .in -2
110 105
111 106 .sp
112 107 .LP
113 108 Use the following command to mount \fBpcfs\fR from non-diskette media:
114 109 .sp
115 110 .in +2
116 111 .nf
117 112 mount \fB-F\fR pcfs \fIdevice-special\fR:\fIlogical-drive\fR \fBdirectory-name\fR
118 113 .fi
119 114 .in -2
120 115 .sp
121 116
122 117 .sp
123 118 .LP
124 119 You can use:
125 120 .sp
126 121 .in +2
127 122 .nf
128 123 mount \fIdirectory-name\fR
129 124 .fi
130 125 .in -2
131 126 .sp
132 127
133 128 .sp
134 129 .LP
135 130 if the following line is in your \fB/etc/vfstab\fR file:
136 131 .sp
137 132 .in +2
138 133 .nf
139 134 \fIdevice-special\fR:\fIlogical_drive\fR \fB\(mi\fR \fIdirectory-name\fR \fBpcfs \(mi no rw\fR
140 135 .fi
141 136 .in -2
142 137
143 138 .sp
144 139 .LP
145 140 \fIdevice-special\fR specifies the special block device file for the diskette
146 141 (\fB/dev/diskette\fIN\fR\fR) or the entire hard disk
147 142 (\fB/dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRp0\fR for a SCSI disk, and
148 143 \fB/dev/dsk/c\fIN\fRd\fIN\fRp0\fR for \fBIDE\fR disks) or the \fBPCMCIA\fR
149 144 pseudo-floppy memory card (\fB/dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRs\fIN\fR\fR).
150 145 .sp
151 146 .LP
152 147 \fIlogical-drive\fR specifies either the \fBDOS\fR logical drive letter
153 148 (\fBc\fR through \fBz\fR) or a drive number (\fB1\fR through \fB24\fR). Drive
154 149 letter \fBc\fR is equivalent to drive number \fB1\fR and represents the Primary
155 150 \fBDOS\fR partition on the disk; drive letters \fBd\fR through \fBz\fR are
156 151 equivalent to drive numbers \fB2\fR through \fB24\fR, and represent \fBDOS\fR
157 152 drives within the Extended \fBFAT\fR partition. Note that \fIdevice-special\fR
158 153 and \fIlogical-drive\fR must be separated by a colon.
159 154 .sp
160 155 .LP
161 156 \fIdirectory-name\fR specifies the location where the file system is mounted.
162 157 .sp
163 158 .LP
164 159 For example, to mount the Primary \fBDOS\fR partition from a SCSI hard disk,
165 160 use:
166 161 .sp
167 162 .in +2
168 163 .nf
169 164 mount \fB-F\fR pcfs /dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRp0:c /pcfs/c
170 165 .fi
171 166 .in -2
172 167 .sp
173 168
174 169 .sp
175 170 .LP
176 171 To mount the first logical drive in the Extended \fBDOS\fR partition from an
177 172 \fBIDE\fR hard disk, use:
178 173 .sp
179 174 .in +2
180 175 .nf
181 176 mount \fB-F\fR pcfs /dev/dsk/c\fIN\fRd\fIN\fRp0:d /pcfs/d
182 177 .fi
183 178 .in -2
184 179 .sp
185 180
186 181 .sp
187 182 .LP
188 183 To mount a \fBDOS\fR diskette in the first floppy drive when volume management
189 184 is not running use:
190 185 .sp
191 186 .in +2
192 187 .nf
193 188 mount \fB-F\fR pcfs /dev/diskette /pcfs/a
194 189 .fi
195 190 .in -2
196 191 .sp
197 192
198 193 .sp
199 194 .LP
200 195 If Volume Management is running, run \fBvolcheck\fR(1) to automatically mount
201 196 the floppy and some removable disks.
202 197 .sp
203 198 .LP
204 199 To mount a \fBPCMCIA\fR pseudo-floppy memory card, with Volume Management not
|
↓ open down ↓ |
114 lines elided |
↑ open up ↑ |
205 200 running (or not managing the \fBPCMCIA\fR media), use:
206 201 .sp
207 202 .in +2
208 203 .nf
209 204 mount \fB-F\fR pcfs /dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRs\fIN\fR /pcfs
210 205 .fi
211 206 .in -2
212 207 .sp
213 208
214 209 .SS "Conventions"
215 -.sp
216 -.LP
217 210 Files and directories created through \fBpcfs\fR must comply with either the
218 211 \fBFAT\fR short file name convention or the long file name convention
219 212 introduced with Windows 95. The \fBFAT\fR short file name convention is of the
220 213 form \fIfilename\fR[.\fIext\fR], where \fIfilename\fR generally consists of
221 214 from one to eight upper-case characters, while the optional \fIext\fR consists
222 215 of from one to three upper-case characters.
223 216 .sp
224 217 .LP
225 218 The long file name convention is much closer to Solaris file names. A long file
226 219 name can consist of any characters valid in a short file name, lowercase
227 220 letters, non-leading spaces, the characters \fB+,;=[]\fR, any number of
228 221 periods, and can be up to 255 characters long. Long file names have an
229 222 associated short file name for systems that do not support long file names
230 223 (including earlier releases of Solaris). The short file name is not visible if
231 224 the system recognizes long file names. \fBpcfs\fR generates a unique short name
232 225 automatically when creating a long file name.
233 226 .sp
234 227 .LP
235 228 Given a long file name such as \fBThis is a really long filename.TXT\fR, the
236 229 short file name will generally be of the form \fBTHISIS~\fR\fIN\fR\fB\&.TXT\fR,
237 230 where \fIN\fR is a number. The long file name will probably get the short name
238 231 \fBTHISIS~1.TXT\fR, or \fBTHISIS~2.TXT\fR if \fBTHISIS~1.TXT\fR already exits
239 232 (or \fBTHISIS~3.TXT\fR if both exist, and so forth). If you use \fBpcfs\fR file
240 233 systems on systems that do not support long file names, you may want to
241 234 continue following the short file name conventions. See \fBEXAMPLES\fR.
242 235 .sp
243 236 .LP
244 237 When creating a file name, \fBpcfs\fR creates a short file name if it fits the
245 238 \fBFAT\fR short file name format, otherwise it creates a long file name. This
246 239 is because long file names take more directory space. Because the root
247 240 directory of a \fBpcfs\fR file system is fixed size, long file names in the
248 241 root directory should be avoided if possible.
249 242 .sp
250 243 .LP
251 244 When displaying file names, \fBpcfs\fR shows them exactly as they are on the
252 245 media. This means that short names are displayed as uppercase and long file
|
↓ open down ↓ |
26 lines elided |
↑ open up ↑ |
253 246 names retain their case. Earlier versions of \fBpcfs\fR folded all names to
254 247 lowercase, which can be forced with the \fBPCFS_MNT_FOLDCASE\fR mount option.
255 248 All file name searches within \fBpcfs\fR, however, are treated as if they were
256 249 uppercase, so \fBreadme.txt\fR and \fBReAdMe.TxT\fR refer to the same file.
257 250 .sp
258 251 .LP
259 252 To format a diskette or a \fBPCMCIA\fR pseudo-floppy memory card in \fBFAT\fR
260 253 format in the SunOS system, use either the \fBfdformat\fR \fB-d\fR or the
261 254 \fBDOS\fR \fBFORMAT\fR command.
262 255 .SS "Boot Partitions"
263 -.sp
264 -.LP
265 256 On x86 systems, hard drives may contain an \fBfdisk\fR partition reserved for
266 257 the Solaris boot utilities. These partitions are special instances of
267 258 \fBpcfs\fR. You can mount an x86 boot partition with the command:
268 259 .sp
269 260 .in +2
270 261 .nf
271 262 mount \fB-F\fR pcfs \fIdevice-special\fR:boot \fIdirectory-name\fR
272 263 .fi
273 264 .in -2
274 265 .sp
275 266
276 267 .sp
277 268 .LP
278 269 or you can use:
279 270 .sp
280 271 .in +2
281 272 .nf
282 273 \fBmount \fIdirectory-name\fR\fR
283 274 .fi
284 275 .in -2
285 276 .sp
286 277
287 278 .sp
288 279 .LP
289 280 if the following line is in your \fB/etc/vfstab\fR file:
290 281 .sp
291 282 .in +2
292 283 .nf
293 284 \fIdevice-special\fR:boot \(mi \fIdirectory-name\fR pcfs \(mi no rw
294 285 .fi
295 286 .in -2
296 287 .sp
297 288
298 289 .sp
299 290 .LP
|
↓ open down ↓ |
25 lines elided |
↑ open up ↑ |
300 291 \fIdevice-special\fR specifies the special block device file for the entire
301 292 hard disk (\fB/dev/dsk/c\fIN\fRt\fIN\fRd\fIN\fRp0\fR)
302 293 .sp
303 294 .LP
304 295 \fIdirectory-name\fR specifies the location where the file system is mounted.
305 296 .sp
306 297 .LP
307 298 All files on a boot partition are owned by super-user. Only the super-user may
308 299 create, delete, or modify files on a boot partition.
309 300 .SH EXAMPLES
310 -.LP
311 301 \fBExample 1 \fRSample Displays of File Names
312 302 .sp
313 303 .LP
314 304 If you copy a file \fBfinancial.data\fR from a UNIX file system to \fBpcfs\fR,
315 305 it displays as \fBfinancial.data\fR in \fBpcfs\fR, but may show up as
316 306 \fBFINANC~1.DAT\fR in systems that do not support long file names.
317 307
318 308 .sp
319 309 .LP
320 310 The following are legal long file names. They are also \fBillegal\fR short file
321 311 names:
322 312
323 -.br
324 313 .in +2
325 314 \fBtest.sh.orig\fR
326 315 .in -2
327 316 .br
328 317 .in +2
329 318 \fBdata+\fR
330 319 .in -2
331 320 .br
332 321 .in +2
333 322 \fB\&.login\fR
334 323 .in -2
335 324 .sp
336 325 .LP
337 326 Other systems that do not support long file names may see:
338 327
339 -.br
340 328 .in +2
341 329 \fBTESTSH~1.ORI\fR
342 330 .in -2
343 331 .br
344 332 .in +2
345 333 \fBDATA~1\fR
346 334 .in -2
347 335 .br
348 336 .in +2
349 337 \fBLOGIN~1\fR
350 338 .in -2
351 339 .sp
352 340 .LP
353 341 The short file name is generated from the initial characters of the long file
354 342 name, so differentiate names in the first few characters. For example, these
355 343 names:
356 344
357 -.br
358 345 .in +2
359 346 \fBWorkReport.January.Data\fR
360 347 .in -2
361 348 .br
362 349 .in +2
363 350 \fBWorkReport.February.Data\fR
364 351 .in -2
365 352 .br
366 353 .in +2
367 354 \fBWorkReport.March.Data\fR
368 355 .in -2
369 356 .sp
370 357 .LP
371 358 result in these short names, which are not distinguishable:
372 359
373 -.br
374 360 .in +2
375 361 \fBWORKRE~1.DAT\fR
376 362 .in -2
377 363 .br
378 364 .in +2
379 365 \fBWORKRE~2.DAT\fR
380 366 .in -2
381 367 .br
382 368 .in +2
383 369 \fBWORKRE~13.DAT\fR
384 370 .in -2
385 371 .sp
386 372 .LP
387 373 These names, however:
388 374
389 -.br
390 375 .in +2
391 376 \fBJanuary.WorkReport.Data\fR
392 377 .in -2
393 378 .br
394 379 .in +2
395 380 \fBFebruary.WorkReport.Data\fR
396 381 .in -2
397 382 .br
398 383 .in +2
399 384 \fBMarch.WorkReport.Data\fR
400 385 .in -2
401 386 .sp
402 387 .LP
403 388 result in the more descriptive short names:
404 389
405 -.br
406 390 .in +2
407 391 \fBJANUAR~1.DAT\fR
408 392 .in -2
409 393 .br
410 394 .in +2
411 395 \fBFEBRUA~1.DAT\fR
412 396 .in -2
413 397 .br
414 398 .in +2
415 399 \fBMARCHW~1.DAT\fR
416 400 .in -2
417 401 .SH FILES
418 -.sp
419 402 .ne 2
420 403 .na
421 404 \fB\fB/usr/lib/fs/pcfs/mount\fR\fR
422 405 .ad
423 406 .RS 26n
424 407 \fBpcfs\fR \fBmount\fR command
425 408 .RE
426 409
427 410 .sp
428 411 .ne 2
429 412 .na
430 413 \fB\fB/usr/kernel/fs/pcfs\fR\fR
431 414 .ad
432 415 .RS 26n
433 416 32-bit kernel module
434 417 .RE
435 418
436 419 .SH ENVIRONMENT VARIABLES
437 -.sp
438 -.LP
439 420 See \fBenviron\fR(5) for descriptions of the following environment variables
440 421 for the current locale setting: LANG, LC_ALL, LC_CTYPE, and LC_COLLATE.
441 422 .SH SEE ALSO
442 -.sp
443 -.LP
444 423 \fBchgrp\fR(1), \fBchown\fR(1), \fBdos2unix\fR(1), \fBeject\fR(1),
445 424 \fBfdformat\fR(1), \fBunix2dos\fR(1), \fBvolcheck\fR(1), \fBmount\fR(1M),
446 425 \fBmount_pcfs\fR(1M), \fBumount\fR(1M), \fBctime\fR(3C), \fBvfstab\fR(4),
447 426 \fBenviron\fR(5), \fBpcmem\fR(7D)
448 427 .SH WARNINGS
449 -.sp
450 -.LP
451 428 Do not physically eject a \fBFAT\fR floppy while the device is mounted as
452 429 \fBpcfs\fR. If Volume Management is managing a device, use the \fBeject\fR(1)
453 430 command before physically removing media.
454 431 .sp
455 432 .LP
456 433 When mounting \fBpcfs\fR on a hard disk, make sure the first block on that
457 434 device contains a valid \fBfdisk\fR partition table.
458 435 .sp
459 436 .LP
460 437 Because \fBpcfs\fR has no provision for handling owner-IDs or group-IDs on
461 438 files, \fBchown\fR(1) or \fBchgrp\fR(1) may generate various errors. This is a
462 439 limitation of \fBpcfs\fR, but it should not cause problems other than error
463 440 messages.
464 441 .SH NOTES
465 -.sp
466 -.LP
467 442 Only the following characters are allowed in \fBpcfs\fR short file names and
468 443 extensions:
469 444 .br
470 445 .in +2
471 446 \fB0-9\fR
472 447 .in -2
473 448 .br
474 449 .in +2
475 450 \fBA-Z\fR
476 451 .in -2
477 452 .br
478 453 .in +2
479 454 \fB$#&@!%()-{}<>`_^~|'\fR
480 455 .in -2
481 456 .sp
482 457 .LP
483 458 SunOS and \fBFAT\fR use different character sets and have different
484 459 requirements for the text file format. Use the \fBdos2unix\fR(1) and
485 460 \fBunix2dos\fR(1) commands to convert files between them.
486 461 .sp
487 462 .LP
488 463 \fBpcfs\fR offers a convenient transportation vehicle for files between Sun
489 464 workstations and \fBPCs.\fR Because the \fBFAT\fR disk format was designed for
490 465 use under \fBDOS,\fR it does not operate efficiently under the SunOS system and
491 466 should not be used as the format for a regular local storage. Instead, use
492 467 \fBufs\fR for local storage within the SunOS system.
493 468 .sp
494 469 .LP
495 470 Although long file names can contain spaces (just as in UNIX file names), some
496 471 utilities may be confused by them.
497 472 .sp
498 473 .LP
499 474 This implementation of \fBpcfs\fR conforms to the behavior exhibited by Windows
500 475 95 version 4.00.950.
|
↓ open down ↓ |
24 lines elided |
↑ open up ↑ |
501 476 .sp
502 477 .LP
503 478 When \fBpcfs\fR encounters long file names with non-ASCII characters, it
504 479 converts such long file names in Unicode scalar values into UTF-8 encoded
505 480 filenames so that they are legible and usable with any of Solaris UTF-8
506 481 locales. In the same context, when new file names with non-ASCII characters are
507 482 created, \fBpcfs\fR expects that such file names are in UTF-8. This feature
508 483 increases the interoperability of \fBpcfs\fR on Solaris with other operating
509 484 systems.
510 485 .SH BUGS
511 -.sp
512 -.LP
513 486 \fBpcfs\fR should handle the disk change condition in the same way that
514 487 \fBDOS\fR does, so you do not need to unmount the file system to change
515 488 floppies.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX