Sponsored Content
Full Discussion: Making boot disks in SCO
Top Forums UNIX for Dummies Questions & Answers Making boot disks in SCO Post 6781 by LowOrderBit on Wednesday 12th of September 2001 01:10:05 PM
Old 09-12-2001
Making boot disks in SCO

This last monday the inittab file became corrupted and the server refused to start... A set of boot / root disks made from another SCO server saved the day.. Anyway, I would like to make a set from the production server just so I have a set created from that machine. The command I would be using is makedv fd .. Will this cause any problems if I do this while the machine is being used??

Also, does anyone know what fms-httpd is / does???

thanks..

e0-
 

10 More Discussions You Might Find Interesting

1. Solaris

making a boot server

I'm trying to make a boot server so I can net boot another machine that doesnt have a cdrom. I want to boot this machine so i can go in and erase the (unknown to us) root password. on solaris 9, i ran setup_install_server -b /export/install I entered the clients machines mac address and ip in... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

2. Solaris

Solaris 10 x86 Installation Will Not Boot From CD Disks

Problem: Am trying to install Solaris 10 x86 on a desktop PC (PC details unspecified) from downloaded iso images (5 in all) on 5 CD disks. These were downloaded from the Sun website and unzipped. I install Disk 1of 5 into the CD drive and then restart the machine, thinkng that it will launch... (5 Replies)
Discussion started by: RobSand
5 Replies

3. UNIX for Dummies Questions & Answers

using grub to boot from different disks

Hello, I'm working on a x86 machine with 3 disks installed. I need to boot from disk to disk, but I cannot figure out how to do this using Grub. The O/S is Solaris 10 and grub version is 0.95 Can anyone give me any help with this? Thanks, James. (0 Replies)
Discussion started by: eeijmae
0 Replies

4. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

5. UNIX for Advanced & Expert Users

Making one binary image containing boot loader and linux

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

6. UNIX for Advanced & Expert Users

how to create multiple-boot system with disks mirrored(RAID1+0) and disk alone

I have a HP proliant ML 570 G3 with two 146GB disk drives mirrored(RAID1+0) windows server 2003 was installed on that disk. I will add a disk.(scsi 300GB) I will install Linux on that additional disk. I want to create multiple-boot system. Is it possible? I wanna know how to create... (0 Replies)
Discussion started by: lifegeek
0 Replies

7. Solaris

Persistent boot disks issue

Hi all, please i need your help urgently I am faced to a serious boot disks issue on an Sun Fire E2900. The system run with two disque in zpool . The operating system is Solaris 10 (ZFS) The first time the issue occured, i got the error below on the two disks: Apr 7 08:04:33... (0 Replies)
Discussion started by: saki_jumeau
0 Replies

8. Solaris

Sun Fire 480 - devfsadm -C not working after replacing one of the boot disks

Our SunFire 480 - one of the boot disks failed. It is mirrored with VxVm. I followed the exact steps that is detailed in the veritas and sun guides (I can not post the URL since I don't have 5 posts yet.) After removing the failed disk, I ran devfsadm -C -c disk and it still shows the device... (7 Replies)
Discussion started by: jtamminen
7 Replies

9. SCO

SCO Will Not Boot

Hello to all , I am new to this forum and also i have very less knowledge about sco unix, but I have good knowlage about Dos-Windows file systems since 1990 year :) and i am a professional IT person about Networking and computer hardware but as i said not know much about Unix based systems :( ,... (7 Replies)
Discussion started by: meraklinext
7 Replies

10. UNIX for Beginners Questions & Answers

SCO OpenServer 5 Will Not Boot

We have a legacy system that runs on SCO OpenServer 5.0.6, and I've rebuilt the server a couple of times so we can have access to old historical data. That system suddenly went offline for no known reason, and I know that the configuration has not been altered, there is nobody with access to the... (63 Replies)
Discussion started by: spock9458
63 Replies
FS(4)							     Kernel Interfaces Manual							     FS(4)

NAME
fs - file server, dump SYNOPSIS
none DESCRIPTION
The file server is the main file system for Plan 9. It is a stand-alone system that runs on a separate computer. It serves the Plan 9 protocol on a variety of networks including Datakit/URP, Ethernet IL/IP and Cyclone fiber direct connections. The name of the main file server at Murray Hill is bootes. The file server normally requires all users except to provide authentication tickets on each attach(5). This can be disabled using the noauth configuration command (see fsconfig(8)). The user none is always allowed to attach to bootes without authentication but has minimal permissions. Bootes maintains three file systems on a combination of disks and write-once-read-many (WORM) magneto-optical disks. other is a simple disk-based file system similar to kfs(4). main is a worm-based file system with a disk-based look-aside cache. The disk cache holds modified worm blocks to overcome the write- once property of the worm. The cache also holds recently accessed non-modified blocks to speed up the effective access time of the worm. Occasionally (usually daily at 5AM) the modified blocks in the disk cache are dumped. At this time, traffic to the file sys- tem is halted and the modified blocks are relabeled to the unwritten portion of the worm. After the dump, the file system traffic is continued and the relabeled blocks are copied to the worm by a background process. dump Each time the main file system is dumped, its root is appended to a subdirectory of the dump file system. Since the dump file sys- tem is not mirrored with a disk cache, it is read-only. The name of the newly added root is created from the date of the dump: /yyyy/mmdds. Here yyyy is the full year, mm is the month number, dd is the day number and s is a sequence number if more than one dump is done in a day. For the first dump, s is null. For the subsequent dumps s is 1, 2, 3, etc. The root of the main file system that is frozen on the first dump of March 1, 1992 will be named /1992/0301/ in the dump file sys- tem. EXAMPLES
Place the root of the dump file system on /n/dump and show the modified times of the MIPS C compiler over all dumps in February, 1992: 9fs dump ls -l /n/dump/1992/02??/mips/bin/vc To get only one line of output for each version of the compiler: ls -lp /n/dump/1992/02??/mips/bin/vc | uniq Make the other file system available in directory /n/bootesother: mount -c /srv/boot /n/bootesother other SOURCE
/sys/src/fs SEE ALSO
yesterday(1), srv(4), fs(8) Sean Quinlan, ``A Cached WORM File System'', Software - Practice and Experience, December, 1991 FS(4)
All times are GMT -4. The time now is 12:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy