From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Cournoyer Subject: Re: Volatile? argument seems to be ignored for system disk images Date: Mon, 18 Nov 2019 14:08:12 +0900 Message-ID: <87v9rhu5z7.fsf@gmail.com> References: <87wocxhih6.fsf@jlicht.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87wocxhih6.fsf@jlicht.xyz> (Jelle Licht's message of "Mon, 21 Oct 2019 23:55:01 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Jelle Licht Cc: bug-guix , help-guix@gnu.org List-Id: bug-guix.gnu.org Jelle Licht writes: > I am trying to dive into some of the code that goes into generating > system disk images for guix, and I ran into the following: > > It seems that commit 932e1f92404d917a91af28737d6631ec45b56875 did more > than what the commit log said: > >> vm: Make sure disk image initrds load 'usb-storage.ko'. >> >> Reported by David Thompson . >> >> * gnu/system/vm.scm (system-disk-image): Add usb-storage.ko to the >> initrd. > > This commit effectively made the `#:volatile?' kwarg to > `system-disk-image' redundant. Should we remove `#:volatile?', or should > it be passed along instead of #t? > > Or am I misunderstanding something subtle here, and is everything as it > should be? No, my understanding is the same as yours: it looks like a bug. Fixed with commit 67ed544212. Thank you! Maxim