Re: m68k netinst cd's

2008-09-25 Thread Michael Schmitz
Hi Stephen, I meant to point out that I have new netinst d-i cdroms available. I tried the etch one on Atari and ran into two problems: - paths on TOS are using the backslash as separator, so the bootstrap failed to locate the ramdisk

Re: m68k netinst cd's

2008-09-25 Thread Stephen R Marenka
On Thu, Sep 25, 2008 at 11:20:52AM +0200, Michael Schmitz wrote: > Hi Stephen, > >> I meant to point out that I have new netinst d-i cdroms available. >> > > I tried the etch one on Atari and ran into two problems: Sweet! > - paths on TOS a

Re: m68k netinst cd's

2008-09-25 Thread Laurent Vivier
Hi, Le 25 sept. 08 à 03:16, Stephen R Marenka a écrit : I meant to point out that I have new netinst d-i cdroms available. I've tested it (the sid one) on my Q800, initrd from /install/cdrom and and kernel from /install/kernels/: i

Re: m68k netinst cd's

2008-09-25 Thread Stephen R Marenka
On Wed, Sep 24, 2008 at 08:16:04PM -0500, Stephen R Marenka wrote: > Now to figure out how to use an iso with aranym! It turns out the problem is that the cdrom images don't have modules installed in the initrd. I'll have that fixed in the next daily. Now to figure out why busybox ip is segfaul

Re: m68k netinst cd's

2008-09-25 Thread Stephen R Marenka
On Thu, Sep 25, 2008 at 07:58:41PM +0200, Laurent Vivier wrote: > Hi, > > Le 25 sept. 08 à 03:16, Stephen R Marenka a écrit : > >> I meant to point out that I have new netinst d-i cdroms available. >> >> > > I've tested it (the sid one) on my

Installing with D-I from d-ports.org

2008-09-25 Thread Frans Pop
Someone asked on IRC a few weeks back how to do this. I asked to mail the question to the list, but that never happened (which IMO is silly). Anyway, I happened to be thinking about that yesterday and thought I'd just spontaneously share my thoughts with you. As always in D-I there are a few th

Re: m68k netinst cd's

2008-09-25 Thread Michael Schmitz
Hi Stephen, - paths on TOS are using the backslash as separator, so the bootstrap failed to locate the ramdisk and bailed out. Copying the bootargs and bootstrap to HD and editing it fixed this. Can you tell me what the bootargs file should look like? Just replace / by \ everywhere, that sho