From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1NCtfZ-0002i4-EG for mharc-grub-devel@gnu.org; Tue, 24 Nov 2009 06:34:53 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCtfW-0002gk-R1 for grub-devel@gnu.org; Tue, 24 Nov 2009 06:34:50 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCtfR-0002dc-G2 for grub-devel@gnu.org; Tue, 24 Nov 2009 06:34:50 -0500 Received: from [199.232.76.173] (port=44841 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCtfQ-0002dI-V9 for grub-devel@gnu.org; Tue, 24 Nov 2009 06:34:45 -0500 Received: from xvm-190-8.ghst.net ([217.70.190.8]:54431 helo=aybabtu.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NCtfQ-0001rB-5s for grub-devel@gnu.org; Tue, 24 Nov 2009 06:34:44 -0500 Received: from [192.168.10.10] (helo=thorin) by aybabtu.com with esmtp (Exim 4.69) (envelope-from ) id 1NCtfK-00038u-4q for grub-devel@gnu.org; Tue, 24 Nov 2009 12:34:38 +0100 Received: from rmh by thorin with local (Exim 4.69) (envelope-from ) id 1NCtfJ-0008RF-Kc for grub-devel@gnu.org; Tue, 24 Nov 2009 12:34:37 +0100 Date: Tue, 24 Nov 2009 12:34:37 +0100 From: Robert Millan To: The development of GNU GRUB Message-ID: <20091124113437.GA32380@thorin> References: <20090801143415.GD22989@thorin> <20090801150529.GD23133@thorin> <20090802213836.GD15139@thorin> <20090802224120.GJ15139@thorin> <20091124112101.GA20451@fencepost.gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091124112101.GA20451@fencepost.gnu.org> Organization: free as in freedom X-Message-Flag: Worried about Outlook viruses? Switch to Thunderbird! www.mozilla.com/thunderbird X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.18 (2008-05-17) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: Re: [RFC] Don't pass filename in multiboot command line X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2009 11:34:51 -0000 On Tue, Nov 24, 2009 at 12:21:01PM +0100, Thomas Schwinge wrote: > Hello! > > On Fri, Aug 14, 2009 at 05:20:09PM +0200, Vladimir 'phcoder' Serbinenko wrote: > > Committed with improvements as ACK'ed by Robert on IRC > > I wasted at least half of a working day due to this change! (As well as > others wasted time, who where trying to help me.) > > Don't get me wrong -- in principle I agree with this change, but what I > do not agree with is simply, silently! changing this behavior: you know, > there are systems that rely on the previous behavior, such as GNU/Hurd, > or the issue I was struggling with, Xen, as reported in this thread, > , > and finally here: . > > I have been looking in a lot of places (initramsfs, udev, lvm, ...) what > was possibly going wrong, but would not have expected that GRUB's module > would suddenly change its behavior. Heck, I'm even on the grub-devel > mailing list, but I can't afford to read its hundreds of messages every > week. > > ``There is NO WARRANTY, to the extent permitted by law.'' of course, but > please think about the consequences before doing such incompatible > changes in the future. You're right. We should have documented this better. Perhaps by mentioning it in NEWS and in the release announcement. Sorry about that. > Wouldn't it have been possible to use something like ``module --arg0 FILE > ARG0 ARG1 ...'', and ``module FILE ARG1 ...'' defaulting to ``module > --arg0 FILE FILE ARG1 ...''? We don't like to carry legacy baggage. Backward compatibility may be fine to keep around for a while in some cases, but in this one there really was no sane way to do it. > PS: In general, thanks for the work all of you are doing with maintaining > GRUB! You're welcome. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all."