Hi,
Aurelien Jarno:
I have just done an install using this image and everything went smoothly.
Was booting done from a CD drive ?
If so, what happens if the ISO is presented on USB stick
or hard disk ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to
Hi,
the ISO
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso
of 2014-10-04 10:17 (CEST) still has no CHRP partition table
and was not produced with -as mkisofs option -chrp-boot-part.
It contains the data file /ppc/bootinfo.txt
Hi,
On Sat, Oct 04, 2014 at 10:58:11AM +0200, Thomas Schmitt wrote:
Hi,
the ISO
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso
of 2014-10-04 10:17 (CEST) still has no CHRP partition table
and was not produced with -as
On Sat, Oct 04, 2014 at 01:44:48PM +0200, Aurelien Jarno wrote:
Hi,
On Sat, Oct 04, 2014 at 10:58:11AM +0200, Thomas Schmitt wrote:
Hi,
the ISO
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso
of 2014-10-04 10:17 (CEST)
Hi,
debian-testing-ppc64el-netinst.iso of 2014-10-04 18:41 CEST
is equipped with CHRP pseudo-MBR.
Everything should be ok now ... theoretically.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Sat, Oct 04, 2014 at 04:24:28PM +0100, Steve McIntyre wrote:
On Sat, Oct 04, 2014 at 01:44:48PM +0200, Aurelien Jarno wrote:
Hi,
On Sat, Oct 04, 2014 at 10:58:11AM +0200, Thomas Schmitt wrote:
Hi,
the ISO
On Fri, Oct 03, 2014 at 01:00:04AM +0100, Steve McIntyre wrote:
On Fri, Oct 03, 2014 at 12:33:01AM +0200, Aurelien Jarno wrote:
Hi Steve,
On Sat, Sep 27, 2014 at 10:02:34AM +0200, Aurelien Jarno wrote:
On Mon, Sep 22, 2014 at 10:47:10PM +0200, Aurelien Jarno wrote:
The tarball should be
Hi,
Steve McIntyre wrote:
I've also just added ppc64el to the daily and weekly build config -
let's see how well it works!
Aurelien Jarno wrote:
It seems the daily build has worked correctly.
If you mean
On Fri, Oct 03, 2014 at 02:34:42PM +0200, Thomas Schmitt wrote:
Hi,
Steve McIntyre wrote:
I've also just added ppc64el to the daily and weekly build config -
let's see how well it works!
Aurelien Jarno wrote:
It seems the daily build has worked correctly.
If you mean
Hi,
if [ -f CD$N/ppc/bootinfo.txt ] ; then
add_mkisofs_opt $CDDIR/../$N.mkisofs_opts -chrp-boot-part
fi
I've switched to that and added a hard dependency on xorriso too.
Well, let's see how much havock this creates.
I was prepared to give some more reasoning after having read
my
On Fri, Oct 03, 2014 at 02:34:42PM +0200, Thomas Schmitt wrote:
Hi,
Steve McIntyre wrote:
I've also just added ppc64el to the daily and weekly build config -
let's see how well it works!
Aurelien Jarno wrote:
It seems the daily build has worked correctly.
If you mean
On Fri, Oct 03, 2014 at 05:12:11PM +0200, Aurelien Jarno wrote:
-chrp-boot is an option supported by genisoimage, but it looks like it's
not the case of xorriso. Note that this option is also use in the
powerpc build.
Yup. the powerpc build is the only one where we still depend on
genisoimage,
Hi Steve,
On Sat, Sep 27, 2014 at 10:02:34AM +0200, Aurelien Jarno wrote:
On Mon, Sep 22, 2014 at 10:47:10PM +0200, Aurelien Jarno wrote:
The tarball should be decompressed in the root of the CD-ROM, while the
kernel and initrd should be placed in the /install directory. The ISO
image
On Fri, Oct 03, 2014 at 12:33:01AM +0200, Aurelien Jarno wrote:
Hi Steve,
On Sat, Sep 27, 2014 at 10:02:34AM +0200, Aurelien Jarno wrote:
On Mon, Sep 22, 2014 at 10:47:10PM +0200, Aurelien Jarno wrote:
The tarball should be decompressed in the root of the CD-ROM, while the
kernel and initrd
Hi,
I've also just added ppc64el to the daily and weekly build config -
let's see how well it works!
If xorriso shall be used, then it must be
-chrp-boot-part
instead of
-chrp-boot
(On the other hand one may omit -cache-inodes, which has no effect.)
Have a nice day :)
Thomas
--
To
On Mon, Sep 22, 2014 at 10:47:10PM +0200, Aurelien Jarno wrote:
On Mon, Sep 22, 2014 at 02:09:29PM +0100, Steve McIntyre wrote:
On Mon, Sep 22, 2014 at 09:57:44AM -0300, Mauricio Faria de Oliveira wrote:
On 09/22/2014 12:00 AM, Lennart Sorensen wrote:
On Sun, Sep 21, 2014 at 06:19:43PM
On Mon, Sep 22, 2014 at 09:57:44AM -0300, Mauricio Faria de Oliveira wrote:
On 09/22/2014 12:00 AM, Lennart Sorensen wrote:
On Sun, Sep 21, 2014 at 06:19:43PM +0100, Steve McIntyre wrote:
I'm adding support for new architectures at the moment. powerpc is one
of the most awkward existing arches to
On 09/22/2014 12:00 AM, Lennart Sorensen wrote:
On Sun, Sep 21, 2014 at 06:19:43PM +0100, Steve McIntyre wrote:
I'm adding support for new architectures at the moment. powerpc is one
of the most awkward existing arches to add boot support for at the
moment, due to the mess of older machines.
On Mon, Sep 22, 2014 at 02:09:29PM +0100, Steve McIntyre wrote:
On Mon, Sep 22, 2014 at 09:57:44AM -0300, Mauricio Faria de Oliveira wrote:
On 09/22/2014 12:00 AM, Lennart Sorensen wrote:
On Sun, Sep 21, 2014 at 06:19:43PM +0100, Steve McIntyre wrote:
I'm adding support for new architectures
Hi,
Aurelien Jarno wrote:
Beside that the
default options of genisoimage should be used, there is no need to
specify any strange HFS option like on powerpc
If no option -hfs is needed, then xorriso should be suitable.
The ISO image should be generated with the --chrp-boot argument.
That
Hi folks,
I'm adding support for new architectures at the moment. powerpc is one
of the most awkward existing arches to add boot support for at the
moment, due to the mess of older machines. I'm hoping that ppc64el is
better, but I don't have much information to go on. What should we be
doing to
On Sun, Sep 21, 2014 at 06:19:43PM +0100, Steve McIntyre wrote:
I'm adding support for new architectures at the moment. powerpc is one
of the most awkward existing arches to add boot support for at the
moment, due to the mess of older machines. I'm hoping that ppc64el is
better, but I don't
22 matches
Mail list logo