Re: [Debian-ppc64-devel] Successful installation in an OpenPower 720 Express
On Thu, Sep 15, 2005 at 12:14:09PM +0100, Colin Watson wrote:
> On Thu, Sep 15, 2005 at 09:39:11AM +0200, Sven Luther wrote:
> > On Thu, Sep 15, 2005 at 09:34:33AM +0200, Harald Görl wrote:
> > > Sven Luther wrote:
> > > >On Wed, Sep 14, 2005 at 04:46:16PM +0200, Harald Görl wrote:
> > > >>Doesn't seem to work without "-U". Perhaps it is a problem with the
> > > >>filename "yaboot.conf" (8.3 notation, not 8.4 ;-) )? Bad news?
> > > >
> > > >Also, i was told that maybe -l would be enough, or -iso-level 2.
> > > >Can you try both of them ?
> > >
> > > Ok, tested both of them separately and --- good news --- both of them
> > > are working.
> >
> > Cool. We still need the above yaboot fix, or not ?
>
> yaboot should be able to remain unchanged.
Indeed, since iso-level 2 supports upto 31 char of filename, not only 8+3.
> > > Manpage of "mkisofs" say:
> > >
> > > -l: [...] Use with caution.
> > >
> > > -iso-level: [...] With all iso9660 levels from 1..3, all filenames are
> > > restricted to upper case letters, numbers and the underscore (_). The
> > > maximum filename length is restricted to 31 characters, the directory
> > > nesting level is restricted to 8 and the maximum path length is limited
> > > to 255 characters. [...]
> > >
> > > I would prefer "-iso-level", but does the content of the Debian CD "fit"
> > > to "-iso-level" notation?
> >
> > Not sure. Don't think so in any case.
> >
> > Anyone from debian-boot can comment on this ? Colin ? you suggested that one.
>
> '-iso-level 2' should be just fine for the powerpc CDs. Remember, this
> only affects the raw ISO9660 names which bootloaders, MS-DOS, and the
> like look at; once Linux is running, we're using Joliet / Rock Ridge
> extensions anyway, so the ISO9660 names don't matter.
Cool. Need to check how the various firmware handle it, i can test prep,
pegasos and apple, need someone with an IBM chrp to test it to to be complete :)
> MS-DOS can't handle '-iso-level 2' as far as I know, but, while that
> might be a very slight concern for i386 CDs, it really shouldn't matter
> for powerpc CDs.
Ok, let's enable it then. joeyh, can you add this patch :
--- boot-powerpc (révision 931)
+++ boot-powerpc (copie de travail)
@@ -35,7 +35,7 @@
install_languages $CDDIR
-echo -n "--chrp-boot --netatalk -hfs -probe -map $BASEDIR/data/hfs.map" \
+echo -n " --iso-level 2 --chrp-boot --netatalk -hfs -probe -map
$BASEDIR/data/hfs.map" \
> $N.mkisofs_opts
# We are still missing this for prep
echo -n " -prep-boot install/powerpc/vmlinuz-prep.initrd" >> $N.mkisofs_opts
@@ -94,15 +94,6 @@
if [ ! "$DI_DIR" ];then
DI_DIR="$MIRROR/dists/$DI_DIST/main/installer-$ARCH/current/images"
fi
- cp -a "$DI_DIR/$subarch/cdrom" "$subarch"
- if [ "$subarch" = "powerpc" ]; then
- cp -a "$DI_DIR/$subarch/cdrom-minimal" "$subarch/minimal" ||
true
- else
- # Supported for netboot only on POWER3 and POWER4.
- rm -rf "$subarch/2.4"
- # POWER3 and POWER4 PReP machines do not exist.
- rm -f "$subarch/vmlinuz-prep.initrd"
- fi
else
wget -r -nd --no-parent --level=1 -P "$subarch" -R 'index*' "$DI_WWW_HOME/$subarch/cdrom/"
fi
The second being the other part of the patch we discussed on irc.
Now, what is the steps to take to actually generate isos using this fixed
debian-cd ?
Friendly,
Sven Luther
Reply to: