buildworld fails on 3.0
Well, I've cvsupped a number of times over the last week, zapped /usr/obj/* , made the includes, and keep getting exactly the same problem: my cvsup tag=RLENG_3 (or something like that) cd /usr/src make includes - this is OK make clean- this is OK nohup make buildworld 21 this is not so OK The first appearance occurs on line 23914 of nohup.out: gzip -cn /usr/src/sbin/i386/nextboot/nextboot.8 nextboot.8.gz === share === share/dict === share/doc === share/doc/psd === share/doc/psd/title touch _stamp.extraobjs (cd /usr/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1- /usr/src/sha re/doc/psd/title/Title) | gzip -cn Title.ascii.gz groff: can't find `DESC' file ^ groff:fatal error: invalid device `ascii' ^ === share/doc/psd/contents touch _stamp.extraobjs (cd /usr/src/share/doc/psd/contents; groff -mtty-char -Tascii -ms -o1- /usr/src/ share/doc/psd/contents/contents.ms) | gzip -cn contents.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' -- and it karks it around line 24128 === share/doc/usd/13.viref sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/usr/src/share/doc/usd/13.vire f/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/d ocs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ref.so\)$:\1/usr/s rc/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ ' s:\(\.so[\ \][\ \ ]*\)\(set.opt.roff\)$:\1/usr/src/share/doc/usd/13.viref/ ../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/usr/src/share/doc/usd/13.viref/../../../../contrib/nvi/d ocs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' /usr/src/share/doc/usd/13.viref /../../../../contrib/nvi/docs/USD.doc/vi.ref/vi.ref | groff -mtty-char -Tascii -t -s -me -o1- /dev/null groff: can't find `DESC' file ^ groff:fatal error: invalid device `ascii' ^ *** Error code 3 Stop. *** Error code 1 What do I do? should I zap the /usr/share/doc/* and re-cvsup? Eddie. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: buildworld fails on 3.0
On 3 Feb, Eddie Irvine wrote: re/doc/psd/title/Title) | gzip -cn Title.ascii.gz groff: can't find `DESC' file ^ groff:fatal error: invalid device `ascii' ^ === share/doc/psd/contents touch _stamp.extraobjs (cd /usr/src/share/doc/psd/contents; groff -mtty-char -Tascii -ms -o1- /usr/src/ share/doc/psd/contents/contents.ms) | gzip -cn contents.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' What do I do? should I zap the /usr/share/doc/* and re-cvsup? Eddie. Do you compile with -O3 (make.conf)? - try again with -O2 or less. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
On Wed, Feb 03, 1999 at 12:42:01PM +0800, Chia-liang Kao wrote: I did a `ping 192.168.100.1', and there is no response and no messages at all. I think the most interesting part of this is that I can see both of the lights on the hub blinking when I ping 192.168.100.1; while only the light of the other side blinks when he pings me. ... I use this driver as well, and have had conversations with Bill Paul before on this. It is now working well enough for my needs (but not anywhere resembling perfect -- transfers either direction have to be initiated from a different host). Maybe your machine and my machine that flakes out are similar: [excerpts from dmesg] CPU: AMD Am5x86 Write-Back (486-class CPU) Origin = AuthenticAMD Id = 0x4f4 Stepping=4 Features=0x1FPU real memory = 67108864 (65536K bytes) chip0: SiS 85c496 rev 0x31 on pci0.5.0 vr0: VIA VT3043 Rhine I 10/100BaseTX rev 0x06 int a irq 9 on pci0.13.0 vr0: Ethernet address: 00:a0:0c:c0:03:c1 vr0: autoneg complete, link status good (half-duplex, 10Mbps) The best conclusion I could come up with is that particular PCI chipset is flakey [maybe the entire chipset]. Only one pci card I have tried in that system has worked properly, and that was a display adapter -- this is out of about 6 different PCI cards of various types. -- Zach Heilig z...@uffdaonline.net / Zach Heilig z...@gaffaneys.com Americans are sensitive about their money, and since this was the first major change in the greenback in nearly 70 years, a radical redesign might have been too much for consumers to comprehend -- John Iddings [COINage, Feb. 1999]. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Linux devel doesn't work with glibc libs
On 03-Feb-99 Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: When trying to link, it complains about libc.os.6 vs libc.so.5. This makes life rather difficult when trying to test glide programs against my version the /dev/3dfx driver. Can someone commit the RedHat dev system (. egcs )? Ahh... This would explain a few things :-/ Damn I can't rebuild a copy of qkHacklib, or Mesa.. ARGH! --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make port and bsd.port.mk
Hi ... I recently upgraded from 3.0-current to 3.0-STABLE ... When running 3.0-current I was able to build ports without a problem. In the new system ... I get the following error : /usr/share/mk/bsd.port.mk, line 2: Could not find /usr/ports/Mk/bsd.port.mk make: fatal errors encountered -- cannot continue There is no /usr/ports/Mk directory on my machine (I did a make buildworld and a installworld ) Where can I find these files or is it a bug ?? Reinier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: make port and bsd.port.mk
On 03-Feb-99 Reinier Bezuidenhout wrote: Hi ... There is no /usr/ports/Mk directory on my machine Where can I find these files or is it a bug ?? cvsup your ports and all will be well. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: make port and bsd.port.mk
On Wed, 3 Feb 1999, Steve O'Hara-Smith wrote: On 03-Feb-99 Reinier Bezuidenhout wrote: Hi ... There is no /usr/ports/Mk directory on my machine Where can I find these files or is it a bug ?? cvsup your ports and all will be well. And make sure you're grabbing the ports-base collection (either explicitly or part of ports-all). Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: * From: Bill Paul wp...@skynet.ctr.columbia.edu * Date: Wed, 3 Feb 1999 00:24:27 -0500 (EST) * * I did a `ping 192.168.100.1', and there is no response and no messages * at all. I think the most interesting part of this is that I can see * both of the lights on the hub blinking when I ping 192.168.100.1; * while only the light of the other side blinks when he pings me. * * What kind of hub is this? It's a nonaccredited 5-port 10Bast-T hub which we used to connect outside world via another interface (my de0 and his ed0). And when we're trying to use this hub for internal connection only via both of our newly bought dfe530s, we're in trouble. Whoa whoa. Wait a minute; stop right there. Let me see if I understand this. You have a 5 port hub. One port has the connection that links you to the outside world (it goes to your router/switch/whatever). Another second port connects to your machine at de0. A third port connects to your roommate's machine on his ed0. And you have your vr0 interface and your roommate's vr0 interface both connected to this _same_ hub as well? (See, this is why I yell: I can see how somebody might try this and not think that it might cause problems. If I was right there looking at your systems I could probably spot this immediately, but it was only blind luck that you happened to mention it now, otherwise I could have spent months going back and forth with you via e-mail before finally dragging this piece of information out of you.) Uhm. I dunno. That doesn't seem right somehow. It adds another variable that has to be accounted for. The problem here is that when one of you sends a packet, it will end up a) delivered to _two_ interfaces on the target host and b) it will be echoed back to the other interface on the source host. Remember: an ordinary hub just retransmits whatever it hears on one port to every otgher port. Given that you don't seem to be experiencing any transmit or receive errors on the vr0 interface, I get the feeling that this configuration may be contributing to the problem somehow. You need to do one of three things to test to see if this is your problem: - Obtain (purchase/borrow/steal) a second hub, and connect all the 192.168.100 interfaces to it all by themselves. - Connect your vr0 interface to your roommate's vr0 interface directly using a crossover cable. (A crossover cable has the transmit and receive pairs reversed on one end.) - Temporarily unplug your de0 interface and his ed0 interface from the hub and leave just the vr0 interfaces plugged in. Use arp -d to remove each others' ARP entries from your respective ARP caches so that we start fresh. If you can successfully ping each other via the 192.168.100 interfaces and exchange traffic, then you have found the problem. (This is the easiest test, and it doesn't cost anything. :) If you had a _switch_ instead of a hub, then your configuration would probably work because a switch will only deliver traffic to one port (the port where the interface with the destination ethernet address is attached) instead of all ports. (Except for broadcasts and multicasts, without extra configuration.) At least, that's my suspicion. * - What does netstat -in show? Are there any input errors? Are there * any input packets? (If the input packet counter keeps incrementing * then it has to be receiving something.) * There are some Ipkts but very few as you can see in the following. # netstat -in Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll de0 1500 Link 00.80.c8.46.1e.d4 313987 3411118717 185 2651 de0 1500 140.112.240/2 140.112.240.59313987 3411118717 185 2651 vr0 1500 Link 00.80.c8.ef.82.09 16 015804 0 0 vr0 1500 192.168.100 192.168.100.2 16 015804 0 0 Hm... No transmit or receive errors. I wonder what all the output traffic is though. * - If you run tcpdump on the vr0 interface (tcpdump -n -e -i vr0) can * you see the traffic from the other host? Try the following: * * # arp -d 192.168.100.1 * # tcpdump -n -e -i vr0 * # ping -c 5 192.168.100.1 * * Show us the output. PING 192.168.100.1 (192.168.100.1): 56 data bytes 14:32:35.481753 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486348 0:80:c8:ef:82:9 ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.100.1 tell 192.168.100.2 14:32:36.486561 0:80:c8:ef:3c:3f 0:80:c8:ef:82:9 0806 60: arp reply 192.168.100.1 is-at 0:80:c8:ef:3c:3f 14:32:36.486625 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 192.168.100.1: icmp: echo request 14:32:37.496739 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f 0800 98: 192.168.100.2 192.168.100.1: icmp: echo request 14:32:38.506383 0:80:c8:ef:82:9 0:80:c8:ef:3c:3f
Re: problem with vr0
* From: Bill Paul wp...@skynet.ctr.columbia.edu * Date: Wed, 3 Feb 1999 09:26:24 -0500 (EST) * * And you have your vr0 interface and your roommate's vr0 interface both * connected to this _same_ hub as well? (See, this is why I yell: I can see * how somebody might try this and not think that it might cause problems. * If I was right there looking at your systems I could probably spot this * immediately, but it was only blind luck that you happened to mention * it now, otherwise I could have spent months going back and forth with * you via e-mail before finally dragging this piece of information out * of you.) Certainly not, sorry that I didn't specify precisely. I meant we used the hub very well connecting us and the outside world, and then we decided to use the hub for internal connection only. So the hub is now connecting our vr0's and nothing else. (Of course, the power adapter is connected. :) * - Obtain (purchase/borrow/steal) a second hub, and connect all the * 192.168.100 interfaces to it all by themselves. * * - Connect your vr0 interface to your roommate's vr0 interface directly * using a crossover cable. (A crossover cable has the transmit and receive * pairs reversed on one end.) * * - Temporarily unplug your de0 interface and his ed0 interface from the * hub and leave just the vr0 interfaces plugged in. Use arp -d to remove * each others' ARP entries from your respective ARP caches so that we * start fresh. If you can successfully ping each other via the * 192.168.100 interfaces and exchange traffic, then you have found the * problem. (This is the easiest test, and it doesn't cost anything. :) We are poor students, so the easiest test has been performed right after we can't get the vr0s to work. (actually it's mine, his works very fine) We even swapped our cards and the result (the ping/trafshow test) is the same. Also, the vr0 currently on my box was originally his, and he used the card to connect outside world in the past. Shouldn't be a kernel issue, since I have tried to get it right by booting his kernel. Anyway, I'll try the first two tests tomorrow. (Ya, you know it, I'll steal one.) * vr0 1500 Link 00.80.c8.ef.82.09 16 015804 0 0 * vr0 1500 192.168.100 192.168.100.216 015804 0 0 * * Hm... No transmit or receive errors. I wonder what all the output traffic is * though. When I ping him, he can receive my packets and replies, while I can't get his reply. I think that's where th output packet came from. (ie the icmp outgoing packets when I ping him). And `netstat -in' on his box shows the input and output packets on vr0 are nearly identical. * Hm. Okay. Here's a slightly different test: * * # tcpdump -n -e -i vr0 * # arp -d 192.168.100.1 * # ping -c 192.168.100.1 * # arp -d 192.168.100.1 * # ping -c 192.168.100.1 * * One possibility is that the receiver is getting stuck and has to be reset; * running tcpdump to put the interface in promiscuous mode implicity * reinitializes and resets the card (it happens that that's how the driver * works). In the above example, we initialize the card once and then leave * it alone, then run the arp -d/ping test twice. If you see the same exact * results both times (i.e. the chip receives at least one frame) then the * receiver is not getting wedged, since it would be receiving at least * two frames correctly without having to be reset. The difference of the above two arp -d/ping are: the first one have 3 `arp who-has' message and 1 arp reply and 3 icmp echo the second one have 5 `arp who-has' and 1 arp reply and 1 icmp echo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: * And you have your vr0 interface and your roommate's vr0 interface both * connected to this _same_ hub as well? (See, this is why I yell: I can see * how somebody might try this and not think that it might cause problems. * If I was right there looking at your systems I could probably spot this * immediately, but it was only blind luck that you happened to mention * it now, otherwise I could have spent months going back and forth with * you via e-mail before finally dragging this piece of information out * of you.) Certainly not, sorry that I didn't specify precisely. I meant we used the hub very well connecting us and the outside world, and then we decided to use the hub for internal connection only. So the hub is now connecting our vr0's and nothing else. (Of course, the power adapter is connected. :) Ah, okay. My bad. It sure looked like you were saying you had everything attached to the same hub. We even swapped our cards and the result (the ping/trafshow test) is the same. Also, the vr0 currently on my box was originally his, and he used the card to connect outside world in the past. Shouldn't be a kernel issue, since I have tried to get it right by booting his kernel. What kind of machine/CPU does your friend have? Anyway, I'll try the first two tests tomorrow. (Ya, you know it, I'll steal one.) * vr0 1500 Link 00.80.c8.ef.82.09 16 015804 0 0 * vr0 1500 192.168.100 192.168.100.216 015804 0 0 * * Hm... No transmit or receive errors. I wonder what all the output traffic is * though. When I ping him, he can receive my packets and replies, while I can't get his reply. I think that's where th output packet came from. (ie the icmp outgoing packets when I ping him). And `netstat -in' on his box shows the input and output packets on vr0 are nearly identical. Hm. I have some more questions: - In your first posting, you mentioned this: vr0: VIA VT3043 Rhine I 10/100BaseTX rev 0x06 int a irq 12 on pci0.19.0 IRQ 12 is normally used by the mouse (if you have a PS/2 mouse). Do you have a mouse or PS/2 mouse port on this machine? (I suspect you don't but I have to ask.) - How many PCI bus slots does your machine have? - Have you tried putting the vr0 card in a different slot? Have you tried putting it in the slot where the de0 card is now? - What PCI chipset do you have? The test machine in which I currently have my sample VIA Rhine card installed is an Intel Pentium 200 system that says the following: chip0 Intel 82437VX PCI cache memory controller rev 1 on pci0:0:0 chip1 Intel 82371SB PCI-ISA bridge rev 1 on pci0:7:0 chip2 Intel 82371SB IDE interface rev 0 on pci0:7:1 [...] vr0 VIA VT3043 Rhine I 10/100BaseTX rev 6 int a irq 9 on pci0:15:0 vr0: Ethernet address: 00:a0:0c:c0:01:e7 vr0: autoneg complete, no carrier - Can you show me the output of the following: pciconf -r pci0:19:0 0xc I want to see what the latency timer setting looks like. This may be something do to with your particular PCI chipset or motherboard; unfortunately, I have only Intel systems here so it's hard to duplicate your exact setup. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
* From: Bill Paul wp...@skynet.ctr.columbia.edu * Date: Wed, 3 Feb 1999 11:12:59 -0500 (EST) * * What kind of machine/CPU does your friend have? my friend's: CPU: Pentium II (233.86-MHz 686-class CPU) Origin = GenuineIntel Id = 0x634 Stepping=4 Features=0x80f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX chip0: Host to PCI bridge (vendor=8086 device=7180) rev 0x03 on pci0.0.0 chip1: PCI to PCI bridge (vendor=8086 device=7181) rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.4.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.4.1 chip3: Intel 82371AB Power management controller rev 0x01 on pci0.4.3 vr0: VIA VT3043 Rhine I 10/100BaseTX rev 0x06 int a irq 10 on pci0.11.0 vr0: Ethernet address: 00:80:c8:ef:3c:3f vr0: autoneg complete, link status good (half-duplex, 10Mbps) Mine: CPU: Pentium/P54C (133.64-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 chip0: Intel 82437VX PCI cache memory controller rev 0x01 on pci0.0.0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX3 Bus-master IDE controller rev 0x00 on pci0.7.1 vr0: VIA VT3043 Rhine I 10/100BaseTX rev 0x06 int a irq 12 on pci0.19.0 vr0: Ethernet address: 00:80:c8:ef:82:09 vr0: autoneg complete, link status good (half-duplex, 10Mbps) * Hm. I have some more questions: * * - In your first posting, you mentioned this: * vr0: VIA VT3043 Rhine I 10/100BaseTX rev 0x06 int a irq 12 on pci0.19.0 * IRQ 12 is normally used by the mouse (if you have a PS/2 mouse). Do you * have a mouse or PS/2 mouse port on this machine? (I suspect you don't but * I have to ask.) No, I use a mouse connected to com port. Actually we thought of the problem caused by irq conflicts, and we made sure it wasn't happening. It is very strange that when I used the incorporated diagnose program, I can connect to my friend's dfe530, running the same program. * - How many PCI bus slots does your machine have? I have 3 PCI bus slots. It's quite an old machine. * - Have you tried putting the vr0 card in a different slot? Have you tried * putting it in the slot where the de0 card is now? Yes, I had previously done exactly the same test you mentioned. * - What PCI chipset do you have? The test machine in which I currently have * my sample VIA Rhine card installed is an Intel Pentium 200 system that * says the following: As you can see in the top of this mail, my chipset configuration seemed to be identical as yours. * - Can you show me the output of the following: * * pciconf -r pci0:19:0 0xc * * I want to see what the latency timer setting looks like. It shows `0x2008' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
LD problems... (Pilot error no doubt)
I have a 4.0-current system which has been upgraded from 3.0-current... I keep getting errors such as: /usr/libexec/ld-elf.so.1: Shared object libmysqlclient.so.5.2 not found (There are numerous other ones for other libraries)... This stops anything that's in '/etc/rc.d' from starting (e.g. Apache, Samba, Squid etc.) If I manually run the /etc/rc.d/ contents after the machine has come up it all works fine... I'm guessing I've missed something - but I can't figure what? - As far as I can see ldconfig has no config file on FreeBSd, and it's confusing me (doesn't take much)... If I run 'ldconfig -elf -R -v' I get no output... If I run 'ldconfig -aout -R -v' I get a stream of all the libraries it found... Any help gratefuly received (as always :-) -Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
3.0 vs 4.0
Can someone summarize the difference and locations between all these things? I've heard of: 2.2.8-stable 3.0-stable 3.0-current 3.0-release 4.0-current Where are all these things? Some in source? Some in binary? I've just been grabbing the things in pub/FreeBSD on current.freebsd.org. I assume those are daily builds of 3.0-stable. Is it still true that 2.2.8 is the thing that folks get when they go to the www.freebsd.org website and grab the the latest stable thing? I've been on this list for a while and there doesn't seem to be a document anywhere saying what any of this is. It is quite confusing. An explanation would be incredibly appreciated. -Rob To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Location of 4.0-current?
Where might I find 4.0 - I've got another development machine available for some thrashing. TIA. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
OBJLINK=yes breaks make buildworld
Make buildworld is broken for the OBJLINK=yes case, and it may have been broken for quite some time. When the a.out legacy libraries are built, the object files end up in the source tree, because the obj links no longer point to the right place. Furthermore, these object files don't get removed when you do a make clean or a make cleandir. I don't have a fix. I never use OBJLINK. As far as I'm concerned, a suitable fix would be to eliminate that option altogether. This is the cause of one kind of libpam build failure, namely the one that ends like this: /usr/src/lib/libpam/libpam/../modules/pam_cleartext_pass_ok/libpam_cleartext_pas s_ok.a: object /usr/src/lib/libpam/libpam/../mo dules/pam_cleartext_pass_ok/libpam_cleartext_pass_ok.a(pam_cleartext_pass_ok.o) in archive is not object *** Error code 1 Thanks to Jon Hamilton for suggesting the OBJLINK connection. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
libpam related buildworld failures
There have been some reports of builds failing in libpam. With help from Jon Hamilton, I've narrowed down the causes. There are at least two different failure modes, but the solution is the same in either case. * Don't define OBJLINK. It is badly broken, and a libpam build failure happens to be the first symptom you're likely to see. * Don't define NOCLEAN. * Scan your entire source tree and make sure there are no symbolic links named obj there. Remove any that you find. * Scan your source tree under /usr/src/lib/libpam and make sure there are no symbolic links at all. Remove any that you find. * Scan your source tree under /usr/src/lib/libpam and make sure there are no files with names matching *.[oa] or *.?o there. Remove any that you find. Don't assume that a make clean or make cleandir will remove the files above. Check manually using find. Once your source tree is cleaned up, if you avoid using OBJLINK, it will stay clean. Note, these problems have nothing to do with libpam. It's just the thing that's getting clobbered by polluted source trees resulting from unrelated breakage. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 3.0 vs 4.0
On Wed, 3 Feb 1999, HighWind Software Information wrote: Can someone summarize the difference and locations between all these things? Think of it as a tree where the trunk is -current and branches are -stable. There is only one -current but potentally many -stables. Each release with a new major version number creates a new branch. Old branches, starved for light, eventually wither and die. current | | | stable || | 3.1 || stable | / || / 2.2.8 | / ||/ 2.2.7 | 3.0 || 2.2.6 | || \ | 2.1 \ | \ | \| 2.0 | | 2.2.8-release is (supposedly) the end of the line for the 2.2 branch of FreeBSD but critical bugs continue to be fixed and they show up in the 2.2.8-stable branch. You can get binary snapshots of this branch to pick up the bug fixes, or you can get the source and make world to get them. Call 2.2.8-stable the trailing edge. 3.0-stable is is the actively maintained stable branch from which the next release (3.1) will come. The primary activity on this--or any stable branch--is bug fixes rather than new features, although new features will appear over time. Call 3.0-stable the cutting edge. There is only one -current at any given time and the version number just indicates what the next major release will be. Since there is only one, it is usually just called -current and this is where exciting new features and bugs are introduced to FreeBSD. Call -current the bleeding edge. Is it still true that 2.2.8 is the thing that folks get when they go to the www.freebsd.org website and grab the the latest stable thing? Speaking only for myself, I'd say that is correct. Once 3.1 comes out, then I would say 3.1 is the latest stable thing. I'm not sure that *any* dot zero release should be considered stable. -john To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Quick vm_map_insert() question
Hopefully somebody who knows the VM system better than I do can answer this easily. In sys/kern/imgact_elf.c, vm_map_insert() is used to map the segments of an ELF file. In all of the calls, the address of the mapping is specified explicitly. I'd like to experiment with letting the system choose the address itself for the ELF dynamic linker. In other words, I want it to be mapped just as if a userland call to mmap(0, ...) had been done. Can somebody tell me how to do that? Thanks, John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
aio_read panics SMP kernel
Hi, I'm using a dual 350MHz Dell Precision 410 with 4.0-19990130-SNAP (SMP enabled) to prototype a program that uses asynchronous read and write (aio_read() and aio_write()), and found that the following simple and not very useful program (it's for demonstration purposes only!) causes the system to do one of three things: 1) panic - page fault in the kernel ... I don't have any other specifics, I will follow up with the details provided by the console as soon as I can make this occur again (I should have written it down the first time). 2) reset - no panic or anything, just a system reset and subsequent reboot 3) hang - everything totally unresponsive, machine does not respond to pings or anything else, no keyboard response. Below, please find the output of 'mptable' for the SMP experts and the program that I used to cause the panic. Any help on fixing this and/or suggestions on what I might be doing wrong are much appreciated. Thanks, -Brian -- Brian Dean Process Engineering brd...@unx.sas.com Following is the output of 'mpinfo' on this machine: [r...@mrose]:/brdean- mptable === MPTable, version 2.0.15 --- MP Floating Pointer Structure: location: BIOS physical address: 0x000fe710 signature:'_MP_' length: 16 bytes version: 1.4 checksum: 0x91 mode: Virtual Wire --- MP Config Table Header: physical address: 0x000f signature:'PCMP' base table length:468 version: 1.4 checksum: 0x33 OEM ID: 'DELL' Product ID: 'WS 410 ' OEM table pointer:0x OEM table size: 0 entry count: 50 local APIC address: 0xfee0 extended table length:0 extended table checksum: 0 --- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model StepFlags 0 0x11BSP, usable 6 5 2 0x183fbff 1 0x11AP, usable 6 5 2 0x183fbff -- Bus:Bus ID Type 0 PCI 1 PCI 2 PCI 3 ISA -- I/O APICs: APIC ID Version State Address 2 0x11usable 0xfec0 -- I/O Ints: TypePolarityTrigger Bus ID IRQAPIC ID PIN# ExtINT active-hiedge3 0 20 INT conformsconforms3 1 21 INT conformsconforms3 0 22 INT conformsconforms3 3 23 INT conformsconforms3 4 24 INT conformsconforms3 5 25 INT conformsconforms3 6 26 INT conformsconforms3 7 27 INT conformsconforms3 8 28 INT conformsconforms3 9 29 INT conformsconforms310 2 10 INT conformsconforms311 2 11 INT conformsconforms312 2 12 INT conformsconforms314 2 14 INT conformsconforms315 2 15 INT conformsconforms0 13:A 2 16 INT conformsconforms0 14:D 2 16 INT conformsconforms0 16:B 2 16 INT conformsconforms1 0:A 2 16 INT conformsconforms2 6:C 2 16 INT conformsconforms2 9:D 2 16 INT conformsconforms0 13:B 2 17 INT conformsconforms0 14:A 2 17 INT conformsconforms0 16:C 2 17 INT conforms
Re: KLD confusion..
Mike Smith writes: Take the following scenario: compiled in: module A kldstat -v shows module 'A' kldload A damned thing succeeds. That's correct. There's a fundamental problem here in that there's a confusion between file names and module names. This is a basic flaw in the way that KLD was implemented (no offense to Doug; it was initially meant to be a better LKM, not necessarily a whole new ball of wax). I've taken about four different runs at a right way of doing this subsequently. I think that, with some help and advice from Doug and Peter, I'm on the right track now, but there's no hope of it being ready for 3.1. This may be oversimplifying, but why wouldn't this work: just do everything at the module level: - All dependencies are inter-*module* dependencies. - Only one *module* with the same name can be loaded at one time. - KLD files (eg, foo.ko) are simply containers for one or more modules. We'd take the conservative stance on loading: if you tried to kldload foo.ko, it would fail unless *all* the modules in it were successfully able to link load. It seems if you just make consistent what the atomic unit of linking is (is it a file?? it is a module??) then all will be well. We just have to make sure we have unique names for all modules as we do now for files. Now, there remains the problem of how do you find the file foo.ko containing module bar, eg, if you want to auto-load dependencies? For starters, we could just assert that only module foo can be found this way. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make port and bsd.port.mk
Steve O'Hara-Smith writes: There is no /usr/ports/Mk directory on my machine Where can I find these files or is it a bug ?? cvsup your ports and all will be well. I'm curious what the reason for moving the includes to /usr/ports/Mk was.. is this to insure better consistency? That would make sense. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make port and bsd.port.mk
On Wed, 3 Feb 1999, Archie Cobbs wrote: Steve O'Hara-Smith writes: There is no /usr/ports/Mk directory on my machine Where can I find these files or is it a bug ?? cvsup your ports and all will be well. I'm curious what the reason for moving the includes to /usr/ports/Mk was.. is this to insure better consistency? That would make sense. It makes since to me, but I'm a little confused about the timing of this change. It was rather annoying to update my 2.2.8-STABLE machine a day or two after being told that cvsuping ports on a 2.2 machine might cause breakage (re: the no more 2.2 support announcement) to find that *not* cvsuping ports broke my ports collection because the makefiles moved to /usr/ports/Mk. Don't get me wrong, I like the change, but the timing seems less the perfect. -- Brooks To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Quick vm_map_insert() question
Look at vm_map_find. Alan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
rc.conf needs updating
Just a note that rc.conf needs updating. --- rc.conf.origWed Feb 3 13:10:46 1999 +++ rc.conf Wed Feb 3 13:12:54 1999 @@ -195,7 +195,7 @@ kern_securelevel_enable=NO # kernel security level (see init(8)), kern_securelevel=-1 # range: -1..3 ; `-1' is the most insecure update_motd=YES # update version info in /etc/motd (or NO) -vinum_slices=# put in names of vinum slices to enable vinum +vinum_drives=# put in names of vinum drives to enable vinum ## ### Allow local configuration override at the very end here ## Cheers! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: problem with vr0
Of all the gin joints in all the towns in all the world, Chia-liang Kao
had to walk into mine and say:
[chop]
* - Can you show me the output of the following:
*
* pciconf -r pci0:19:0 0xc
*
* I want to see what the latency timer setting looks like.
It shows `0x2008'
Hmm... Alright, I have a patch I'd like you to try. I don't know that
this will really have an effect, but I'm curious to see what it does.
If this doesn't work, then the only other thing I can think of is if
you can give me login access to your machine so that I can try some
experiments.
Anyway, to apply the patch, do the following:
- Save this message to /tmp/vr.patch (or something similar).
- Become root.
- Type the following:
# cd /sys/pci
# patch /tmp/vr.patch
- Compile a new kernel and boot it.
Let me know if this has any effect on the card's behavior.
-Bill
--
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: wp...@ctr.columbia.edu | Center for Telecommunications Research
Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City
=
It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness
=
*** ../CVSWORK/sys_pci/if_vr.c Mon Feb 1 16:25:52 1999
--- if_vr.c Wed Feb 3 16:11:24 1999
***
*** 899,905
vm_offset_t pbase, vbase;
#endif
u_char eaddr[ETHER_ADDR_LEN];
! u_int32_t command;
struct vr_softc *sc;
struct ifnet*ifp;
int media = IFM_ETHER|IFM_100_TX|IFM_FDX;
--- 899,905
vm_offset_t pbase, vbase;
#endif
u_char eaddr[ETHER_ADDR_LEN];
! u_int32_t command, lat;
struct vr_softc *sc;
struct ifnet*ifp;
int media = IFM_ETHER|IFM_100_TX|IFM_FDX;
***
*** 988,993
--- 988,1002
goto fail;
}
+ /* bump up the latency timer a little */
+ command = pci_conf_read(config_id, VR_PCI_LATENCY_TIMER);
+ lat = (command 0xFF00) 8;
+ if (lat 64) {
+ command = 0x00FF;
+ command |= 0x4000;
+ pci_conf_write(config_id, VR_PCI_LATENCY_TIMER, command);
+ }
+
/* Reset the adapter. */
vr_reset(sc);
***
*** 1675,1680
--- 1684,1692
VR_CLRBIT(sc, VR_TXCFG, VR_TXCFG_TX_THRESH);
VR_SETBIT(sc, VR_TXCFG, VR_TXTHRESH_STORENFWD);
+
+ /* Adjust configuration a little */
+ CSR_WRITE_2(sc, VR_BCR0, 0x0006);
/* Init circular RX list. */
if (vr_list_rx_init(sc) == ENOBUFS) {
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: How do I query system temperature probes ?
On Wed, Feb 03, 1999 at 02:51:37PM +1030, Matthew Thyer wrote: I seem to have all the hardware required for querying the temperature probes in the system (At least I can do it from the BIOS). How can I query this info ? I assume I need controller smbus0 and controller intpm0 in my kernel. But do I also need device smb0 at smbus? and/or any of the following: # ici2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. You need: controller intpm0 # the PIIX4 interface controller smbus0 # the SMBus system device smb0 at smbus? # user access to the SMBus Once I have all this stuff in my kernel, what commands do I use to query the probes ?? Takanori Watanabe takaw...@shidahara1.planet.sci.kobe-u.ac.jp as example code to do this. My system is FreeBSD 4.0-CURRENT (of CTM 3722 - but will soon be really -CURRENT) Extract from dmesg: chip0: Host to PCI bridge (vendor=8086 device=7180) rev 0x03 on pci0.0.0 chip1: PCI to PCI bridge (vendor=8086 device=7181) rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 chip3: Intel 82371AB Power management controller rev 0x01 on pci0.7.3 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ppbus0: VLSI Vision Ltd PPC2 Camera MEDIA CPIA_1-20
On Wed, Feb 03, 1999 at 02:15:39AM +, Stephen Palmer wrote: While looking at the output from dmesg, I noticed the following which I don't remember having seen before. (Of course I might not have had the camera hooked up to this system while running FreeBSD before ;-) Sure, this is really new. Probing for PnP devices on ppbus0: ppbus0: VLSI Vision Ltd PPC2 Camera MEDIA CPIA_1-20 What it means: the parallel port bus system - ppbus - probes the parallel port in order to detect eventually an IEEE1284 (parallel port standard released in 1994) compliant device. So your camera is IEEE1284 compliant because ppbus could enter the NIBBLE-get_device_id mode and retrieve PnP info from it. The line before tells you something like IEEE1284 device found... with the available IEEE1284 modes supported by your device. This is actualy a Zoom/Video Cam PPC which I use under Win98 from time to time. Any chance of getting working images from this device under FreeBSD-current? How would I go about this? The link protocol is supported by FreeBSD, this is what the IEEE1284 stuff is for. But you'll also need info about higher protocols of the device to drive it correctly. (1) The device is really simple and a 'cat' from the parallel port in any of the supported modes is enough. That would suppose the camera dumps pictures to the port as they are captured. Of course, you should guess the format. This is the case with printers supporting IEEE1284: cat /dev/lpt0 gives printer info (READY, OUT OF PAPER...). If NIBBLE mode is supported by your device, which is not certain if I remember well your logs, you can try cat /dev/lpt0. Otherwise we'll have to hack ppi(4) to give it a try.. (2) The device is more complicated and an analyser under windows may give you the magic sequence to enter plain reverse mode to retrieve pictures as they are captured. This system is not currently very current (Jan 14, 1999 / no pun intended) but I'm cvsup'ing as I type this... Stephen L. Palmer slpal...@netscape.net Nicholas. More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
Speaking of pam, when will it be fixed to support all the various service types? Or is that a do it yourself project? - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
Alex Zepeda wrote: Speaking of pam, when will it be fixed to support all the various service types? Or is that a do it yourself project? As you know, questions of the form when will X happen rarely get useful answers around here. So here's my useless answer: When it's finished. :-) I'm working on it as fast as my available time permits. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
On Wed, 3 Feb 1999, John Polstra wrote: Alex Zepeda wrote: Speaking of pam, when will it be fixed to support all the various service types? Or is that a do it yourself project? As you know, questions of the form when will X happen rarely get useful answers around here. So here's my useless answer: When it's finished. :-) I'm working on it as fast as my available time permits. Well I should have rephrased that. I was curious if anyone knew about it or was working on it. What exactly needs to be done here (I know next to nothing about pam)? - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: OBJLINK=yes breaks make buildworld
Make buildworld is broken for the OBJLINK=yes case, and it may have been broken for quite some time. When the a.out legacy libraries are built, the object files end up in the source tree, because the obj links no longer point to the right place. Furthermore, these object files don't get removed when you do a make clean or a make cleandir. I don't have a fix. I never use OBJLINK. As far as I'm concerned, a suitable fix would be to eliminate that option altogether. As far as I'm concerned, and speaking as the author of that hack, I agree with you! :-) Kill it. Kill it dead. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
Alex Zepeda wrote: Well I should have rephrased that. I was curious if anyone knew about it or was working on it. What exactly needs to be done here (I know next to nothing about pam)? Well, if by service types you meant login, ftp, telnet, etc., then what needs to be done is to convert ftpd, telnetd, etc. to use PAM instead of doing their own authentication. For ftpd that will require a few relatively minor PAM module fixes having to do with the fact that FTP as viewed from the server is sort of an event-driven machine rather than an interactive conversation. That's what my near-term focus is on. If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
No I meant service as in authentication types or tasks whatever ya call it. From the man page: PAM separates the tasks of authentication into four inde- pendent management groups: account management; authentica- tion management; password management; and session manage- ment. (We highlight the abbreviations used for these groups in the configuration file.) authentication works.. but everything else gives unresolved (or defined) symbols... so kdm, xdm, and samba don't work with pam on FreeBSD (well those are the ones I've tried). - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
Alex Zepeda wrote: No I meant service as in authentication types or tasks whatever ya call it. From the man page: Well, service type is a specific term in PAM that refers to things like login, ftp, ppp, and so forth. PAM separates the tasks of authentication into four inde- pendent management groups: account management; authentica- tion management; password management; and session manage- ment. (We highlight the abbreviations used for these groups in the configuration file.) authentication works.. but everything else gives unresolved (or defined) symbols... so kdm, xdm, and samba don't work with pam on FreeBSD (well those are the ones I've tried). That's what I meant by: If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. I'm going to work now. Gotta keep food on the table. Bye! :-) John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Nobody ever went broke underestimating the taste of the American public. -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: About /usr/mdec/cdboot
On Sun, 31 Jan 1999, Tomoyoshi ASANO wrote: When CD booting, some error messages is displayed. And I tested other machines supported atapi-cdrom booting. (In /usr/sys/i386/boot/cdboot/boot.c) Your BIOS int 0x13 extensions seem to be disabled. It's impossible to boot a CD-ROM without them. (BIOS int 0x13 fn 0x4b01 yielded error ?) I'm sorry I don't know 0x13 extensions. Is /usr/mdec/cdrom supported atapi-cdrom booting ? Check that your BIOS is enabled. It's talking about hooking into the BIOS disk IO routines such that they can access the SCSI device. If you can boot from a hard disk on this controller, then you should be able to boot from a CD-ROM on the same controller, if it supports CD-ROM booting at all. Adrian -- [ adr...@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: libpam related buildworld failures
On Wed, 3 Feb 1999, John Polstra wrote: That's what I meant by: If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. No. I don't want/need radious support. kdm and samba only do password authentication AFAIK, why they don't use the auth method (or whatever) I don't know. They work without Radius and without Pam.. but that doesn't fix the underlying problem I'm going to work now. Gotta keep food on the table. Bye! :-) Have fun! ;) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Reading a text file with BTX
On 30-Jan-99 Robert Nordier wrote about Re: Reading a text file with BTX: Daniel C. Sobral wrote: Robert Nordier wrote: Daniel C. Sobral wrote: Y'know, in my computer that F5 is Drive 0, and the system will not boot unless I select it first. Selecting it, makes the OSes boot and F5 disappear. Right on the mark. BTW, my BIOS is set so the cd drive is searched before the hd on boot. Could that be the cause? Seems a reasonable assumption, but I don't know for sure. It is. Robert Nordier Bye, UP To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make world: fail
Hi! At least for a week now i can't make world with following message: === sys/modules/syscons/logo make: don't know how to make /usr/src/sys/modules/syscons/logo/@/i386/isa/videoio.h. Stop *** Error code 2 Stop. *** Error code 1 ... What i'm getting wrong? Maybe i've missed something? Adios, /KONG To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world: fail
On Thu, 4 Feb 1999, Hostas Red wrote: Hi! At least for a week now i can't make world with following message: === sys/modules/syscons/logo make: don't know how to make /usr/src/sys/modules/syscons/logo/@/i386/isa/videoio.h. Stop *** Error code 2 Stop. *** Error code 1 ... What i'm getting wrong? Maybe i've missed something? cd /usr/src/sys/modules/syscons/logo make cleandepend Did you compile this module before? That's the remnants. Adios, /KONG Regards, Vladimir ===|=== Vladimir Kushnir | ku...@mail.kar.net, |Powered by FreeBSD kush...@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Reading a text file with BTX
Ugo Paternostro wrote: On 30-Jan-99 Robert Nordier wrote about Re: Reading a text file with BTX: Daniel C. Sobral wrote: Robert Nordier wrote: Daniel C. Sobral wrote: Y'know, in my computer that F5 is Drive 0, and the system will not boot unless I select it first. Selecting it, makes the OSes boot and F5 disappear. Right on the mark. BTW, my BIOS is set so the cd drive is searched before the hd on boot. Could that be the cause? Seems a reasonable assumption, but I don't know for sure. It is. Proof? -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: rc.conf needs updating
On Wednesday, 3 February 1999 at 13:15:04 -0800, Jake wrote: Just a note that rc.conf needs updating. --- rc.conf.orig Wed Feb 3 13:10:46 1999 +++ rc.conf Wed Feb 3 13:12:54 1999 @@ -195,7 +195,7 @@ kern_securelevel_enable=NO # kernel security level (see init(8)), kern_securelevel=-1# range: -1..3 ; `-1' is the most insecure update_motd=YES# update version info in /etc/motd (or NO) -vinum_slices= # put in names of vinum slices to enable vinum +vinum_drives= # put in names of vinum drives to enable vinum ## ### Allow local configuration override at the very end here ## Oops. Thanks for prodding me. It's done now. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up: comitted optimization to vm_map_insert()
On Tue, 2 Feb 1999, Matthew Dillon wrote: I've comitted an optimization to vm_map_insert() after initial tests seemed to indicate that it works. Basically it allows OBJT_SWAP objects to be optimized in addition to OBJT_DEFAULT objects already optimized in certain specific cases. However, a followup test that I had never run before had a temporary seg-fault ( i.e. it didn't repeat when I re-ran the test ). I think the seg fault may have revealed a new bug and is not related to the optimization I comitted, so I haven't backed out the commit. I am not 100% sure though, and I am testing this now. What test? If we had this exact test, it could be exploiting the exact bug, could it not? I'll let you know of any weird crashes in previously stable programs. If anyone notices weird seg-faulting that didn't occur before tonight, please notify me! Will do! CPU_WT_ALLOC actually seemed to have caused instability before... -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Network Cards
I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... -- Rod Taylor Proud Member of Team OS/2 User of FreeBSD KDE To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Boot block problem
Just upgraded to 3.0-stable snapshot circa 2/1 and noticed that the new booteasy does not seem to remember the selection from the previous time. Eg., I need to press F5 to get to disk 2 but it always defaults to F2 (which is FreeBSD slice containing only a swap partition). This means my box won't reboot automatically anymore, e.g., if the power goes out. Is this a new bug or a new feature? :-) Thanks, -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
On Wed, 3 Feb 1999, Rod Taylor wrote: I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). look at /etc/rc* , try to formulate something like rc.conf where you define internet interfaces like: eth0 = xl0 look at rc.firewall for better examples. However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... ifconfig -a Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/4.0-current To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
locale errors
While browsing through some directories I noticed an annoying error in locale based sorting. My LANG is set to de_DE.ISO_8859-1 Sorting treats ss as a single character instead of two. This leads to some interesting (at least) errors in displaying sorted output. My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII If I type 2 characters ss, I mean 2 characters ss. If I type ß I mean the single character ß. This sorting behaviour is just wrong. Not every apperence of ss even in pure ASCII does mean ß. I suggest removing any multi character definition out of the collate files. Daniel To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
various -CURRENT nits
I've got a few patches today; let's see:
The TCB hash check is broken, because ffs() returns offsets starting
at 1, not 0.
Some of VoxWare doesn't compile.
In addition, if anyone thinks it should be done, should I make PQ_L[12]_SIZE
config(8) tuneable (individually, not via PQ_FOOCACHE)? I use different
values because I have a K6-2 (8+8 pages L1) that does not match PQ_L1_SIZE.
I'd also like to readd the comment that CPU_WT_ALLOC might not be stable on
a K6-2, because it actually _doesn't_ seem to be stable here. The fixes to
the two problems follow.
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
--- src/sys/netinet/tcp_subr.c.orig Wed Feb 3 21:40:42 1999
+++ src/sys/netinet/tcp_subr.c Wed Feb 3 21:42:17 1999
@@ -136,8 +136,8 @@
tcbinfo.listhead = tcb;
if (!(getenv_int(net.inet.tcp.tcbhashsize, hashsize)))
hashsize = TCBHASHSIZE;
- if ((1 ffs(hashsize)) != hashsize) {
- printf(WARNING: TCB hash size not a power of 2\n);
+ if ((1 (ffs(hashsize) - 1)) != hashsize) {
+ printf(WARNING: TCB hash size (%d) not a power of 2\n,
hashsize);
hashsize = 512; /* safe default */
}
tcbinfo.hashbase = hashinit(hashsize, M_PCB, tcbinfo.hashmask);
--- src/sys/i386/isa/sound/os.h.origWed Feb 3 20:51:52 1999
+++ src/sys/i386/isa/sound/os.h Wed Feb 3 20:51:47 1999
@@ -18,6 +18,7 @@
#include sys/malloc.h
#include sys/buf.h
#include sys/signalvar.h
+#include sys/select.h
#include machine/soundcard.h
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: locale errors
On Thu, Feb 04, 1999 at 03:50:21AM +0100, D. Rock wrote: Sorting treats ss as a single character instead of two. This leads to some interesting (at least) errors in displaying sorted output. My locale is set do de_DE.ISO_8859-1, not de_DE.ASCII If I type 2 characters ss, I mean 2 characters ss. If I type ъ I mean the single character ъ. This sorting behaviour is just wrong. Not every apperence of ss even in pure ASCII does mean ъ. I suggest removing any multi character definition out of the collate files. It was Joerg initiative, I don't know DE enough to judge here. Please resolve this problem with him (CC'ed). -- Andrey A. Chernov a...@null.net MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Boot block problem
Just upgraded to 3.0-stable snapshot circa 2/1 and noticed that the new booteasy does not seem to remember the selection from the previous time. Eg., I need to press F5 to get to disk 2 but it always defaults to F2 (which is FreeBSD slice containing only a swap partition). This means my box won't reboot automatically anymore, e.g., if the power goes out. Is this a new bug or a new feature? :-) It's supposed to work, and it does for me here. Check you haven't got your BIOS 'boot virus protection' stuff enabled, then talk to Robert Nordier (in that order 8). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
How many people use VI? This is unbelievable..
I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. y x w v u t s r q Chris Csanady To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
clock / timer running very slow?
After upgrading 3.0-RELEASE to -stable I noticed various time related things have been acting strange. Obviously one of the timers is running extremely slow, since effects have been observed such as: reported ping times are about 35 times shorter than actual values. 'date' increments at a rate of one or two seconds per minute. 'shutdown -r now' announces the shutdown about a minute later and 'reboot' seems to hang indefinitely requiring Ctrl-Alt-Del to sync the disks. So I tried upgrading to 4.0-current and it still misbehaves in this way. Is this a known problem? Any ideas? This is an AMD K5-PR90 with VIA chipset, world compiled -O2 and kernel compiled -O without options MATH_EMULATE or FAILSAFE if that makes any difference. -- Adam David a...@veda.is To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How many people use VI? This is unbelievable..
On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote: I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. y x w v u t s r q You don't say what terminal emulator you're using, but with xterm, the application keypad option gets enabled when entering vi, which prevents the keypad from generating numbers. You can change it once in vi with the Ctrl+left-button menu. I haven't looked into this sufficiently to know the direct cause of this behaviour. Maybe it could be avoided by tuning the termcap entry? Maybe 'vi' (as the application) should interpret the sequences in the correct way? David To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How many people use VI? This is unbelievable..
On Wed, Feb 03, 1999 at 09:53:05PM -0600, a little birdie told me that Chris Csanady remarked I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. That's not a function of vi, that's a function of your terminal. Lemme guess; xterm, right? If I start vi in console mode, works fine. From a raw xterm, no dice. I haven't tracked down what precisely is causing it to roll over and start twitching under X because it doesn't bug me that much, but it may you. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/~fullermd | * fulle...@futuresouth.com fulle...@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | The only reason I'm burning my candle at both ends, | *is because I haven't figured out how to light the* | middle yet | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How many people use VI? This is unbelievable..
Chris Csanady wrote: I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. FWIW, this message is being edited with vi on a 2.2.8-STABLE machine rlogged in from a dxterm running on an OSF/1 box. The keyboard is one of DEC's LK401 things with the funny Do keys etc from back when VAX was just a twinkle in PDP's eye. I have TERM=vt100 in my FreeBSD environment, dxterm configured with the Numeric Keypad option checked and vt100 emulation, so keypad keys are 0.123456789, just like you'd expect. It's not vi that's the problem, just your termcap setting doesn't match the keyboard. -- John Birrell - j...@cimlogic.com.au; j...@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How many people use VI? This is unbelievable..
On Thursday, 4 February 1999 at 15:18:42 +1100, John Birrell wrote: Chris Csanady wrote: I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. FWIW, this message is being edited with vi on a 2.2.8-STABLE machine rlogged in from a dxterm running on an OSF/1 box. The keyboard is one of DEC's LK401 things with the funny Do keys etc from back when VAX was just a twinkle in PDP's eye. I have TERM=vt100 in my FreeBSD environment, dxterm configured with the Numeric Keypad option checked and vt100 emulation, so keypad keys are 0.123456789, just like you'd expect. It's not vi that's the problem, just your termcap setting doesn't match the keyboard. Correct, and he doesn't say what he's using, but I see that I have problems with both vi and terminal Emacs when using an xterm. Emacs goes crazy: it's obviously interpreting the keypad entries as commands. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up: comitted optimization to vm_map_insert()
: the test ). I think the seg fault may have revealed a new : bug and is not related to the optimization I comitted, so I : haven't backed out the commit. I am not 100% sure though, : and I am testing this now. : : What test? If we had this exact test, it could be exploiting the exact bug, :could it not? I'll let you know of any weird crashes in previously stable :programs. My do lots of things that force the machine to page up the wazoo and try to make it crash test :-) -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How many people use VI? This is unbelievable..
On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote: I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. y x w v u t s r q You don't say what terminal emulator you're using, but with xterm, the application keypad option gets enabled when entering vi, which prevents the keypad from generating numbers. You can change it once in vi with the Ctrl+left-button menu. I haven't looked into this sufficiently to know the direct cause of this behaviour. Maybe it could be avoided by tuning the termcap entry? Maybe 'vi' (as the application) should interpret the sequences in the correct way? This was using the xterm termcap entry. Although when I login to other machines running DU4.0 or Irix6, vi works without touching anything. Regardless, I would be inclined to blame this on our vi. I don't understand much about tercap entries, but this certainly violates POLA. :( So does this mean that the default xterm entry should be different? Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How many people use VI? This is unbelievable..
On Wed, Feb 03, 1999 at 10:27:15PM -0600, Chris Csanady wrote: On Wed, Feb 03, 1999 at 09:53:05PM -0600, Chris Csanady wrote: I unfortunately have a lot of data to type in, and to my surprise the keypad is unuseable in vi. It doesn't even work in vim. Thank god it works on Irix--I thought I would be using ee. Anyways, here is what happens when I type the digits 1-9 on the keypad while in insert mode.. y x w v u t s r q You don't say what terminal emulator you're using, but with xterm, the application keypad option gets enabled when entering vi, which prevents the keypad from generating numbers. You can change it once in vi with the Ctrl+left-button menu. I haven't looked into this sufficiently to know the direct cause of this behaviour. Maybe it could be avoided by tuning the termcap entry? Maybe 'vi' (as the application) should interpret the sequences in the correct way? This was using the xterm termcap entry. Although when I login to other machines running DU4.0 or Irix6, vi works without touching anything. Regardless, I would be inclined to blame this on our vi. I don't understand much about tercap entries, but this certainly violates POLA. :( So does this mean that the default xterm entry should be different? OK, I've looked into it a little now. It is the ks sequence, which is defined to set the cursor keys and the keypad to application mode in both the FreeBSD (3.0-stable as of a week ago) and XFree86 3.3.3.1 versions of the xterm termcap entries. In the FreeBSD case, it ends up falling back to the vt100 entry for this. Here are the definitions: ks=\E[?1h\E=:ke=\E[?1l\E: \E[?1h sets the cursor keys to application mode \E= sets the keypad to application mode Maybe xterm could use a keksInhibit resource like the titeInhibit resource? David To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make port and bsd.port.mk
Reinier Bezuidenhout writes: In the new system ... I get the following error : /usr/share/mk/bsd.port.mk, line 2: Could not find /usr/ports/Mk/bsd.port.mk make: fatal errors encountered -- cannot continue You just need to update or install /usr/ports/Mk, which contains the current ports stuff. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How do I query system temperature probes ?
Thanks, Takanori, are you going to commit your example code in say /usr/src/share/examples/smbus ? If not can you send me a copy please ? Nicolas Souchu wrote: On Wed, Feb 03, 1999 at 02:51:37PM +1030, Matthew Thyer wrote: I seem to have all the hardware required for querying the temperature probes in the system (At least I can do it from the BIOS). How can I query this info ? I assume I need controller smbus0 and controller intpm0 in my kernel. But do I also need device smb0 at smbus? and/or any of the following: # ici2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. You need: controller intpm0 # the PIIX4 interface controller smbus0 # the SMBus system device smb0 at smbus? # user access to the SMBus Once I have all this stuff in my kernel, what commands do I use to query the probes ?? Takanori Watanabe takaw...@shidahara1.planet.sci.kobe-u.ac.jp as example code to do this. My system is FreeBSD 4.0-CURRENT (of CTM 3722 - but will soon be really -CURRENT) Extract from dmesg: chip0: Host to PCI bridge (vendor=8086 device=7180) rev 0x03 on pci0.0.0 chip1: PCI to PCI bridge (vendor=8086 device=7181) rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.7.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 chip3: Intel 82371AB Power management controller rev 0x01 on pci0.7.3 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- nso...@teaser.fr / nso...@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax:+61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: locale errors
As Andrey A. Chernov wrote: I suggest removing any multi character definition out of the collate files. It was Joerg initiative, I don't know DE enough to judge here. Please resolve this problem with him (CC'ed). Well, not completely. :) For testing, i've restored the file from before my change, and it missorts similarly. I'm probably too stupid to understand all of this collate stuff. So far, i haven't been able to come up with any locale definition that does the right thing for every input. To make matters worse, German doesn't even have a single collate defintion at all. There are at least two dissenting definitions: one is the phonebook sorting order, and the other one (certainly more widely accepted and thus should be the base of our collate definition) the `Duden' (German dictionary). According to my Duden, the following words Maße Maßeinheit Masse Massaua Massel should be sorted like: Massaua Maße Masse Maßeinheit Massel If anybody could come up with a set of collate definition files that does this, it probably would be the right thing. ;) Maybe it's simply impossible to express using the current collate stuff? -- cheers, Jorg joerg_wun...@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
config(8) putting (null) into config files
Hi
I am trying to get my laptop's config file as clean as possible
and one of the lines I experimented with is:
controller fdc0 at isa? disable port ? bio
(notice the lack of an irq and the wildcarding of at isa).
This results in a line in ioconf.c of:
{ 10, fdcdriver, (null), 0, -1, C 0x0, 0, 0, 0, 0x,
0,0, 0, 0, 0,0, 0 },
Notice the (null). I want the line in my config file to be like that
as I do not use the floppy drive very often, and I am quite content for
it to be kicked into action by pccardd when I plug it in. So my config
line above is just a device placeholder. The (null) causes a compile
failure, which is fixed by the kluge below. Is there a better way of
doing this, or is this OK to commit?
(WARNING! Cut 'n Paste alert!)
Index: mkioconf.c
===
RCS file: /home/ncvs/src/usr.sbin/config/mkioconf.c,v
retrieving revision 1.45
diff -u -d -r1.45 mkioconf.c
--- mkioconf.c 1998/11/15 18:07:35 1.45
+++ mkioconf.c 1999/02/04 06:38:37
@@ -721,7 +721,7 @@
mp == TO_NEXUS || !eq(mp-d_name, table))
continue;
fprintf(fp, { -1, %3sdriver, %8s,,
- mp-d_name, mp-d_port);
+ mp-d_name, mp-d_port ? mp-d_port : 0);
fprintf(fp, %6s, %2d, C 0x%05X, %5d, 0, %3d, 0x%04X, %5d,
0, 0, 0, %6d, %8d, 0 },\n,
sirq(mp-d_irq), mp-d_drq, mp-d_maddr,
mp-d_msize, dp-d_unit,
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: 3.0 vs 4.0
In message 199902031748.maa25...@highwind.com HighWind Software Information writes: : Can someone summarize the difference and locations between all these : things? : : I've heard of: : 2.2.8-stable : 3.0-stable : 3.0-current : 3.0-release : 4.0-current : : Where are all these things? Some in source? Some in binary? I've just : been grabbing the things in pub/FreeBSD on current.freebsd.org. I : assume those are daily builds of 3.0-stable. 2.2.8-stable is the current name of the 2.2 branch of FreeBSD. It was created some time ago. This is the branch that all the 2.2.x releases came from. 2.2.8-stable means that you are on teh 2.2 branch sometime after the 2.2.8 release. 3.0-stable is the name of the 3.x branch of FreeBSD. All 3.x based releases will be based on this, except for 3.0-release. 3.0-release was based on a pre-branch version of this code. 3.0-stable is more stable than 3.0-release in many ways and is currently marching along towards a 3.1 release slated for later this month. 3.0-current is the old name for the bleeding edge. It was until recently the most up to date copy of FreeBSD that you could get. This was both good and bad depending on the day since minor problems crop up and bugs are fixed. 4.0-current is the new name for the bleeding edge. Here's an approximate graphical picture of the branches in the CVS tree: --+- 3.0-current -*+# 4.0-current \\ \\ 3.0 stable banch - \ \ --1--2-5-6-7-8- 2.2 stable branch [*] in the above picture is where 3.0 was release (and hence is 3.0-release). [#] in the above is where the main trunk changed its name from 3.0-current to 4.0-current. [1-8] on the 2.2 stable branch above are release points for 2.2.1R, 2.2.2R, etc. I say approximate because I've hand waved the earlier 2.x releases and the exact point that the branch was made for 2.2. It is enough to understand what is going on. The 2.2 stable branch is coming to its end of life. It is becoming more than just stable, it is effectively frozen with very few bug fixes being propigated back to it now. : Is it still true that 2.2.8 is the thing that folks get when they go : to the www.freebsd.org website and grab the the latest stable thing? Yes. 3.0 release had some problems, and 3.1 isn't ready. When 3.1 comes out, I'd say go for that. If it is for your personal machine, I'd be tempted to install 3.0 but be prepared to back off to 2.2.8 if there are major problems. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: locale errors
On Thu, Feb 04, 1999 at 07:38:12AM +0100, J Wunsch wrote: Well, not completely. :) For testing, i've restored the file from before my change, and it missorts similarly. I'm probably too stupid to understand all of this collate stuff. So far, i haven't been able to come up with any locale definition that does the right thing for every input. I mean no particular commit but whole idea how to sort doubled letters - it comes from you, I can't invent this. Collating scheme is very simple - we have two sorting orders - primary and secondary (f.e. Posix have four levels for Unicode). If two strings are the same by primary order, they compare using secondary one. That's all. I will apreciate your any decision regarding to DE locale, fixing, backing out etc. since I even can't display characters you use in your example, nor have strong desire to dig in DE language area starting from zero background. -- Andrey A. Chernov a...@null.net MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
