diskless boot situation

I would like to set up my client PC to remotely boot DOS from my Linux
server (Debian 3.0).

I have created an image of the boot disk, and I've placed it in
/tftpboot/boot.img. In my dhcpd.conf, under the host that will be booting
this image, I've put "filename "/tftpboot/boot.img"".

My client has a Gigabyte M/B with onboard Ethernet that supports PXE.

What more do I need to do to get this all to work? I would definitely prefer
a solution that doesn't require running any more software on the server
(i.e. I would ideally only need to run tftpd and dhcpd).

Ideas are welcome.

C3 wrote:

> I would like to set up my client PC to remotely boot DOS from my Linux
> server (Debian 3.0).
>
> I have created an image of the boot disk, and I've placed it in
> /tftpboot/boot.img. In my dhcpd.conf, under the host that will be booting
> this image, I've put "filename "/tftpboot/boot.img"".
>
> My client has a Gigabyte M/B with onboard Ethernet that supports PXE.
>
> What more do I need to do to get this all to work?

Switch on the client ;-)

Really - what you want it to configure the bootp server.
DHCP wasn't made for this, you want bootp.
All you need to do is specify the MAC address of the client in the
config file and specify what image you want to load.

Then boot - and watch the magic happen ;-)



--
J

All your bits are belong to us - again.

I thought DHCP was a superset of BOOTP?

Am I doing everything I need to? Do I need to do anything to my client?

"Jeroen Geilman" <(E-Mail Removed)> wrote in message
news:jngj02-(E-Mail Removed)...
> C3 wrote:
>
> > I would like to set up my client PC to remotely boot DOS from my Linux
> > server (Debian 3.0).
> >
> > I have created an image of the boot disk, and I've placed it in
> > /tftpboot/boot.img. In my dhcpd.conf, under the host that will be
booting
> > this image, I've put "filename "/tftpboot/boot.img"".
> >
> > My client has a Gigabyte M/B with onboard Ethernet that supports PXE.
> >
> > What more do I need to do to get this all to work?
>
> Switch on the client ;-)
>
> Really - what you want it to configure the bootp server.
> DHCP wasn't made for this, you want bootp.
> All you need to do is specify the MAC address of the client in the
> config file and specify what image you want to load.
>
> Then boot - and watch the magic happen ;-)
>
>
>
> --
> J
>
> All your bits are belong to us - again.

Help! The client manages to get an IP address from the DHCP server and then
starts trying to download the boot image (1.44MB), but it then gives the
error "TFTP: Too many options" and then quits.

There must be something I have to set up on the client! Help!

"Jeroen Geilman" <(E-Mail Removed)> wrote in message
news:jngj02-(E-Mail Removed)...
> C3 wrote:
>
> > I would like to set up my client PC to remotely boot DOS from my Linux
> > server (Debian 3.0).
> >
> > I have created an image of the boot disk, and I've placed it in
> > /tftpboot/boot.img. In my dhcpd.conf, under the host that will be
booting
> > this image, I've put "filename "/tftpboot/boot.img"".
> >
> > My client has a Gigabyte M/B with onboard Ethernet that supports PXE.
> >
> > What more do I need to do to get this all to work?
>
> Switch on the client ;-)
>
> Really - what you want it to configure the bootp server.
> DHCP wasn't made for this, you want bootp.
> All you need to do is specify the MAC address of the client in the
> config file and specify what image you want to load.
>
> Then boot - and watch the magic happen ;-)
>
>
>
> --
> J
>
> All your bits are belong to us - again.

Help! The client manages to get an IP address from the DHCP server and then
starts trying to download the boot image (1.44MB), but it then gives the
error "TFTP too many packages" and then quits.

Help!

C3 wrote:
> I thought DHCP was a superset of BOOTP?

DHCP is for configuring interfaces on machines already running a
kernel, and BOOTP it's for a kernel to get it's IP so it can
probably mount the root filesystem from an NFS server or a similar
situation.

--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
(E-Mail Removed)
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jose Maria Lopez Hernandez wrote:
| C3 wrote:
|
|> I thought DHCP was a superset of BOOTP?
|
|
| DHCP is for configuring interfaces on machines already running a
| kernel, and BOOTP it's for a kernel to get it's IP so it can
| probably mount the root filesystem from an NFS server or a similar
| situation.

DHCP is a superset of BOOTP; it is possible for an OS-less machine to use DHCP
(booted from the NIC's PROM) to acquire it's OS, and networked files. It's not
just "for configuring interfaces on machines already running a kernel".


- --
Lew Pitcher

Master Codewright & JOAT-in-training | GPG public key available on request
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBORKaagVFX4UWr64RAhIDAJ41rek19wxd1FjfPcPVea OarWx2MgCfQVSR
4MIxfZjlDj5gG6z9moVPEkg=
=E4qt
-----END PGP SIGNATURE-----