Re: m68k port status update

2004-02-25 Thread Stephen R Marenka
On Tue, Feb 24, 2004 at 05:09:51PM -0500, Joey Hess wrote: > Stephen R Marenka wrote: > > How about I create a new type called nativehd or something? > > With i386's hd-media, only the cdrom iso is loopback mounted, the > initrd, kernel, and bootloader can all be on the HD the same way. Agreed,

Re: m68k port status update

2004-02-24 Thread Joey Hess
Stephen R Marenka wrote: > On Tue, Feb 24, 2004 at 01:51:38PM -0500, Joey Hess wrote: > > Wouter Verhelst wrote: > > > You don't. In both cases, you need to download an image, boot the native > > > OS, start a kernel loader which will put the image up as a RAMdisk, and > > > go from there. The diff

Re: m68k port status update

2004-02-24 Thread Stephen R Marenka
On Tue, Feb 24, 2004 at 01:51:38PM -0500, Joey Hess wrote: > Wouter Verhelst wrote: > > You don't. In both cases, you need to download an image, boot the native > > OS, start a kernel loader which will put the image up as a RAMdisk, and > > go from there. The difference is that the CD-ROM image wil

Re: m68k port status update

2004-02-24 Thread Joey Hess
Wouter Verhelst wrote: > You don't. In both cases, you need to download an image, boot the native > OS, start a kernel loader which will put the image up as a RAMdisk, and > go from there. The difference is that the CD-ROM image will get its > udebs from CDROM, whereas the network image will work w

Re: m68k port status update

2004-02-24 Thread Sven Luther
On Tue, Feb 24, 2004 at 12:16:41PM -0500, Joey Hess wrote: > Stephen R Marenka wrote: > > So you'd rather call these floppy? > > > > I'll note that i386 can boot off floppy, whereas amiga and mac > > cannot. Would another target name be clearer? > > > > I don't care much one way or the other. S

Re: m68k port status update

2004-02-24 Thread Wouter Verhelst
On Tue, Feb 24, 2004 at 12:16:41PM -0500, Joey Hess wrote: > Stephen R Marenka wrote: > > So you'd rather call these floppy? > > > > I'll note that i386 can boot off floppy, whereas amiga and mac > > cannot. Would another target name be clearer? > > > > I don't care much one way or the other. S

Re: m68k port status update

2004-02-24 Thread Joey Hess
Stephen R Marenka wrote: > So you'd rather call these floppy? > > I'll note that i386 can boot off floppy, whereas amiga and mac > cannot. Would another target name be clearer? > > I don't care much one way or the other. So far everything will fit on > a floppy, but I hadn't much been paying a

Re: m68k port status update

2004-02-24 Thread Stephen R Marenka
On Mon, Feb 23, 2004 at 09:24:35PM -0500, Joey Hess wrote: > Stephen R Marenka wrote: > > Atari and mvme147 should have netboot targets. > > > > I'm using the term netboot inconsistently on m68k. Ya'll tell me if it > > should be changed. Amiga, atari, and mac cannot be tftp booted. So the > > net

Re: m68k port status update

2004-02-23 Thread Joey Hess
Stephen R Marenka wrote: > Atari and mvme147 should have netboot targets. > > I'm using the term netboot inconsistently on m68k. Ya'll tell me if it > should be changed. Amiga, atari, and mac cannot be tftp booted. So the > netboot target really just loads components and base off the net instead >

Re: m68k port status update

2004-02-23 Thread Stephen R Marenka
On Fri, Feb 20, 2004 at 05:14:46PM -0500, Joey Hess wrote: > Stephen R Marenka wrote: > I've updated the d-i ports status page for d-i. Check it out in 4 hours > or so and make sure it's now accurate. I don't think there's a real point for a floppy version for amiga or mac. You can't boot from

Re: m68k port status update

2004-02-20 Thread Joey Hess
Stephen R Marenka wrote: > I know ya'll have been just been waiting to hear about the m68k port! > ;-) Thanks for the report. > kernels: if someone else hasn't gotten there first, I plan on looking > at integrating 2.2 with linux-kernel-di and make sure the > packaging is uniform betw

Re: m68k port status update

2004-02-20 Thread Jeff Bailey
On Fri, Feb 20, 2004 at 12:35:42PM -0600, Stephen R Marenka wrote: > kernels: if someone else hasn't gotten there first, I plan on looking > at integrating 2.2 with linux-kernel-di and make sure the > packaging is uniform between 2.2 and 2.4 m68k kernels. (I'd hate > to mess with

m68k port status update

2004-02-20 Thread Stephen R Marenka
I know ya'll have been just been waiting to hear about the m68k port! ;-) I still haven't completed a full install from scratch, with no work-arounds. However, I think all of the obstacles have been overcome. kernels: if someone else hasn't gotten there first, I plan on looking at integra