10-26-2016
For some strange reason RecoverEDGE only let me make a floppy, but since it's virtual machine it doesn't have floppy to be formatted. I've read through documentation and it should have more options including ISO that could be burned, but I didn't have that option.
Ultimately I've checked our other deoployed SCO that was virtualised and compared settings and it seems that disk extension is not that necessary and I will just go with easiest solution to add additional disks and create apropriate mountpoints.
Nevertheless thanks for help.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My /tmp is full, and the oracle installation is crashing. How can I increase the size of /tmp, even though I have allocated all the available disk space to other partitions? (2 Replies)
Discussion started by: pkappaz
2 Replies
2. HP-UX
Hi All,
one of the mount point in Hp ux server has reached 95%
its a data base file and can not be deleted.
so i want to know how to increase the size of mount point
i am new to unix ,please help me (1 Reply)
Discussion started by: jyoti
1 Replies
3. Solaris
Hi all,
I have a 130gb HDD of which 95b is taken up by various partitions of windows xp...
I partitioned my HDD and gave solaris 10gb of space, but now owing to some development stuff i need to increase the space!!!
How do i do it!!
Please note that i do have ~20gb of space left still...... (2 Replies)
Discussion started by: wrapster
2 Replies
4. Solaris
Dear all,
I am very new to solaris,
I have installed solaris 10,
i tried installing few softwares into file system, unfortunately system failed to install stating "No space left on device "
i searched few threads and it says, we have to increase root size. where my root size is... (2 Replies)
Discussion started by: radhnki
2 Replies
5. UNIX for Dummies Questions & Answers
Unix protect its password by using salt
It that mean larger the salt size the more secure?
if the salt size increase greatly, will the password still able to be cracked?
thank you for helping (1 Reply)
Discussion started by: cryogen
1 Replies
6. AIX
Hello,
I am working AIX VIO server and extended Virtual Disk of one of the Partition with 10GB. After starting partition, i am not able to see increased size of disk.
Can you please help me what I need to do to increase the size of virtual disk from partition?
Thanks
Kishor
... (7 Replies)
Discussion started by: kishorbhede
7 Replies
7. UNIX for Dummies Questions & Answers
hi guys
I am working on my vmware workstation.
I have a /dev/sdb which is 5GB. I am using LVM.
Now I increase /dev/sdb 2 more GB.
fdisk -l shows 7 GB but pvscan still shows 5GB.
how do I make my system recognize the new 7GB added and be able to add those to my physical volumen and... (1 Reply)
Discussion started by: kopper
1 Replies
8. Solaris
Hi Experts,
I have a problem wih /var. Disk /var is full. After i investigate, i found file /var/log/syslog.0 is growing rapidly. The size is 4.3G. I tried to move syslog.0 to another disk and file was moved successfully.
My question is why size /var can't increase? used space still 100%.
... (7 Replies)
Discussion started by: edydsuranta
7 Replies
9. AIX
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
10. Solaris
Host System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. running Solaris 11.3.
Last login: Tue Sep 19 14:42:42 2017 from xxx.xxx.xxx
Oracle Corporation SunOS 5.11 11.3 June 2017
$ uname -a
SunOS sog01 5.11 11.3 sun4v sparc sun4v
$
Original physical systems: Sun... (0 Replies)
Discussion started by: apmcd47
0 Replies
LEARN ABOUT FREEBSD
fdwrite
FDWRITE(1) BSD General Commands Manual FDWRITE(1)
NAME
fdwrite -- format and write floppy disks
SYNOPSIS
fdwrite [-v] [-y] [-f inputfile] [-d device]
DESCRIPTION
The fdwrite utility formats and writes one and more floppy disks. Any floppy disk device capable of formatting can be used.
The fdwrite utility will ask the user (on /dev/tty) to insert a new floppy and press return. The device will then be opened, and queried for
its parameters, then each track will be formatted, written with data from the inputfile, read back and compared. When the floppy disk is
filled, the process is repeated, with the next disk. This continues until the program is interrupted or EOF is encountered on the inputfile.
The options are as follows:
-v Toggle verbosity on stdout. Default is ``on''. After device is opened first time the format will be printed. During
operation progress will be reported with the number of tracks remaining on the current floppy disk, and the letters I, Z,
F, W, R and C, which indicates completion of Input, Zero-fill, Format Write, Read and Compare of current track respec-
tively.
-y Do not ask for presence of a floppy disk in the drive. This non-interactive flag is useful for shell scripts.
-f inputfile
Input file to read. If none is given, stdin is assumed.
-d device The name of the floppy device to write to. Default is /dev/fd0.
The fdwrite utility actually closes the device while it waits for the user to press return, it is thus quite possible to use the drive for
other purposes at this time and later resume writing with the next floppy.
The parameters returned from device are used for formatting. If custom formatting is needed, please use fdformat(1) instead.
EXAMPLES
The fdwrite utility was planned as a tool to make life easier when writing a set of floppies, one such use could be to write a tar-archive:
tar cf -. | gzip -9 | fdwrite -d /dev/fd0.1720 -v
The main difference from using tar(1)'s multivolume facility is of course the formatting of the floppies, which here is done on the fly, thus
reducing the amount of work for the floppy-jockey.
SEE ALSO
fdformat(1)
HISTORY
The fdwrite utility was written while waiting for ``make world'' to complete. Some of the code was taken from fdformat(1).
AUTHORS
The program has been contributed by Poul-Henning Kamp <phk@FreeBSD.org>.
BUGS
Diagnostics are less than complete at present.
If a floppy is sick, and the inputfile is seekable, it should ask the user to frisbee the disk, insert another, and rewind to the right spot
and continue.
This concept could be extended to cover non-seekable input also by employing a temporary file.
An option (defaulting to zero) should allow the user to ask for retries in case of failure.
At present a suitable tool for reading back a multivolume set of floppies is missing. Programs like tar(1) for instance, will do the job, if
the data has not been compressed. One can always trust dd(1) to help out in this situation of course.
BSD
September 16, 1993 BSD