All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Raif S. Berent" <rsb@berentweb.com>
To: Ben Hildred <42656e@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Chainloadig from grub2 to isolinux
Date: Tue, 22 Jul 2014 00:55:25 +0300	[thread overview]
Message-ID: <20140722005525.0872c093@rsbsd.rsb> (raw)
In-Reply-To: <CAKcyEGq9fJDEU5B=JBRJghQ5yF_YH-j9GPdhjLyjT0DETi9L5w@mail.gmail.com>

> Debian has no provisions for booting iso images from a server. 
The regular live iso also fails to boot from HDD with loopback. As
posted somewhere along the thread, it seems that debian's loopback
kernel module must be extracted and placed on the HDD. Then one must
interrupt the install, drop to a shell, load debian's loopback module,
mount the debian iso with loopback and exit the shell. Only then will
the iso-loopback install work.

I'm not claiming to be correct - it's just what I read and the iso
file's behavior seems to support the theory.

> The netboot images work just fine. (including live images)
Yes, but this is a "minimal image" as I understand and additional
binaries (for example if you want an lxde desktop) will be downloaded.
That's fine for a single install, but requires re-download of same
packages should one aim to install on several systems.

If there is one, I have not come across a desktop (gnome/kde/lxde) live
image+netboot iso file in the repository.


  parent reply	other threads:[~2014-07-21 21:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  9:46 Chainloadig from grub2 to isolinux Beeblebrox
2014-07-02  9:48 ` Vladimir 'phcoder' Serbinenko
2014-07-02 13:37 ` Beeblebrox
2014-07-02 13:46   ` Vladimir 'phcoder' Serbinenko
2014-07-02 14:52   ` Beeblebrox
2014-07-02 15:00     ` Vladimir 'phcoder' Serbinenko
2014-07-08 13:39     ` Raif S. Berent
2014-07-08 15:47       ` Andrey Borzenkov
2014-07-08 22:22       ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 19:18     ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 21:37       ` Ben Hildred
2014-07-21 21:41         ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-21 21:55         ` Raif S. Berent [this message]
2014-07-21 22:22           ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-07-22  4:24           ` Ben Hildred
2014-07-22 10:37             ` tuxracer
2014-07-22 11:04               ` Vladimir 'phcoder' Serbinenko
2014-07-22 12:44                 ` tuxracer
2014-08-07 14:52             ` Beeblebrox
2014-08-07 17:59               ` adrian15
2014-09-21 17:05                 ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140722005525.0872c093@rsbsd.rsb \
    --to=rsb@berentweb.com \
    --cc=42656e@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.