public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: tcheer@gmx.de (Eric Tchepannou)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about the dd command
Date: Wed, 18 Sep 2002 11:02:58 +0100 (BST)	[thread overview]
Message-ID: <200209181002.g8IA2w52001416@darkstar.example.net> (raw)
In-Reply-To: <18955.1032342092@www26.gmx.net> from "Eric Tchepannou" at Sep 18, 2002 11:41:32 AM

Hi,

> I am trying to build a boot image in order to boot from a CD device. I have
> already created all the parts ( Kernel, Lilo and Rootfs ) and try to bring
> them together. I first copied it on a floppy in order to see wether I could
> boot from it and  it worked. In the Linux-Bootdisk-HOWTO It is said that on
> should transfer the rootfs with the following command
> 
> dd if=rootfs of=/dev/fd0 bs=1k seek=KERNEL_BLOCKS 
> 
> I calculated the KERNEL_BLOCK value in my case and applied the command. It
> is supposed to transfer the rootfs file into the same floppy containing the
> kernel. I am surprised to see that with a ls-command the rootfs.gz is invisible
> on the floppy, though the boot process from floppy works properly. Later i
> created an image of the floppy ( dd if=/dev/fd0 of=boot.img bs=10k count=144
> as in the Linux-Bootdisk-HOWTO ), created an iso file from it with mkisofs and
> copied it on CD. Now I can't boot the image from this CD!

I'm assuming that you're trying to create a bootable CD for an X86 machine.

In that case, this is not how bootable CDs work.  You need to look up the 'El-Torito' bootable CD specs, and take it from there.

John.

  reply	other threads:[~2002-09-18  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  9:41 Question about the dd command Eric Tchepannou
2002-09-18 10:02 ` jbradford [this message]
2002-09-18 23:48 ` Bourne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200209181002.g8IA2w52001416@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tcheer@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox