netdev - Re: [PATCH] dnet: Dave DNET ethernet controller driver

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]

Date:	Thu, 12 Mar 2009 10:43:45 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	christer@...nigel.se
Cc:	nhorman@...driver.com, shemminger@...tta.com,
	s.hauer@...gutronix.de, yanok@...raft.com,
	linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org,
	wd@...x.de, dzu@...x.de
Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver

From: Christer Weinigel <christer@...nigel.se>
Date: Thu, 12 Mar 2009 17:25:27 +0100

> In theory, nothing.  In practice, well, where do I find an example
> initrd that I can build on that has a DHCP client that hands over
> the NFS root information from the DHCP response to a tool that
> mounts the NFS root file system?  So far I haven't seen anything
> like that and the infrastructure to build initrds (such as klibc) is
> still hard to find and use.  Every time I've tried to build an
> initrd that can do DCHP+NFS root it has turned out to be too much
> trouble and I've had to drop it as deadlines come closer.

Just about every single distribution has to build a initrd
that has to be able to setup a network, and have the necessary
infrastructure to access things over NFS in order to implement
their installer.

You can start with the debian installer, that's probably the
easiest to hack on and extend.

Or you can just continue to list excuses, that might be easier.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html