Re: mkisofs (was: Installer image for installation via ssh)

[Thomas Schmitt]

Hi,

Curt wrote:
> > > > http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/

Leandro Noferini wrote:
> > > mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
> > > -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew

Steve McIntyre wrote:
> > genisoimage should be an exact drop-in replacement for mkisofs

Leandro Noferini wrote:
> genisoimage worked as mkisofs but the resulting image does not boot.

silviu writes at www.sgvulcan.com
  "Your headless machine should already be set to boot of cd if one
   is present, otherwise it will not work."
  "The image you just obtained is ready to burn."

So does your headless machine have a CD-ROM (or DVD, or Blu-ray) drive
from which it is set to boot if a bootable medium is present ?

If you try this from USB stick, hard disk, or memory card, then you need
to specially prepare the ISO before putting it onto the storage device.
In above case, a run of program "isohybrid" from package "syslinux-utils".
Just run

  isohybrid custom_install.iso


I just finished the initial text of a wiki page about the step of
packing up a Debian ISO without losing any of its boot capabilities.
  https://wiki.debian.org/RepackBootableISO


Have a nice day :)

Thomas

Re: mkisofs (was: Installer image for installation via ssh)

[Brian]

On Thu 19 Apr 2018 at 22:14:05 +0200, Thomas Schmitt wrote:

> Hi,
> 
> i wrote:
> > > But [genisoimage's] main problem is that nobody wants to do work in its
> > > code, of which Joerg Schilling claims intellectual ownership.
> 
> > The first is regrettable. The second does not seem unjustified.
> 
> The man page of xorriso ends by
>   CREDITS
>   ...
>   Compliments towards Joerg Schilling whose cdrtools served  me for ten
>   years.
> 
> But said that, it is annoying to get accused of code stealing from a GPLed
> software package, to get invited to contribute to cdrtools, and to get told
> that you are not skilled enough to understand the greatness of cdrtools,
> all simultaneously.

It takes all sorts :)

> > >   https://wiki.debian.org/DebianInstaller/Modify/CD
> 
> > I lost the will to live after reading the third section. Like most
> > accounts of this nature, it is long on commands to run but short on
> > explanation of what is going on.
> 
> The experts want to dump knowledge before it falls victim to Alois Alzheimer.
> 
> That article seems to demonstrate in detail how one would add packages to
> an existing installation ISO. Heavy googling might be needed to understand
> what it does and how it is to be done nowadays.

You have understood the main purpose of the page (as I did). The article
could be made a little more explanatory (IMO). Fortunately, there is
remedial action which can be taken to make it a little more accessible.

> > The wiki (AFAIK) has no structure in place to
> > co-ordinate or drive essential changes. The best one can do is to alter
> > individual pages. Or write new ones.
> 
> But from that it won't get better but only more fragmented.

My point was really about co-ordination, co-operation and discussion on
the direction a particular topic should take. There is no central point
to address this. Perhaps it isn't needed. 

I am not asking for such a change to take place; in fact, I rather like
the freedom and disciplne offered at present.
 
[...]

-- 
Brian.

Re: mkisofs (was: Installer image for installation via ssh)

[Thomas Schmitt]

Hi,

i wrote:
> > But [genisoimage's] main problem is that nobody wants to do work in its
> > code, of which Joerg Schilling claims intellectual ownership.

> The first is regrettable. The second does not seem unjustified.

The man page of xorriso ends by
  CREDITS
  ...
  Compliments towards Joerg Schilling whose cdrtools served  me for ten
  years.

But said that, it is annoying to get accused of code stealing from a GPLed
software package, to get invited to contribute to cdrtools, and to get told
that you are not skilled enough to understand the greatness of cdrtools,
all simultaneously.


> >   https://wiki.debian.org/DebianInstaller/Modify/CD

> I lost the will to live after reading the third section. Like most
> accounts of this nature, it is long on commands to run but short on
> explanation of what is going on.

The experts want to dump knowledge before it falls victim to Alois Alzheimer.

That article seems to demonstrate in detail how one would add packages to
an existing installation ISO. Heavy googling might be needed to understand
what it does and how it is to be done nowadays.


> The wiki (AFAIK) has no structure in place to
> co-ordinate or drive essential changes. The best one can do is to alter
> individual pages. Or write new ones.

But from that it won't get better but only more fragmented.


> > That's why i propose file /.disk/mkisofs in the ISO as source of inspiration
> > about repacking that particular ISO.

> But no proposal to enhance https://wiki.debian.org/ManipulatingISOs
> with EFI information?

I could enhance it for firmware-9.4.0-i386-netinst.iso (too lazy to
search for 9.3.0) which was made by quite the same xorriso run as the
vanilla amd64 netinst.
But already arm64 would get its EFI boot equipment in a different way.

The ISOs themselves know best. If only there were not the many -jigdo-*
options which one has to remove to avoid the need for preparing suitable
Jigdo control files.
This reduces the salad substantially:

  $ sed -e "s/-jigdo.* '.*' //g" -e 's/-checksum.* md5.*,sha512 //' < 
/mnt/iso/.disk/mkisofs
  xorriso -as mkisofs -r -V 'Debian 9.4.0 i386 n' -o 
/srv/cdbuilder.debian.org/dst/deb-cd/out/Ci386/firmware-9.4.0-i386-NETINST-1.iso
 -J -J -joliet-long -cache-inodes -isohybrid-mbr 
syslinux/usr/lib/ISOLINUX/isohdpfx.bin -b isolinux/isolinux.bin -c 
isolinux/boot.cat -boot-load-size 4 -boot-info-table -no-emul-boot 
-eltorito-alt-boot -e boot/grub/efi.img -no-emul-boot -isohybrid-gpt-basdat 
-isohybrid-apm-hfsplus boot1 CD1

Then one has to explain that "syslinux/usr/lib/ISOLINUX/isohdpfx.bin"
is a path on hard disk, not in the ISO, whereas "isolinux/isolinux.bin"
is a path in the ISO. "isohdpfx.bin" may be taken from installed package
"isolinux" (/usr/lib/ISOLINUX/isohdpfx.bin) but better is to take it from
the ISO.

Further, option -isohybrid-apm-hfsplus is inappropriate, and -J is needed
only once. (Both does not harm, though.)

The path "/srv/cdbuilder.debian.org/...-NETINST-1.iso" should be replaced
by some suitable hard disk path, where the resulting ISO shall be stored.
The paths "boot1" and "CD1" should be replaced by the path to the unpacked
directory tree of the original ISO.

Now the task for enhancing the wiki would be to generalize this and to
explain it without driving the reader into suicide.
Not so easy.


Have a nice day :)

Thomas

Re: mkisofs (was: Installer image for installation via ssh)

[Brian]

On Thu 19 Apr 2018 at 20:29:29 +0200, Thomas Schmitt wrote:

> Hi,
> 
> i wrote:
> > > genisoimage is obviously in post-maintainance mode.
> 
> Brian wrote:
> > Decorating the house here is in post-maintenance mode and has been
> > (like genisoimage) in that state for four years. If it is not broke,
> > why fix it? That's my excuse, but other users have a different view.
> 
> Well, genisoimage has some issues, among them those at
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=genisoimage
> 
> But its main problem is that nobody wants to do work in its code, of which
> Joerg Schilling claims intellectual ownership.

The first is regrettable. The second does not seem unjustified.

> xorriso came to its job as producer of most Debian ISOs because i was
> willing to work in libisoburn, which i founded myself.

A good thing, too.

> > > > https://wiki.debian.org/ManipulatingISOs
> 
> > > still lacks the ISO preparations for booting via EFI.
> 
> > You know what they say? - It's a wiki.
> 
> Yeah. But one should rather consolidate the various wikis about that topic.
> There is e.g.
>   https://wiki.debian.org/DebianInstaller/Modify/CD

I lost the will to live after reading the third section. Like most
accounts of this nature, it is long on commands to run but short on
explanation of what is going on.

> and chances are that one could find more of them.

Easily.

> This would need a plan and afterwards active maintainance.

Active maintenance? Plan? The wiki (AFAIK) has no structure in place to
co-ordinate or drive essential changes. The best one can do is to alter
individual pages. Or write new ones.
 
> That's why i propose file /.disk/mkisofs in the ISO as source of inspiration
> about repacking that particular ISO.

But no proposal to enhance https://wiki.debian.org/ManipulatingISOs
with EFI information?

-- 
Brian.

Re: mkisofs (was: Installer image for installation via ssh)

[Thomas Schmitt]

Hi,

i wrote:
> > genisoimage is obviously in post-maintainance mode.

Brian wrote:
> Decorating the house here is in post-maintenance mode and has been
> (like genisoimage) in that state for four years. If it is not broke,
> why fix it? That's my excuse, but other users have a different view.

Well, genisoimage has some issues, among them those at
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=genisoimage

But its main problem is that nobody wants to do work in its code, of which
Joerg Schilling claims intellectual ownership.
xorriso came to its job as producer of most Debian ISOs because i was
willing to work in libisoburn, which i founded myself.


> > > https://wiki.debian.org/ManipulatingISOs

> > still lacks the ISO preparations for booting via EFI.

> You know what they say? - It's a wiki.

Yeah. But one should rather consolidate the various wikis about that topic.
There is e.g.
  https://wiki.debian.org/DebianInstaller/Modify/CD
and chances are that one could find more of them.
This would need a plan and afterwards active maintainance.

That's why i propose file /.disk/mkisofs in the ISO as source of inspiration
about repacking that particular ISO.


Have a nice day :)

Thomas

Re: mkisofs (was: Installer image for installation via ssh)

[Brian]

On Thu 19 Apr 2018 at 19:32:13 +0200, Thomas Schmitt wrote:

> Hi,
> 
> Cindy-Sue Causey wrote:
> > My memory this second is that the chatter went beyond just that
> > genisoimage was not being maintained,
> 
> At least the last maintainer of genisoimage did not reveil himself as
> wearing that hat when he made a statement in this thread. So yes,
> genisoimage is obviously in post-maintainance mode.

Decorating the house here is in post-maintenance mode and has been
(like genisoimage) in that state for four years. If it is not broke,
why fix it? That's my excuse, but other users have a different view.

[...]
 
> Brian wrote:
> > https://wiki.debian.org/ManipulatingISOs
> 
> This seems to be more modern than
> > > http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/
> but still lacks the ISO preparations for booting via EFI.
> (The prescription to install "isolinux" can be replaced by the MBR
>  harvesting of "isohdpfx.bin" from the original ISO.)

You know what they say? - It's a wiki.

-- 
Brian.

Re: mkisofs (was: Installer image for installation via ssh)

[Thomas Schmitt]

Hi,

Cindy-Sue Causey wrote:
> My memory this second is that the chatter went beyond just that
> genisoimage was not being maintained,

At least the last maintainer of genisoimage did not reveil himself as
wearing that hat when he made a statement in this thread. So yes,
genisoimage is obviously in post-maintainance mode.


> One question I'm left with now is that I'm getting zero response for
> "apt-cache search xorrisofs". I must have hit up the Internet yet
> again to find xorriso as an option. That or I chipped the "fs" off the
> tailend and tried "apt-cache search xorriso" instead... ? :)

  $ apt-file search xorrisofs
  xorriso: /usr/bin/xorrisofs
  xorriso: /usr/share/man/man1/xorrisofs.1.gz

Adding to the confusion is the name of the source package
  https://tracker.debian.org/pkg/libisoburn

But the fog gets thinner if you look at the file list of the binary package
  https://packages.debian.org/sid/amd64/xorriso/filelist
which has
  /usr/bin/osirrox
  /usr/bin/xorrecord
  /usr/bin/xorriso
  /usr/bin/xorrisofs
  
The relation of the four commands is:

- xorriso is the actual binary program, a thin frontent to libisoburn.so.

The following three are just symbolic links to xorriso, which learns
from argv[0] that it was called by one of those names:

- osirrox starts xorriso with initial command -osirrox "on" which enables
  commands that have the capability to write, change, or delete files on
  hard disk. Mainly used for extracting files from ISO or for mounting
  older sessions of a multi-session ISO.

- xorrisofs starts xorriso in a mode which prepends "-as mkisofs" to the
  program arguments. This command interpets its arguments similar to mkisofs
  until the emulation mode is ended by argument "--".
  (The same happens if you start xorriso as "mkisofs" or "genisoimage".)

- xorrecord starts xorriso in a mode which prepends "-as cdrecord" to the
  program arguments. This command interpets its arguments similar to
  cdrecord until the emulation mode is ended by argument "--".
  It can write CD, DVD, and BD media for data storage. Not audio CD.
  (The same happens if you start xorriso as "cdrecord" or "wodim".)


Brian wrote:
> https://wiki.debian.org/ManipulatingISOs

This seems to be more modern than
> > http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/
but still lacks the ISO preparations for booting via EFI.
(The prescription to install "isolinux" can be replaced by the MBR
 harvesting of "isohdpfx.bin" from the original ISO.)


Have a nice day :)

Thomas

Re: mkisofs (was: Installer image for installation via ssh)

[Thomas Schmitt]

Hi,

Curt wrote:
> > http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/

Leandro Noferini wrote:
> In the article there is this command
>   mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
>   -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
> But mkisofs does not exist in debian anymore.

As others said, these options are supposed to work with genisoimage
and with xorriso's mkisofs emulation.

They enable booting from CD or DVD, but not from USB stick.
Further they do not enable booting via EFI but only via legacy BIOS
or its emulation by EFI.

The xorriso arguments that were used to build a Debian installation ISO are
recorded in file /.disk/mkisofs of the ISO. 1048 characters, of which you
may omit the Jigdo specific options.
My renarration of this ISO production in the article is as follows:

  # The example names get mapped to their roles here
  orig_iso=/path/to/.../debian-9.3.0-amd64-netinst.iso
  mount_point=isoorig
  new_files=isonew
  new_iso=custom_install.iso
  mbr_template=isohdpfx.bin

The article proposes to do
  mount "$orig_iso" "$mount_point"
  mkdir "$new_files"
  rsync -a -H –exclude=TRANS.TBL "$mount_point"/ "$new_files"
and then to edit files underneath directory "$new_files".

Now for step 8, the mkisofs run.
We need an MBR template for booting via BISO from USB stick. The ISO bears
an MBR which will work fine with the rest of the ISOLINUX stuff in the ISO.
So we harvest this one by

  # Step 7 left us in "$new_files". Move up to parent.
  cd ..

  # Extract MBR template file to disk
  dd if="$orig_iso" bs=1 count=432 of="$mbr_template"

Now we can build the ISO

  xorriso -as mkisofs \
 -o "$new_iso" \
 -r -J -joliet-long \
 -V 'Debian 9.3.0 amd64 n' \
 -cache-inodes \
 -isohybrid-mbr "$mbr_template" \
 -c isolinux/boot.cat \
 -b isolinux/isolinux.bin \
   -boot-load-size 4 -boot-info-table -no-emul-boot \
 -eltorito-alt-boot \
 -e boot/grub/efi.img \
   -no-emul-boot -isohybrid-gpt-basdat \
 "$new_files"

The options of the mkisofs emulation of xorriso are explained in
  https://www.gnu.org/software/xorriso/man_1_xorrisofs.html


As for mkisofs, genisoimage, and xorriso:
- mkisofs fell into disgrace at Debian in 2006 because of the attitude
  of its developer
- genisoimage was then forked from a slighly older mkisofs version.
- xorriso was founded by me in 2007 as independent effort to integrate
  ISO 9660 production and CD/DVD/BD burning. It got a mkisofs emulation
  mode to keep migration effort low for the distros.

The (more or less former) maintainer of genisoimage lets xorriso do any
job that it can take over from genisoimage. (HFS for debian powerpc ISOs
is not in its repertoire, nor is UDF for DVD video.)


Have a nice day :)

Thomas

Re: mkisofs (was: Installer image for installation via ssh)

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Apr 19, 2018 at 12:08:56PM -0400, Cindy-Sue Causey wrote:

[...]

