Date: Thu, 24 Jan 2002 03:46:48 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Nik Clayton <nik@freebsd.org> Cc: David Schultz <dschultz@uclink.Berkeley.EDU>, "f.johan.beisser" <jan@caustic.org>, freebsd-chat@freebsd.org Subject: Re: FreeBSD Intaller (was "Re: ... RedHat ...") Message-ID: <3C4FF428.F439B7FB@mindspring.com> References: <20020123114658.A514@lpt.ens.fr> <20020123091107.T32624-100000@localhost> <20020123124025.A60889@HAL9000.wox.org> <3C4F5BEE.294FDCF5@mindspring.com> <20020124014413.F53456@clan.nothing-going-on.org> <3C4F6CAB.76D9CAE2@mindspring.com> <20020124095742.J53456@clan.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nik Clayton wrote: > > > But you must also include, somewhere, the project's installation > > > routine, and provide a mechanism that lets the end user choose what gets > > > run. > > > > How about we call this mechanism "buying CDROM A instead of CDROM B"? > > How about we call it "Providing a fall back that the project can point > to on -questions so they can say 'We can't answer questions about any > installer except the project's -- please contact your vendor if you're > having problems with their installation routine'". Actually, they can say that without a fallback. It seems you really want to be able to say "Use our installer instead". How about "Boot the ``Ports and Packages'' CD", with a multiple CD distribution? > > > For example, you might ship on CDROM, and include the project's floppy > > > disk images, and instructions on how to use them to create a "FreeBSD > > > Project" install. > > > > This is actually the first time this particular option has > > been raised as "permissable". > > I've mentioned this before, and to you. > > Date: Tue, 10 Jul 2001 11:25:13 +0100 > Subject: Re: FreeBSD Mall now BSDCentral > Message-ID: <20010710112513.D16152@clan.nothing-going-on.org> Was this "To:" me? Or "To:" Brett? I think that it was pointed out the "fdimage" didn't get level 3 and 0 volume locks on the disk, so it couldn't write raw floppies from revent versions of Windows... ...Still, this approach is not listed as being acceptable, in writing, by the trademark license agreement, which doesn't exist, and you aren't the trademark holder, so you saying this and it being true past the point of legal risk are two very different things, aren't they? > If you would prefer to use the standard FreeBSD installer, boot from > CDROM as normal. When you see the '>' prompt, press SPACE to > interrupt the boot process. Then type > > set init_path=/stand/sysinstall > boot Apparently you missed the "size restriction" of 2.88M for the floppy image for the boot floppy MFS, which (probably) would not be able to fit both the "/stand/sysinstall" and the "/stand/goodinstall" at the same time. This would be less of a problem if you could figure out a way of portably running code directly off the CDROM, but if we could do that, then the MFS wouldn't be so large, and FreeBSD would be able to boot in a small amount of memory again (e.g. 4M). Of course, since we can't assume a BIOS interface to the CDROM drive, we're screwed here. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C4FF428.F439B7FB>