Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 30 Jan 2003 20:19:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 30 Jan 2003 20:19:30 -0500 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:26462 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Thu, 30 Jan 2003 20:19:29 -0500 Date: Thu, 30 Jan 2003 20:28:51 -0500 From: Pete Zaitcev Message-Id: <200301310128.h0V1SpL00558@devserv.devel.redhat.com> To: Wakko Warner Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] USB HardDisk Booting 2.4.20 In-Reply-To: References: <1043947657.7725.32.camel@steven> <1043952432.31674.22.camel@irongate.swansea.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >> Is there a reason for not using initrd for this. That should let you >> use any kind of root device even ones requiring user space work before >> the real root is mounted. > > Yes, I believe there is. IMO initrd is too much of an annoyance to setup. I believe it's going to be mandatory anyway, perhaps not as initrd, but as initfs, but the result is the same. Besides, it's not that big a deal if rpm -i makes initrd for you automagically. -- Pete - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/