> One question I'm left with now is that I'm getting zero response for
> "apt-cache search xorrisofs". I must have hit up the Internet yet
> again to find xorriso as an option. That or I chipped the "fs" off the
> tailend and tried "apt-cache search xorriso" instead... ? :)

Yes. Try "apt-cache search xorriso" (or "apt search xorriso").
Alternatively, "apt-file search" will find xorrisofs:

  tomas@trotzki:~$ apt-file search xorrisofs
  xorriso: /usr/bin/xorrisofs
  xorriso: /usr/share/info/xorrisofs.info.gz
  xorriso: /usr/share/man/man1/xorrisofs.1.gz

...since there *is* a file with this name (in package xorriso).

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrYxEYACgkQBcgs9XrR2kbDbgCfSfCFyTKvn/moUYeZ1NvGBqhB
g3gAn3C4jyhupBngIN4ScpvPzuNw+Nsm
=+Qno
-END PGP SIGNATURE-

Re: mkisofs (was: Installer image for installation via ssh)

[Brian]

On Thu 19 Apr 2018 at 16:42:30 +0200, Leandro Noferini wrote:

> Curt  writes:
> 
> 
> [...]
> 
> > If not, this is the closest to "pre-cooked" I've found:
> >
> > http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/
> >
> > In the comment area Wojciech Gomoła opines it "works pretty good
> > with Debian 9.1.0."
> >
> > The solution does require the headless machine to be capable of booting from
> > cd.
> 
> [...]
> 
> I tried this solution but I had to stop at last passage, when we need to
> recreate the new image. In the article there is this command
> 
> mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
> -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
> 
> But mkisofs does not exist in debian anymore. In its place (?) we have
> genisoimage but I cannot find the right options to have the same result.
> 
> What do I need to give as options?

The word can be searched for from the wiki.

https://wiki.debian.org/ManipulatingISOs

is one source of information.

-- 
Brian.

Re: mkisofs (was: Installer image for installation via ssh)

[Cindy-Sue Causey]

On 4/19/18, to...@tuxteam.de  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Apr 19, 2018 at 04:42:30PM +0200, Leandro Noferini wrote:
>
> [...]
>> I tried this solution but I had to stop at last passage, when we need to
>> recreate the new image. In the article there is this command
>>
>> mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
>> -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
>>
>> But mkisofs does not exist in debian anymore. In its place (?) we have
>> genisoimage but I cannot find the right options to have the same result.
>>
>> What do I need to give as options?
>
> Hm. Going by what the Internet says [1], [2] (I know, I know),
> genisoimage should be command-line compatible with mkisofs.
>
> Cheers
>
> [1]
> https://askubuntu.com/questions/557910/difference-between-mkisofs-and-genisoimage
> [2]
> https://www.linuxquestions.org/questions/linux-software-2/what-should-we-use-to-make-iso-images-mkisofs-or-genisoimage-674086/


The only reason I knew anything about "xorriso -as mkisofs" is because
something related to both genisoimage and mkisofs wasn't working for
me, either. This Debian Wiki page is part of what I remember visiting
last year:

https://wiki.debian.org/genisoimage

My memory this second is that the chatter went beyond just that
genisoimage was not being maintained, but I don't remember exactly
what convinced me to install yet another package (xorriso). Maybe it
was that mention about licensing combined with the possibility of a(n
alleged) stalled maintenance program. :)

One question I'm left with now is that I'm getting zero response for
"apt-cache search xorrisofs". I must have hit up the Internet yet
again to find xorriso as an option. That or I chipped the "fs" off the
tailend and tried "apt-cache search xorriso" instead... ? :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: mkisofs (was: Installer image for installation via ssh)

[Curt]

On 2018-04-19, Leandro Noferini  wrote:
>
> I tried this solution but I had to stop at last passage, when we need to
> recreate the new image. In the article there is this command
>
> mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
>boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
>
> But mkisofs does not exist in debian anymore. In its place (?) we have
> genisoimage but I cannot find the right options to have the same result.
>
> What do I need to give as options?
>

As Tomas has pointed out, and after glancing at the man, it would seem
you can use the very same command line parameters with genisoimage as
those you've quoted above for mkisofs. 

Awaiting your report from the trenches.

C.

-- 
"Three prisoners were locked in a cell. When the largest of them finished his
food, he immediately ate the others. Too bad. An apostrophe in the right place
might have prevented a horrible crime." Joe Gunn

Re: mkisofs (was: Installer image for installation via ssh)

[Steve McIntyre]

lnofe...@cybervalley.org wrote:
>
>I tried this solution but I had to stop at last passage, when we need to
>recreate the new image. In the article there is this command
>
>mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
>-boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
>
>But mkisofs does not exist in debian anymore. In its place (?) we have
>genisoimage but I cannot find the right options to have the same result.
>
>What do I need to give as options?

genisoimage should be an exact drop-in replacement for mkisofs, or you
can also use xorriso with the same arguments so long as you use "-as
mkisofs" as an argument first. (That's what we do for debian-cd.)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html

Re: mkisofs (was: Installer image for installation via ssh)

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Apr 19, 2018 at 04:42:30PM +0200, Leandro Noferini wrote:

[...]
> I tried this solution but I had to stop at last passage, when we need to
> recreate the new image. In the article there is this command
> 
> mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
> -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
> 
> But mkisofs does not exist in debian anymore. In its place (?) we have
> genisoimage but I cannot find the right options to have the same result.
> 
> What do I need to give as options?

Hm. Going by what the Internet says [1], [2] (I know, I know),
genisoimage should be command-line compatible with mkisofs.

Cheers

[1] 
https://askubuntu.com/questions/557910/difference-between-mkisofs-and-genisoimage
[2] 
https://www.linuxquestions.org/questions/linux-software-2/what-should-we-use-to-make-iso-images-mkisofs-or-genisoimage-674086/
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrYs2UACgkQBcgs9XrR2kb8XgCeKxEhBPMPiNDrKFsL+K/6iT2J
IoQAnjUBacmPG+tSmBfKqEEfAGiJgSsK
=RKjd
-END PGP SIGNATURE-

Re: mkisofs (was: Installer image for installation via ssh)

[Cindy-Sue Causey]

On 4/19/18, Leandro Noferini  wrote:
> Curt  writes:
>
>
> [...]
>
>> If not, this is the closest to "pre-cooked" I've found:
>>
>> http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/
>>
>> In the comment area Wojciech Gomoła opines it "works pretty good
>> with Debian 9.1.0."
>>
>> The solution does require the headless machine to be capable of booting
>> from
>> cd.
>
> [...]
>
> I tried this solution but I had to stop at last passage, when we need to
> recreate the new image. In the article there is this command
>
> mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
> -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew
>
> But mkisofs does not exist in debian anymore. In its place (?) we have
> genisoimage but I cannot find the right options to have the same result.
>
> What do I need to give as options?


I've had some mostly bad luck in this topic (relative to messing
around with virtual machines), BUT... I did learn that you can do
something like:

xorriso -as mkisofs

Try researching that and see if you can find something that does what
you're trying to do. You might need to drop the hyphen (-) in searches
because that sometimes tells search engines you do NOT want that word
when you DO want it included in this particular search. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

mkisofs (was: Installer image for installation via ssh)

[Leandro Noferini]

Curt  writes:


[...]

> If not, this is the closest to "pre-cooked" I've found:
>
> http://www.sgvulcan.com/2010/01/06/installing-debian-using-only-ssh/
>
> In the comment area Wojciech Gomoła opines it "works pretty good
> with Debian 9.1.0."
>
> The solution does require the headless machine to be capable of booting from
> cd.

[...]

I tried this solution but I had to stop at last passage, when we need to
recreate the new image. In the article there is this command

mkisofs -o ../custom_install.iso -r -J -no-emul-boot -boot-load-size 4
-boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat ../isonew

But mkisofs does not exist in debian anymore. In its place (?) we have
genisoimage but I cannot find the right options to have the same result.

What do I need to give as options?

-- 
Ciao
leandro
http://6xukrlqedfabdjrb.onion/blog/
Alla bellezza preferisco la verità.
E il dubbio è l'unità di misura.


signature.asc
Description: PGP signature