UPDATING
hi, there!
--- cut here ---
2129:
{set,get}flags have been added to the tree for rather dubious
reasons. An unintended side effect of this is that you must
rebuild install before the rest of the world.
cd src/usr.bin/xinstall
make depend all install clean
before make world or buildworld. This issue may be resolved
before 4.0 goes out.
--- cut here ---
actually xinstall cannot be built before make world or make buildworld
because of undefined symbols `setflags'.
/fjoe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Tue, 1 Feb 2000, Peter Wemm wrote: > We do need something when we use PNPBIOS because the motherboard > devices are not programmable and their port space is "fixed". Their > space needs to either be allocated to something or otherwise avoided > when we are choosing ports for real programmable devices. If we can make the relevent code use RF_ALLOCATED vs. RF_ACTIVE for determining resource availability I think this will work fine. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sun, Jan 30, 2000 at 10:38:57PM -0500, David Gilbert wrote: > >> "Michael" == Michael Remski <[EMAIL PROTECTED]> writes: > >Michael> ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset >Michael> (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with >Michael> 16/16/7 bytes threshold lpt0: on ppbus 0 >Michael> lpt0: Interrupt-driven port > >I don't get the FIFO portion of the probe. With ECP mode available? You should. > >Dave. > >-- > >|David Gilbert, Velocet Communications. | Two things can only be | >|Mail: [EMAIL PROTECTED] | equal if and only if they | >|http://www.velocet.net/~dgilbert | are precisely opposite. | >=GLO > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
On 31 Jan 2000 15:02:52 -0500, in sentex.lists.freebsd.current you wrote: >The only thing I discovered a few days ago is that when I dialin to the >company network I have to unload and reload the filter rules to get ppp >over the tun0 device working. Before starting /usr/sbin/ppp I do a >ifconfig xl0 down to disable the cable modem interface completely. >Anybody any idea where I can start to debug this weird problem? What does your routing table look like before and after ? ---Mike Mike Tancsa ([EMAIL PROTECTED]) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
"Matthew N. Dodd" wrote: > On Mon, 31 Jan 2000, Mike Smith wrote: > > This is because the unknown driver is never revoked once it owns your > > device. It's a(nother) bug in the ISA bus code. 8( > > Looking at the code in sys/kern/subr_bus.c I'm not sure how any drivers > are revoked by a higher priority match. > > This is probably desirable given the nature of most drivers and one of the > reasons for letting BUS_PROBE_NOMATCH announce your 'unknown' hardware. > I never liked the unknown driver. I vote we kill it and let > isa_probe_nomatch() deal with things. (I'll have to write > isa_probe_nomatch() but I don't see that as a problem.) I'll dig out my patches for that area and send you a copy. We do need something when we use PNPBIOS because the motherboard devices are not programmable and their port space is "fixed". Their space needs to either be allocated to something or otherwise avoided when we are choosing ports for real programmable devices. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
> On Tue, 1 Feb 2000, Nikolai Saoukh wrote: > > Comments for 'unknown' driver says '... for unknown pnp cards ...'. > > Will my driver be called on computer _without_ any pnp card? > > Does your driver have an identify method for non-PnP cards? This particular card can be "downgraded" to previous model (Auto 16/4) in strict legacy mode (no pnp at all). Or with some pnp. Well, my question was not about my case, rather general one. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Doug Rabson wrote: > This patch doesn't (shouldn't) compile since it uses private > information from bus_private.h. I hope you are not including > bus_private.h anywhere in your code - its strictly off limits to > driver code, even bus drivers. Yea, I figured that out. My patch didn't change the function of the code anyway. Not sure what I was thinking. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Tue, 1 Feb 2000, Nikolai Saoukh wrote: > Comments for 'unknown' driver says '... for unknown pnp cards ...'. > Will my driver be called on computer _without_ any pnp card? Does your driver have an identify method for non-PnP cards? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Matthew N. Dodd wrote: > On Mon, 31 Jan 2000, Nikolai Saoukh wrote: > > THE PROBLEM is that tok_isa_probe is not called at all, > > when driver kldloaded. Return value is irrelevant for this case. > > Try the attached patch. > > (cd /sys/isa && patch < isa_common.c.patch) This patch doesn't (shouldn't) compile since it uses private information from bus_private.h. I hope you are not including bus_private.h anywhere in your code - its strictly off limits to driver code, even bus drivers. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
> Nikolai, your easy fix is to comment out the relevent module declaration > for the 'unknown' driver in isa_common.c. Yes, this fix does the job, BUT Comments for 'unknown' driver says '... for unknown pnp cards ...'. Will my driver be called on computer _without_ any pnp card? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Matthew N. Dodd wrote: > On Mon, 31 Jan 2000, Mike Smith wrote: > > This is because the unknown driver is never revoked once it owns your > > device. It's a(nother) bug in the ISA bus code. 8( > > Looking at the code in sys/kern/subr_bus.c I'm not sure how any drivers > are revoked by a higher priority match. > > This is probably desirable given the nature of most drivers and one of the > reasons for letting BUS_PROBE_NOMATCH announce your 'unknown' hardware. > > If a driver is attached and providing interfaces to the system (network, > scsi, what have you.) then loading a higher priority driver shouldn't > cause that device to detach as it would potentially cause the system to > become confused. > > I never liked the unknown driver. I vote we kill it and let > isa_probe_nomatch() deal with things. (I'll have to write > isa_probe_nomatch() but I don't see that as a problem.) > > Nikolai, your easy fix is to comment out the relevent module declaration > for the 'unknown' driver in isa_common.c. This is probably the right workaround for now. The unknown driver does serve a purpose. It indirectly allows resources associated with the device to be allocated so that other PnP devices are not allocated on top. On reviewing the code, this seems to happen (in isa_probe_children) whether or not the preceding call to device_probe_and_attach() succeeded so removing the unknown driver would mean that resources are allocated for the un-attached device which is likely to cause trouble. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Mike Smith wrote: > This is because the unknown driver is never revoked once it owns your > device. It's a(nother) bug in the ISA bus code. 8( Looking at the code in sys/kern/subr_bus.c I'm not sure how any drivers are revoked by a higher priority match. This is probably desirable given the nature of most drivers and one of the reasons for letting BUS_PROBE_NOMATCH announce your 'unknown' hardware. If a driver is attached and providing interfaces to the system (network, scsi, what have you.) then loading a higher priority driver shouldn't cause that device to detach as it would potentially cause the system to become confused. I never liked the unknown driver. I vote we kill it and let isa_probe_nomatch() deal with things. (I'll have to write isa_probe_nomatch() but I don't see that as a problem.) Nikolai, your easy fix is to comment out the relevent module declaration for the 'unknown' driver in isa_common.c. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
> > > I am trying to make kldloadable driver. But none of functions are > > > called when I kldload it. Is this a bug or I am missing something > > > essential? > > > > You're missing something essential. > > > > The return values for the DEVICE_PROBE method should be 0 or negative for > > priority, or positive to indicate an error. > > THE PROBLEM is that tok_isa_probe is not called at all, > when driver kldloaded. Return value is irrelevant for this case. This is because the unknown driver is never revoked once it owns your device. It's a(nother) bug in the ISA bus code. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Nikolai Saoukh wrote:
> THE PROBLEM is that tok_isa_probe is not called at all,
> when driver kldloaded. Return value is irrelevant for this case.
Try the attached patch.
(cd /sys/isa && patch < isa_common.c.patch)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
Index: isa_common.c
===
RCS file: /cvs/src/sys/isa/isa_common.c,v
retrieving revision 1.15
diff -u -r1.15 isa_common.c
--- isa_common.c2000/01/18 02:15:05 1.15
+++ isa_common.c2000/01/31 20:42:03
@@ -783,8 +783,7 @@
static void
isa_driver_added(device_t dev, driver_t *driver)
{
- device_t *children;
- int nchildren, i;
+ device_t child;
/*
* Don't do anything if drivers are dynamically
@@ -796,11 +795,10 @@
return;
DEVICE_IDENTIFY(driver, dev);
- if (device_get_children(dev, &children, &nchildren))
- return;
- for (i = 0; i < nchildren; i++) {
- device_t child = children[i];
+ for (child = TAILQ_FIRST(&dev->children);
+child;
+child = TAILQ_NEXT(child, link)) {
struct isa_device *idev = DEVTOISA(child);
struct resource_list *rl = &idev->id_resources;
struct resource_list_entry *rle;
@@ -831,8 +829,6 @@
}
}
}
-
- free(children, M_TEMP);
}
static int
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Nikolai Saoukh wrote: > THE PROBLEM is that tok_isa_probe is not called at all, > when driver kldloaded. Return value is irrelevant for this case. Yea, I see what could be the problem. I'll get back to you. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
> > I am trying to make kldloadable driver. But none of functions are > > called when I kldload it. Is this a bug or I am missing something > > essential? > > You're missing something essential. > > The return values for the DEVICE_PROBE method should be 0 or negative for > priority, or positive to indicate an error. THE PROBLEM is that tok_isa_probe is not called at all, when driver kldloaded. Return value is irrelevant for this case. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NO_NAMED (patch attached)
Well, the corporate firewall doesn't allow send-pr, so I'm trying this the noisy way. Sorry. :( We have a no_named flag in /usr/src/usr.sbin/Makefile, right by no_sendmail. A recent discussion on -security shows that at least a couple people have a use for this. Therefore, submitted for your approval, as per the Handbook: *** make.conf~ Mon Jan 24 13:55:29 2000 --- make.conf Mon Jan 31 15:25:49 2000 *** *** 28,33 --- 28,36 # To avoid building sendmail #NO_SENDMAIL= true # + # To avoid building named and related tools + #NO_BIND= true + # # To have 'obj' symlinks created in your source directory # (they aren't needed/necessary) #OBJLINK= yes This is against -stable, about a week old. Sorry, don't have -current on my laptop... I'm not a real hacker. ==ml (Wow, my first patch. Trivial, yet I find myself heady with success. ;) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: Mount root failure: 6
For the archive of this ml: Some of the commits over the time since I got this error solved the problem silently. I'm now using ata this machine w/o any problem. On another machine that had problems with DMA with the old wd drivers UDMA33 now works ok, too. Nice. Thanks! Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: identcpu.c change causes panic - not identcpu.c?
On Mon, 31 Jan 2000, Greg Childers wrote: > A panic also occurred on my Pentium (P54C) 66MHz, but backing identcpu.c > to 1.79 didn't stop the panic. Here is the panic info, copied by hand. (I > hope there are no typos!) Well, I rebuilt a kernel with 1.80 of identcpu.c and it booted fine this time, so it looks like you can ignore my previous report. My best guess is that something in my kernel was out of sync with itself (I built multiple times to try and get the ipfw6 error to go away, perhaps it didn't recompile an object file when it should have). Sorry for the false alarm, Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On Sun, Jan 30, 2000 at 02:12:45PM +1030, Greg Lehey wrote: > On Saturday, 29 January 2000 at 20:04:18 -0500, TrouBle wrote: > > Just imagine, too bad its not an 8086 or a 286 prolly take a month or so. > > > > > > Warner Losh wrote: > > > >> In message <[EMAIL PROTECTED]> >Andy Farkas writes: > >> : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and > >> : both src and obj on the same local disk (softupdates enabled): > >> > >> I'm doing this over NFS and only have 12MB of RAM. > >> > >> : Scriptdone on Thu Jan 20 16:22:31 2000 > >> : Script started on Thu Jan 20 01:01:00 2000 > >> > >> 15:21:31. Hmmm, no wonder things have been taking a while... > >> > >> The crypto file that's building now has been going for about 15 > >> minutes now... > >> > >> I think that I'll get my whole week at this rate. > > I did a make world on my PDP-11 yesterday. It took less than a day. > But that's 2.11BSD. That is hard- or software hardware ? Joerg -- Joerg B. MicheelEmail: <[EMAIL PROTECTED]> Waikato Applied Network DynamicsPhone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP-Filter w/FreeBSD-current
In article <[EMAIL PROTECTED]> you write: >With the impending release of FreeBSD-4.0, is anyone on this list using >IP-Filter on FreeBSD-current? I'm planning to install -current Yep, I'm using it as a stateful packet filtering firewall for my cable modem connection. >w/IP-Filter on a testbed and would like to know of there are any >gotchas or if it even runs on FreeBSD-current. No serious problems so far. The only thing I discovered a few days ago is that when I dialin to the company network I have to unload and reload the filter rules to get ppp over the tun0 device working. Before starting /usr/sbin/ppp I do a ifconfig xl0 down to disable the cable modem interface completely. Anybody any idea where I can start to debug this weird problem? Arjan -- Arjan de Vet, Eindhoven, The Netherlands <[EMAIL PROTECTED]> URL: http://www.iae.nl/users/devet/ for PGP key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldloaded driver not called at load time
On Mon, 31 Jan 2000, Nikolai Saoukh wrote:
> I am trying to make kldloadable driver. But none of functions are
> called when I kldload it. Is this a bug or I am missing something
> essential?
You're missing something essential.
The return values for the DEVICE_PROBE method should be 0 or negative for
priority, or positive to indicate an error.
if_tok.c:tok_probe() returns ENXIO which is in the return value you use
for if_tok_isa.c:tok_isa_probe().
You should take a good look at /sys/dev/{ex,ep} for an example of how to
accommodate PnP probes.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make installworld broken???
> "Rodney W. Grimes" wrote:
> > Good analysis deleted...
> >
> > > src/usr.bin/xinstall could probably have been named src/usr.bin/install,
> > > but PROG has to be xinstall regardless. I guess they kept the two as
> > > xinstall for consistancy and in case there were other gotcha's like this.
> >
> > But you forgot what happens if you have a ``file'' named install:
> >
> > cd /tmp
> > mkdir install
> > make install
> >
> > Now you know the real reason the directory is called ``xinstall''.
>
> Ahh yes, of course. 'cd src/usr.bin; make install' would fail. :-)
Actually it use to silently do the wrong thing... nothing at all that is :-)
It doesn't anymore since the .mk system has a special internal target
that deals with the fact that src/usr.bin is simply a directory that has to
be iterated over:
Orbit.hpc1.com:root{101}# cd /usr/src/usr.bin
Orbit.hpc1.com:root{102}# mkdir install
Orbit.hpc1.com:root{103}# make install
===> apply
install -c -s -o root -g wheel -m 555 apply /usr/bin
install -c -o root -g wheel -m 444 apply.1.gz /usr/share/man/man1
===> at
install -c -s -o root -g wheel -m 4555 at /usr/bin
...
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
On Mon, Jan 31, 2000 at 01:02:29PM -0500, Will Andrews wrote: > On Mon, Jan 31, 2000 at 03:54:00PM +0200, Ruslan Ermilov wrote: > > Under a big pressure from the FreeBSD community, GNU grep > > maintainers released grep-2.4d, which has a new option -I, > > a short equivalent to --binary-files='without-match'. > > Is this also equivalent to the old grep's -a option? I mean OLD grep, from > like 6 months ago? > Yes, that's why all this fuss have taken place ;=) > grep -a normally ignored binary files completely, back then. > It was a local FreeBSD feature; now it is part of the official GNU grep. -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: GNU grep 2.4d
On Mon, Jan 31, 2000 at 03:54:00PM +0200, Ruslan Ermilov wrote: > Under a big pressure from the FreeBSD community, GNU grep > maintainers released grep-2.4d, which has a new option -I, > a short equivalent to --binary-files='without-match'. Is this also equivalent to the old grep's -a option? I mean OLD grep, from like 6 months ago? grep -a normally ignored binary files completely, back then. -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ G++>+++ e-> h! r-->+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kldloaded driver not called at load time
I am trying to make kldloadable driver. But none of functions are called when I kldload it. Is this a bug or I am missing something essential? Sources, dmesg, config and makefile (for module) are at http://ethereal.ru/~nms/TR/tk.tar (~40Kb) P.S. I am chasing for IBM Token Ring Adapter (unknown0:). Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IP-Filter w/FreeBSD-current
With the impending release of FreeBSD-4.0, is anyone on this list using IP-Filter on FreeBSD-current? I'm planning to install -current w/IP-Filter on a testbed and would like to know of there are any gotchas or if it even runs on FreeBSD-current. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX GroupInternet: [EMAIL PROTECTED] ITSD Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installworld broken???
"Rodney W. Grimes" wrote: > Good analysis deleted... > > > src/usr.bin/xinstall could probably have been named src/usr.bin/install, > > but PROG has to be xinstall regardless. I guess they kept the two as > > xinstall for consistancy and in case there were other gotcha's like this. > > But you forgot what happens if you have a ``file'' named install: > > cd /tmp > mkdir install > make install > > Now you know the real reason the directory is called ``xinstall''. Ahh yes, of course. 'cd src/usr.bin; make install' would fail. :-) Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installworld broken???
Good analysis deleted... > src/usr.bin/xinstall could probably have been named src/usr.bin/install, > but PROG has to be xinstall regardless. I guess they kept the two as > xinstall for consistancy and in case there were other gotcha's like this. But you forgot what happens if you have a ``file'' named install: cd /tmp mkdir install make install Now you know the real reason the directory is called ``xinstall''. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installworld broken???
Andrzej Bialecki wrote:
> On Sun, 30 Jan 2000, John Polstra wrote:
>
> > > > It's source-dir is called "xinstall" btw.
> > > Why is the source called "xinstall"?
> >
> > To avoid colliding with the standard make target "install". If we
> > had utilities named "all", "depend", and "clean" we'd have to do the
> > same thing for them.
>
> Mhmmm... Isn't this something that .PHONY target is supposed to handle?
No. Consider:
PROG= install
all: ${PROG}
${PROG}:${OBJS}
cc -o ${PROG} ${OBJS}
install:
${INSTALL} ${PROG} ${BINDIR}
and with ${PROG} expanded out:
all: install
install:${OBJS}
cc -o install ${OBJS}
install:
${INSTALL} install ${BINDIR}
Spot the problem.. Does the target "install" mean "build the binary" or
"install the binary"?
src/usr.bin/xinstall could probably have been named src/usr.bin/install,
but PROG has to be xinstall regardless. I guess they kept the two as
xinstall for consistancy and in case there were other gotcha's like this.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
HEADS UP: GNU grep 2.4d
Hi! Under a big pressure from the FreeBSD community, GNU grep maintainers released grep-2.4d, which has a new option -I, a short equivalent to --binary-files='without-match'. Grep 2.4d is now in the source tree (Approved by: jkh). This, I hope, will finally close this can of worms ;=) Enjoy, -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "conflicts" keyword gone?
On Mon, Jan 31, 2000 at 06:06:09AM -0500, Donn Miller wrote: > I noticed that the "conflicts" keyword was eliminated from the kernel > config file syntax. Do we just eliminate this keyword, or is there > another keyword that we should use in its place? Sorry if I missed > this... > > - Donn > : peter 2000/01/29 10:07:08 PST : : Modified files: : sys/i386/confGENERIC LINT : sys/alpha/conf GENERIC : sys/pc98/confGENERIC98 : Log: : Remove 'conflicts' token - it has been effectively doing absolutely : nothing for quite some time. The only thing that cared was userconfig, : but it was for one invisible device so we never saw it's effects. : : Revision ChangesPath : 1.239 +2 -2 src/sys/i386/conf/GENERIC : 1.742 +2 -2 src/sys/i386/conf/LINT : 1.68 +2 -2 src/sys/alpha/conf/GENERIC : 1.126 +2 -2 src/sys/pc98/conf/GENERIC98 -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installworld broken???
On Mon, 31 Jan 2000, you wrote:
> On Sun, 30 Jan 2000, John Polstra wrote:
>
> > > > It's source-dir is called "xinstall" btw.
> > > Why is the source called "xinstall"?
> >
> > To avoid colliding with the standard make target "install". If we
> > had utilities named "all", "depend", and "clean" we'd have to do the
> > same thing for them.
>
> Mhmmm... Isn't this something that .PHONY target is supposed to handle?
How does that help? The problem is namespace pollution.
Consider
cd /usr/src/usr.bin
make install
Does this mean
cd /usr/src/usr.bin/install
make all
or
.for d in ${SUBDIRS}
(cd /usr/src/usr.bin/${d}; make install)
.endfor
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
for testing - suspend fix for UHCI controllers
When committing the patch to get suspend to work I managed to forget to
commit the parts for pci/[ou]hci_pci.c. The patch is given below. It
should make your devices suspend.
It is included in the big patchset as well.
This is against CURRENT (== 4.0-RC)
Thanks in advance.
Nick
Index: sys/pci/uhci_pci.c
===
RCS file: /home/ncvs/src/sys/pci/uhci_pci.c,v
retrieving revision 1.21
diff -w -u -r1.21 uhci_pci.c
--- uhci_pci.c 2000/01/26 10:52:27 1.21
+++ uhci_pci.c 2000/01/30 15:15:57
@@ -93,8 +93,13 @@
static int
uhci_pci_suspend(device_t self)
{
+ uhci_softc_t *sc = device_get_softc(self);
+ int err;
- bus_generic_suspend(self);
+ err = bus_generic_suspend(self);
+ if (err)
+ return err;
+ uhci_power(PWR_SUSPEND, sc);
return 0;
}
@@ -102,11 +107,9 @@
static int
uhci_pci_resume(device_t self)
{
-#if 0
uhci_softc_t *sc = device_get_softc(self);
- uhci_reset(sc);
-#endif
+ uhci_power(PWR_RESUME, sc);
bus_generic_resume(self);
return 0;
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] USB project
http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"conflicts" keyword gone?
I noticed that the "conflicts" keyword was eliminated from the kernel config file syntax. Do we just eliminate this keyword, or is there another keyword that we should use in its place? Sorry if I missed this... - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
patches for USB
As many things are still being tested, especially wrt OHCI controllers (support for them is fairly non-functional at the moment), I'll be updating a set of patches available from http://www.etla.net/~n_hibma/usb/USB-patch-CURRENT The patch is not for the faint of heart. It contains a snapshot of what I am doing at the moment, and, allthough I do my best to make things work, I'm pretty sure it will bomb your system. The list of things that are patched in there: CHANGELOG 2131 - Test bug-fix for handling of the done queue - handling of error queues where the transfer consists of more than one TD (OHCI_TD_HANDLED) - Better handling of the done queue when the TD that was in tailp is added to the done queue. In that case we simply skip it and proceed with the rest of the queue instead of dropping the whole queue. - Updated umass driver ** Be warned: While using it /bin/login all of a sudden coredumped ** and other things in the kernel went wrong mysteriously (vm ** errors, etc.). - Fix for the handling of suspend (patch has been posted on usb-bsd) - Fix for deallocation of resources when attach fails (both OHCI and UHCI). Please note that discussions on USB are held in usb-bsd and anyone interested is encouraged to subscribe to that mailing list at www.egroups.com. It is also available through the web interface http://www.egroups.com/. Cheers. Nick P.S.: The patch is not mentioned on the web page because the site is out of date. I'll be updating the site tomorrow or the day after. -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installworld broken???
On Sun, 30 Jan 2000, John Polstra wrote: > > > It's source-dir is called "xinstall" btw. > > Why is the source called "xinstall"? > > To avoid colliding with the standard make target "install". If we > had utilities named "all", "depend", and "clean" we'd have to do the > same thing for them. Mhmmm... Isn't this something that .PHONY target is supposed to handle? 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: More world breakage
> only. In -stable, and in -current before the end of December the > following tools: ls, rm, chflags, find, xinstall and mtree used > a common set of routines to manipulate file flags. [snip] > tool. At the beginnig of January, because of the proliferation of > utilities using these functions, I moved them to libutil in -current. [snip] > modes (setmode/getmode). This was what I did last week, renaming > flags_to_string to getflags, and string_to_flags to setflags. I [also moved to libc -- snip] > It may be argued that we should back out _both_ commits and resurrect > bin/ls/stat_flags.c. Would this gain us anything? Yes and no. The commits had a reason. Backing them out completely would only result in a second series of equivalent commits. It seems that install(1) is the only problem child. We can revert install(1) to have it's own set of functions and leave the rest as is. After installworld has been completed, install(1) can be changed back to use the libc versions. Comments? marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NEC ohci
It seems that support for OHCI type controllers for USB is completely broken at the moment. Why things all of a sudden fall over (before I committed the changes to ohci.c even) is beyond me, but there must be a reason. Please subscribe to [EMAIL PROTECTED] That's were most of the discussion is going on. Nick On Thu, 20 Jan 2000, Jun Kuriyama wrote: > From: Nick Hibma <[EMAIL PROTECTED]> > > Try running usbd -e and see if that makes your mouse show up. usbd -e > > does the explore once. > > I've tested on another machine with same NEC OHCI (Toshiba Libretto SS > 1000). > > - dmesg > ohci0: mem 0xffaff000-0xffaf irq 11 at device 11.0 >on pci0 > usb0: OHCI version 1.0 > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > - > > When I plugged USB ethernet device (aue0), there is no message. And > I've got message if I use "usbd -e". > > - > usb0: unrecoverable error, controller halted > usbd_new_device: addr=2, getting first desc failed > uhub_explore: usb_new_device failed, error=TIMEOUT > uhub0: device problem, disabling port 1 > - > > PCI IRQ 11 of this machine is shared with other devices. > > > Jun Kuriyama // [EMAIL PROTECTED] > // [EMAIL PROTECTED] > -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
