From owner-freebsd-net Mon Mar 11 23:29:32 2002 Delivered-To: freebsd-net@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6A24A37B621 for ; Mon, 11 Mar 2002 23:26:50 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g2C7Qoc51216; Mon, 11 Mar 2002 23:26:50 -0800 (PST) (envelope-from rizzo) Date: Mon, 11 Mar 2002 23:26:50 -0800 From: Luigi Rizzo To: net@freebsd.org Subject: bootp tags used in FreeBSD ? Message-ID: <20020311232650.E48429@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, does anyone have up-to-date information on which bootp/dhcp tags are used by FreeBSD ? I am asking because of two reasons: + I would like to pass some info from the bootp/dhcp server to userland, so they can be used at runtime to customize system's behaviour (specific example: I have ~100 clients in different labs booting from the same server, where configuration should be lab-specific but not host-specific. A bootp server could easily pass the "domain" each host belong to. I know I could derive this info using the hostname as a search key, but this would involve an additional configuration file...). + I was going to fix the bootptab manpage and i see that there are several vendor tags used in bootpc_subr and in etherboot which are not documented. Even worse, some of those tags are not consistent across different systems, and even etherboot and bootpc_subr.c have different ideas on T129 and T130 cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message