Sponsored Content
Operating Systems HP-UX Error upon completion of ddcommand Post 302137595 by porter on Tuesday 25th of September 2007 10:37:48 PM
Old 09-25-2007
Old machines don't like booting from things which are not 512 byte sectors. For example, it can be tough finding CD-ROMs these days that old machines can use.

What device are you using?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Tar error after backup completion

After perfomring a remote backup from HP-UX to a SUN, it prompt the following error. Can you please advise what does this error means? How to retify this error? "dd: unexpected short write, wrote 0 bytes, expected 10240 205802517+126 records in 10290129+0 records out" The command used is ... (1 Reply)
Discussion started by: gelbvonn
1 Replies

2. Shell Programming and Scripting

file name completion

I'ld like to enable file name completion in ksh88 on AIX 5.2. My terminal is set to xterm. I've set the shell editor to emacs and ampped the arrow keys. Is there a way to map the tab key to a command like ESC= or any other file name completion command in emacvs that I may be not aware of since I'm... (1 Reply)
Discussion started by: rein
1 Replies

3. UNIX for Advanced & Expert Users

line completion in vim

how we achive line completion and word completion in vim editor? (2 Replies)
Discussion started by: lakshmananindia
2 Replies

4. UNIX for Dummies Questions & Answers

Monitoring SCP for completion

I have several servers, A, B, & C that run various routines then scp the results to server X. On X I then have to do some data manipulation with the received files before sending the files on to another location. Because of policy here I cannot pull the files from servers A, B & C, but have to... (2 Replies)
Discussion started by: thumper
2 Replies

5. Shell Programming and Scripting

bash completion

hello, I have been trying for a couple days to figure this out to no avail. I am converting some csh code to bash. I have converted everything except the completion code. #bashrc (I set this alias in my bashrc) alias test='source ${PATH}/test.sh' #${PATH}/test.sh (returns some aliases and... (0 Replies)
Discussion started by: platypuus
0 Replies

6. UNIX Desktop Questions & Answers

TAB completion in cygwin

Hi there, I ve been using cygwin for some time now without any problems. However, recently I ve mapped a new drive on Windows and are now having problems with TAB completion for awk scripts in cygwin on this newly mapped drive (cygdrive t). I can access and run all files but cygwin doesn't do... (5 Replies)
Discussion started by: Tommes
5 Replies

7. UNIX for Dummies Questions & Answers

Background Process Completion

I have my unix machine configured to run locate.updatedb on login in the background and after it completes, when I run a command such as ls-- the console returns the results of ls and + Done sudo /usr/libexec/locate.updatedbIs there... (3 Replies)
Discussion started by: Prodiga1
3 Replies

8. Shell Programming and Scripting

inotifywait to wait until completion

Hi, I am using inotifywait to monitor a directory where files are being transferred into. I want inotifywait to tell me when a file has been completely transferred not just part of it. I tried "create", "close" and "close_write" but it seems that inotifywait always gets triggered even if the... (4 Replies)
Discussion started by: jejeking
4 Replies

9. Shell Programming and Scripting

Identifying the file completion

Hi, A script is running for multiple databases so data is also being populated for multiple DBs in a.txt file. I need to rename this file once all the data is populated. Kindly suggest me How can I check once file is populated completely before renaming? Thanks in advance. (3 Replies)
Discussion started by: ravigupta2u
3 Replies

10. Shell Programming and Scripting

Bash-Completion, an example

Hello I've followed several bash-completion threads, usualy none were answered, because of obvious reasons. (of which i'm just aware since a day or a few) Non-the-less, because i was writing scripts, i never considered it to be possible to add this functionality. Also, because i though that... (0 Replies)
Discussion started by: sea
0 Replies
mpartition(1)						      General Commands Manual						     mpartition(1)

Name
       mpartition - partition an MSDOS hard disk

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 mpartition command is used to create MS-DOS filesystems as partitions.  This is intended to be used on non-Linux systems, i.e.  systems
       where fdisk and easy access to Scsi devices are not available.  This command only works on drives whose partition variable is set.

       mpartition  -p drive mpartition -r drive mpartition -I [-B bootSector] drive mpartition -a drive mpartition -d drive mpartition -c [-s sec-
       tors] [-h heads] [-t cylinders] [-v [-T type] [-b begin] [-l length] [-f]

       Mpartition supports the following operations:

       p      Prints a command line to recreate the partition for the drive.  Nothing is printed if the partition for the drive is not defined, or
	      an inconsistency has been detected.  If verbose (-v) is also set, prints the current partition table.

       r      Removes the partition described by drive.

       I      Initializes the partition table, and removes all partitions.

       c      Creates the partition described by drive.

       a      "Activates" the partition, i.e. makes it bootable.  Only one partition can be bootable at a time.

       d      "Desactivates" the partition, i.e. makes it unbootable.

       If no operation is given, the current settings are printed.

       For partition creations, the following options are available:

       s sectors
	      The number of sectors per track of the partition (which is also the number of sectors per track for the whole drive).

       h heads
	      The  number of heads of the partition (which is also the number of heads for the whole drive).  By default, the geometry information
	      (number of sectors and heads) is figured out from neighbouring partition table entries, or guessed from the size.

       t cylinders
	      The number of cylinders of the partition (not the number of cylinders of the whole drive.

       b begin
	      The starting offset of the partition, expressed in sectors. If begin is not given, mpartition lets the partition begin at the  start
	      of the disk (partition number 1), or immediately after the end of the previous partition.

       l length
	      The  size  (length) of the partition, expressed in sectors.  If end is not given, mpartition figures out the size from the number of
	      sectors, heads and cylinders.  If these are not given either, it gives the partition the biggest	possible  size,  considering  disk
	      size and start of the next partition.

       The following option is available for all operation which modify the partition table:

       f      Usually,	before	writing  back  any  changes to the partition, mpartition performs certain consistenct checks, such as checking for
	      overlaps and proper alignment of the partitions.	If any of these checks fails, the partition table is not changes.  The	-f  allows
	      you to override these safeguards.

       The following options are available for all operations:

       v      Together with -p prints the partition table as it is now (no change operation), or as it is after it is modified.

       vv     If the verbosity flag is given twice, mpartition will print out a hexdump of the partition table when reading it from and writing it
	      to the device.

       The following option is available for partition table initialization:

       B bootSector
	      Reads the template master boot record from file bootSector.

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							     mpartition(1)
All times are GMT -4. The time now is 10:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy