10 More Discussions You Might Find Interesting
1. Red Hat
Heyas
So i have my custom Fedora with AwesomeWM spin with alots of customizations using the kickstart method for a liveimage.
A few weeks (2-3 months) ago, i've done some changes i cannot remember.
Those changes made the image from bootable to gui, to not booting to gui any more.
Just... (3 Replies)
Discussion started by: sea
3 Replies
2. AIX
i've installed vios 2.2 on blade PS700
there are 2 disk, hdisk0 dan hdisk1 and i want to mirror it
but blv (boot logic volume) does not appear on hdisk1 (bootlist -mode normal -ls) only on hdisk0
i've already did command (bootlist -mode normal hdisk0 hdisk1"
does anyone know the command to... (1 Reply)
Discussion started by: jpmei
1 Replies
3. Solaris
In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
I want to have one binary image that contains both my boot loader as well as the OS(linux) image at pre defined offsets which i can use to program flash . Can anyone help in this direction?
Regards
Subrata (0 Replies)
Discussion started by: subratasaharia
0 Replies
5. Red Hat
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image (by mondorestore) on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
"... (13 Replies)
Discussion started by: shamik
13 Replies
6. Filesystems, Disks and Memory
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
" .....
EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies
7. Red Hat
I'm running redhat linux: 2.6.18-128.1.6.el5xen #1 SMP Tue Mar 24 12:28:27 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux as my Dom0.
I have several other DomU's running on this system, but for this test I've shut them down.
I'm attempting to boot winXP from an image.
Here is my config file:
#... (3 Replies)
Discussion started by: willjw1
3 Replies
8. AIX
My mksysb scripts gives the following text on standard error:
bosboot: Boot image is 22995 512 byte blocks.
How come on a Aix 5200-07 aix-system.
I thought this message meant that the tape (/dev/rmt0) is not bootable,
but I read about a limit of 12 MB and 22995 block is less than 12 MB
... (0 Replies)
Discussion started by: frankwiel
0 Replies
9. AIX
hello
i saved my system this morning, mksysb tape, and i have the message: "boot.image exceeded the size....." i have not the end because the message is disappeared.
where can i find the mksysb message in a log ?
the message is scary ?
thank you (6 Replies)
Discussion started by: pascalbout
6 Replies
10. Filesystems, Disks and Memory
Where can I find the boot floppy disk image file(*.vfd)of SCO UNIX 5.0.5?:confused: (1 Reply)
Discussion started by: whiteknight
1 Replies
mcat(1) General Commands Manual mcat(1)
Name
mcat - dump raw disk image
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 mcat command is used to copy an entire disk image from or to the floppy device. It uses the following syntax:
mcat [-w] drive:
Mcat performs the same task as the Unix cat command. It is included into the mtools package, since cat cannot access remote floppy devices
offered by the mtools floppy daemon. Now it is possible to create boot floppies remotely.
The default operation is reading. The output is written to stdout.
If the -w option is specified, mcat reads a disk-image from stdin and writes it to the given device. Use this carefully! Because of the
low-level nature of this command, it will happily destroy any data written before on the disk without warning!
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://www.gnu.org/software/mtools/manual/mtools.html'
* 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-4.0.18 09Jan13 mcat(1)