Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Multi-booting Win2000 and FreeBSD with boot.ini Post 12397 by odinwolph on Friday 28th of December 2001 04:06:51 PM
Old 12-28-2001
Hi DownSouthMoe

Suggest you consider lilo?

Maybe I am barking up thw wrong tree here.... But my preferance in booting differnt OS's would be (without a doubt) LILO.

It's quite flexible.
 

8 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Can I multi-boot that?

http://www.maximumpc.com/features/feature_2002-09-24.html If I was a real man, I'd be able to multi-boot to 37 different OSs on one box... :) (3 Replies)
Discussion started by: auswipe
3 Replies

2. Windows & DOS: Issues & Discussions

Multi booting file systems

Hi all, I'm trying to get Mandrake 9.0, XP & 2K happening on the same machine. I've been reading about osl 2000 (bootmanager) and it says I should convert my Windows (currently ntfs) to fat 32 "if possible". Why? Also, when I connect the linux drive my machine boots straight to Mandrake - no... (2 Replies)
Discussion started by: onestepto
2 Replies

3. Red Hat

Dual boot (Booting Windows from Linux MBR)

Hi , I have two disk installed with Linux(disk 1) and WinXP(disk 2) .Now i am changing Hardisk jumbper manualy to get in to Linux/Windows .I want to configure my REDHAT linux boot manager to list Linux and WindowXP and wanna boot according to my choice . Here is what my fdisk -l shows (Only... (2 Replies)
Discussion started by: gkrishn
2 Replies

4. Ubuntu

system not booting after running local boot scripts

I have two systems in my computer . I update the ubuntu system these days and always interrupt it and exit the system . now the system cannot boot after Running local boot scripts(/etc/rc.local), it just stops there. i have to terminate the gnome display manager. what can i do with it ? thank... (0 Replies)
Discussion started by: tcb3210
0 Replies

5. Windows & DOS: Issues & Discussions

multi boot XP and W2K - how to change

I had single SATA drive win W2K on it. Then I added another SATA and installed XP on it. Now I have a choice of OS when I boot up my PC. After I boot into XP it is D: that has XP installed. I wanted to take and use my 1st disk somewhere else, but quickly learned that I can not boot off of... (1 Reply)
Discussion started by: migurus
1 Replies

6. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

7. Solaris

How to eject boot cdrom after booting from it?

Hey everyone, I currently have a sparcstation 5, and am trying to run some scripts on it without booting off the hard drive. Currently I am using a Solaris 8 install cd to boot into single user mode. However, the scripts I have are on a different CD. What I would like to do is to use the... (6 Replies)
Discussion started by: idlechatter
6 Replies

8. Red Hat

Booting 2nd mirrored boot disk

Hi guys, thanks for helping out. If you have two boot disk mirrored and your primary boot disk fails, how will you boot the system from the second disk? Thank you very much for your assistance on this matter. Arrey (5 Replies)
Discussion started by: cjashu
5 Replies
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 02:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy