Sponsored Content
Operating Systems SCO Need to make an Installation CD Post 302542810 by Corona688 on Thursday 28th of July 2011 04:21:30 PM
Old 07-28-2011
Floppy emulation is part of the spec for bootable CDROMs, so if you have mkisofs and can image one of your SCO boot floppies, you could do this:

Making a bootable CD from a bootable floppy image

That might be able to boot the first floppy. You wouldn't be able to read in successive floppies that way. If the first floppy is enough to get CDROM support going, you might be able to cram the rest of the files just into the ISO image -- the files would show up seperately, the first floppy in A:, the rest accessed by however SCO usually accesses CDROM drives.
 

10 More Discussions You Might Find Interesting

1. Solaris

installation of Solaris: installation bypasses network config.

hello solaris friends, I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url: http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png I'm able to install it all the way through but I get no... (2 Replies)
Discussion started by: cadmiumgreen
2 Replies

2. Linux

Error in issuing a make and make install

Hi, Recently I install a package and try to do a make and make install. However, in the make it gives me below error:- make:Nothing to be done for 'install-exec-am' make:Nothing to be done for 'install-data-am' Can anyone please explain to me what does this mean? I have been trying... (1 Reply)
Discussion started by: ahjiefreak
1 Replies

3. Solaris

how do I make my workstation an installation server for a remote server?.

Is there a way I can make my Sun workstation as a installation server for a remote server?. (3 Replies)
Discussion started by: calsum
3 Replies

4. Solaris

Solaris 10 Core Installation wsftpd make problem

Hello, I have just installed a Solaris10 server with core installation option. I tried to install vsftp on this server but it's asking me "make" to compile the program. But I could'nt find make. I searched that on web and installed SUNWarc SUNWbinutils SUNWgcc SUNWgccruntime SUNWgcmn... (2 Replies)
Discussion started by: shadowfaxxxx
2 Replies

5. UNIX for Advanced & Expert Users

make test fails for DBD::Oracle installation

I've already installed the DBI Perl Module with no issues and now I'm attempting to install the DBD::Oracle driver on a Red Hat Enterprise 4 server and am having some trouble. I've checked through the forums and haven't seen anything helpful at this point. Everything goes fine during the perl... (1 Reply)
Discussion started by: pstrosnyder
1 Replies

6. Solaris

Gani Network Driver Won't Install - make: Fatal error: Don't know how to make targ...

I attached a README file that I will refer to. I successfully completed everything in the README file until step 4. # pwd /gani/gani-2.4.4 # ls COPYING Makefile.macros gem.c Makefile Makefile.sparc_gcc gem.h Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies

7. UNIX for Dummies Questions & Answers

Difference between configure/make/make install.

Hi, While installation of apache on linux, we perform the below tasks. 1) Untar 2) configure 3) make 4) make install. I wanted to understand the difference and working of configure/make/make install. Can any one help me understanding this? Thanks in advance. (1 Reply)
Discussion started by: praveen_b744
1 Replies

8. Solaris

mailman installation error during make install

I have problem installing mailman 2.5 onto Solaris10 sparc. During make instal, the error message I got is as follows. .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /var/mailman/data if ; \ then \ rm -rf... (0 Replies)
Discussion started by: cchoe
0 Replies

9. Programming

Issue with make, no rule to make target etc.

I have been trying to split up my src directory to clear out files that are not re-compiled very often. Now I have the following setup in my trunk, trunk/bld trunk/src/ trunk/src/src_server trunk/makefile.linux In the make file, I have compile rules SOURCELOC = src # compile src c++... (4 Replies)
Discussion started by: LMHmedchem
4 Replies

10. Red Hat

How to make boot.iso image from rhel6 installation dvd iso ?

Hello Everyone, Can anyone let me know how to make minimal boot.iso from rhl6 installation dvd iso image. I have a dvd image with me but i want to make just a minimal boot media. Somehow it is not shipped with dvd iso. I know we can download boot.iso from redhat site but is there any anyway we... (5 Replies)
Discussion started by: Rohit Bhanot
5 Replies
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy SYNOPSIS
/sbin/mkrescue - make 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 with: --append "", the null string. --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 sec- tors 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 cdrecord 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 loopback 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
lilo(8), lilo.conf(5), mkfs(8), dd(1), mount(8), mkinitrd(8), mkisofs(8), cdrecord(1). AUTHOR
John Coffman <johninsd@san.rr.com> (3.0) 16 Nov 2004 MKRESCUE(8)
All times are GMT -4. The time now is 03:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy