Re: GuixSD bootable ISO-9669 image

Howdy, Danny Milosavljevic skribis: > On Tue, 16 May 2017 10:31:36 +0200 > l...@gnu.org (Ludovic Courtès) wrote: >> Honestly, I was under the assumptions that DCE UUIDs was all that >> mattered: it works for ext2 and btrfs, right? I would think that people >> would

Re: GuixSD bootable ISO-9669 image

On Tue, 16 May 2017 10:31:36 +0200 l...@gnu.org (Ludovic Courtès) wrote: > Honestly, I was under the assumptions that DCE UUIDs was all that > mattered: it works for ext2 and btrfs, right? I would think that people > would rarely add FAT32 or ISO9660 UUIDs to the OS config. With UEFI I thought

Re: GuixSD bootable ISO-9669 image

Hi Danny, Danny Milosavljevic skribis: > On Fri, 12 May 2017 17:33:21 +0200 > l...@gnu.org (Ludovic Courtès) 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

Re: GuixSD bootable ISO-9669 image

Hi Ludo, On Fri, 12 May 2017 17:33:21 +0200 l...@gnu.org (Ludovic Courtès) 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

Re: GuixSD bootable ISO-9669 image

Hi, Danny Milosavljevic skribis: >>I’d prefer to add a special ‘iso-9660-uuid’ form similar to ‘uuid’ in (gnu >>system file-systems). >> That way we could detect that we get a valid UUID at macro-expansion >> time or system-instantiation time, rather than end up with an

Re: GuixSD bootable ISO-9669 image

Hi Ludo, >I’d prefer to add a special ‘iso-9660-uuid’ form similar to ‘uuid’ in (gnu >system file-systems). > That way we could detect that we get a valid UUID at macro-expansion > time or system-instantiation time, rather than end up with an error at > boot time. Hmm, I've never seen that

Re: GuixSD bootable ISO-9669 image

Danny Milosavljevic skribis: > Hi Ludo, > > On Tue, 02 May 2017 23:11:05 +0200 > l...@gnu.org (Ludovic Courtès) wrote: >> OK. Are these “UUIDs” 160-bit long like the “real” ones? If they are, >> I’d suggest ignoring the problem for now. > > No, unfortunately not.

Re: GuixSD bootable ISO-9669 image

Hi Ludo, On Tue, 02 May 2017 23:11:05 +0200 l...@gnu.org (Ludovic Courtès) wrote: > OK. Are these “UUIDs” 160-bit long like the “real” ones? If they are, > I’d suggest ignoring the problem for now. No, unfortunately not. There's also a similar problem in the FAT support in the same module.

Re: GuixSD bootable ISO-9669 image

ng0 writes: > Ludovic Courtès transcribed 5.2K bytes: >> Anyway, I think we should polish and commit real soon. :-) Perhaps we >> can add a note about endianness and assume little endian for now. > > Excuse me if I didn't pay much attention to the thread, I just

Re: GuixSD bootable ISO-9669 image

Heya, Danny Milosavljevic skribis: > On Tue, 02 May 2017 14:37:04 +0200 > l...@gnu.org (Ludovic Courtès) wrote: > >> Seems to work! > > Nice :) > >> Could you clarify the two “See grub” in here: >> >> --8<---cut here---start->8--- >>

Re: GuixSD bootable ISO-9669 image

> (define (iso9660-superblock-uuid sblock) > "Return the Volume ID of a iso9660 superblock SBLOCK as a 4-byte > bytevector." > ;; Note: The field is the volume creation time. > ;; FIXME Use only certain parts (See grub). Grub drops the timezone. So do blkid and /dev/disk/by-uuid . > ;;

Re: GuixSD bootable ISO-9669 image

Hi Ludo, On Tue, 02 May 2017 14:37:04 +0200 l...@gnu.org (Ludovic Courtès) wrote: > Seems to work! Nice :) > Could you clarify the two “See grub” in here: > > --8<---cut here---start->8--- > (define (iso9660-superblock-uuid sblock) > "Return the Volume ID

Re: GuixSD bootable ISO-9669 image

Ludovic Courtès transcribed 5.2K bytes: > Hi! > > I just tested your patch, Danny (last version attached): I took the > image at > > and then did: > > --8<---cut

Re: GuixSD bootable ISO-9669 image

Hi! I just tested your patch, Danny (last version attached): I took the image at and then did: --8<---cut here---start->8--- scheme@(guile-user)> ,m (gnu build

Re: GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements])

Small fix below On Thu, 27 Apr 2017 22:00:09 +0200 Danny Milosavljevic wrote: > Something like this (totally untested): > > diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm > index 0cb84b8aa..be512d59c 100644 > --- a/gnu/build/file-systems.scm > +++

Re: GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements])

Something like this (totally untested): diff --git a/gnu/build/file-systems.scm b/gnu/build/file-systems.scm index 0cb84b8aa..be512d59c 100644 --- a/gnu/build/file-systems.scm +++ b/gnu/build/file-systems.scm @@ -230,6 +230,55 @@ Trailing spaces are trimmed." ^L ;;; +;;; ISO9660 file systems.

Re: GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements])

>... -V gnu-disk-image /mnt/disk-image-partition-1. > xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules That's because all characters in an ISO 9660 volume identification need to be one of "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_". If you use more complicated labels you

Re: GuixSD bootable ISO-9669 image

Hello! Chris Marusich skribis: > Chris Marusich writes: > >> l...@gnu.org (Ludovic Courtès) writes: >> There appear to be (at least) two problem that prevent this naive solution from working, which might point us in the right direction:

GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements])

Chris Marusich writes: > l...@gnu.org (Ludovic Courtès) writes: > >>> There appear to be (at least) two problem that prevent this naive >>> solution from working, which might point us in the right direction: >>> >>> First, the GRUB menu is trying to find a file system with