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

Re: hfsprogs: Removal of sys/sysctl.h



Hi,

if nothing else helps:

What happens if you destroy the Apple Partition Map of the ISO before you
burn it to the CD.

  cp debian-10.0.0-powerpc-NETINST-1.iso test.iso
  dd if=/dev/zero conv=notrunc bs=2048 count=16 of=test.iso

  ... burn test.iso with SAO ...

This won't boot. But maybe it lures the Mac firmware into doing things
with the drive which then confuse Linux.
(Does Linux on powerpc have any special preference for HFS/HFS+ which
Linux on other systems has not ?)

----------------------------------------------------------------------
Source studies:

Do i get it right that cdrom-detect is a part of Debian's installation
software ?
If so, where is the shell function or program
  list-devices
which is used in
  https://sources.debian.org/src/cdrom-detect/1.91/debian/cdrom-detect.postinst/
?

This shell script obviously emits the following messages:

  [timestamp] cdrom-detect: Devices: '/dev/sr0'
  [timestamp] cdrom-detect: CD-ROM mount failed: device=/dev/sr0 fstype=iso9660
  [timestamp] cdrom-detect: CD-ROM mount failed: device=/dev/cdrom fstype=iso9660
  [timestamp] cdrom-detect: CD-ROM mount failed; unmounting CD just to be sure

The origin of these is obscure:

  [timestamp] (process:1560): mount: mounting /dev/sr0 on /cdrom faiked: No such device
  [timestamp] (process:1560): mount: mounting /dev/cdrom on /cdrom failed: No such device

Whatever, it would be interesting to see what
  ls -l /dev/sr0 /dev/cdrom
has to say at that moment.

Further i do not understand why /dev/cdrom is tried but not listed in
the "Devices:" line.

The messages "(process:1560): mount:" seem not to come directly from
mount(8), because if i do on Debian 10 or on Debian 8

  mount  -t iso9660 -o ro,exec /dev/sr7 /mnt/iso

i get

  mount: special device /dev/sr7 does not exist

rather than

  mount: mounting /dev/sr0 on /cdrom faiked: No such device

So, not regarding the s/failed/faiked/ discrepancy, what kind of mount
program issued that message ?


Have a nice day :)

Thomas


Reply to: