Formatting Diskettes

Table 14-1 Task Map: How Diskettes Are Typically Formatted

Using Diskette Names

When working with diskettes, you can identify them by name or with a designator from Table 14-2, below. For brevity, task descriptions use floppy0, but you can replace it with either the diskette name or a different designator.

Table 14-2

CD	Alternate Name
First CD-ROM drive	cdrom0
Second CD-ROM drive	cdrom1
Third CD-ROM drive	cdrom2

Also note that diskettes that are not named (that is, have no "label") are assigned the default name of noname.

Hardware Considerations

A Solaris system can format diskettes for use on both Solaris and DOS systems. However, the hardware platform imposes some limitations. They are summarized in the table below.

Solaris on this Platform ...	Can Format Diskettes For ...
Solaris on SPARC	Solaris on SPARC (UFS) MS-DOS or NEC-DOS (PCFS)
Solaris on x86	Solaris on x86 (UFS) MS-DOS or NEC-DOS (PCFS)

Diskettes formatted for UFS are restricted to the hardware platform on which they were formatted. In other words, a UFS diskette formatted on a SPARC system cannot be used for UFS on an x86 system, nor can a diskette formatted on an x86 system be used on a SPARC system. This is because the SPARC and x86 UFS formats are different.¹

---

1. SPARC uses little-endian bits coding, x86 uses big-endian.

A complete format for SunOS file systems consists of the basic "bit" formatting plus the structure to support a SunOS file system. A complete format for a DOS file system consists of the basic "bit" formatting plus the structure to support either an MS-DOS or an NEC-DOS file system. The procedures required to prepare a diskette for each type of file system are different. Therefore, before you format a diskette, consider which procedure to follow. See Table 14-1 on page 218.

On a Solaris system (either SPARC or x86), you can format diskettes of seven different densities (provided you have the appropriate drive).

Diskette Size	Diskette Density	Capacity
3.5"	Extended Density	2.88 Mbytes
3.5"	High Density (HD)	1.44 Mbytes
3.5"	Medium Density (DD)	1.2 Mbytes
3.5"	Low Density	720 Kbytes
5.25"	High Density (HD)	1.2 Mbytes
5.25	Medium Density (DD)	720 Kbytes
5.25"	Low Density	360 Kbytes

By default, the diskette drive formats a diskette to a like density. In other words, a 1.44 Mbyte drive attempts to format a diskette for 1.44 Mbytes, whether the diskette is in fact a 1.44 Mbyte diskette or not --unless you instruct it otherwise. You can tell a 1.44 Mbyte drive to format a diskette to, for instance, 720 Kbytes. You cannot, however, instruct a 720 Kbyte drive to format a diskette to 1.44 Mbyte. In other words, a diskette can be formatted to its capacity or lower, and a drive can format to its capacity or lower.

To instruct a drive to format a diskette to a non-default density, use the fdformat command as instructed in the following tasks, but use the appropriate density option from Table 14-3, below.

Table 14-3

To Format a Diskette with this Density ...	In a Drive with this Default Density ...	Use this density option to the fdformat Command ...
2.88 Mbytes	2.88 Mbytes	-E
1.44 Mbytes	2.88 Mbytes	-H
1.44 Mbytes	1.44 Mbytes	none
1.2 Mbytes	1.44 Mbytes	-t nec -M
720 Kbytes	1.44 Mbytes	-D or -t dos -D
1.2 Mbytes	1.2 Mbytes	none
720 Kbytes	1.2 Mbytes	-D
720 Kbytes	720 Kbytes	none
360 Kbytes	720 Kbytes	-D

To view all the options to the fdformat command, either see fdformat(1) or enter fdformat -z. The -z option displays all the options to the command.

If you don't know the default density of your drive, begin the formatting process with the default setting (that is, no density options) and observe the configuration message. It will look something like this:

Formatting 1.44 M in /vol/dev/rdiskette0/unformatted Press return to start formatting floppy.

The confirmation message indicates the drive's default density. For instance, in the example above, the default density of the drive is 1.44 Mbytes. If the density is not what you expected, use Control-c to escape the formatting process and start over.

· How to Format a UFS Diskette

As mentioned in "Hardware Considerations" on page 219, a UFS diskette formatted on a SPARC system can only be used on another SPARC system, and a UFS diskette formatted on an x86 system can only be used on an x86 system running Solaris.

---

Caution - Formatting a diskette erases any pre-existing content.

---

1. Quit File Manager.

   File Manager automatically displays a formatting window when you insert an unformatted diskette. Unfortunately, File Manager formatting is unreliable. To avoid the window, quit from File Manager. If you prefer to keep File Manager open, quit the formatting window when it appears.

2. Make sure the diskette is write-enabled.

   On both 3.5-inch and 5.25 inch diskettes, write-protection is controlled by a small tab in either the lower left or lower right corner. If you can see through the square hole behind the tab, the diskette is write-protected. If the hole is covered by the tab, the diskette is write-enabled. (If you need to eject the diskette to examine it, simply type eject floppy in a shell.)

3. Insert the diskette.

   Make sure the diskette is completely inserted.

4. Invoke formatting.

$ fdformat -v -U [density-options convenience-options]

In this command,

-v	Verifies whether the diskette was formatted correctly.
-U	Unmounts the diskette if it is mounted.
density-options	If the drive density is 1.44 Mbytes, density-options are:
--none--	Formats a 1.44 Mbyte diskette.
-D	Formats a 720 Kbyte diskette.

A complete list of density-options appears in Table 14-3 on page 221.

convenience-options

-e	Ejects the diskette when done formatting.
-f	Forces formatting without asking for confirmation.
-b label	Names the diskette. label must be eight characters or less. Case is ignored.
-z	Lists all the options to the fdformat command, but does not format the diskette.

---

Note - If you try to format a 720Kbyte (DD) diskette for 1.44 Mbytes, fdformat will not stop you unless you include the -v option. With the -v option, fdformat will format the diskette, but the verification will catch the error and notify you with the following message:

fdformat: check diskette density, I/O error

---

The fdformat command displays a confirmation message (unless you used the -f option), indicating the type of formatting to be performed:

Formatting 1.44 M in /vol/dev/rdiskette0/unformatted
Press return to start formatting floppy.

5. Select one of the options in the table below.

To ...	Press ...
Confirm the type of formatting	Return (unless you used the -f option in the previous step, in which case no confirmation is necessary).
Cancel formatting	Control-c.

As the formatting progresses, a series of dots is displayed. As the verification progresses, a series of V's appears beneath the dots. When the series stops, the formatting is complete.

6. Eject the diskette.

$ eject floppy0

The diskette is now ready for raw character operations such as tar and cpio. To prepare the diskette for Solaris file system operation, add a UFS file system to the diskette, as described in "How to Format a UFS Diskette" on page 222.

Examples--Formatting a UFS Diskette

Following are several examples of UFS formatting. The first example formats a 1.44 Mbyte diskette on a 1.44 Mbyte drive:

$ fdformat -v -U Formatting 1.44 M in /vol/dev/rdiskette0/unformatted Press return to start formatting floppy. [ Return ] ............................................................. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

The following example performs the same job, but assigns the diskette the name myfiles:

$ fdformat -v -U -b myfiles Formatting 1.44 M in /vol/dev/rdiskette0/unformatted Press return to start formatting floppy. [ Return ] ............................................................. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

The following example formats a 720Kbyte diskette on a 1.44 Mbyte drive, and names it myfiles:

$ fdformat -v -U -D -b myfiles Formatting 720 KB in /vol/dev/rdiskette0/unformatted Press return to start formatting floppy. [ Return ] ............................................................. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

· How Place a UFS File System on a Diskette

Even though the procedure for adding a UFS file system is the same for UFS diskettes formatted on x86 systems and SPARC systems, a UFS diskette formatted on a SPARC system can only be used on another SPARC system, and a UFS diskette formatted on an x86 system can only be used on an x86 system running Solaris.

1. Format the diskette for a UFS file system.

   Use "How to Format a UFS Diskette" on page 222.

2. Re-insert the diskette.

3. Notify Volume Management.

$ volcheck -v media was found

The status message "media was found" is displayed in the shell, but the following error messages appear in the Console:

fd0: unformatted diskette or no diskette in the drive
fd0: read failed (40 1 0)
fd0: bad format

Ignore this messages. It appears because the diskette has no file system yet.

4. Create a SunOS file system on the diskette.

$ newfs -v /vol/dev/aliases/floppy0

In this command,

-v................Prints status messages.

/vol/dev/aliases/floppy0             Indicates the location of the floppy.

The newfs command displays message asking you to confirm the creation of the file system.

5. Confirm the creation of the file system.

newfs: construct a new file system \ /vol/dev/aliases/floppy0:(y/n)? y

A status message is displayed, indicating the particulars of the file system and the diskette's formatting:

mkfs -F ufs /vol/dev/aliases/floppy0 2880 18 2 8192 1024 16 \
    10 5 2048 t 0 -1 8 -1
/vol/dev/aliases/floppy0:  2880 sectors in 80 cylinders of \
    2 tracks, 18 sectors
1.4 MB in 5 cyl groups (16 c/g, 0.28MB/g, 128 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
    32, 640, 1184, 1792, 2336

The diskette is now ready to be used on a SPARC system. However, before Volume Management recognizes it, you must eject and reinsert it, as described in the following steps.

6. Eject the diskette.

$ eject floppy0

7. Reinsert the diskette and notify Volume Management.

$ volcheck -v media was found

The diskette should now be mounted under /floppy/floppy0.

Verification--Placing a UFS File System on a Diskette

Use the ls command on the /floppy directory.

$ ls /floppy floppy0

If the floppy0 subdirectory appears, the diskette has a UFS file system and has been mounted properly.

Example--Placing a UFS File System on a Diskette

$ volcheck -v media was found $ newfs -v /vol/dev/aliases/floppy0 newfs: construct a new file system \ /vol/dev/aliases/floppy0:(y/n)? y mkfs -F ufs /vol/dev/aliases/floppy0 ... $ eject floppy0 --re-insert the diskette-- $ volcheck -v media was found

· How to Format a DOS Diskette

You can format a DOS diskette on a SPARC or x86 Solaris system. The steps are similar, except that instead of a SunOS file system being placed on the diskette, a DOS file system, either MS-DOS or NEC-DOS, is put on the file system.

---

Caution - Formatting a diskette erases any pre-existing content.

---

1. Quit File Manager.

   File Manager automatically displays a formatting window when you insert an unformatted diskette. Unfortunately, File Manager formatting is unreliable. To avoid the window, quit from File Manager. If you prefer to keep File Manager open, quit the formatting window when it appears.

2. Make sure the diskette is not write-protected.

   On both 3.5-inch and 5.25 inch diskettes, write-protection is controlled by a small tab in either the lower left or lower right corner. If you can see through the square hole behind the tab, the diskette is write-protected. If the hole is covered by the tab, the diskette is write-enabled. (If you need to eject the diskette to examine it, simply type eject floppy in a shell.)

3. Insert the diskette.

   Make sure the diskette is completely inserted. It must drop down into the drive.

4. Invoke formatting.

$ fdformat -v -U [density-options convenience-options]

In this command,

-v	Verifies whether the diskette was formatted correctly.
-U	Unmounts the diskette if it is mounted.
density-options	If the drive density is 1.44 Mbytes, density-options are:
-d	Formats at 1.44 Mbytes for MS-DOS.
-d -D	Formats at 720 Kbytes for MS-DOS.

-t nec -M      Formats at 1.2 Mbytes for NEC-DOS.

A complete list of density-options appears in Table 14-3 on page 221.

convenience-options

-e	Ejects the diskette when done formatting.
-f	Does not ask for confirmation before formatting.
-b label	Name the diskette. label must be eight characters or less. Case is ignored.
-z	Lists all the options to the fdformat command, but does not format the diskette.

---

Note - If you try to format a 720Kbyte (DD) diskette for 1.44 Mbytes, fdformat will not stop you unless you include the -v option. With the -v option, fdformat will format the diskette, but the verification will catch the error and notify you with the following message:

fdformat: check diskette density, I/O error

---

The fdformat command displays a confirmation message, indicating the type of formatting to be performed:

Formatting 1.44 M in /vol/dev/rdiskette0/unformatted
Press return to start formatting floppy.

5. Select one of the options in the table below.

To ...	Press ...
Confirm the type of formatting	Return (unless you used the -f option in the previous step, in which case no confirmation is necessary).
Cancel formatting	Control-c.

As the formatting progresses, a series of dots is displayed. As the verification progresses, a series of V's appears beneath the dots. When the series stops, the formatting is complete and the diskette is ready for use on a DOS system.

6. Eject the diskette.

$ eject floppy0

7. Reinsert the diskette and notify Volume Management.

$ volcheck -v media was found

Volume Management mounts the diskette under /floppy/floppy0.

Using Diskettes

Table 14-4 Task Map: How Diskettes Are Typically Used

· How to Load a Diskette

1. Make sure the diskette is formatted.

   If you aren't sure, insert it and check the status messages in the console, as described in Step 3, below. If you need to format the diskette, go to "How to Format a UFS Diskette" on page 222 or "How to Format a DOS Diskette" on page 228.

2. Insert the diskette.

   Make sure the diskette is completely inserted. It must drop down into the drive. If the drive has a door, close it.

3. Notify Volume Management.

$ volcheck -v media was found

Two status messages are possible:

media was found Volume Management detected the diskette and will attempt to

mount it in the /floppy directory.

If the diskette is formatted properly, no error messages appear in the console.

If the diskette is not formatted, the "media was found" message is still displayed, but the following error messages appear in the Console:

                     fd0: unformatted diskette or no diskette in
                   the drive
                      fd0: read failed (40 1 0)
                      fd0: bad format

You must format the diskette before Volume Management can mount it. Instructions are provided on page 222 (for UFS) and page 228 (for DOS).

no media was	Volume Management did not detect a diskette. Make sure the
found	diskette is inserted properly and run volcheck again. If unsuccessful, check the diskette; it could be damaged. You can also try to mount the diskette manually.

Verification--Loading a Diskette

Verify that the diskette was mounted by listing its contents.

$ ls /floppy/floppy0 floppy0 myfiles

As described earlier, floppy0 is a symbolic link to the actual name of the diskette; in this case, myfiles. If the diskette has no name but is formatted correctly, the system will refer to it as unnamed_floppy.

If nothing appears under the /floppy directory, the diskette was either not mounted or is not formatted properly. To find out, run the mount command and look for the line that begins with /floppy (usually at the end of the listing):

/floppy/name on /vol/dev/diskette0/name ...

If the line does not appear, the diskette was not mounted. Check the Console for error messages.

· How to Examine the Contents of a Diskette

Use the -L option to the ls command, because some directories under /floppy are symbolic links.

$ ls -L [-l] floppy0

In this command,

-L	Includes symbolic links in the output
-l	Long format. Includes permissions and owners in the output.

Example--Examining the Contents of a Diskette

The following example lists the contents of the diskette in the first floppy drive, identified by floppy0.

$ ls -L -l /floppy/floppy0 -rwxrwxrwx 1 smith staff 362284 Nov 16 20:54 text.doc -rwxrwxrwx 1 smith staff 24562 Nov 16 12:20 art.gif

Once you have inserted a diskette, you can access its files and directories just as you would those of any other file system. The only restrictions to be aware of are ownership and permissions. For instance, if you are not the owner of a file on a diskette, you won't be able to overwrite it on the diskette. Or, if you copy a file into your file system, you'll be the owner, but it won't have write permissions (because it never had them on the diskette); you'll have to change the permissions yourself.

· How to Copy or Move Information From a Diskette

1. Make sure the diskette is formatted and mounted.

$ ls /floppy floppy0 diskette-name

If the diskette is properly formatted and mounted, its name and the symbolic link will appear under /floppy.

If nothing appears under the /floppy directory, the diskette is not mounted. See the task titled, "How to Load a Diskette" on page 232. The diskette might also need to be formatted. See the task titled, "How to Format a UFS Diskette" on page 222 or "How to Format a DOS Diskette" on page 228.

2. Copy the files or directories.

To Copy ...	Use ...
A file	cp
A directory	cp -r

Verification--Copying or Moving Information from a Diskette

To verify a copy or move operation, use the ls command.

Examples--Copying or Moving Information from a Diskette

The first example, below, moves a file (readme.doc) from the diskette to the current directory (indicated by the "." symbol). The second example copies a file (readme2.doc) from the diskette to the current directory. The third example copies a directory (morefiles) and everything below it from the diskette to the current directory.

$ mv /floppy/floppy0/readme.doc . $ cp /floppy/floppy0/readme2.doc . $ cp -r /floppy/floppy0/morefiles .

· How to Copy or Move Information to a Diskette

1. Make sure the diskette is not write-protected.

   On both 3.5-inch and 5.25 inch diskettes, write-protection is controlled by a small tab in either the lower left or lower right corner. If you can see through the square hole behind the tab, the diskette is write-protected. If the hole is covered by the tab, the diskette is write-enabled.

2. Make sure the diskette is formatted and mounted.

$ ls /floppy floppy0 diskette-name

If the diskette is properly formatted and mounted, its name and the symbolic link, floppy0, will appear under /floppy.

If nothing appears under the /floppy directory, the diskette is not mounted. See the task titled, "How to Load a Diskette" on page 232. The diskette might also need to be formatted. See the task titled, "How to Format a UFS Diskette" on page 222 or "How to Format a DOS Diskette" on page 228.

3. Move or copy the files or directories.

To ...	Use ...
Copy a file	cp
Copy a directory	cp -r
Move a file or directory	mv

Verification--Copying or Moving Information to a Diskette

To verify a move or copy operation, use the ls command.

Examples--Copying or Moving Information to a Diskette

The first example, below, moves a file (readme.doc) from the current directory to the diskette loaded into the first floppy drive (indicated by /floppy/floppy0). The second example copies a file (readme2.doc) from the current directory to the diskette loaded into the second floppy drive (indicated by /floppy/floppy1). The third example copies a directory (morefiles) and its contents from the /home/smith/directory to the diskette loaded into the first floppy drive.

$ mv readme.doc /floppy/floppy0 $ cp readme.doc /floppy/floppy1 $ cp -r /home/smith/morefiles /floppy/floppy0

· How to Find Out If a Diskette Is Still in Use

1. Become root.

2. Invoke the fuser command.

   The fuser command lists the processes that are currently accessing the CD that you specify.

# fuser -u [ -k ] floppy0

In this command,

-u	Displays the user of the diskette.
-k	Kills the process accessing the diskette.

Example--Finding Out If a Diskette Is Still In Use

In the following example, the processes 6400c and 6399c are accessing the /floppy/floppy0 directory, and the process owners are root and smith, respectively.

# fuser -u /floppy/floppy0 /floppy/floppy0: 6400c(root) 6399c(smith)

You can kill the processes individually (as root), or you can use the fuser command with the -k option, which kills all the processes accessing that file system:

# fuser -u -k /floppy/floppy0 /floppy/floppy0: 6400c(root)Killed 6399c(smith)Killed

The fuser command may not always identify all the killed processes. To be sure, run it again with the -u option.

· How to Eject a Diskette

1. Make sure the diskette is not being used.

   Remember, a diskette is "being used" if a shell or an application is accessing any of its files or directories.

   If you are not sure whether you have found all users of a diskette (a renegade shell hidden behind a desktop tool may be accessing it), use the fuser command, as described in "How to Find Out If a Diskette Is Still in Use" on page 237.

2. Eject the diskette.

$ eject floppy0

On a SPARC system the floppy is physically ejected from its drive, but on an x86 system you'll have to eject the diskette by hand. If you are running Windows, look for an onscreen message that says you can now eject the diskette.

If the diskette is still in use, the following message appears:

/vol/dev/rdiskette0/noname: Device busy

In this case, return to Step 1 and make sure no one is using the diskette, then eject it again.

If the diskette jams, eject it manually by inserting an unfolded paper clip about an inch into the small hole in the front of the drive.

· How to Access Diskettes on Other Systems

You can access a diskette on another system by mounting it manually into your file system--provided the other system has exported its diskette drive according to the instructions in "How to Make Local Diskettes Available to Other Systems" on page 241.

1. Select an existing directory to serve as the mount point or create one.

$ mkdir directory

In this command,

directory.......Is the name of the directory that you create to serve as a mount point for the other system's diskette.

2. Find the name of the diskette you want to mount.

   When you manually mount a remote diskette, you cannot use the floppy0 or floppy1 variables available with your local diskettes. You must use the exact diskette name. To find it, use the ls command on the remote system's /floppy directory. If the automounter is running, you can simply cd to the system whose diskette you want to mount and then use the ls command. If the automounter is not running, you'll have to use another method, such as logging in remotely.

3. As root, mount the diskette.

# mount -F nfs -o rw system-name:/floppy/diskette-name local-mount-point

In this command,

system-name	Is the name of the system whose diskette you will mount.
diskette-name	Is the name of the diskette you want to mount
local-mount-point	Is the local directory onto which you will mount the remote diskette.

Verification--Accessing Diskettes on Other Systems

To verify that the diskette is indeed mounted, use the ls command to list the contents of the mount point.

$ ls /floppy

Example--Accessing Diskettes on Other Systems

This example mounts the diskette named MyFiles from the remote system mars onto the /floppy directory of the local system.

$ cd /net/mars $ ls /floppy floppy0 MyFiles $ su Password: password # mount -F nfs rw mars:/floppy/MyFiles /floppy # exit $ ls /floppy MyFiles

· How to Make Local Diskettes Available to Other Systems

You can configure your system to share its diskettes; in other words, make any diskettes in those drives available to other systems. Once your diskette drives are shared, other systems can access the diskettes they contain simply by mounting them, as described in "How to Access Diskettes on Other Systems" on page 239.

1. Become root.

2. Find out whether the NFS daemon (nfsd) is running.

# ps -ef | grep nfsd root 14533 1 17 10:46:55 ? 0:00 /usr/lib/nfs/nfsd -a 16 root 14656 289 7 14:06:02 pts/3 0:00 /grep nfsd

If the daemon is running, a line for /usr/lib/nfs/nfsd will appear, as shown above. If the daemon is not running, only the /grep nfsd line will appear.

3. Select an option from the following table.

If ...	Then ...
nfsd is running	Go to Step 8
nfsd is not running	Continue with Step 4

4. Create a dummy directory for nfsd to share.

# mkdir /dummy-dir

In this command,

dummy-dir......Can be any directory name; for example, dummy. This directory will not contain any files. Its only purpose is to "wake up" the NFS daemon so that it notices your shared diskettes.

5. Add the following entry into /etc/dfs/dfstab.

share -F nfs -o ro [-d comment] /dummy-dir

When you start the NFS daemon, it will see this entry, "wake up," and notice the shared diskette drive. Note that the comment (preceded by -d) is optional.

6. Start the NFS daemon.

# /etc/init.d/nfs.server start

7. Verify that the NFS daemon is indeed running.

# ps -ef | grep nfsd root 14533 1 17 10:46:55 ? 0:00 /usr/lib/nfs/nfsd -a 16 root 14656 289 7 14:06:02 pts/3 0:00 /grep nfsd

8. Eject any diskette currently in the drive.

# eject floppy0

9. Assign root write permissions to /etc/rmmount.conf.

# chmod 644 /etc/rmmount.conf

10. Add the following lines to /etc/rmmount.conf.

# File System Sharing share floppy*

These lines share any diskette loaded into your system's diskette drives.

11. Remove write permissions from /etc/rmmount.conf.

# chmod 444 /etc/rmmount.conf

This step returns the file to its default permissions.

12. Load a diskette.

--Insert the diskette-- # volcheck -v media was found

The diskette you now load, and all subsequent diskettes, will be available to other systems. To access the diskette, the remote user must mount it by name, according to the instructions in "How to Access Diskettes on Other Systems" on page 239.

Verification--Making Local Diskettes Available to Other Systems

To verify that the diskette is indeed available to other systems, use the share command. If the diskette is available, its share configuration will be displayed. (The shared dummy directory will also be displayed.)

# share - /dummy ro "dummy dir to wake up NFS daemon" - /MyFiles rw ""

Example--Making Local Diskettes Available to Other Systems

The following example makes any diskette loaded into the local system's diskette drive available to other systems on the network.