On Thu, Jan 21, 1999 at 01:41:09PM -0500, Bruce Ide wrote: > > Well, the only bright light for an installer right now is Joel's new > > machine - which doesn't want to boot. I am afraid that I don't have > > the resources or time to work on an installer right now, and the > > current one is messy. I may try to rebuild the base tarball, though. > > > > Installing without the installer is ... messy. > > > > I'm somewhat curious as to how you can have all those packages in potato > and no boot/install disks. Have you guys really done that many on the 4 or > 5 machines you have up? I'm assuming the stuff in Potato will work on my > Mac G3 (It's symlinked to sid/*-powerpc) Please let me know if this is not > the case.
It is the case. Most of them didn't require as much human attention as CPU attention. Boot disks are the other way around. > I tried mounting the RAMDISK on my intel system and tweaking it so that it > would boot to a command prompt where I could partition and format the > drives, mount them up, and detar the base tar. I assume dselect/dpkg/apt > works reasonably well and so I should be home free at that point. However, > when I try to boot my modified RAMDISK, it gripes that no init was found. > I thougt init was supposed to live in /sbin, so I'm not sure what's up > there. I copied the init from the base tarball in potato. > > Does this sound like a reasonable line of attack? Once I get the system > up, I'd be happy to try to build a ramdisk people could boot that has the > installer on it. *shrug* It does sound reasonable, and BootX is going to be a supported boot/installation method - eventually. We need to see about getting the installer compiled, first. Dan /--------------------------------\ /--------------------------------\ | Daniel Jacobowitz |__| CMU, CS class of 2002 | | Debian GNU/Linux Developer __ Part-Time Systems Programmer | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \--------------------------------/ \--------------------------------/
