How do you create your own boot disk with a ramdisk image as well??

How do you create your own boot disk with a ramdisk image as well??

Post by Damon Atki » Wed, 11 Aug 1993 11:19:23


        How can you create a boot disk like the orginal installation boot
disk, however with a different ramdisk contents?

Thanks Damon.

 
 
 

How do you create your own boot disk with a ramdisk image as well??

Post by Kevin Burt » Wed, 11 Aug 1993 23:46:15



Quote:>    How can you create a boot disk like the orginal installation boot
>disk, however with a different ramdisk contents?

>Thanks Damon.

    To create a boot disk, all you have to do is "dd if=/Image of=/dev/fd0".
To set whatever parameters you want (startup video mode, ramdisk, etc.)
type rdev -h and you will get a list of options. E-mail me if you have any
problems or questions. This will give you a custom boot disk for your
system. As far as a custom install disk, I'm not sure, as it's compressed.
    You might want to e-mail someone at SLS.

Kevin

P.S. dd only works on a formatted floppy. (I think)

 
 
 

How do you create your own boot disk with a ramdisk image as well??

Post by David C. Nie » Thu, 12 Aug 1993 06:20:22



Quote:>    To create a boot disk, all you have to do is "dd if=/Image of=/dev/fd0".
>To set whatever parameters you want (startup video mode, ramdisk, etc.)
>type rdev -h and you will get a list of options. E-mail me if you have any
>problems or questions. This will give you a custom boot disk for your
>system. As far as a custom install disk, I'm not sure, as it's compressed.

The above command should be fine for Linux.
In systems like Suns that, unlike Linux, don't have highly optimized floppy
drivers, you should use something like:

gzip -cd Image.gz | dd of=/dev/rfd0c obs=18432

The "obs" parameter is the output block size, which nicely buffers up a 1.44MB
floppy track.  For a 1.2MB floppy, use obs=15360.  The device will vary with
the UN*X being used.

Quote:>P.S. dd only works on a formatted floppy. (I think)

That is correct.  However, it only has to be low-level formatted, and any
junk or MS-DOS filesystems on it are erased.
---

 
 
 

1. New Booting Image and Ramdisk Image for Alpha DS10/XP1000/DS20

We developed Alzza Linux 6.0 for Alpha systems at September.
Alzza Linux is 100% compatible Korean Linux version of Redhat.
But we removed unaligned trap in RedHat6.0 and included new booting
images for DS10/XP1000/DS20.
If you have some problems using generic.img in Redhat6.0 and you are not
satisfied with RedHat6.0,
then I recommand our Linux for Alpha system.

Ftp site is ftp://pvmcube4.snu.ac.kr
In this site, we also uploaded iso images for our Linux.
New booting image is 'ds10.img' and 'ramdisk.img'... We tested only 4
arch. - ds10, ds20, xp1000, 164LX, 164UX -
If you are not Korean, then modify the '/etc/profile.d/hangul-init.sh'
and /etc/profile.d/hangul-init.csh' as below.
set LANG variables as 'c' not 'ko'.

We will release 6.1 version of Alzza Linux for Intel/Alpha next monday.
New 6.1 version is somewhat different from Redhat6.1 and S.u.S.E. 6.1

If you have some problem in downloading in that site, send mail to me.
We will migrate new server at next week.

--
Lee, Bo-sung
Director of Cluster Team, Linux One Inc.
Invited Researcher, ETRI Supercomputer Center


2. Stop KDE Autostart & xmkmf Question

3. How to create your own boot disk.

4. [PATCH] IDE clean 12 3rd attempt

5. Q: Need Script to create own boot disks

6. Installing QT 3.0.0 beta6

7. Booting disk image from DOS?

8. which distribution?

9. Using FBK to Create a Ramdisk Image

10. Creating a boot disk from an old version of DOS

11. - ramdisk.image.gz (0/78) Re: potato on beige G3: where is ramdisk?

12. Creating a boot Disk for RH5 when DOS and RH linux installed.

13. problem with creating ramdisk: kernel loads, but hangs when it tries to mount ramdisk