linux-kernel - Re: Univeral Protocol Driver (using UNDI) in Linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0608071958160.3365@yvahk01.tjqt.qr>
Date:	Mon, 7 Aug 2006 20:00:49 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Daniel Rodrick <daniel.rodrick@...il.com>
cc:	"H. Peter Anvin" <hpa@...or.com>,
	Linux Newbie <linux-newbie@...r.kernel.org>,
	kernelnewbies <kernelnewbies@...linux.org>,
	linux-net@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Univeral Protocol Driver (using UNDI) in Linux

>
> Agreed. But still having a single driver for all the NICs would be
> simply GREAT for my setup, in which all the PCs will be booted using
> PXE only. So apart from performance / relilability issues, what are
> the technical roadblocks in this?

Netboot, in the current world, could be done like this:

1. Grab the PXE ROM code chip manufacturers offer in case your network card 
does not support booting via PXE yet and write it to an EPROM which most 
PCI network cards have a socket for

2. Use PXELINUX, boot that with the help of the PXE ROM code

3. Put all drivers needed into the kernel or initrd; or send out different 
initrds depending on the DHCP info the PXE client sent. 

Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/