Re: FreeBSD/i386 make release breakage
On Tue, Feb 26, 2002 at 06:39:22PM +0900, Makoto Matsushita wrote: Note that new dhclient requires some libraries which are *not* installed to /usr/lib (libdhcp, libres, libomapi, and libdst). Installing them to /usr/lib wouldn't help for the crunched case anyway. I have tried a quick hack to solve this; here is a patch to boot_crunch.conf. I tried a different approach and I was able to build a properly brunched dhclient. However, src/release/Makefile tries to rebuild all of the object files so my near-fix still falls over when building a release. There are several possible ways to solve this problem : 1. Use the existing boot_crunch.conf, but fix crunchgen(1) to recurse into subdirectories to find object files. This would require significant changes to the way that crunchgen currently works. 2. Use the existing boot_crunch.conf, but move sbin/dhclient/* back to a single top-level Makefile. This does not work at the moment, because the objects in each subdirectory are built with different command line options to conditionally compile different parts of the header files. 3. Add an explicit OBJ list in the top level dhclient Makefile wrapped in a .ifdef (RELEASE_CRUNCH). This works well to build a crunched dhclient binary, however, src/release/Makefile tries to rebuild all of the objects individually, and gets confused when asked to rebuild 'client/clparse.o' from the top level, for example. src/release/Makefile could be changed to fix this. I'm currently looking into #2 and #3, as well as working with Ted Lemon from the ISC to fix some symbol pollution that this whole mess has exposed. Any other ideas? - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
murray I'm currently looking into #2 and #3, as well as working with Ted murray Lemon from the ISC to fix some symbol pollution that this whole mess murray has exposed. Any other ideas? Currently nothing, it seems that #3 (or its variant) is better IMHO. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
On Wed, Feb 27, 2002 at 12:19:01AM +0900, Makoto Matsushita wrote: murray I'm currently looking into #2 and #3, as well as working with Ted murray Lemon from the ISC to fix some symbol pollution that this whole mess murray has exposed. Any other ideas? Currently nothing, it seems that #3 (or its variant) is better IMHO. Ok. Fixed in r1.15 of sbin/dhclient/Makefile. I'm not sure if make release will succeed now (just started a build), but release.4 will at least build a crunched dhclient again. - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
On Tue, Feb 26, 2002 at 06:39:22PM +0900, Makoto Matsushita wrote: Note that new dhclient requires some libraries which are *not* installed to /usr/lib (libdhcp, libres, libomapi, and libdst). They are built and linked statically. This is not possible with crunch_gen? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
On Tue, Feb 26, 2002 at 05:30:50AM -0800, [EMAIL PROTECTED] wrote: 2. Use the existing boot_crunch.conf, but move sbin/dhclient/* back to a single top-level Makefile. This does not work at the moment, because the objects in each subdirectory are built with different command line options to conditionally compile different parts of the header files. Also there is at least one filename that is the same in two of the directories. We can work around this at import time thru a FREEBSD-updating set of instructions. (or even better, get ISC to rename them). I can work around the CFLAGS issue if desired. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FreeBSD/i386 make release breakage
Current 5-current fails 'make release' when processing release.4 target (making a crunch binary). Here's sample session: === doc rm -f cpio.info cpio.info.gz rm -f .depend /usr/obj/usr/src/gnu/usr.bin/cpio/GPATH /usr/obj/usr/src/gnu/usr.bin/cpio/GRTAGS /usr/obj/usr/src/gnu/usr.bin/cpio/GSYMS /usr/obj/usr/src/gnu/usr.bin/cpio/GTAGS === doc make: don't know how to make dhclient_clean. Stop src/sbin/dhclient/Makefile doesn't know 'dhclient_clean' target. % cd /usr/src/sbin/dhclient % make -n dhclient_clean make: don't know how to make dhclient_clean. Stop It seems that crunchgen misunderstands src/sbin/dhclient/Makefile, and fails to generate a Makefile for crunch binary. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
Ouch. matusita src/sbin/dhclient/Makefile doesn't know 'dhclient_clean' target. Of course that's normal, dhclient_clean target should be created by crunchgen. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
At 01:27 PM 2/25/2002 +0900, Makoto Matsushita wrote: Current 5-current fails 'make release' when processing release.4 target (making a crunch binary). Here's sample session: === doc rm -f cpio.info cpio.info.gz rm -f .depend /usr/obj/usr/src/gnu/usr.bin/cpio/GPATH /usr/obj/usr/src/gnu/usr.bin/cpio/GRTAGS /usr/obj/usr/src/gnu/usr.bin/cpio/GSYMS /usr/obj/usr/src/gnu/usr.bin/cpio/GTAGS === doc make: don't know how to make dhclient_clean. Stop src/sbin/dhclient/Makefile doesn't know 'dhclient_clean' target. % cd /usr/src/sbin/dhclient % make -n dhclient_clean make: don't know how to make dhclient_clean. Stop It seems that crunchgen misunderstands src/sbin/dhclient/Makefile, and fails to generate a Makefile for crunch binary. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Makoto I can't even get that far. On current as of today: make release BUILDNAME=5.0-20020224-CURRENT \ CHROOTDIR=/usr/tmp/release/5.0-20020224-CURRENT \ CVSROOT=/usr/home/ncvs NOPORTS=YES | tee /usr/src/release/release.log After the cvs checkout completes: cvs checkout: Updating doc/zh_TW.Big5/share cvs checkout: Updating doc/zh_TW.Big5/share/sgml U doc/zh_TW.Big5/share/sgml/catalog U doc/zh_TW.Big5/share/sgml/freebsd.dsl if [ -d /usr/src/release/../../ports/distfiles/ ]; then cp -rp /usr/src/release/../../ports/distfiles /usr/tmp/release/5.0-20020224-CURRENT/usr/ports/distfiles; else mkdir -p /usr/tmp/release/5.0-20020224-CURRENT/usr/ports/distfiles fi Syntax error: end of file unexpected (expecting fi) *** Error code 2 Stop in /usr/src/release. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD/i386 make release breakage
null After the cvs checkout completes: Ah, big sorry... I just fixed in src/release/Makefile rev 1.658. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make release breakage: src/sbin/ifconfig
With 5-current as of Dec/04/2001 15:00:00 GMT. It seems that this is because 'WARNS=0' line is inside of !defined(RELEASE_CRUNCH) clause. IMO, if an application's code requires to set 'WARNS=0 for build, it should also be set when building as a part of a crunched binary. -- - Makoto `MAR' Matsushita (cd /usr/src/sbin/ifconfig make -DRELEASE_CRUNCH -Dlint depend make -DRELEASE_CRUNCH -Dlint ifconfig.o ifmedia.o ifieee80211.o) rm -f .depend mkdep -f .depend -a-DUSE_IF_MEDIA -DUSE_IEEE80211 -DNO_IPX -DNS -I.. /usr/src/sbin/ifconfig/ifconfig.c /usr/src/sbin/ifconfig/ifmedia.c /usr/src/sbin/ifconfig/ifieee80211.c cd /usr/src/sbin/ifconfig; make _EXTRADEPEND echo ifconfig: /usr/lib/libc.a .depend cc -O -pipe -DUSE_IF_MEDIA -DUSE_IEEE80211 -DNO_IPX -DNS -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -c /usr/src/sbin/ifconfig/ifconfig.c cc1: warnings being treated as errors /usr/src/sbin/ifconfig/ifconfig.c:157: warning: declaration of `name' shadows global declaration /usr/src/sbin/ifconfig/ifconfig.c:197: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:197: warning: (near initialization for `cmds[0].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:198: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:198: warning: (near initialization for `cmds[1].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:199: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:199: warning: (near initialization for `cmds[2].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:200: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:200: warning: (near initialization for `cmds[3].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:201: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:201: warning: (near initialization for `cmds[4].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:202: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:202: warning: (near initialization for `cmds[5].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:203: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:203: warning: (near initialization for `cmds[6].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:204: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:204: warning: (near initialization for `cmds[7].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:205: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:205: warning: (near initialization for `cmds[8].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:206: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:206: warning: (near initialization for `cmds[9].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:207: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:207: warning: (near initialization for `cmds[10].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:213: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:213: warning: (near initialization for `cmds[11].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:226: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:226: warning: (near initialization for `cmds[12].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:227: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:227: warning: (near initialization for `cmds[13].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:228: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:228: warning: (near initialization for `cmds[14].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:229: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:229: warning: (near initialization for `cmds[15].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:230: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:230: warning: (near initialization for `cmds[16].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:232: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:232: warning: (near initialization for `cmds[18].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:233: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:233: warning: (near initialization for `cmds[19].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:234: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:234: warning: (near initialization for `cmds[20].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:235: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:235: warning: (near initialization for `cmds[21].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:236: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:236: warning: (near initialization for `cmds[22].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:237: warning: missing initializer /usr/src/sbin/ifconfig/ifconfig.c:237: warning: (near initialization for `cmds[23].c_func2') /usr/src/sbin/ifconfig/ifconfig.c:238: warning: missing initializer
Re: make release breakage: src/sbin/ifconfig
Makoto Matsushita [EMAIL PROTECTED] writes: With 5-current as of Dec/04/2001 15:00:00 GMT. It seems that this is because 'WARNS=0' line is inside of !defined(RELEASE_CRUNCH) clause. IMO, if an application's code requires to set 'WARNS=0 for build, it should also be set when building as a part of a crunched binary. Should be fixed now. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
hosokawa Maybe it's current.jp.freebsd.org's problem I don't think so. It's a mismatch that all object files are created under /usr/src/modules but make install assumes that these are under (maybe) /usr/obj. Maybe it's a fault of some Makefiles (sorry I dunno who change the policy of module compilation directories, did you?). I've done "cd /usr/src/modules; make clean" under -current buildtree to remove them. You say that I should always run "make clean" under all source code directory since somebody causes a mistake to use /usr/src for object? Maybe it's O.K., but before I'm doing, the committer who breaks the policy should be blamed :-) BTW, I've not received your email; are you busy working? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
At Fri, 03 Nov 2000 12:05:46 +0900, Makoto MATSUSHITA [EMAIL PROTECTED] wrote: BTW, I've not received your email; are you busy working? Last night, I tested "make release" on my machine, and failed twice because of unloaded vn driver (this causes last trouble). It successfly finished this morning. I'm Sorry. I wanted to test it on my machine with Celeron 300MHz. hosokawa Maybe it's current.jp.freebsd.org's problem I don't think so. It's a mismatch that all object files are created under /usr/src/modules but make install assumes that these are under (maybe) /usr/obj. Maybe it's a fault of some Makefiles (sorry I dunno who change the policy of module compilation directories, did you?). I've done "cd /usr/src/modules; make clean" under -current buildtree to remove them. You say that I should always run "make clean" under all source code directory since somebody causes a mistake to use /usr/src for object? Maybe it's O.K., but before I'm doing, the committer who breaks the policy should be blamed :-) I understood the situation. I'll look into the Makefile's under src/sys. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
hosokawa Last night, I tested "make release" on my machine, and hosokawa failed twice because of unloaded vn driver (this causes last hosokawa trouble). It successfly finished this morning. I'm Sorry. 'vn' device is a great pitfall of "make release" :-) hosokawa I understood the situation. I'll look into the Makefile's hosokawa under src/sys. Uncutted logfile of Nov/01/2000 may also helps you. You can fetch it from URL:ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/log/. However, this problem (use /usr/src/sys/modules for compilation) is disappeared already according to the logfile of Nov/02/2000. -- - Makoto `MAR' MATSUSHITA go to lunch right now... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
matusita However, this problem (use /usr/src/sys/modules for compilation) is matusita disappeared already according to the logfile of Nov/02/2000. Hmm, sorry, it is not yet fixed. cd ../../modules env MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules KMODIR= make obj all === 3dfx === 3dfx Warning: Object directory not changed from original /usr/src/sys/modules/3dfx Maybe it doesn't occur before, and today's make release is also failed. cd ../../modules env MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules KMDDIR= make install === 3dfx install -c -o root -g wheel -m 555 3dfx.ko /R/stage/kernels install: 3dfx.ko: No such file or directory -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
Forget to note:
matusita Warning: Object directory not changed from original /usr/src/sys/modules/3dfx
dinosaur % pwd
${CHROOT_DIRECTORY_FOR_CURRENT}/usr/src/sys/modules
dinosaur % ls */*.o
3dfx/setdef0.o 3dfx/setdef1.o 3dfx/tdfx_pci.o
Only 3dfx module uses /usr/src/sys/modules for compilation.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage -dokern.sh patch 2)
I'm not sure whether the problem of loading secondary usb modules is a problem in 4.x but it is easy to try. Boot a machine without usb support compiled in. after login, kldload usb, then the miibus and then the if_aue modules. If that works, you should be ok. I cannot test this as at the moment as I don't have a STABLE box (will have once the first RC comes out of JKH factories). Nick On Mon, 30 Oct 2000, Takanori Watanabe wrote: In message [EMAIL PROTECTED], Tatsumi Hosokawa さんいわく: I moved PCI/PCCARD/USB if_xx.ko driver to mfsroot.flp, and I've got 100KB of free blocks in the first floppy. If we move more drivers to mfsroot.flp or coming drivers.flp, we can get not only free blocks in the first floppy, but also more installation devices. Just FYI: If usb itself is module-ifed, USB ether modules cannot be load until MODULE_DEPEND,MODULE_VERSION is defined. Takanori Watanabe a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html" Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
I'm not sure whether the problem of loading secondary usb modules is a problem in 4.x but it is easy to try. Boot a machine without usb support compiled in. after login, kldload usb, then the miibus and then the if_aue modules. If that works, you should be ok. I cannot test this as at the moment as I don't have a STABLE box (will have once the first RC comes out of JKH factories). I usually do the following: # kldload usb (probes USB controllers) # kldload miibus # kldload if_aue # usbd -f /dev/usb0 If the device has already been plugged in, starting usbd will cause it to be probed/attached by the aue driver. If not, it will be detected when it's plugged in later. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
My driver-floppy patch broke "make release" on current.jp.freebsd.org (ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i3865.0-CURRENT-20001101-JPSNAP.log). Of course "make boot.flp" works very well on my enviroment. I'm debugging this problem, but it'll take hours and hours because testing "make release" takes about 8 hours on my machine. Anyway, I'll fix this bug as soon as possible. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
At Thu, 02 Nov 2000 10:34:03 +0900, Tatsumi Hosokawa [EMAIL PROTECTED] wrote: My driver-floppy patch broke "make release" on current.jp.freebsd.org (ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i3865.0-CURRENT-20001101-JPSNAP.log). Of course "make boot.flp" works very well on my enviroment. I'm debugging this problem, but it'll take hours and hours because testing "make release" takes about 8 hours on my machine. Anyway, I'll fix this bug as soon as possible. Hmm. Binaries on current.freebsd.org seems to be successfuly compiled. I'm not guilty :-). % gzip kern-20001028.flp kern-20001101.flp (got from current.freebsd.org) % ls -l kern-20001* -rw-r--r-- 1 hosokawa hosokawa 1330551 11/ 2 13:53 kern-20001028.flp.gz -rw-r--r-- 1 hosokawa hosokawa 1245853 11/ 2 13:50 kern-20001101.flp.gz Maybe it's current.jp.freebsd.org's problem and I'll talk with the administrator of this host. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
In message [EMAIL PROTECTED], Tatsumi Hosokawa さんいわく: I moved PCI/PCCARD/USB if_xx.ko driver to mfsroot.flp, and I've got 100KB of free blocks in the first floppy. If we move more drivers to mfsroot.flp or coming drivers.flp, we can get not only free blocks in the first floppy, but also more installation devices. Just FYI: If usb itself is module-ifed, USB ether modules cannot be load until MODULE_DEPEND,MODULE_VERSION is defined. Takanori Watanabe a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html" Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Driver Floppy implementation (Re: make release breakage - dokern.sh patch 2)
Hi! In "make release breakage" discussion, I said that I'll write a patch to load kernel module from sysinstall to get more free space in the first floppy. This is my implementation. I'll commit this patch to -current if there's no objection. I moved PCI/PCCARD/USB if_xx.ko driver to mfsroot.flp, and I've got 100KB of free blocks in the first floppy. If we move more drivers to mfsroot.flp or coming drivers.flp, we can get not only free blocks in the first floppy, but also more installation devices. I've put the patche and the binary images of *.flp at, http://people.freebsd.org/~hosokawa/driver-floppy/ I've tested these floppies on my machine with Intel PRO/100+ fxp network card. Sysinstall loads if_fxp.ko from mfsroot.flp, and listed it as network installation media (Alt-F2 shows debug messages). -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Tue, 24 Oct 2000, Jordan Hubbard wrote: Believe me, if we were to put out a serious call to kill NFS from the installation boot images, you'd very quickly hear from all of those people and they would be screaming. We need to exhaust all other possibilities before we even contemplate that option. IMHO the battle to keep the floppies from overflowing is already lost. Each time it's like cutting out your limbs to fit into tight clothes. What I think we need is to find new clothes, so to speak, i.e. some other way of organizing the content on the floppies. If we don't do it, we will keep loosing. E.g. we could move some of the drivers to the mfsroot.flp as KLDs, and either autoload them later (i.e. not from the bootloader, but using kldload), or have some options in the menu for loading. This way at least we will avoid overflowing kern.flp. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
At Wed, 25 Oct 2000 04:48:14 +0900, Motomichi Matsuzaki [EMAIL PROTECTED] wrote: I vote for 'remove NFS away'. How about mergeing ifconfig kldload function into sysinstall, and move /boot/kernel/if_xxx.ko into mfsroot.gz mfs image. hosokawa -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
At Wed, 25 Oct 2000 19:37:42 +0900,
Tatsumi Hosokawa [EMAIL PROTECTED] wrote:
How about mergeing ifconfig kldload function into sysinstall, and move
/boot/kernel/if_xxx.ko into mfsroot.gz mfs image.
or simply add,
main()
{
+ for ( i in /kernel/*.ko ) {
+ kdload(i);
+ }
How about it? If it's acceptable, I'll try to write this patch this
weekend.
--
Tatsumi Hosokawa
[EMAIL PROTECTED]
http://www.sm.rim.or.jp/~hosokawa/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Again. There is no public NFS servers for distributing FreeBSD as I know. You can't get any FreeBSD, even if you sends NFS packets to the Internet. Can I and anybody access your favorite NFS servers? MIT, gatekeeper.dec.com, and Sunsite all run anonymous NFS mountable archives. Also, be aware, that webnfs is getting more support in some browsers, recently, and it rides on top of NFS. 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: make release breakage on today's -current
obrien I just diked out more bits. Lets see if that will give us obrien enough space on tonights snapshot build. Whole release procedures are works fine. Thank you. Here's summary of current size of floppies (i386 architecture): * boot.flp (639k left) Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted /dev/vnn1c 2843 2204 41284% 6 5610% /mnt * kern.flp (19k left) Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted /dev/vnn1c 1407 1388 -93 107% 6 2420% /mnt * mfsroot (926k left) Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted /dev/vnn1c 2803 1877 70273% 67 31518% /mnt * mfsroot.flp (579k left) Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted /dev/vnn1c 1407 828 46664% 2 28 7% /mnt * fixit.flp (37k left) Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted /dev/vnn1c 1363 1326 -72 106% 263 11969% /mnt FYI for hosokawa-san: We have total 912kbytes of 'if_*' modules, and it can be shrinked to 328kbytes if gzip -9. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
At Wed, 25 Oct 2000 21:23:01 +0900, [EMAIL PROTECTED] wrote: From: "David O'Brien" [EMAIL PROTECTED] Date: Tue, 24 Oct 2000 13:15:26 -0700 Before removing NFS, I'd remove the new `ncv', `nsp', and `stg' drivers. Please do not remove them. Many people are waiting for them to switch from 3.x with PAO3 or even with 2.x with PAO to more recent FreeBSD. If sysinstall with kldload works, we don't have to remove no driver and no protocols from boot.flp. I'll work on it this weekend. -- Tatsumi Hosokawa [EMAIL PROTECTED] http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. There are no services distributing FreeBSD via NFS in public. In such site-specific situation, you can make your *specific* floppies with NFS and without INET6 or some. IPv6 is site specific, but it has been important since April 24th of this year to support IPv6, since that was the date that Cisco released code to support it in all their supported routers. But right now, we all know that widescale acceptance of IPv6 is going to have to come in at the client level, with Microsoft driving the deployment process. It wouldn't hurt if someone were to build a highly efficient NAT box for IPv6-IPv4, so that once Microsoft CDROMs could be pressed by ATT @HOME or some other severable network provider, that IPv6 deployment could go forward a large chunk of the net at a time, instead of being an all-or-nothing crash-fest. Take this as a hint to the IPv6 advocates in the audience that they need to do something. NFS is also important. NFS is hard to load as a driver, and keep the LEASE code working. NFSv4 is looming on the horizon, and it appears to finally fix locking, for once and for all, for non-coelescing clients, as well as for stacking VFS layers including an NFS VFS somewhere in the stack. There is some possibility that it will actually be useful to Windows systems. I think it's time to look at supporting "drivers" floppies, and the pain in having no floppies is certainly incentive for someone to do the work, should that become stated policy of the project to support most things through driver floppies that are loaded post-boot. 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
make release breakage on today's -current
Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. *** linking BOOTMFS textdata bss dec hex filename 2613503 196388 130744 2940635 2cdedb BOOTMFS install -c -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel Setting up /boot directory for kern floppy /R/stage/image.kern/kernel: 54.9% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 8 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn1c:2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** FYI: You can also fetch (last 50 lines of) logfile via: URL:ftp://current.jp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-CURRENT-20001024-JPSNAP.log "finger [EMAIL PROTECTED]" will also provide you the same result. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
The following patch brings the floppy size down enough to fix the problem. One is a leftover from the config file syntax change. Also, I don't know how useful INET6 is to a GENERIC kernel on todays' networks (faith gif are already removed). Index: dokern.sh === RCS file: /mirror/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.37 diff -r1.37 dokern.sh 43c43 -e '/apm0/d' \ --- -e '/apm/d' \ 46a47 -e '/INET6/d' \ 65c66 -e '/apm0/d' \ --- -e '/apm/d' \ 68a70 -e '/INET6/d' \ I'll commit this later today unless I hear objections. -John - Makoto MATSUSHITA's Original Message - Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. *** linking BOOTMFS text data bss dec hex filename 2613503196388 130744 2940635 2cdedb BOOTMFS install -c -m 555 -o root -g wheel -fschg BOOTMFS /R/stage/kernels mv /R/stage/kernels/BOOTMFS /R/stage/image.kern/kernel Setting up /boot directory for kern floppy /R/stage/image.kern/kernel:54.9% -- replaced with /R/stage/image.kern/kernel.gz sh -e /usr/src/release/scripts/doFS.sh /R/stage/floppies/kern.flp /R/stage /mnt 1440 /R/stage/image.kern 8 fd1440 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn1c: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32 cpio: write error: No space left on device *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. *** FYI: You can also fetch (last 50 lines of) logfile via: URL:ftp://current.jp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-CURRENT-20001024-JPSNAP.log "finger [EMAIL PROTECTED]" will also provide you the same result. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
jwd Also, I don't know how useful INET6 is to a GENERIC kernel on jwd todays' networks (faith gif are already removed). It is mandatory for FreeBSD installation via IPv6 network (via network devices; using gif(4) pseudo interface is a rare case, so it should be removed). Please keep INET6 option as it is. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 09:51:32PM +0900, Makoto MATSUSHITA wrote: It is mandatory for FreeBSD installation via IPv6 network (via network devices; using gif(4) pseudo interface is a rare case, so it should be removed). Please keep INET6 option as it is. I agree with this sentiment.. please leave INET6 support in the GENERIC kernel. I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
will I'm sure there are better things to disable, like MFS, SYSV*, will P1003_P1B and friends, and ICMP_BANDLIM. MFS is required; don't forget we have mfsroot.flp :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 10:27:50PM +0900, Makoto MATSUSHITA wrote: MFS is required; don't forget we have mfsroot.flp :-) Oh yeah... time to drink some more caffeinated pop and wake up.. -- Will Andrews [EMAIL PROTECTED] - Physics Computer Network wench To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
will I'm sure there are better things to disable,
How about removing /boot/boot[12] from floppies ?
--- src/release/Makefile.oldMon Oct 23 23:53:50 2000
+++ src/release/MakefileTue Oct 24 22:38:15 2000
@@ -821,7 +821,7 @@
mv ${RD}/kernels/BOOTMFS ${RD}/image.${FSIMAGE}/kernel
@echo "Setting up /boot directory for ${FSIMAGE} floppy"
@mkdir -p ${RD}/image.${FSIMAGE}/boot
- @cp /boot/boot[12] /boot/loader ${RD}/image.${FSIMAGE}/boot
+ @cp /boot/loader ${RD}/image.${FSIMAGE}/boot
@[ -r ${RD}/kernels/BOOTMFS.${FSIMAGE}.hints ] \
sed -e '/^hint/s/^/set /' -e '/^#/d' \
${RD}/kernels/BOOTMFS.${FSIMAGE}.hints \
Only 8kbytes, but does reduce its size.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, 24 Oct 2000 08:15:12 -0500, Will Andrews [EMAIL PROTECTED] said: I agree with this sentiment.. please leave INET6 support in the GENERIC kernel. I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. Um, let's only disable things that give us a useful amount of space back. (We may just be screwed at this point.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, 24 Oct 2000 07:55:42 -0400 "John W. De Boskey" [EMAIL PROTECTED] said: jwd The following patch brings the floppy size down enough to fix jwd the problem. One is a leftover from the config file syntax jwd change. Also, I don't know how useful INET6 is to a GENERIC jwd kernel on todays' networks (faith gif are already removed). Please don't remove INET6. IPv6 only install is usual thing at least around me. :-) Though the person who installs FreeBSD via IPv6 is relatively few so far, IPv6 enabled installer is important for IPv6 deployment. I heared recent NetBSD's installer has IPv6 capability, too. This is demand of these days. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release breakage - dokern.sh patch 2
Ok, folks want INET6. It's back.. It's been pointed out to me by "Thomas D. Dean" [EMAIL PROTECTED] that the 'le' driver does not work. Can someone provide additional information about why it's in GENERIC? Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS (which I seem to remember Jordan axing at one point before we went to a 2 disk set). So, the 2nd try at the patch is below. Comments welcome. -John Index: dokern.sh === RCS file: /mirror/ncvs/src/release/scripts/dokern.sh,v retrieving revision 1.37 diff -r1.37 dokern.sh 40a41 -e '/ le/d' \ 43c44 -e '/apm0/d' \ --- -e '/apm/d' \ 63c64,65 sed -e '/pty/d' \ --- sed -e '/ le/d' \ -e '/pty/d' \ 65c67 -e '/apm0/d' \ --- -e '/apm/d' \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
In message [EMAIL PROTECTED] "John W. De Boskey" writes: : The following patch brings the floppy size down enough to fix : the problem. One is a leftover from the config file syntax : change. Also, I don't know how useful INET6 is to a GENERIC : kernel on todays' networks (faith gif are already removed). apm is a good one to remove. INET6 is needed for many Japanese installs since IPv6 is very large there due to ARIN giving them such a small range of IPv4 numbers. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
In message [EMAIL PROTECTED] "John W. De Boskey" writes: : It's been pointed out to me by "Thomas D. Dean" : [EMAIL PROTECTED] that the 'le' driver does : not work. Can someone provide additional information : about why it's in GENERIC? Likely because it compiles and the devices are rare enough that not too many people have noticed. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 03:59:20PM +0900, Makoto MATSUSHITA wrote: Maybe kernel image for kern.flp is a little bit larger than a 1.44MB floppy. I just diked out more bits. Lets see if that will give us enough space on tonights snapshot build. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 08:15:12AM -0500, Will Andrews wrote: I'm sure there are better things to disable, like MFS, SYSV*, P1003_P1B and friends, and ICMP_BANDLIM. Only SYSVMSG is removed for the i386 case. SYS* for the Alpha. I'm assuming the SYS* left compiled in on the i386 is for X? Does P1003_P1B and ICMP_BANDLIM actually add code, or just set defaults, etc? If someone beats me to it, please compile GENERIC and GENERIC w/o ICMP_BANDLIM (and then again without P1003_P1B) and let us know how much space savings they would provide. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 03:32:16PM +0200, John Hay wrote: Why not remove NFS? That is what I do here when the snap floppy gets too big. How many people install using NFS? (And can't easily change to ftp.) Many. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 10:44:31PM +0900, Makoto MATSUSHITA wrote: How about removing /boot/boot[12] from floppies ? Committed! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 12:43:16PM -0600, Warner Losh wrote: apm is a good one to remove. We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? INSTALL goes on the floppies and has just enough for all the different sorts of installations. GENERIC has almost LINT proportions so newbies don't have to try and make their own kernel. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Hi. At Tue, 24 Oct 2000 12:15:09 -0700, David O'Brien [EMAIL PROTECTED] wrote: Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. There are no services distributing FreeBSD via NFS in public. In such site-specific situation, you can make your *specific* floppies with NFS and without INET6 or some. IMHO, making install-floppies should be more easy. -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Wed, Oct 25, 2000 at 04:48:14AM +0900, Motomichi Matsuzaki wrote: Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. And INET6 isn't site specific. It certainly is everywhere but maybe .jp. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On Tue, Oct 24, 2000 at 09:42:54PM +0200, Rogier R. Mulhuijzen wrote: We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? Nope, the two would be quickly out of sync. What make you think the person that forgot to change `apm0' to `apm' in dokern.sh would have remembered to have made the change in an INSTALL kernel config? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Before removing NFS, I'd remove the new `ncv', `nsp', and `stg' drivers. Not to mention the `vpo' Parellel port Zip drive device. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
On 24-Oct-00 David O'Brien wrote: On Tue, Oct 24, 2000 at 09:42:54PM +0200, Rogier R. Mulhuijzen wrote: We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? Nope, the two would be quickly out of sync. What make you think the person that forgot to change `apm0' to `apm' in dokern.sh would have remembered to have made the change in an INSTALL kernel config? Because they are more obvious in that they are in the same place (same directory) whereas dokern.sh is stuffed away in src/release/scripts/. Besides, when doing the 3rd floppy idea, using a custom INSTALL kernel config is going to be the way to go. Just as soon as we can get Peter to finish his latest round of config changes. :) -- 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: make release breakage - dokern.sh patch 2
At Tue, 24 Oct 2000 13:08:26 -0700, David O'Brien [EMAIL PROTECTED] wrote: I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. And INET6 isn't site specific. It certainly is everywhere but maybe .jp. I think INET6 is a grobal and public feature, because there are some IPv6 servers. IPv6 networks (6bone) WORKS, and you can get full FreeBSD distribution via IPv6 network if you have connectibity to world-wide 6bone. Not site-specific, IPv6 servers open to the world. Again. There is no public NFS servers for distributing FreeBSD as I know. You can't get any FreeBSD, even if you sends NFS packets to the Internet. Can I and anybody access your favorite NFS servers? -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
will I'm sure there are better things to disable, like MFS, SYSV*, will P1003_P1B and friends, and ICMP_BANDLIM. MFS is required; don't forget we have mfsroot.flp :-) The name is historical; we use md(4) not MFS. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
- David O'Brien's Original Message - On Tue, Oct 24, 2000 at 02:36:44PM -0400, John W. De Boskey wrote: the 'le' driver does not work. Can someone provide additional information about why it's in GENERIC? Get confirmation that it does not work (one user isn't suffient in my book as there could be many issues which could make it ``not work'' for one person). That's part of what this mail is/was for. Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I haven't removed it. But it is an option. I was a very heavy user of NFS, but it didn't matter to jkh when he removed it last time. The switch to ftp isn't hard. P.S. PLEASE trim the CC line. It has gotten redictulously long. To the point some might consider not sending a single message on this thread, else they'll get their mailbox flooded from then on. I copied those folks who responded to my original mail. Standard curtesy. I did not copy you on this. -John -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
Only SYSVMSG is removed for the i386 case. SYS* for the Alpha. I'm assuming the SYS* left compiled in on the i386 is for X? That is correct. It's not mandatory, but it emits a scary-looking error message when X starts up and a lot of folks were commenting on it, so I put it (SYSVSHM) back in. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Tue, Oct 24, 2000 at 02:36:44PM -0400, John W. De Boskey wrote: Ok, folks want INET6. It's back.. It's been pointed out to me by "Thomas D. Dean" [EMAIL PROTECTED] that the 'le' driver does not work. Can someone provide additional information That is correct. See kern/19219. I've verified this on a DEC le card. That is also as far as I got.. about why it's in GENERIC? To annoy people? ;) -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Wed, Oct 25, 2000 at 04:48:14AM +0900, Motomichi Matsuzaki wrote: Hi. At Tue, 24 Oct 2000 12:15:09 -0700, David O'Brien [EMAIL PROTECTED] wrote: Other candidates I've been pointed to include the removal of /boot/boot[12] and NFS IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. The same argument goes for IPV6. In other words: it all depends on your viewpoint. IMHO, making install-floppies should be more easy. Yes!!! -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
On Tue, Oct 24, 2000 at 04:49:41PM -0400, John W. De Boskey wrote: IMO NFS needs to stay. It is *very* useful to many (including me). I haven't removed it. But it is an option. I was a very heavy user of NFS, but it didn't matter to jkh when he removed it last time. The switch to ftp isn't hard. Ultimately that is a call for JKH. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Again. There is no public NFS servers for distributing FreeBSD as I know. You can't get any FreeBSD, even if you sends NFS packets to the Internet. Can I and anybody access your favorite NFS servers? I think this misses the point. Not everyone installs FreeBSD from public servers and, in fact, there is a large percentage of FreeBSD users who have *never* installed FreeBSD from a public server and never will due to various firewall / corporate policy issues. Instead, they transfer the bits to an intermediate server or mount the installation CD and export it, doing all installs over NFS or anon FTP (internal use only) from there. Believe me, if we were to put out a serious call to kill NFS from the installation boot images, you'd very quickly hear from all of those people and they would be screaming. We need to exhaust all other possibilities before we even contemplate that option. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
[Why is -current on the cc line twice? One instance removed] I haven't removed it. But it is an option. I was a very heavy user of NFS, but it didn't matter to jkh when he removed it last time. The switch to ftp isn't hard. Well, that's not quite accurate. It did matter, it just seemed like you were the one lone voice calling for it at the time. I very quickly learned otherwise and, what do you know, it came back. :) NFS is a big, bloated and obvious candidate for removal and I'd be very happy to see it go away forever (not just from the boot floppy, but everywhere :-) but that's not likely to happen, now is it? :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
At Wed, 25 Oct 2000 00:28:41 +0200, Wilko Bulte [EMAIL PROTECTED] wrote: IMO NFS needs to stay. It is *very* useful to many (including me). I vote for 'remove NFS away'. Yes, there are many people using NFS install, but it is site-specific. The same argument goes for IPV6. In other words: it all depends on your viewpoint. Again. NFS is site-specific service. IPv6 is world-wide service. Indeed, world-wide NFS is capable, but is somewhat ridiculous idea. And more, IPv6 is network layer feature, and NFS is session and higher layer feature like FTP, HTTP, AFS and so on. If IPv6 is disabled in IPv6-only environment, any of FTP, HTTP, NFS does not work. Disabling NFS causes minor impact compared with that, because switching to FTP is very easy, as already pointed out. NFS is for convenience, IPv6 is for life. The same argument goes for device drivers. Device drivers of storage devices are also for their lives. -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Believe me, if we were to put out a serious call to kill NFS from the installation boot images, you'd very quickly hear from all of those people and they would be screaming. We need to exhaust all other possibilities before we even contemplate that option. Are there maybe other large pieces which could use something like NFS_NOSERVER is to NFS? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
msmith The name is historical; we use md(4) not MFS. I should read md(4) manpage... sorry. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release breakage
Hello, make release fails with the following diagnosis: === bin/csh/nls === bin/csh/nls/finnish install -c -o root -g wheel -m 444 tcsh.cat /R/stage/trees/bin/../usr/share/nls/fi_FI.ISO_8859-1/tcsh.cat *** Error code 71 -- Best regards, Ilya mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage
Ilya Naumov wrote: Hello, make release fails with the following diagnosis: === bin/csh/nls === bin/csh/nls/finnish install -c -o root -g wheel -m 444 tcsh.cat /R/stage/trees/bin/../usr/share/nls/fi_FI.ISO_8859-1/tcsh.cat *** Error code 71 I just finished one a couple of hours ago with a cvsup and world this morning of course I do it with NODOC=yes. ed Making fixit floppy. disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 1216 sector(s) in last cylinder unallocated /dev/rvnn0c:2880 sectors in 1 cylinders of 1 tracks, 4096 sectors 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 2606 blocks Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounte d on /dev/vnn0c 1363 1322 -68 105% 353 2992% /mnt Filesystem is 1440 K, -68 left 4000 bytes/inode, 29 left touch release.9 0 blocks Setting up CDROM distribution area 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks Setting up FTP distribution area 0 blocks 0 blocks Release done + echo make release Finished make release Finished To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release breakage (readline.h)
My make releases here keep falling over... === gnu/usr.bin/binutils/doc === gnu/usr.bin/binutils/gdb Making init.c yacc -o c-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-exp.y yacc -o f-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-exp.y yacc: 4 rules never reduced yacc -o jv-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/jv-exp.y yacc -o m2-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/m2-exp.y rm -f .depend mkdep -f .depend -a-D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -DNO_MMALLOC -I/usr/obj/usr/src/i386/usr/include init.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/annotate.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ax-general.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ax-gdb.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/bcache.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/blockframe.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/breakpoint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/buildsym.c c-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-lang.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/c-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-lang.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/ch-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/coffread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/command.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/complaints.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/copying.c /../../../contrib/gdb/gdb/corefile.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/corelow.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/core-regset.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/cp-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dcache.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/demangle.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarfread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarf2read.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/elfread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/environ.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/eval.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/exec.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/expprint.c f-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-lang.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/f-valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/findvar.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/fork-child.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/gdbarch.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/gdbtypes.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/infcmd.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/inflow.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/infptrace.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/infrun.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/inftarg.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/language.c jv-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/jv-lang.c /usr/src/gnu/usr.bin/binutils/gd -valprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/jv-typeprint.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/nlmread.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/m2-lang.c m2-exp.c /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/m2-typeprint.c
