Editor Wars! Post: 14462

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Pasting text in VI editor from a different editor

Hi, I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question. How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'? As i see, p & P options does work only within 'vi'.

2. Shell Programming and Scripting

set EDITOR=vi -> default editor not setting for cron tab

Hi All, I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by set EDITOR=vi it does not open a vi editor , rather it do as below..... ///////////////////////////////////////////////////// $ set...

3. Solaris

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :Licen

Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down

LEARN ABOUT REDHAT

mbadblocks

mbadblocks(1) General Commands Manual mbadblocks(1)

Name
mbadblocks - tests a floppy disk, and marks the bad blocks in the FAT

Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.

Description
The mbadblocks command is used to scan an MS-DOS floppy and mark its unused bad blocks as bad. It uses the following syntax:

mbadblocks drive:

Mbadblocks scans an MS-DOS floppy for bad blocks. All unused bad blocks are marked as such in the FAT. This is intended to be used right
after mformat. It is not intended to salvage bad disks.

Bugs
Mbadblocks should (but doesn't yet :-( ) also try to salvage bad blocks which are in use by reading them repeatedly, and then mark them
bad.

See Also
Mtools' texinfo doc

Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.

* To generate a printable copy from the texinfo doc, run the following commands:

./configure; make dvi; dvips mtools.dvi

* To generate a html copy, run:

./configure; make html

A premade html can be found at: `http://mtools.linux.lu' and also at: `http://www.tux.org/pub/knaff/mtools'

* To generate an info copy (browsable using emacs' info mode), run:

./configure; make info

The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.

mtools-3.9.8 02Jun01 mbadblocks(1)