From owner-freebsd-install Sun Feb 15 07:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18483 for freebsd-install-outgoing; Sun, 15 Feb 1998 07:46:40 -0800 (PST) (envelope-from owner-freebsd-install@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18455 for ; Sun, 15 Feb 1998 07:46:35 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id HAA09136; Sun, 15 Feb 1998 07:46:39 -0800 (PST) To: dag-erli@ifi.uio.no (Dag-Erling Coidan Sm rgrav) cc: freebsd-install@FreeBSD.ORG Subject: Re: Questions to the gurus :) In-reply-to: Your message of "15 Feb 1998 16:35:33 +0100." Date: Sun, 15 Feb 1998 07:46:39 -0800 Message-ID: <9132.887557599@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-install@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I was thinking of putting distribution descriptions etc. into the .inf > files and having sysinstall scan for them at runtime rather than > hardcoding the distribution list into sysinstall. Something like this: Yeah, one could do that. > packages =[ > bin/bin.inf > catpages/catpages.inf > ... Don't forget that XFree86 tarballs would have to have .inf files made up for them in order to work as well. > Perhaps we can assign identifiers to each distribution: > > packages ={ > p_bin > p_catpages > ... > p_subin > p_susbin > } > > and then: > > p_bin = bin/bin.inf > p_catpages = catpages/catpages.inf Gosh, these are almost starting to sound like... variables! Could the .inf file simply be on its way to becoming a .tcl file, thus saving anyone from having to write extra parsing code? Agh! Paradigm Shift! Brace for impact! :-) > I noticed that the current sysinstall code spends quite some time > making sure it is (or isn't) running on a VTY. This is something I'm > going to have to read closely (or just rip out). Just as long as it still runs on a vt100... :-) > libdialog has some bugs in which menus get screwed up under certain > circumstances (or perhaps there is a bug in the way sysinstall uses > them). I'll have to take some time to RTFM for libdialog... In which release? Are you sure you're running the latest along either the 2.2 or 3.0 branches? There was a display bug at one point which caused nested menus to be garbled, but I finally found and stomped that one before 2.2.5 went out. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-install" in the body of the message