Re: Our kernel just got too big again. :)
David O'Brien wrote: On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: We've blown out the kern.flp image. Time for me to chop something out again, unless there are any other suggestions. :| Mind if I commit this patch? Index: dokern.sh === RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.35 diff -u -r1.35 dokern.sh --- dokern.sh 2000/09/29 03:24:03 1.35 +++ dokern.sh 2000/10/14 22:55:45 @@ -72,7 +72,15 @@ -e '/SOFTUPDATES/d' \ -e '/MFS/d' \ -e '/NFS_ROOT/d' \ + -e '/ncr/d' \ -e '/atapist/d' \ + -e '/lpt/d' \ + -e '/ppi/d' \ + -e '/vpo/d' \ + -e '/ugen/d' \ + -e '/uhid/d' \ If you remove uhid, will you prohibit installing on an USB-only system? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
On 15-Oct-00 Wes Peters wrote: David O'Brien wrote: On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: We've blown out the kern.flp image. Time for me to chop something out again, unless there are any other suggestions. :| Mind if I commit this patch? Index: dokern.sh === RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.35 diff -u -r1.35 dokern.sh --- dokern.sh 2000/09/29 03:24:03 1.35 +++ dokern.sh 2000/10/14 22:55:45 @@ -72,7 +72,15 @@ -e '/SOFTUPDATES/d' \ -e '/MFS/d' \ -e '/NFS_ROOT/d' \ + -e '/ncr/d' \ -e '/atapist/d' \ + -e '/lpt/d' \ + -e '/ppi/d' \ + -e '/vpo/d' \ + -e '/ugen/d' \ + -e '/uhid/d' \ If you remove uhid, will you prohibit installing on an USB-only system? No, but you already can't install on USB-only systems due to hokieness for USB keyboards. Intel UHCI controller USB keyboards don't work in the loader, so you can't hit Enter in between floppies, and due to the way they emulate older keyboards and the ugliness of the console probe, you won't have a usable keyboard once the system is booted. For OHCI controllers, you can't use the keyboard during the kernel userconfig stuff, though they work fine otherwise. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
[ ... manual driver load from third floppy ... ] The problem with such an approach is that it's not very user-friendly to first-time installers who have no idea how to drive the loader. Let's not forget the linux installation floppy saga and all the confusion it's caused people just in trying to figure out which floppies to use. That would be where the forth hackery comes in - an additional set of menu options which make it a no-brainer to insert the kernel module floppy. Jordan's right. This is a non-starter, unless it says: "Please insert the optional drivers floppy now, and hit return. If you have no more optional drivers to load, please insert the root floppy now, and hit return." Ideally, the thing will be DOS formatted, and have a "\freebsd" directory, in which drivers are located, and a "\freebsd\drivers.ini" that contained name/value pairs indicating files to load and version(s) available. This would make it easy for the FreeBSD project to provide binary drivers which vendors could then just include some more files on their disks, since duplication costs won't change by adding more files, so long as they fit. A nice win, all around. Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
Mike Smith points out that removing `vpo' kills parallel port Zip drives. Is this something we can live w/o for installs? Index: dokern.sh === RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.35 diff -u -r1.35 dokern.sh --- dokern.sh 2000/09/29 03:24:03 1.35 +++ dokern.sh 2000/10/14 22:55:45 @@ -72,7 +72,15 @@ -e '/SOFTUPDATES/d' \ -e '/MFS/d' \ -e '/NFS_ROOT/d' \ + -e '/ncr/d' \ -e '/atapist/d' \ + -e '/lpt/d' \ + -e '/ppi/d' \ + -e '/vpo/d' \ + -e '/ugen/d' \ + -e '/uhid/d' \ + -e '/ulpt/d' \ + -e '/urio/d' \ -e '/maxusers/d' \ -e 's/ident.*GENERIC/ident BOOTMFS/g' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Our kernel just got too big again. :)
We've blown out the kern.flp image. Time for me to chop something out again, unless there are any other suggestions. :| - Jordan --- Forwarded Message Return-Path: [EMAIL PROTECTED] Delivery-Date: Sat Oct 14 06:50:52 2000 Return-Path: [EMAIL PROTECTED] Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9EDopA52343 for [EMAIL PROTECTED]; Sat, 14 Oct 2000 06:50:52 -0700 (PDT) (envelope-from [EMAIL PROTECTED]) Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C733C6E2504 for [EMAIL PROTECTED]; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) Received: by hub.freebsd.org (Postfix) id B4E3237B66C; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) Delivered-To: [EMAIL PROTECTED] Received: from usw2.freebsd.org (usw2.freebsd.org [209.180.6.226]) by hub.freebsd.org (Postfix) with ESMTP id 6B36537B502 for [EMAIL PROTECTED]; Sat, 14 Oct 2000 06:50:55 -0700 (PDT) Received: (from root@localhost) by usw2.freebsd.org (8.11.1/8.11.0) id e9EDosg03413 for [EMAIL PROTECTED]; Sat, 14 Oct 2000 08:50:54 -0500 (CDT) (envelope-from root) Date: Sat, 14 Oct 2000 08:50:54 -0500 (CDT) From: USW2 Root [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: -current build report for Sat Oct 14 02:07:34 CDT 2000 Doing nightly build attempt for 5.0-20001014-CURRENT at Sat Oct 14 02:07:34 CDT 2000 Updating source tree... Making release... Release build of 5.0-20001014-CURRENT was an abject failure. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/atkbd_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/atkbdc_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/fd.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/ppc.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/psm.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/sio.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/syscons_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../isa/vga_isa.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../kern/subr_diskmbr.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/divdi3.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../libkern/moddi3.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
Re: Our kernel just got too big again. :)
I had asked for a 3rd floppy earlier that we could put f/w images and other That sounds nice in theory, but somebody needs to write the code which deals with floppy switching and module loading before this is anything but yet another request. How's your forth? :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: We've blown out the kern.flp image. Time for me to chop something out again, unless there are any other suggestions. :| Mind if I commit this patch? Index: dokern.sh === RCS file: /home/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.35 diff -u -r1.35 dokern.sh --- dokern.sh 2000/09/29 03:24:03 1.35 +++ dokern.sh 2000/10/14 22:55:45 @@ -72,7 +72,15 @@ -e '/SOFTUPDATES/d' \ -e '/MFS/d' \ -e '/NFS_ROOT/d' \ + -e '/ncr/d' \ -e '/atapist/d' \ + -e '/lpt/d' \ + -e '/ppi/d' \ + -e '/vpo/d' \ + -e '/ugen/d' \ + -e '/uhid/d' \ + -e '/ulpt/d' \ + -e '/urio/d' \ -e '/maxusers/d' \ -e 's/ident.*GENERIC/ident BOOTMFS/g' @@ -115,6 +123,7 @@ -e '/ulpt/d' \ -e '/umass/d' \ -e '/ums/d' \ + -e '/urio/d' \ -e '/aue/d' \ -e '/cue/d' \ -e '/kue/d' \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
Hmm?... my forth is poor, but I don't believe that's the issue. If I understand how the floppies currently work is that it's just like our normal boot loader- we start coming up. If you want to load other drivers or modules (like ispfw), you hit the 'other than Enter' to stop the loading progress, switch floppies and load ispfw, davicom ethernet, a splash screen with jordan's face, whatever...then you type 'boot'- then the normal mfsroot flopp The problem with such an approach is that it's not very user-friendly to first-time installers who have no idea how to drive the loader. Let's not forget the linux installation floppy saga and all the confusion it's caused people just in trying to figure out which floppies to use. That would be where the forth hackery comes in - an additional set of menu options which make it a no-brainer to insert the kernel module floppy. you're sure this doesn't work. If you're email to -current was "only answers with patches against -current will be heard", you really should have said so. No, that wasn't the point of my email. My email was originally intended to solicit suggestions about options to remove from the kernel so that the *existing* mechanism would go back to working again. Adding a 3rd floppy to the mix is an option which has occurred to all of us at one time or another and even been a topic for fierce debate in the FreeBSD mailing lists. I would have preferred not to go there in this thread. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
Hmm?... my forth is poor, but I don't believe that's the issue. If I understand how the floppies currently work is that it's just like our normal boot loader- we start coming up. If you want to load other drivers or modules (like ispfw), you hit the 'other than Enter' to stop the loading progress, switch floppies and load ispfw, davicom ethernet, a splash screen with jordan's face, whatever...then you type 'boot'- then the normal mfsroot flopp The problem with such an approach is that it's not very user-friendly to first-time installers who have no idea how to drive the loader. Let's not forget the linux installation floppy saga and all the confusion it's caused people just in trying to figure out which floppies to use. That would be where the forth hackery comes in - an additional set of menu options which make it a no-brainer to insert the kernel module floppy. Okay. It's your thuktun, as Niven would write you're sure this doesn't work. If you're email to -current was "only answers with patches against -current will be heard", you really should have said so. No, that wasn't the point of my email. My email was originally intended to solicit suggestions about options to remove from the kernel so that the *existing* mechanism would go back to working again. Adding a 3rd floppy to the mix is an option which has occurred to all of us at one time or another and even been a topic for fierce debate in the FreeBSD mailing lists. I would have preferred not to go there in this thread. :) Okay. I have no suggestions as to what to remove then. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
The problem with such an approach is that it's not very user-friendly to first-time installers who have no idea how to drive the loader. Most of the relevant modules can actually be tried by sysinstall. In the CD case we can just put them on the CDROM. I'd be inclined to look for somewhere that you can fit ~110k and put nfs.ko.gz there. 8) I was thinking about making sure that drivers that would get you to your install media would be what you'd load- nothing else. This would include network drivers... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
At Sat, 14 Oct 2000 13:57:07 -0700 (PDT), Matthew Jacob [EMAIL PROTECTED] wrote: I had asked for a 3rd floppy earlier that we could put f/w images and other drivers on. Now that we have a mostly loadable system, it strikes me that this would be an excellent time to trim down the GENERIC to the common denominator per-platform and then have compressed driver images available on a 3rd floppy if people need them. It's a nice idea, but this means that boot.flp can exceed 2.88MB limit. As far as I know, the maximum size of boot image of El-Torito bootable CD-ROM is 2.88MB. When I install from CD-ROM, I have to enable ATAPI or SCSI drivers first, and then load Network dirvers and so on. When I install from the net, I have to enable Ethernet, PLIP or PPP drivers first, and then load ATAPI or SCSI drivers and so on. Currently, sysinstall supports two types of install media: local media and remote media. Boot.flp should be capable of loading drivers from the install media. Local media installation: Disk1-1: kernel, atapi + scsi drivers Disk2: sysinstall and utilities Disk3: driver disk Remote media installation: Disk1-2: kernel, network drivers Disk2: sysinstall and utilities Disk3: driver disk I think that disk 2 and 3 can be shared by them. Sysinstall have to ask user about installation media first, and then get compressed *.ko modules from the installation media. P.S.: Japanese/Korean boot.flp for 4.1.1 will be available in a few days (test version is available at http://people.freebsd.org/~hosokawa/boot-ja/), and I believe that it can be ported to -current easily, but it needs pty support in the Disk1 currently -- --- Tatsumi Hosokawa [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Our kernel just got too big again. :)
On Sat, Oct 14, 2000 at 01:54:39PM -0700, Jordan Hubbard wrote: We've blown out the kern.flp image. Time for me to chop something out again, unless there are any other suggestions. :| Things the Alpha has already diked out: ncr SYS* (not just SYSVMSG) lpt \ ppi / should not be needed for PLIP installs vpo (should it get turned on again) ugen uhid ulpt urio To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
