Sponsored Content
Operating Systems SCO unable to find a root hard disk Post 302215428 by spredwood on Wednesday 16th of July 2008 09:34:16 AM
Old 07-16-2008
Our last server had not floppy, so I burnt them to a CD. Bit of a waste puting 1M on a CD but, they are cheaper than floppy disks nowadays
 

9 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Hard Disk

I have a cuestion. How Can I to add other hard disk to my computer? I need to configurate anyone? (4 Replies)
Discussion started by: hmaraver
4 Replies

2. Solaris

Solaris 10 - How to find the total size of my hard disk?

Friends, I have an 80 GB HDD, but I wish to know if there is a direct command in Solaris 10 to find out the size of my hard disk (similar to fdisk -l in Linux). Thank you saagar (3 Replies)
Discussion started by: saagar
3 Replies

3. UNIX for Dummies Questions & Answers

Hard Disk at 99% Help!

:eek: I use this Solaris to run CMS a call acounting software package for my job. No one could run reports today because it said the this when you logged on "The following file systems are low, and could adversely affect server performance: File system /: 99%full" Can some one please explain... (9 Replies)
Discussion started by: mannyisme
9 Replies

4. SCO

unable to find a root hard disk on vmware

Hello guys i need some guidence on why i am getting the unable to find a root disk and how i can overcome this problem. Thanks :confused:Paddyl (1 Reply)
Discussion started by: paddyl
1 Replies

5. SCO

declare disk driver for IDE hard disk

hi I've a fresh installation of SCO 5.0.7 on the IDE hard disk. For SCSI hard disk I can declare, for example blc disk driver using: # mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies

6. Shell Programming and Scripting

Unable to preserve hard links. Why?

Hi, I'm trying to create a Makefile that would automate remastering Knoppix distribution. As a part of the process I am mounting using linux cloop device a compressed filesystem and copy the content out of it to separate dir. However during that process I need to preserve hard links and it... (9 Replies)
Discussion started by: dpc.ucore.info
9 Replies

7. Linux

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

Hi all, I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies

8. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

9. Solaris

Unable to find utilized disk space on zone server.

Hi, I am unable to find remaining space on solaris 10. below is output. I am facing this issue on zone server. bash-3.00# df -h / Filesystem size used avail capacity Mounted on / 59G 59G 0K 100% / bash-3.00# pwd / bash-3.00# du -sh * 1K File_Stores 19K TT_DB 9K app 1K bin... (4 Replies)
Discussion started by: manoj.solaris
4 Replies
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
All times are GMT -4. The time now is 09:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy