From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 19 May 2001 04:17:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 19 May 2001 04:17:06 -0400 Received: from nat-pool-meridian.redhat.com ([199.183.24.200]:50634 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Sat, 19 May 2001 04:16:54 -0400 Date: Sat, 19 May 2001 04:16:53 -0400 (EDT) From: Ben LaHaise X-X-Sender: To: Alexander Viro cc: Andrew Clausen , , Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 19 May 2001, Alexander Viro wrote: > On Sat, 19 May 2001, Ben LaHaise wrote: > > > It's not done yet, but similar techniques would be applied. I envision > > that a raid device would support operations such as > > open("/dev/md0/slot=5,hot-add=/dev/sda") > > Think for a moment and you'll see why it's not only ugly as hell, but simply > won't work. Yeah, I shouldn't be replying to email anymore in my bleery-eyed state. =) Of course slash seperated data doesn't work, so it would have to be hot-add= or somesuch. Gah, that's why the options are all parsed from a single lookup name anyways... -ben (who's going to sleep)