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 compilat
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
===
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
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
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 co
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
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 "m
>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
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 momen
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,
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.f
> > > 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 serv
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 sw
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.
/
> 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 aw
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);
+
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://
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 t
>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
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 o
[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
> 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 f
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 f
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*
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'
- 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
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 publ
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
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 p
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 p
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 i
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 enou
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 (wh
33 matches
Mail list logo
