From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 08:38:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 920CF16A417 for ; Thu, 16 Nov 2006 08:38:43 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EA643D60 for ; Thu, 16 Nov 2006 08:38:42 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so235589nzh for ; Thu, 16 Nov 2006 00:38:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=se+Dg1vLGqp7M3VRKmfxLrzbuOFN2o5JG0B9tk+k9yRcOjpf5Eq3KYosid00hDpyAHhFtb0ONtstZEPQ/MNSNJ0zessA+sYiIGT6sWYF5WjspUVBHaqgp92xdjwhA8FUwRJeryuC7fQnX0HW4XosCGJQ8hzpqUcLu5IYcrUEspY= Received: by 10.35.115.18 with SMTP id s18mr304780pym.1163666322235; Thu, 16 Nov 2006 00:38:42 -0800 (PST) Received: by 10.35.59.14 with HTTP; Thu, 16 Nov 2006 00:38:42 -0800 (PST) Message-ID: <2f3a439f0611160038g5349f25bn8a1970120bc52b0@mail.gmail.com> Date: Thu, 16 Nov 2006 14:08:42 +0530 From: "Aditya Godbole" To: freebsd-hackers@freebsd.org In-Reply-To: <200611151344.kAFDiZmh097517@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f3a439f0611150355n3dd81845ydbeb0a7b597fb087@mail.gmail.com> <200611151344.kAFDiZmh097517@lurza.secnetix.de> Subject: Re: Ramdisk support 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: Thu, 16 Nov 2006 08:38:43 -0000 On 11/15/06, Oliver Fromme wrote: > > You can also put the image of the root file system into the > kernel itself, so it doesn't have to be loaded separately. > The kernel option to allocate appropriate space is called > MD_ROOT_SIZE. Thanks. I'm investigating this option. How do I specify the filesystem image that should be put into the kernel? > Then where are you booting from? At least your kernel has > to come from somewhere, i.e. you need either networking or > some kind of media (disk, USB stick or similar). Currently I'm using u-boot to get the kernel image from the network and boot it. Since I'm using u-boot, I proabably need to do something in my kernel bootstrap code that the loader would do otherwise. -- aditya