From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: GuixSD bootable ISO-9669 image Date: Sun, 14 May 2017 23:25:07 +0200 Message-ID: <20170514232507.382d5472@scratchpost.org> References: <20170418141719.llp77itz7vyq5rij@abyayala> <87k26hwxt0.fsf@gmail.com> <8760i0m7vg.fsf@gnu.org> <87pog3u3ms.fsf@gmail.com> <87k26afl07.fsf_-_@gmail.com> <20170427190840.79bcaa76@scratchpost.org> <20170427220009.1d0d4607@scratchpost.org> <20170428101844.540ce399@scratchpost.org> <87efw7igen.fsf@gnu.org> <20170502220904.3f27ce9f@scratchpost.org> <871ss72cd2.fsf@gnu.org> <20170507213711.4eaec310@scratchpost.org> <87wp9rmo4d.fsf@gnu.org> <20170512013019.49c3d33d@scratchpost.org> <87o9uyqeda.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60279) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dA10x-0003j5-1I for guix-devel@gnu.org; Sun, 14 May 2017 17:25:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dA10t-0003nL-Ui for guix-devel@gnu.org; Sun, 14 May 2017 17:25:19 -0400 In-Reply-To: <87o9uyqeda.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?ISO-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org Hi Ludo, On Fri, 12 May 2017 17:33:21 +0200 ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > Then users should pick the right one, usually the macro, and get an > error when they pass an invalid UUID. Note that the directory /dev/disk/by-uuid doesn't contain any marker about = what kind of uuid it is. So it would make things complicated for the user. I wouldn't expect anyone that isn't a programmer to know that fat32 uuids a= re different from btrfs uuids. If we have different uuid macros, we should have *-uuid macros for *every* = possible filesystem type, whether the uuids differ or not - at least then t= here's a pattern for the user to learn. Not like 3 macros and 14 filesyste= m types so you'd have to have a mapping function in your head. But really, I myself use uuids only for file-system entries to be bus indep= endent so I can plug known disks on whatever slot I want and they'll be mou= nted at the same place regardless. I guess another use case is for the Gui= x LiveCD to find itself - for the same reason. Not sure what the complicat= ion of bytevectors, multiple macros etcetc buys us. The user is probably c= opy&pasting the uuid from /dev/disk/by-uuid anyway. It's not like you type= in uuids (ever).