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
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Process control initialization SYNOPSIS
/sbin/init [0123456789MmQqSs] DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in the inittab file. The init program reads and processes the entries in the inittab file. The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init that tell it which run level to change to. Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a message on the console stating the location of the virtual console. To change the run level, the user specifies either the 0, 2, 3, or s flag. For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to be handled for that level. Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi- ately reexamine the inittab file, invoke the init program with the q flag. FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from /etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter- minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single user state with only the essential kernel services. FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8) Calls: kill(2), reboot(2) Files: inittab(4) delim off init(8)
All times are GMT -4. The time now is 10:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy