[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Some help with dd backing up into an iso



Hi,

GiaThnYgeia wrote:
> /mnt/usb-Kingston_DataTraveler_3.0_08606E69C773BFC06965007B-0:0-part1

Although it is ugly, i guess it is reproducible whenever you plug in
that stick and other sticks get other reproducible addresses.
(Better test whether the address is indeed the same each time.)


> How safe is it to relabel these to something more common and logical?

I assume the ugly one is created automatically.
Is it a symbolic link to something else, perhaps ?
This will tell after "->" a possible link target:
  ls -l /mnt/usb-Kingston_DataTraveler_3.0_08606E69C773BFC06965007B-0:0-part1

In any case, i would rather create a symbolic link with a convenient name.
E.g. by

  ln -s /mnt/usb-Kingston_DataTraveler_3.0_08606E69C773BFC06965007B-0:0-part1 /mnt/blue_kingston_1


> I downloaded a system from your neighbors "siduction"

Mind to tell me the URL of the ISO ?

> it does not register.

Register = Show up in some EFI boot manager ?

> On this one I added a boot flag on its primary partition and this is how
> it worked.

That's what i read as user report on grub-devel. Some EFIs when presented
an MBR partition table do not recognize the partition of type 0xef if there
is no boot flag on some other partition.
Another known firmware quirk is that some EFIs demand all partitions except
the 0xef partition to have type 0x00.
Debian installation ISOs avoid both pitfalls thanks to Matthew J. Garrett's
original research.

> The other pc is very similar,

What about the firmware's version numbers and release dates ?


> Strange behavior that makes no sense to me.

An EFI implementation has enough brain to outsmart everybody.


Have a nice day :)

Thomas


Reply to: