|John W. De Boskey||Oct 24, 2000 11:36 am|
|Warner Losh||Oct 24, 2000 11:47 am|
|David O'Brien||Oct 24, 2000 12:14 pm|
|Wilko Bulte||Oct 24, 2000 12:17 pm|
|Motomichi Matsuzaki||Oct 24, 2000 12:47 pm|
|David O'Brien||Oct 24, 2000 1:08 pm|
|David O'Brien||Oct 24, 2000 1:15 pm|
|Motomichi Matsuzaki||Oct 24, 2000 1:31 pm|
|John W. De Boskey||Oct 24, 2000 1:49 pm|
|Wilko Bulte||Oct 24, 2000 3:28 pm|
|David O'Brien||Oct 24, 2000 3:41 pm|
|Jordan Hubbard||Oct 24, 2000 3:47 pm|
|Jordan Hubbard||Oct 24, 2000 3:52 pm|
|Motomichi Matsuzaki||Oct 24, 2000 3:53 pm|
|Rogier R. Mulhuijzen||Oct 24, 2000 5:09 pm|
|Andrzej Bialecki||Oct 25, 2000 1:07 am|
|Tatsumi Hosokawa||Oct 25, 2000 3:37 am|
|Tatsumi Hosokawa||Oct 25, 2000 3:48 am|
|Terry Lambert||Oct 25, 2000 3:50 am|
|Terry Lambert||Oct 25, 2000 3:52 am|
|no...@ever.sanda.gr.jp||Oct 25, 2000 5:22 am|
|Tatsumi Hosokawa||Oct 25, 2000 5:29 am|
|Tatsumi Hosokawa||Oct 29, 2000 1:39 am|
|Takanori Watanabe||Oct 30, 2000 6:15 am|
|Nick Hibma||Nov 1, 2000 2:38 am|
|Bill Paul||Nov 1, 2000 10:06 am|
|Tatsumi Hosokawa||Nov 1, 2000 5:33 pm|
|Tatsumi Hosokawa||Nov 1, 2000 9:34 pm|
|Makoto MATSUSHITA||Nov 2, 2000 7:05 pm|
|Tatsumi Hosokawa||Nov 2, 2000 7:31 pm|
|Makoto MATSUSHITA||Nov 2, 2000 7:39 pm|
|Makoto MATSUSHITA||Nov 2, 2000 9:51 pm|
|Makoto MATSUSHITA||Nov 2, 2000 9:57 pm|
|Subject:||Re: "make release" breakage - dokern.sh patch 2|
|From:||Terry Lambert (tlam...@primenet.com)|
|Date:||Oct 25, 2000 3:50:02 am|
Other candidates I've been pointed to include the removal of /boot/boot 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 AT&T @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 ter...@lambert.org
--- Any opinions in this posting are my own and not those of my present or previous employers.
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message