From owner-freebsd-hackers@FreeBSD.ORG Fri May 28 00:27:24 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40A681065674 for ; Fri, 28 May 2010 00:27:24 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id C59D58FC12 for ; Fri, 28 May 2010 00:27:23 +0000 (UTC) Received: by fxm20 with SMTP id 20so657032fxm.13 for ; Thu, 27 May 2010 17:27:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=1dVFYV1QfQ8kDiQy6vrF//tdnYBQRlDAVFOxvWhOJ/s=; b=ZxQ81PxZgAwkKjB/qgcf79Iem3ViiiY22u3XNnOK8RjedzNWU8cYTS2GvDL/AL02s2 xaF6zW4s4PN808mZIaANMb0yMKiBqP2wnowTg1W8hO4W/sTnqyP9yLSGZGcvIWXxmF5t k3Mg5xtRXQY2FjDzgGkAkm+5ttxyFi8Zxufug= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=XnARzXw81EOXDGtkRfaMNaJizv+Gk3gU8JL+QAHn6oePhTEQS4ZAlo6O/gDRUnkvpU qMaaXAwpmMjFxa6XYA902deD3HyTRuhHIPJ39uXkxB2DtMKGgVI8YPADtAFogZJt+W7q x2vEcbCZF/SukpTnfGvUrk8Jz1znNjFVv7idk= MIME-Version: 1.0 Received: by 10.223.45.22 with SMTP id c22mr1258378faf.107.1275006442514; Thu, 27 May 2010 17:27:22 -0700 (PDT) Received: by 10.223.118.10 with HTTP; Thu, 27 May 2010 17:27:22 -0700 (PDT) In-Reply-To: References: <20100513.205343.421.1@DEV> <201005132211.o4DMB4sG018935@fire.js.berklix.net> <4BEDCB32.8070206@buffalo.edu> Date: Fri, 28 May 2010 02:27:22 +0200 Message-ID: From: "Domagoj S." To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Custom USB layout & sysinstall (Starting FIXIT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2010 00:27:24 -0000 On Fri, May 28, 2010 at 1:02 AM, Garrett Cooper wrote: > On Thu, May 27, 2010 at 3:53 PM, none none wrote: >> Still no answer? >> >> Hey, there is also a thread: >> http://forums.freebsd.org/showthread.php?t=14059 > > Hate to say but you're doing something unsupported, so unless you walk > through the process by yourself to figure out where things are going > wrong, I'm not sure others have the time to help you in this endeavor. I did found and posted code snippet that is responsible for detecting devices. But I have no C lang knowledge needed to do any coding. I know PHP and JS, ..., so have been observing patterns and echo-ed text/strings to terminal > sysinstall(8) assumes a custom environment and setup; trying to > unravel it would be painful, so I don't suggest doing that. sysinstall(8) expects precise enviroment. Anything deviating from it's hardcoded path is being ignored. > If you're going to roll your own solution you might as well roll the entire > thing from scratch. > > Thanks, > -Garrett My solution is to get rid of sysinstall. Idealy, if sysinstall would be skipped upon boot and Fixit# started immediately I have a blueprint in my head, with beginning, that I am hammering here, but without knowledge to code it. > With respect to your "Still no answer" message I'm not sure what > you're expecting for an answer. You answer yourself above. I expected a patch, an .diff, which I would apply to /usr/src/usr.sbin/sysinstall/... And finally recompile it. > The customizations you're doing that you refer to as "B" do indeed > confuse sysinstall's disk recognition semantics. As part of > your customizations you'll need to adjust sysinstall's disk > recognition semantics to understand the layout you are setting > up. I'm not quite sure what else you are expecting. Someone, to do that for me and handed over, to me, on a silver plate. I am not a FreeBSD dev. Hell, I've just entered this list and this is my first "topic"., > I can't think of some easy fix that would get you past the problem you > are experiencing without some hacking done to sysinstall. I'm > also not sure if that sort of hacking would be suitable for > the general case (what works now). > > - -- > Ken Smith I think it would be, as it would just look in a extended way for devices. Thus, covering old ones and satisfying my needs/aims Domagoj S.