Sponsored Content
Full Discussion: Problem with booting
Top Forums UNIX for Dummies Questions & Answers Problem with booting Post 13640 by LivinFree on Tuesday 22nd of January 2002 01:57:42 AM
Old 01-22-2002
Depending on the bootloader you're using (most likely lilo, check out the HOWTOs at this link:
http://www.linuxdoc.org/HOWTO/HOWTO-...os.html#OSBOOT
You'll most likely want the "Multiboot-with-LILO" doc...

Hope that helps.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Booting Problem

Hai I have installed win 98 o.s in my system after that i have installed Red Hat Linux 7.0,there is a problem in dual booting,by default win98 is being booted, when i insert bootable linux floppy linux is loaded My doubt how to overwrite windows MBR and palce the lilo in MBR.so that it... (2 Replies)
Discussion started by: rajashekaran
2 Replies

2. UNIX for Dummies Questions & Answers

<< booting problem with redhat 8.0 >>

i have the Redhat installed in this Hard Drive and i wanna use it in this old computer of mine.. it works fine in my new computer.. but when i put it in my old one.. which is.. P1 150MHz 32MBramz it wont load the kernal and keeps on restarting the computer.. keeps on goin like this.. i get the GRUB... (2 Replies)
Discussion started by: dezithug
2 Replies

3. Solaris

Problem with 280R not booting

The box is in Houston, and I am in Dallas. Anyway, I do have serial access to the console. The box is hanging just after the WARNING's for the SDS modules not loading (normal boot message). I booted off CD, and mounted up all the file systems. Everything looked normal, and I could not find any... (3 Replies)
Discussion started by: 98_1LE
3 Replies

4. Solaris

Booting problem Veritas

Hi , I am having 490 Sun Fire Server ,Server having Two 72 GB each Disk.Disk are under veritas VM 4 control. Both disk are mirred with veritas VM4. Fisrt disk is encapsulate and other disk is mirred.System is working Fine but when I removed Fitrst Disk and reboot the system it does not boot from... (4 Replies)
Discussion started by: pradeeprajput_k
4 Replies

5. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

6. Ubuntu

Problem while booting linux

Hi all, We are using linux Redhat 9. While booting the server, it says /proc not mounted and it says "Segmentation fault" and doesn't continue with booting. Basically, it started while we inserted a pen drive and removed it without mounting and un mounting it. After removing the pen drive &... (1 Reply)
Discussion started by: mjdarm
1 Replies

7. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

8. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies

9. AIX

Problem to booting up p730

Hi Everyone, We have IBM p730 that I am trying to booting up to AIX 7.1. But it stops at RUNTIME. C7004087 C7004091 C7004091 (show is code number twice) STANDBY RUNTIME The explanation for C7004091 is the final IPL status progress code to be displayed before the system reaches... (5 Replies)
Discussion started by: lilyn
5 Replies
BOOTCD2DISK.CONF(5)						   bootcd utils 					       BOOTCD2DISK.CONF(5)

NAME
bootcd2disk.conf - configuration file for bootcd2disk DESCRIPTION
The file bootcd2disk.conf contains configuration option for the bootcd2disk(1) program of the same named package. The file must be located in the configuration directory which is usually /etc/bootcd. Blank lines are ignored and lines with leading # are comments. Values have to be set with name=value You can use a wildcard named DISK<number> to specify partitions instead of e.g. /dev/hda<number>. DISK was replaced by $DISK, which can be set by the same named parameter. FORMAT
ERRLOG=<path> Write all errors to this file. Required. DISK=<device|auto> Specify the disk you want to use for the installation, e.g. /dev/hda for the first IDE drive in the system. If you use "auto", bootcd2disk automatically try to use the first hard disk in the system. Required. SFDISK=<partitions in sfdisk syntax|auto> Configuration options for sfdisk, which creates the partitions for us. If you use "auto", we create default partitions "/", "/boot" and a swap partition. Required. VFAT=<partitions separated by spaces> Configure vfat partitions there, if you need some. Optional. EXT2FS=<partitions separated by spaces|auto> Specify the partitions with ext2 or ext3 (see next parameter) here. This partitions would be created and formated. If you use "auto", the "/" and the "/boot" partition would be created. Required. EXT3FS=<yes|no> Enter "yes" If you want ext3 partitions. If you use "auto", the systems use ext3 partition, if the kernel supports it. Required. SWAP=<partitions separated by spaces|auto> The partitions configured there are created as swap. If you use "auto", one swap partition is been created. Required. MOUNT=<mount <partition> <mountpoint>; ... |auto> Insert here the mount command line to mount your partitions or use "auto". Required. UMOUNT=<umount <mountpoint>; ... |auto> Insert here the mount command line to umount your partitions or use "auto". Required. FSTAB=<entries for the systems fstab |auto> Configure here all partitions you need to mount after target systems startup in the fstab syntax or use "auto". Required. LILO=<entries for the systems lilo.conf |auto> This variable includes the complete configuration file for the lilo bootloader on the target system. Use "auto" for automatically generated file. Only required, if you want LILO. Make sure GRUB and GRUB2 are defined as empty if you want to use LILO. GRUB=<entries for the systems grub/menu.lst |auto> This variable includes the complete configuration file for the grub bootloader on the target system. Use "auto" for automatically generated file. Only required, if you want GRUB. GRUB2=<entries for the systems grub/grub.cfg |auto> This variable includes the complete configuration file for the grub2 bootloader on the target system. Use "auto" for automatically generated file. Only required, if you want GRUB 2. GRUBBOOTDIR=<number of partition which contains grub-dir | 0> This variable defines the partition where the grub bootloader information is stored. You want to use this if you have defined your own partition layout and the grub information is not on the first partition. Remember that grub starts counting partitions at 0. So if you decided that /boot is on partition /dev/sda2 you need to set the parameter to 1. GRUBBOOTDISK=<grub disk> This should be "hd0". Only if your BIOS sees another disk as the first disk you may have to change it. GRUBDEVICEMAP=<auto|no|<value>> GRUBDEVICEMAP="auto" means, bootcd2disk deletes the original device.map, so that it will be auto-created by grub again. This should work also when installing on different hardware with different disks. GRUBDEVICEMAP="no" means bootcd2disk does not change device.map. This should work if a bootcd is installed on the original hardware Everything else will be used as new value for device.map. ELILO=<entries for the systems elilo.conf |auto> Same as LILO but for the elilo bootloader on ia64 systems. Use "auto" for automatically generated file. Only required, if you want ELILO. SSHOSTKEY=<yes|no> If you are using ssh it is helpful to have a unique ssh hostkey for each system installed with bootcd2disk. This will be generated if this option is set to "yes". Required. UDEV_FIXNET=<yes|no> If you are using the udev filesystem and want to install the image on other machines, you need to set this to "yes" because the net- work interfaces are hardwired in /etc/udev/rules.d/z25_persistent-net.rules (etch) or in /etc/udev/rules.d/70-persistent-net.rules (lenny) and we must remove them. Required. IMAGEURL=<url> If bootcd2disk is slow on your system (because of a slow CD/DVD drive or the HP ILO virtual CD interface), you can use a image server to get the bootcdimage from. bootcd2disk use the swap partition of your upcoming system as temporary space and copy the image from the configured image server to this partition and use it as image. May be overwritten from command line "-url". Need the following parameter "IMAGEURL". Required. The <url> is used with wget, all url syntax from wget are possible. Please use a ip because of failed DNS and you need also the con- figured ip interface. May be overwritten from command line (-url). Required. example: IMAGEPURL="https://192.168.1.1:81/cdimage.iso" function before_copy() { return } If you want some action before copying the system to the target disk, like remount or other thinks, you can write this action to the body of this function. Optional. function after_copy() { return } If you want some action after copying the system to the target disk, like remount or other thinks, you can write this action to the body of this function. Optional. SEE ALSO
bootcd2disk(1), bootcd(1), bootcdflopcp(1), bootcdwrite(1) AUTHOR
This manual page was written by Carsten Dinkelmann <carsten.dinkelmann@foobar-cpa.de>, for the Debian GNU/Linux system (but may be used by others). bootcd2disk.conf 2007-04-04 BOOTCD2DISK.CONF(5)
All times are GMT -4. The time now is 09:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy