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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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
