Re: INSTALL kernel [Re: CVS commit: src/distrib]

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Nov 25, 2008 at 10:20:01AM +0000, Andrew Doran wrote:
> On Mon, Nov 24, 2008 at 08:15:27PM +0100, Manuel Bouyer wrote:
> > On Fri, Nov 21, 2008 at 03:49:52PM +0000, Andrew Doran wrote:
> > > 
> > > Module Name:      src
> > > Committed By:     ad
> > > Date:             Fri Nov 21 15:49:52 UTC 2008
> > > 
> > > Modified Files:
> > >   src/distrib/cdrom: current.conf
> > >   src/distrib/i386: Makefile
> > >   src/distrib/i386/cdroms: Makefile.cdrom
> > >   src/distrib/i386/cdroms/bootcd: Makefile boot.cfg.in
> > >   src/distrib/i386/cdroms/bootcd-com: Makefile
> > >   src/distrib/i386/cdroms/installcd: Makefile boot.cfg.in
> > >   src/distrib/i386/ramdisks/common: dot.profile
> > > Removed Files:
> > >   src/distrib/i386/kmod: Makefile
> > > 
> > > Log Message:
> > > Switch the i386 installation CDs away from RAM disks and instead use the
> > > CD-ROM as the root file system. It contains a limited subset of $DESTDIR
> > > along with sysinst. This will help to massively reduce the amount of 
> > > memory
> > > needed to install from CD or netboot, and allow us to continue using the
> > > generic kernel on the CDs.
> > 
> > Another side effect of this change is that it makes it impossible to load
> > via tftp a standalone kernel for install/rescue (i.e.
> > you need a NFS server along with the tftp server). the INSTALL_FLOPPY
> > is not suitable for this because it lacks drivers for the most recent
> > ethernet and disk adapters.
> 
> It is possible: provide the kernel modules via tftp (including your
> miniroot.kmod)

AFAIK there is no miniroot.kmod any more.

> and you can netboot GENERIC to do this. pxeboot doesn't grok
> boot.cfg which is a pain. I will look into it.

Yes, please. loading miniroot.kmod before the kernel is acceptable.
loading miniroot.kmod, filesystems and all exec modules by hand
before kernel isn't.

> 
> > Should we add back a INSTALL kernel for this purpose, which would hold
> > the needed device, filesystems and kernel options to do a PXE install ?
> 
> No. I will add back the automatically built miniroot.kmod instead, I was too
> hasty in removing it.
> 
> > The requirement for a root on NFS makes things much more difficult,
> > because it needs a specific dhcp config on a case by case basis (while,
> > with a tftp-only solution, all can be done from a pxelinux menu).
> 
> I don't see how it is much more difficult, see above. For non-bespoke setups
> we now have a simple net install procedure, which is to my mind a lot easier
> for the uninitiated:
> 
> - mount the install CD-ROM image
> - export via tftp+nfs
> - configure dhcp/bootp server
> - boot

before it was:
copy netbsd-INSTALL.gz and the pxe boot loader to tftp
configure dhcp/bootp server
boot

one less step, and no need for a NFS server; this is easier in my view.
Also, you may not have full control on the dhcp server.

> ... no copying files around, no searching for boot loaders, no changing file
> permissions or whatever. You don't even have to enter paths or NFS server
> information on the client.

you have to setup a NFS server instead, which is not so easy.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--