Re: why 'The legacy aout build' was removed from current ?
Hi, YAMAMOTO Shigeru [EMAIL PROTECTED]wrote: In a log of @src/Makefile, revision 1.230, o The legacy aout build has been removed. Why 'The legacy aout build' was removed from current? Are we now living in the TRUE ELF world? I also wonder why a.out support was removed from -current. I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Thanks. -- Motoyuki Konno [EMAIL PROTECTED] (Univ) [EMAIL PROTECTED] (Home) [EMAIL PROTECTED] (FreeBSD Project) Yamanashi Medical Universityhttp://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
It seems Blaz Zupan wrote: On Wed, 8 Dec 1999, Christopher Masto wrote: I fully agree that these things are neccessary and good. I just think we need avoid jumping the gun on removing the old code, when some people still need it to boot their machines. Actually I completely disagree. When you leave in old code in the tree, people who can't use the new code for whatever reason (technical problems, laziness, etc.) will use the old code. Forever. And people tend to not report such things - if it works with the old code, why bother? If you take something away from them, they will at least notice that it's broken and report it to the author. From my own experience, I lost the WaveLAN driver with the newbus stuff. If it was somehow still working (for example through some compatibility code for the old bus system), I'd not have done anything about it. But as it was broken, I sat down and fixed it. Although my time is as limited as everybody else's and it took me a whole day, I leared a lot through this. Wonderfully put, this is the _exact_ problem we are facing here. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after Mounting root from ufs:/dev/ad0s2a
Kelvin Farmer wrote: Problem: Computer _sometimes_ stops after the "Mounting root from ufs:/dev/ad0s2a" line. Running Current, built world yesterday. (Problem appeared fairly recently (as in ~2 weeks?, but didn't have ddb in previous kernel) dmesg: [...] ad0: QUANTUM FIREBALL ST2.1A/A0F.0800 ATA-3 disk at ata0 as master ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ^^ Is this the correct size of your hard disk? -- Daniel C. Sobral(8-DCS) who is as social as a wampas [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after Mounting root from ufs:/dev/ad0s2a
Maxim Sobolev wrote: Kelvin Farmer wrote: Problem: Computer _sometimes_ stops after the "Mounting root from ufs:/dev/ad0s2a" line. Running Current, built world yesterday. (Problem appeared fairly recently (as in ~2 weeks?, but didn't have ddb in previous kernel) I've also observed this problem and it is interesting that my HDD is Quantum FB ST 2.1 too. Does it report the correct size, btw? If not, does it report 4092 cylinders? -- Daniel C. Sobral(8-DCS) who is as social as a wampas [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
Julian Elischer wrote: please do not remove it.. just make it non-default. Retire it to LINT if you must, but I'd also like to see it around until the last release on RELENG_3. -- Daniel C. Sobral(8-DCS) who is as social as a wampas [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound card support
[subject changes and thread hijacked] On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Also, I hope to contribute in some way to broaden FreeBSD's sound card support. I have the ESS 1868. I just made a printout of the data sheets for this particular sound card. If anyone out there needs the pdf version of the ESS 1868 datasheet/specs, just email me and I can send you a copy via email. So far, it looks like the 1868 only does full duplex in mono. ;-( (Is the 1868 even worth worrying about?) Also, how well does the ProAudio Spectrum 16 work at this point right now in -current? Does it work flawlessly? Whatever happened to the company that made the PAS 16? I saw where MediaVision doesn't exist anymore. Has another company taken over PAS development? Anyhow, as far as ISA cards go... how does the PAS 16 compare to the ESS 1868? I think the PAS only gets full duplex when you've got both the PAS and the SB compatibility side working in tandem. Well, I've got a PCI machine (Pentium), so I imagine a PCI sound card would be worlds better. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
On Thu, 09 Dec 1999 17:00:50 +0900, Motoyuki Konno wrote: I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Are you sure? Any a.out binaries for FreeBSD are going to be desgined to work with 3.x or older. So producing a.out libraries for CURRENT is silly. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Cleaning house on /usr/src/*
John Polstra wrote: When you change the tag (e.g., go from -stable to -current or vice versa), it's a special case. Thanks, I'll remember that. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
which is right? 'controller pcic0 at isa?' or 'device pcic0 at isa?'?
I wonder about configuration for pcic in -current. In GENERIC, '#device pcic0 at isa?' In LINT and PCCARD, 'controller pcic0 at isa?' Which is right? Thanks, --- YAMAMOTO ShigeruInternet Initiative Japan Inc. [EMAIL PROTECTED] Network Engineering Div. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release broken
Hi, Make release in a -current cvsuped just now broke. It looks like the aout directory is not there. - === libtacplus sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/tmp/usr/include sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libtacplus.a /usr/obj/usr/src/tmp/usr/lib sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libtacplus_p.a /usr/obj/usr/src/tmp/usr/lib sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444 libtacplus.so.1 /usr/obj/usr/src/tmp/usr/lib ln -sf libtacplus.so.1 /usr/obj/usr/src/tmp/usr/lib/libtacplus.so === compat === compat/compat1x sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libc.so.1.1 libcurses.so.1.1 libf2c.so.1.1 libg++.so.1.1 libgcc.so.1.1 libgnumalloc.so.1.1 libgnuregex.so.1.1 libln.so.1.1 libm.so.1.1 libmalloc.so.1.1 libreadline.so.1.1 libresolv.so.1.1 librpcsvc.so.1.1 libskey.so.1.1 libtelnet.so.1.1 libtermcap.so.1.1 libutil.so.1.1 liby.so.1.1 /usr/obj/usr/src/tmp/usr/lib/compat/aout usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 1 Stop in /usr/src/lib/compat/compat1x. *** Error code 1 Stop in /usr/src/lib/compat. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 -- John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after Mounting root from ufs:/dev/ad0s2a
On Thu, Dec 09, 1999 at 08:39:46AM +0600, Boris Popov [EMAIL PROTECTED] wrote: Problem: Computer _sometimes_ stops after the "Mounting root from ufs:/dev/ad0s2a" line. Running Current, built world yesterday. (Problem appeared fairly recently (as in ~2 weeks?, but didn't have ddb in previous kernel) I can confirm that behaviour of new ata driver. This happens one time per 5-6 reboots. In addition, machines with VIA chipset work fine, but all machines with i440BX chipset suffer from this problem: Same here, one for about 10 reboots. Just sits quietly after "Mounting root from .." message. No other ill effects. SiS 530 chipset (5591), Seagate 6GB ATA-3 disk, new ata driver. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MCA support
Just wondering how far along MCA support is. I tried booting up a kern.flp from the latest snapshot circa dec. 7. and I got a "Read error" during boot, which halted the machine. My machine was an IBM PS/2 model 77s. I'd like to make an mca picobsd release as well. -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after Mounting root from ufs:/dev/ad0s2a
It seems Vallo Kallaste wrote: On Thu, Dec 09, 1999 at 08:39:46AM +0600, Boris Popov [EMAIL PROTECTED] wrote: Problem: Computer _sometimes_ stops after the "Mounting root from ufs:/dev/ad0s2a" line. Running Current, built world yesterday. (Problem appeared fairly recently (as in ~2 weeks?, but didn't have ddb in previous kernel) I can confirm that behaviour of new ata driver. This happens one time per 5-6 reboots. In addition, machines with VIA chipset work fine, but all machines with i440BX chipset suffer from this problem: Same here, one for about 10 reboots. Just sits quietly after "Mounting root from .." message. No other ill effects. SiS 530 chipset (5591), Seagate 6GB ATA-3 disk, new ata driver. I just searched a bit in the lists etc, and this problem also exists in 3.x with the old driver, hmm, there is even one mentioning it on a SCSI only system, more hmmm I guess its not only related to the ata driver alone -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
YAMAMOTO Shigeru wrote: In a log of @src/Makefile, revision 1.230, o The legacy aout build has been removed. Why 'The legacy aout build' was removed from current? There's no point in building legacy a.out stuff from -current sources. The result has nothing to do with legacy but only with a.out. Compatibility with legacy a.out binaries can best be achieved by installing the proper compat distribution (compat22 for example). -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AWE64 problems
On Thu, Dec 09, 1999 at 12:25:33PM +0900, Seigo Tanimura wrote:
[snipped some part]
On Tue, 7 Dec 1999 23:00:02 +0100 (MET),
Thomas Schuerger [EMAIL PROTECTED] said:
--- sbc.c.orig Mon Dec 6 19:26:31 1999
+++ sbc.c Tue Dec 7 22:15:25 1999
@@ -110,7 +110,7 @@
if (error)
return error;
else
- return -100;
+ return -1;
}
static int
On Wed, 8 Dec 1999 08:54:15 -0500,
"Charles Anderson" [EMAIL PROTECTED] said:
Charles So then what is -1 and why does it work when -100 doesn't? (I tried it)
sys/kern/subr_bus.c:device_probe_child() receives the value returned
by DEVICE_PROBE(child dev). If the value is zero, no further probes
occur. The device then gets attached in sys/kern/subr_bus.c:
device_probe_and_attach().
Ahh, now it makes sense to me.
In case of an unknown device, error = ISA_PNP_PROBE(...) set error to
a value larger than 0. In case of a successfull match error is set to
0.
IMHO the correct probe should be:
sbc_probe(device_t dev)
{
int error;
/* Check pnp ids */
error = ISA_PNP_PROBE(device_get_parent(dev), dev, sbc_ids);
if (error = 0)
return error;
else
return -100;
}
Is it possible that error gets a value below 0 ? In that case the
probe should arrange for this case.
Any comments ?
Frank
--
~/.signature not found: wellknown error 42
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: OHCI weirdness?
I've seen this problem under stress, not normally during boot. Time
permitting I will have a look into this next week.
Probably a race condition somewhere.
Could you tell me whether the panic appears after a lengthy wait or is
it directly related to a an event like plugging in a device or starting
to talk to it (usbd, ugen, etc.)
Cheers,
Nick
"me too" (but only if there is a device plugged in)
I get this same panic with both devices I've tried; a Kodak
DC265 and a
Sandisk CompactFlash reader. Its not obvious why this is
happening (at
least from where I'm sitting.)
Any ideas?
Should I report back with a kernel compiled with OHCI_DEBUG?
Thanks.
...
ohci0: OPTi 82C861 (FireLink) USB controller irq 9 at device
11.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0: OPTi 82C861 (FireLink) USB controller on ohci0
usb0: USB revision 1.0
uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
panic: ohci_hash_find_td: addr 0x03e7c770 not found
Debugger("panic")
Stopped at Debugger+0x37: movl$0,in_Debugger
db t
Debugger(c0289aa3) at Debugger+0x37
panic(c029c0c0,3e7c770,c0373cbc,c0225142,c07a5800) at
panic+0x74
ohci_hash_find_td(c07a5800,3e7c770,6,c07a5800,2) at
ohci_hash_find_td+0x33
ohci_process_done(c07a5800,3e7c7d0,6b9457,c07a5800,c07a6e80) at
ohci_process_done+0x1e
ohci_intr1(c07a5800) at ohci_intr1+0x10c
ohci_waitintr(c07a5800,c07a6e80,c07a6e80,c07a6e80,c0373d20) at
ohci_waitintr+0x69
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-End of Included Message--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On 8 Dec, Soren Schmidt wrote: Søren: I didn´t want to flame you, I only want to convince Paul-Henning to wait until you have time to fix those bugs. Welcome to the real world, I've promised to look at this and I will, but a day has only so many hours. I asumed this, and because of this I made my statement above. Instead of complaining, help the project, when have you last closed a PR ?? Am I allowed to repeat your "real world" statement? Bye, Alexander. -- Withdrawal is for quitters. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release broken
John Hay wrote: Make release in a -current cvsuped just now broke. It looks like the aout directory is not there. Fixed. Thanks. I'm testing as well, so if anything comes up, let me know. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
Motoyuki Konno wrote: I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. For this, the proper compat distribution should/can be installed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. No, we only have to *run* them. This we do. If Netscape were to compile on -current, they would have an ELF version... Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
Motoyuki Konno wrote: I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. For this, the proper compat distribution should/can be installed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. No, we only have to *run* them. This we do. If Netscape were to compile on -current, they would have an ELF version... Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after Mounting root from ufs:/dev/ad0s2a
On Thu, Dec 09, 1999 at 11:16:10AM +0100, Soren Schmidt [EMAIL PROTECTED] wrote: Same here, one for about 10 reboots. Just sits quietly after "Mounting root from .." message. No other ill effects. SiS 530 chipset (5591), Seagate 6GB ATA-3 disk, new ata driver. I just searched a bit in the lists etc, and this problem also exists in 3.x with the old driver, hmm, there is even one mentioning it on a SCSI only system, more hmmm I guess its not only related to the ata driver alone Hard to say.. my work machine is SCSI only and I track -current on both my home and work machine. Haven't had such behavior on my work machine. I can't remember that I had such problems using 3.0-current or are you pointing to -stable? I'm running only -current for a while now and we don't reboot our -stable machines often :-) -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: which is right? 'controller pcic0 at isa?' or 'device pcic0 at isa?'?
YAMAMOTO Shigeru wrote: I wonder about configuration for pcic in -current. In GENERIC, '#device pcic0 at isa?' In LINT and PCCARD, 'controller pcic0 at isa?' "device" is just about the same as "controller", there is only one difference. If you use "controller", then config allows you to have other lines: device foo at pcic0 This is solely to keep config(8) happy. It makes no difference to the kernel at all. Which is right? Thanks, --- YAMAMOTO Shigeru Internet Initiative Japan Inc. [EMAIL PROTECTED] Network Engineering Div. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Using USB modules with an USB keyboard...
I added your recommendations above to the kernel config file (TWELVE). It didn't work. As can be seen from the dmesg below, when the USB options are present in the kernel, ukbd0 is found. When USB KLDs are used, uhid0 seems to grab the keyboard. this is correct. Both drivers know how to handle a HID device, but ukbd has a higher priority. if you load the ukbd driver and then unplug-plug the keyboard, the ukbd driver will attach to the keyboard. Dec 7 19:57:33 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1. 00/1.10, addr 2, iclass 3/1 Could you send me the output of usbdevs -v when the mouse is connected? usbdevs -v | mail [EMAIL PROTECTED] Dec 7 19:57:33 frabjous /kernel: ums0: 4 buttons and Z dir. Dec 7 19:57:33 frabjous /kernel: uhid0: QTRONIX USB Keyboard and Mouse, Dec 7 19:57:33 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, You have a QTronix keyboard. It has been reported to me that the keyboard repeats keys sometimes. Let me know whether this is the case. Also, the firmware in the keyboard is very broken. If you hook up a PS/2 mouse to the keyboard, and notice that you get spurious button up events (in X windows the window is dropped and picked up several times when moving it), make sure you have an up to date version of the ums driver. If you don't run current and run into this problem, let me know and I'll see whether I can back port that fix to STABLE. Nick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
In message [EMAIL PROTECTED] Julian Elischer writes: : more importantly we lost the aha driver for a while. No we didn't. Well, the aha driver did loose support for the 1542A cards, but the aha driver was done so that cam could be committed to the tree. Maybe you are confusing things with the aic driver? Also, the cam uha driver hasn't gotten past the cp aha - query replace aha with uha stage... Warner I lost support on my 1542B until I came up with a patch, which I believe was incorporated into 3.3-R. - Dave R. - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after
Problem: Computer _sometimes_ stops after the "Mounting root from ufs:/dev/ad0s2a" line. Running Current, built world yesterday. (Problem appeared fairly recently (as in ~2 weeks?, but didn't have ddb in previous kernel) I've also observed this problem and it is interesting that my HDD is Quantum FB ST 2.1 too. I've seen this on a Toshiba Disk, A WD 2.1Gb drive (which almost but not quite dead), and two Seagate 106Mb drives (flakey). So I guess you'r assumption is flakey. Also, with respect to the trace shown somewhere earlier, I've not seen consistent behaviour in where it stops, but this could be EBADMEM. Nick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is there any way to use ATAPI CD-R?
Thus spake Andrey A. Chernov ([EMAIL PROTECTED]): As I see by quick check, CD-related soft from ports understand SCSI only. Does anybody use new ATAPI CD-R (acd)? If yes, please tell me how. Take a look at /usr/share/examples/atapi/burn* Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) Not really. You have to have a.out crt0.o and friends to be able to link it. You probably have some old versions around in your system, but they are not built by "world" target. Hence, they are not a part of binary distrib. 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
Make world breakage (12/09/99)
Getting this from this morning's make world (after doing a make clean, just for good measure): -- Rebuilding dependencies -- cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/ bin LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib OBJFORMA T_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" PERL5LIB=/usr/l ibdata/perl/5.00503 PATH=/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/loca l/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/ X11R6/bin :/usr/local/samba/bin:/usr/local/home/forrie/bin make DESTDIR=/usr/obj/usr/src/tmp I NSTALL="sh /usr/src/tools/install.sh" -f Makefile.inc1 par-depend === share/info === include === include/rpcsvc === lib === lib/csu/i386-elf rm -f .depend mkdep -f .depend -a -nostdinc -I/usr/obj/usr/src/tmp/usr/include/usr/src/lib/cs u/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S mkdep -f .depend -a -nostdinc -I/usr/obj/usr/src/tmp/usr/include /usr/src/lib/csu/ i386-elf/crt1.c /usr/src/lib/csu/i386-elf/crtbegin.c /usr/src/lib/csu/i386-elf/crtend .c In file included from /usr/src/lib/csu/i386-elf/crt1.c:32: /usr/obj/usr/src/tmp/usr/include/stddef.h:39: machine/ansi.h: No such file or directo ry In file included from /usr/src/lib/csu/i386-elf/crt1.c:33: /usr/obj/usr/src/tmp/usr/include/stdlib.h:39: sys/cdefs.h: No such file or directory /usr/obj/usr/src/tmp/usr/include/stdlib.h:41: machine/ansi.h: No such file or directo ry /usr/src/lib/csu/i386-elf/crtbegin.c:28: sys/cdefs.h: No such file or directory /usr/src/lib/csu/i386-elf/crtend.c:28: sys/cdefs.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
In message [EMAIL PROTECTED] Christopher Masto writes: : Right now, I have no sound (not detected), no USB (panic on removal), : can't use my sio pccard, can't eject my ed pccard, my IDE drives are : taking hours to dump and fsck, and my TV card is missing every other : line if I try to use the (not working anyway) closed caption decoder. I have some patches for the can't eject the network cards from a user that I'm trying out and would then need to get committed to the network layer to properly support if_detach(). What's wrong with your sio pccard? Mine works well enough... Mine hasn't worked since a kernel built from Nov 23 sources. It broke sometime between then and December 4th. Just built a new kernel from todays sources, and still no go. pccardd[47]: driver allocation failed for Motorola(MONTANA 33.6 FAX/MODEM): Device not configured My 3c589D luckily still works correctly: ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 9 slot 1 on pccard1 ep0: Ethernet address 00:60:08:8c:32:34 Excerpt from dmesg: pcic0: VLSI 82C146 at irq 3 on isa0 pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 ppc0: not probed (disabled) pcm0: ESS1868 rev 11 at irq 7 drq 1 flags 0x10 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled Mounting root from ufs:/dev/wd0s3a pccard: card inserted, slot 0 pccard: card inserted, slot 1 ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 9 slot 1 on pccard1 ep0: Ethernet address 00:60:08:8c:32:34 `pccardc dumpcis` now behaves as `pccardc dumpcore` :-) Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 1 000: 00 Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x15 (Version 1 info), length = 39 000: 04 01 4d 6f 74 6f 72 6f 6c 61 00 4d 4f 4e 54 41 010: 4e 41 20 33 33 2e 36 20 46 41 58 2f 4d 4f 44 45 020: 4d 00 56 32 2e 30 00 Version = 4.1, Manuf = [Motorola],card vers = [MONTANA 33.6 FAX/MODEM] Addit. info = [V2.0],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[ [ and much more garbage before dumping core] Email me privately if you need other info. Dan Eischen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
Andrzej Bialecki wrote: On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) Not really. You have to have a.out crt0.o and friends to be able to link it. You probably have some old versions around in your system, but they are not built by "world" target. Hence, they are not a part of binary distrib. Yes, I have c++rt0.o in /usr/lib/aout. If I didn't have it, I would be given directions on how to get it (from the port): 1. extract /usr/src/lib (distribution files: src/slib.??) 2. cd /usr/src/lib/csu/i386 3. make depend 4. make OBJFORMAT=aout clean all install -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world breakage (12/09/99)
Forrest Aldrich wrote: Getting this from this morning's make world (after doing a make clean, just for good measure): re-cvsup. The problem should be fixed already. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Andrzej Bialecki wrote: On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) Not really. You have to have a.out crt0.o and friends to be able to link it. You probably have some old versions around in your system, but they are not built by "world" target. Hence, they are not a part of binary distrib. Yes, I have c++rt0.o in /usr/lib/aout. If I didn't have it, I would be given directions on how to get it (from the port): 1. extract /usr/src/lib (distribution files: src/slib.??) 2. cd /usr/src/lib/csu/i386 3. make depend 4. make OBJFORMAT=aout clean all install True. But this adds a dependency for this port on the src/lib tree. I was thinking about average people that have binary distribution + kernel sources. They are screwed. 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: why 'The legacy aout build' was removed from current ?
Andrzej Bialecki wrote: 1. extract /usr/src/lib (distribution files: src/slib.??) 2. cd /usr/src/lib/csu/i386 3. make depend 4. make OBJFORMAT=aout clean all install True. But this adds a dependency for this port on the src/lib tree. I was thinking about average people that have binary distribution + kernel sources. They are screwed. The dependency always existed, because people without src/lib cannot make legacy a.out as part of their world, for which you also need more than kernel sources alone :-) The point here is that you don't need a legacy a.out build as part of your world to get this port working. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Reaping fortran cruft
Steve Kargl writes: Kris Kennaway wrote: On Wed, 8 Dec 1999, Steve Kargl wrote: I was going to fix fsplit. Yes, I program in Fortran (note the proper spelling of Fortran). No, I don't use fsplit. A rewrite is certainly desperately needed :) We might also want to remove fpr(1). Noted. Are there any other crufty Fortran candidates you can do without? No. I haven't found any other programs. If no-one disagrees with this, I'll move them both to ports (probably in a combined fortran-utils port) in a couple of days. Would you like to be the maintainer? :) The dates in fsplit suggest that it hasn't seen any development since 1983. The functionality it provided then can be accomplished with vi and cp. Yes, and one can do text editing with cat and sed. Fsplit has its place, as does fpr. Please keep them as ports rather than nuke them completely. Being in the attic is substantially more difficult for casual *BSD users than being available as a port. I wholeheartedly endorse a fortran-utils port. I haven't looked at fpr, but you can get fancy program listings with a2ps (and probably apsfilter) which is (are) already in the ports collections. Yes, but as a shell script it is easier to teach apsfilter about Fortran if fpr is available to do the heavy lifting. That is easier than hacking a2ps. I do not find any mention of Fortran knowledge in the man page for the version of a2ps-letter I installed on this workstation about 6 weeks ago. (I used the port.) Sorry. I'm all in favor of this bike shed but disagree with the suggested paint color. I say kill them (of course asbestos under garments might be needed). It should be noted that cvs will maintain a copy of both in the attic, so anyone who wants the source can get it. -- Steve Bud Dodson -- M. L. Dodson[EMAIL PROTECTED] 409-772-2178FAX: 409-772-1790 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fallback paths (was: HEADSUP: wd driver will be retired!)
On Wednesday, 8 December 1999 at 21:00:36 +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Kris Ken naway writes: On Wed, 8 Dec 1999, Poul-Henning Kamp wrote: Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or /dev/rwd* Can't we keep the same device names? I thought that was the original plan way back when, once the new driver was ready for prime-time. Also, perhaps we should have a changing-over period where the old drivers are still available under a new name - until recently, Soren was advertising the driver as "WARNING: This is pre-alpha code and may trash your filesystems", etc, which may well have limited his testing base (it certainly scared me off). I'm all for moving forward, but I'd hate to eliminate a fallback path in case the transition proves less than smooth. The fallback path is not eliminated, and may never be, but it may become rather uncomfortable to linger on it longer than you absolutely need to. Would you care to expand on that statement? Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: At 10:56 AM -0800 1999/12/8, Mike Smith wrote: The right attitude to be taking now is "here is where the ata drivers still fall down" or "here are patches to them to replace this functionality". Think about the longer-term goals here folks. I understand where Julian is coming from. In fact, my initial reaction was the same. However, I have reluctantly been converted to be in agreement with Mike and Søren (among others). This is -CURRENT. It pains me to say it, but anyone trying to run anything "useful" on -CURRENT gets what they deserve. This is the only place where we can make clean breaks with the past, and as painful as that can be, we simply have to do that occasionally. Next month it'll be -RELEASE. This isn't the time to remove such significant functionality. If it weren't for that, I'd agree with you. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Continuity (was: HEADSUP: wd driver will be retired!)
On Wednesday, 8 December 1999 at 12:52:37 -0800, Mike Smith wrote: On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: You shouldn't remove a function until it has been properly replaced. A very simple concept some people seem to have trouble grasping. Actually, that's not at all correct. We've demonstrated a number of times now that you reach a point where a brutal cutover is required. Failure to do so leaves people clutching the old security blanket for years, and massively impedes further development. Unfortunately, FreeBSD has far too many examples of a working system being replaced with a less functional system. Just off the top of my head, there were the SCSI drivers lost to CAM, the PCCARD system, sound drivers, and now ATA. Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; we actually _gained_ from it. If you were the owner of a number of older SCSI host adaptors, you lost. We haven't "lost" the pccard system at all, We certainly seem to have mislaid it. My modem has got lost again, and the number of supported cards is greatly diminished. and the new sound code is on a feature-par with both of the old ones. I don't have a comparison there. What we need here is a commitment to these new initiatives, not a lot of fence-sitting and clutching our knitting to our chests. All of these initiatives were started to deal with massive problems in the subsystems they replace; clinging to the old code rather than getting on-board and helping with the new code directly impedes the resolution of these problems. I don't think this is an accurate view of the objections. Again, I say, think of what we're trying to achieve here. One thing, I hope, is continuity. I don't see this helping. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Wednesday, 8 December 1999 at 15:23:49 -0800, Jonathan M. Bresler wrote: [snip] We gained quite a bit from it, but let's not rewrite history. I remember quite clearly that there was a very popular Adaptec SCSI controller missing when the switch to CAM was made, and a lot of [snip] we lost teh aic controller at that time. [snip] Again, this is not accurate. I have a laptop with which, two months ago, I could use my LinkSys ethernet card, and I could use my digital then we need to get your LinkSys ethernet card support fixed. i am using one to write this message. mine is a LinkSys 10/100 PCMCIA card. what do you have? What version of -CURRENT are you using? Mine is a PCMPC200, and I haven't been able to get it to work for 6 weeks. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Wednesday, 8 December 1999 at 17:09:39 +0100, Soren Schmidt wrote: It seems Alexander Leidinger wrote: It isn´t only a matter of providing feedback... the maintainer also has to work on it. Yeah, right... I offered feedback in every mail regarding my problem with ata msdos-ZIPs (they aren´t accessible), but most of the time I havn´t got a reply (Søren replied recently to Fritz Heinrichmeyer, he has the same problem). I´m not able to test it at the moment, but I havn´t seen a cvs-all message which said "Problems with MSDOS formated ZIPs fixed". I assume it isn´t fixed and I want to use the wd driver until it´s fixed. Poul-Henning: please wait until Søren fixed the problems some users have (we didn´t want to loose features, right?). Søren: I didn´t want to flame you, I only want to convince Paul-Henning to wait until you have time to fix those bugs. Welcome to the real world, I've promised to look at this and I will, but a day has only so many hours. We're not talking about deadlines here, we're talking about sequences: 1. Write a new driver with sexy new features. 2. Make sure it can do everything the old driver can do. 3. Remove the old driver. At the moment, we seem to be trying to do (3) before (2). No question of hours/day or anything else. Instead of complaining, help the project, when have you last closed a PR ?? It's been a while. The day has only so many hours. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Progress or procedure? (was: HEADSUP: wd driver will be retired!)
On Wednesday, 8 December 1999 at 22:31:22 +0100, Soren Schmidt wrote: It seems Christopher Masto wrote: On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: You shouldn't remove a function until it has been properly replaced. A very simple concept some people seem to have trouble grasping. Actually, that's not at all correct. We've demonstrated a number of times now that you reach a point where a brutal cutover is required. Failure to do so leaves people clutching the old security blanket for years, and massively impedes further development. Unfortunately, FreeBSD has far too many examples of a working system being replaced with a less functional system. Just off the top of my head, there were the SCSI drivers lost to CAM, the PCCARD system, sound drivers, and now ATA. Hmm, well, if you want support for any of the new ata-66 controllers you have to use the ata driver, so you loose some you win some. Given that my patch for the SiS works and a patch I got from Luoqi, the ONLY support you are loosing is the Cyrix. If we maintain wd for the Cyrix people, we don't lose anything. Right now, I have no sound (not detected), no USB (panic on removal), can't use my sio pccard, can't eject my ed pccard, my IDE drives are taking hours to dump and fsck, and my TV card is missing every other line if I try to use the (not working anyway) closed caption decoder. Now, I running -current on this machine, I've asked for problems, and I have them. I try to fix them and/or send decent bug reports when I can, and I don't piss and moan when something breaks, because it's -current. I just get a feeling sometimes like we're moving forward on a treadmill that's moving backward just slightly faster. Well, progress doesn't come for free you know, somebody has to do the hard work of actually implementing things. So if you think its going too slowly, do something about it, help out where you can, but complaining isn't helping anybody :) We're not talking progress here, we're talking procedure. Nobody doubts that the new driver will be better than the old one, and nobody doubts that the new one should be the default (at least, I haven't seen anybody doubting it). But why throw away functionality? People need time to adapt, and we have a perfectly good solution: keep the wd driver for 4.0, make it clear it's deprecated, and remove it (functionality permitting) for 4.1. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!)
On Wednesday, 8 December 1999 at 15:02:37 +0100, Soren Schmidt wrote: It seems Richard Seaman, Jr. wrote: On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote: In a few days time the wd driver will be retired from FreeBSDs i386 architecture. Since the ata driver does not support DMA on my chipset, at least the last time I tried (SiS 5591), it would be nice to leave the wd driver in the tree for a while, even if its not the default. Possibly there are others in the same boat? OK, you asked for it, following is a patch to support the sis 5591 chipset. Remember this is done blindfolded, I have no HW to test on, but you guys do :) Let me know what happens... OK. Let's defer removing wd until we know that ata DMA works on these platforms. We'll have a lot of unhappy customers otherwise, myself (wearing another hat) included. If nobody else gets there first, I'll look at this next week. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pccard sio problems (Re: HEADSUP: wd driver will be retired!)
Zitiere Daniel Eischen [EMAIL PROTECTED]: In message [EMAIL PROTECTED] Christopher Masto writes: : Right now, I have no sound (not detected), no USB (panic on removal), : can\\\'t use my sio pccard, can\\\'t eject my ed pccard, my IDE drives are : taking hours to dump and fsck, and my TV card is missing every other : line if I try to use the (not working anyway) closed caption decoder. I have some patches for the can\'t eject the network cards from a user that I\'m trying out and would then need to get committed to the network layer to properly support if_detach(). What\'s wrong with your sio pccard? Mine works well enough... Mine hasn\'t worked since a kernel built from Nov 23 sources. It broke sometime between then and December 4th. Just built a new kernel from todays sources, and still no go. pccardd[47]: driver allocation failed for Motorola (MONTANA 33.6 FAX/MODEM): Device not configured I also had problems with latest -current. After a little debugging I noticed that sio.c doesn\'t include \"card.h\" which defines NCARD, so the pccard stuff isn\'t compiled in. I added that line to sio.c, recompiled, and sio for pccard was at least again partially functional. I have two pccard sio devices, one seems to work, the other one freezes the machine during a simple \"stty -a /dev/cuaaX\". I have attached the CIS information of these cards with my pccard.conf. Ejecting sio also doesn\'t seem to work. The machine is freezed afterwards. I can eject my DLink ed card, but after a re-insertion the driver isn\'t attached any more. Daniel Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 32 000: 04 01 49 6e 74 65 6c 6c 69 67 65 6e 74 00 50 43 010: 4d 43 49 41 20 46 41 58 2b 4d 4f 44 45 4d 00 ff Version = 4.1, Manuf = [Intelligent],card vers = [PCMCIA FAX+MODEM] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 02 01 00 PCMCIA ID = 0x200, OEM ID = 0x1 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 02 00 Serial port/modem Tuple #5, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 5c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even, Tuple #6, code = 0x22 (Functional EXT), length = 9 000: 05 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #7, code = 0x22 (Functional EXT), length = 9 000: 06 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #8, code = 0x22 (Functional EXT), length = 12 000: 02 06 00 3f 1c 03 03 0f 07 00 01 b5 Data modem services available: Tuple #9, code = 0x22 (Functional EXT), length = 8 000: 13 06 00 1f 00 02 00 b5 Tuple #10, code = 0x22 (Functional EXT), length = 8 000: 23 06 00 1f 00 02 00 b5 Tuple #11, code = 0x1a (Configuration map), length = 5 000: 01 27 80 ff 67 Reg len = 2, config register addr = 0xff80, last config = 0x27 Registers: XXX--XX- Tuple #12, code = 0x1b (Configuration entry), length = 19 000: cf 41 99 79 55 3d 86 46 26 4c aa 60 f8 03 07 f0 010: bc 86 28 Config index = 0xf(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 3.5 x 10mA Max current average over 1 second: 1 x 100mA, ext = 0x46 Max current average over 10 ms: 2 x 100mA Power down supply current: 4.5 x 1mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level, Pulse, Shared IRQs: 4 5 6 7 10 11 12 13 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #13, code = 0x1b (Configuration entry), length = 7 000: 17 08 aa 60 f8 02 07 Config index = 0x17 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #14, code = 0x1b (Configuration entry), length = 7 000: 1f 08 aa 60 e8 03 07 Config index = 0x1f Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #15, code = 0x1b (Configuration entry), length = 7 000: 27 08 aa 60 e8 02 07 Config index = 0x27 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #16, code = 0xff (Terminator), length = 0 Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2
Re: HEADSUP: wd driver will be retired!
On 9 Dec, Maxim Sobolev wrote: Excuse me for possible off-topic, but I have what is seems for me fresh idea about this question. Why do not remove from wd driver support for chipsets already implemented/tested in ata driver? Thus both clans would satisfied i.e. users with unsupported by ata chips still will have a chance, while all other will be encouraged to use and test better (IMHO) ata... Eventually at There also exist cases where the chipset is supported but a particular functionality isn´t supported yet (in my case it´s the possibility to access MS-DOS formated ZIP-disks, harddisk access works well, and I´m not the only one with this problem (not counting the people which have not tried to use the ata driver but need to access MS-DOS-ZIPs too)). And I think it´s better to spend someones time with other issues than with digging into the wd driver. Bye, Alexander. -- Go fascinate someone else. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!)
It seems Greg Lehey wrote: OK, you asked for it, following is a patch to support the sis 5591 chipset. Remember this is done blindfolded, I have no HW to test on, but you guys do :) Let me know what happens... OK. Let's defer removing wd until we know that ata DMA works on these platforms. We'll have a lot of unhappy customers otherwise, myself (wearing another hat) included. If nobody else gets there first, I'll look at this next week. It already being tested, and it works, but at the same tike I found out that the code in the old driver for the sis is schizofrenic, it has one way of setting things up, and another way of reporting how it is set :(, that way it is difficult to compare results from the two drivers.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fallback paths (was: HEADSUP: wd driver will be retired!)
In message [EMAIL PROTECTED], Greg Lehey writes: The fallback path is not eliminated, and may never be, but it may become rather uncomfortable to linger on it longer than you absolutely need to. Would you care to expand on that statement? Apart from the fsck/root/reload issue (for which there is a manual work-around) is the only thing which doesn't work with block devices in /dev. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
Alexander Leidinger wrote: On 9 Dec, Maxim Sobolev wrote: Excuse me for possible off-topic, but I have what is seems for me fresh idea about this question. Why do not remove from wd driver support for chipsets already implemented/tested in ata driver? Thus both clans would satisfied i.e. users with unsupported by ata chips still will have a chance, while all other will be encouraged to use and test better (IMHO) ata... Eventually at There also exist cases where the chipset is supported but a particular functionality isn´t supported yet (in my case it´s the possibility to access MS-DOS formated ZIP-disks, harddisk access works well, and I´m not the only one with this problem (not counting the people which have not tried to use the ata driver but need to access MS-DOS-ZIPs too)). Does Soren know about that? And I think it´s better to spend someones time with other issues than with digging into the wd driver. IMHO not much digging - several #ifdef 0 here and there will do the trick. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!)
On Thu, Dec 09, 1999 at 04:03:58PM +0100, Soren Schmidt wrote:
It seems Greg Lehey wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember this is done blindfolded, I
have no HW to test on, but you guys do :)
Let me know what happens...
OK. Let's defer removing wd until we know that ata DMA works on these
platforms. We'll have a lot of unhappy customers otherwise, myself
(wearing another hat) included. If nobody else gets there first, I'll
look at this next week.
It already being tested, and it works, but at the same tike I found
out that the code in the old driver for the sis is schizofrenic, it
has one way of setting things up, and another way of reporting how
it is set :(, that way it is difficult to compare results from
the two drivers..
I think the old wd code was broken on reporting. The reporting
was changed from the original submission, when it was committed.
See the attached message:
From [EMAIL PROTECTED] Thu May 6 15:14:56 1999
Date: Thu, 6 May 1999 15:14:56 -0500
From: "Richard Seaman, Jr." [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Buglet in SiS support in ide_pci.c
Message-ID: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=tKW2IUtsqtDRztdT
X-Mailer: Mutt 0.95.4i
Status: RO
Content-Length: 1468
Lines: 44
--tKW2IUtsqtDRztdT
Content-Type: text/plain; charset=us-ascii
I was just installing a new drive on the machine with the
SiS 5591 chipset, and noticed strange results on the
verbose status probes.
It appears to me that the UDMA status register reported
somehow got flipped. It appears to only affect the
status report in verbose mode, and not the actual setting
of the controller.
If you would like me to commit this fix, let me know.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
--tKW2IUtsqtDRztdT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="ide_pci.c.diff"
Index: sys/pci/ide_pci.c
===
RCS file: /home/ncvs/src/sys/pci/ide_pci.c,v
retrieving revision 1.33
diff -u -r1.33 ide_pci.c
--- ide_pci.c 1999/04/24 20:13:58 1.33
+++ ide_pci.c 1999/05/06 18:36:30
@@ -1161,8 +1161,8 @@
printf ("SiS 5591 status: %s drive %d Ultra DMA %s",
unitno 2 ? "primary" : "secondary",
unitno 1,
- (DATC 0x80) ? "disabled\n" : "enabled");
- if ((DATC 0x80) == 0)
+ (DATC 0x80) ? "enabled" : "disabled\n");
+ if (DATC 0x80)
printf (", %d PCICLK data out\n", ((DATC 5) 0x3) + 1);
printf ("SiS 5591 status: %s drive %d postwrite %s, prefetch %s prefetch count
is %d\n",
unitno 2 ? "primary" : "secondary",
--tKW2IUtsqtDRztdT--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: MCA support
On Thu, 9 Dec 1999, Donn Miller wrote: Just wondering how far along MCA support is. I tried booting up a kern.flp from the latest snapshot circa dec. 7. and I got a "Read error" during boot, which halted the machine. My machine was an IBM PS/2 model 77s. MCA support isn't in GENERIC and wouldn't be on kern.flp. My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. I've observed problems with the graphics console keyboard. I suspect I'm not doing something about the differences b/t a PS2 keyboard controller and a normal AT controller but I've no idea what needs to be done. The baseboard SCSI on the m77 isn't supported. You'll want an Adaptec AHA-1640. -- | 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: HEADSUP: wd driver will be retired!
It seems Maxim Sobolev wrote: There also exist cases where the chipset is supported but a particular functionality isn_t supported yet (in my case it_s the possibility to access MS-DOS formated ZIP-disks, harddisk access works well, and I_m not the only one with this problem (not counting the people which have not tried to use the ata driver but need to access MS-DOS-ZIPs too)). Does Soren know about that? Yes I do, I just have to get my ZIP drive in a machine and find the hours to work on it... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!)
It seems Richard Seaman Jr. wrote: It already being tested, and it works, but at the same tike I found out that the code in the old driver for the sis is schizofrenic, it has one way of setting things up, and another way of reporting how it is set :(, that way it is difficult to compare results from the two drivers.. I think the old wd code was broken on reporting. The reporting was changed from the original submission, when it was committed. Yep, but it does mean that people _belive_ they are running UDMA where in fact they aren't, and now they blaim the ata driver for doing worse :( I'm not sure the other values reported are valid either as they are reported differently from what they are set to -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!)
It seems Greg Lehey wrote: I think the old wd code was broken on reporting. The reporting was changed from the original submission, when it was committed. Yep, but it does mean that people _belive_ they are running UDMA where in fact they aren't, and now they blaim the ata driver for doing worse :( Well, the wd driver definitely ran DMA on the 5591. And the fix Richard reports is not normally output; IIRC it's only on a verbose boot. On my machine, the driver reports: ide_pci0: SiS 5591 Bus-master IDE Controller irq 14 at device 0.1 on pci0 ... wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa0 wdc0: unit 0 (wd0): ST51270A, LBA, DMA, 32-bit, multi-block-32 wd0: 1223MB (2504880 sectors), 621 cyls, 64 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xb0ffb0ff on isa0 wdc1: unit 0 (wd2): IBM-DHEA-36480, LBA, DMA, 32-bit, multi-block-16 wd2: 6197MB (12692736 sectors), 790 cyls, 255 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): IBM-DHEA-38451, LBA, DMA, 32-bit, multi-block-16 wd3: 8063MB (16514064 sectors), 1027 cyls, 255 heads, 63 S/T, 512 B/S DMA is definitely enabled. There's no mistaking the difference between DMA and no DMA. That was not what I said, it may run DMA but it says UDMA when not and vice versa, there is a difference between WDMA and UDMA I'm not sure the other values reported are valid either as they are reported differently from what they are set to I took a look at this a while back and never got round to committing the changes. I believe most of the discrepancies were minor. I'll take charge of fixing that if you like. I dont care, but for 3.x that might be a good idea -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Modules and sysctl tree
Hi, I'd like to know whether we reached some conclusions concerning the naming of sysctl variables created (or related to) KLDs. I know that Linux emulator creates "compat.linux". I don't know if any other module creates sysctls (well, except my SPY module.. :-). So, what is the current thinking? Should we use modules.my_module.whatever, or kld.my_kld.whatever, or just sprinkle the new sysctls randomly over the tree, according to their functions, e.g. kern.my_module_kern_hook net.inet.my_module_inet_hook ... Also, it seems that you cannot create new sysctls (leaves and nodes) at runtime, i.e. after the module has been loaded. 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: HEADSUP: wd driver will be retired!
[snip] Again, this is not accurate. I have a laptop with which, two months ago, I could use my LinkSys ethernet card, and I could use my digital then we need to get your LinkSys ethernet card support fixed. i am using one to write this message. mine is a LinkSys 10/100 PCMCIA card. what do you have? What version of -CURRENT are you using? Mine is a PCMPC200, and I haven't been able to get it to work for 6 weeks. PCMPC100 LinkSys PCMCIA 10/100 jmb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
What version of -CURRENT are you using? Mine is a PCMPC200, and I haven't been able to get it to work for 6 weeks. PCMPC100 LinkSys PCMCIA 10/100 jmb Greg, yours is a card bus card. it is not supported at this time. i have one right next to me with the label melted. you might not want to try using it until card bus is better supported. jmb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
In message [EMAIL PROTECTED] Brian Somers writes: : The aha driver broke somewhere between the 5th and 8th of this month. : Boot -v says ``aha0: status reg test failed ff''. Odd.. What kind of card do you have? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
In message [EMAIL PROTECTED] Wilko Bulte writes: : Not quite true: the esp driver for the alphas got lost. No attack on anyone, : just stating a fact. As did the sea and uha drivers. I had a fantacy that I'd have time to write one. However, I didn't... :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: which is right? 'controller pcic0 at isa?' or 'device pcic0 at isa?'?
In message [EMAIL PROTECTED] YAMAMOTO Shigeru writes: : I wonder about configuration for pcic in -current. : : In GENERIC, '#device pcic0 at isa?' : In LINT and PCCARD, 'controller pcic0 at isa?' : : Which is right? LINT and PCCARD is right, although there is little difference between a controller and a device anymore, iirc. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
In message [EMAIL PROTECTED] Thomas David Rivers writes: : I lost support on my 1542B until I came up with a patch, which : I believe was incorporated into 3.3-R. Yes. I stand corrected. The B that I had worked w/o the patch, but many B's in the field didn't :-(. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 06:59], Warner Losh ([EMAIL PROTECTED]) wrote: : P.S. I'm not trying to cut down Warner, but I do think we really need to : focus on regaining support for things we've lost in the past 6 months. I agree with this completely. The newbus excursion of the old code likely was a big mistake. We have a basically working system now, but I've not had time to focus on the new system because of the amount of time I've spent on legacy issues. Part of this is too blame on the sparse documentation available about newbus. The relevant people clued about newbus know I am working on manpages/documents to get into the basesystem. It's coming (and hopefully with less typo's as in elf.5 ;) ) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 12:00], Wilko Bulte ([EMAIL PROTECTED]) wrote: As Mike Smith wrote ... On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: [there] were the SCSI drivers lost to CAM Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; Not quite true: the esp driver for the alphas got lost. No attack on anyone, just stating a fact. Another state of fact, until no-one finds it annoying enough to fix it it will be Atticised for quite some time longer. Apparantly the people whom caused a ruckus about losing some functionality when moving to better designed new driver framework weren't quite that bothered at all. Else we would've seen submissions for those drivers to be upgraded to the new framework. Luoqi is a prime example for aic. (If my memory serves me right.) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 16:03], Greg Lehey ([EMAIL PROTECTED]) wrote: On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: This is -CURRENT. It pains me to say it, but anyone trying to run anything "useful" on -CURRENT gets what they deserve. This is the only place where we can make clean breaks with the past, and as painful as that can be, we simply have to do that occasionally. Next month it'll be -RELEASE. This isn't the time to remove such significant functionality. If it weren't for that, I'd agree with you. Think about that some more. After that it will be 4.1. Nice to give people a driver and then rip it out when 4.1 comes when Soren fixes the last of the things people needed to have into the ata driver. I was already testing the ata driver and even procured some more info for Soren than he already had. Same goes for a bunch of other people. But the opposite goes for a lot of people. People running CURRENT to be cutting edge as in being elite with the latest FreeBSD thus get bitten. I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Flash (was: Re: Sound card support)
[again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
On Thu, Dec 09, 1999 at 08:32:05PM +0100, Jeroen Ruigrok/Asmodai wrote: [again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. I don't even use the FreeBSD Netscape any more. As far as I'm concerned, there might as well NOT be a native binary for FreeBSD, because it's not very stable. I use the Linux netscape with macromedia's flash4 plugin and it works very well. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. If you can hack on the flash plugin's Makefile, try add -fno-exceptions there. Dima To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is there any way to use ATAPI CD-R?
-On [19991209 06:58], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as NetBSD already does? It will solve problems with all SCSI-only CD* soft automatically. I thought this was the original idea back then when work started on the new drivers. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
-On [19991209 00:03], Bill Fumerola ([EMAIL PROTECTED]) wrote: On Wed, 8 Dec 1999, Soren Schmidt wrote: The same thing is about to apply to the woxware sound code, we have a new shiny system that works and is much better designed... For some definitions of "works". Low shot. If not for Cameron and Sanimura-san we would still be left dangling with the hopeless kludge of pcm vs VoxWare. They finally put their effort into something which all questions plus remarks on the topic would already have released a long time ago. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Thu, 9 Dec 1999, Jeroen Ruigrok/Asmodai wrote: For some definitions of "works". Low shot. If not for Cameron and Sanimura-san we would still be left dangling with the hopeless kludge of pcm vs VoxWare. They finally put their effort into something which all questions plus remarks on the topic would already have released a long time ago. It wasn't meant to be low or insulting. I'm making the simple obervation that my office has been oddly silent ever since switching to newpcm. It's not for unwillingness to test patches either. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
Motoyuki Konno wrote: I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Current is not a general use platform. And if we want them (third party) to support FreeBSD-elf by the time 4.x becomes -stable, we better lock them out of it *now*. The main reason for removing the legacy support is forcing people to switch. -- Daniel C. Sobral(8-DCS) who is as social as a wampas [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is there any way to use ATAPI CD-R?
On Thu, Dec 09, 1999 at 06:38:46AM +0300, Andrey A. Chernov wrote: On Wed, Dec 08, 1999 at 09:34:24PM +0100, Soren Schmidt wrote: I use it every day, well almost :) Look in /usr/share/examples/atapi... Thanks! Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as NetBSD already does? It will solve problems with all SCSI-only CD* soft automatically. I'd love to see that. I have an ATAPI CD-R that doesn't seem to work properly with the worm stuff, but is supposedly supported by the cdrecord program. But we don't yet have the interface cdrecord wants. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why 'The legacy aout build' was removed from current ?
On Thu, 9 Dec 1999, Daniel C. Sobral wrote: Motoyuki Konno wrote: I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Current is not a general use platform. And if we want them (third party) to support FreeBSD-elf by the time 4.x becomes -stable, we better lock them out of it *now*. The main reason for removing the legacy support is forcing people to switch. This isn't taking the execution of aout binaries out, just stopping a world build. This is only going to stop 3rd party developers from making a 4.0 aout platform to create *more* aout binaries. They'll probably hang on for dear life on 2.2, just as long as they can. Looking at copious examples from real life, forcing 3rd party developers to upgrade is a good way to lose 3rd party developers. It just *sounds* like a good way to go. As long as this is a change for building world, and not making changes to the kern/imgact things (so we keep on executing aout binaries) then this is probably the best way to go. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is there any way to use ATAPI CD-R?
It seems Jeroen Ruigrok/Asmodai wrote: -On [19991209 06:58], Andrey A. Chernov ([EMAIL PROTECTED]) wrote: Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as NetBSD already does? It will solve problems with all SCSI-only CD* soft automatically. I thought this was the original idea back then when work started on the new drivers. No, the idea was to get all the lowlevel ata/atapi stuff sorted out and layered so that it was maintainable and extendable. You could add a CAM top to the atapisubsystem instead of the "native" atapi drivers, it would be more work for the disks (lots more). My priority is still to get all the lowlevel stuff stabilized, and to get support for various controller HW, including top notch performance. Also CAM has to be de-SCSIfied before any of this is possible, and frankly I dont se anybody having the time/knowledge to do that for the foreseable future... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Route table leaks
The patch previously mentioned has completely fixed my problem, as far as I
can tell.
routetbl 13117K 25K 40960K936240 0 16,32,64,128,256
after a day of uptime.
here's mine..
this is from a single homed machine, with a default route. it's also a IRC
server (irc.stanford.edu), with a LOT of filtering of inbound traffic.
FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999
11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00
routetbl 20529K 10489K 10489K 34799600 0 16,32,64,128,256
note that the table maxed out at some point (during a DoS attack.)
root-irc.stanford.edu-[11:34pm-52]#t netstat -ran | wc
70 4094741
looks like it leaked 135 in 2.8 days..
-- Welcome My Son, Welcome To The Machine --
Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | [EMAIL PROTECTED]
| P.O. Box 9792, Stanford, Ca 94309-9792
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --
--
... Joe
---
Joe Greco - Systems Administrator [EMAIL PROTECTED]
Solaria Public Access UNIX - Milwaukee, WI 414/342-4847
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Is there any way to use ATAPI CD-R?
It seems Christopher Masto wrote: On Thu, Dec 09, 1999 at 06:38:46AM +0300, Andrey A. Chernov wrote: On Wed, Dec 08, 1999 at 09:34:24PM +0100, Soren Schmidt wrote: I use it every day, well almost :) Look in /usr/share/examples/atapi... Thanks! Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as NetBSD already does? It will solve problems with all SCSI-only CD* soft automatically. I'd love to see that. I have an ATAPI CD-R that doesn't seem to work properly with the worm stuff, but is supposedly supported by the cdrecord program. But we don't yet have the interface cdrecord wants. I wouldn't hold my breath :) What CD-R is that, and whats the problem. There has been a period until a week or so ago where the fixating didn't work right... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MCA support
Just wondering how far along MCA support is. I tried booting up a kern.flp from the latest snapshot circa dec. 7. and I got a "Read error" during boot, which halted the machine. My machine was an IBM PS/2 model 77s. That's probably a bad floppy. You should at least get the kernel and mfsroot loaded before MCA becomes an issue at all. -- \\ 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: HEADSUP: wd driver will be retired!
On 9 Dec, Maxim Sobolev wrote: Excuse me for possible off-topic, but I have what is seems for me fresh idea about this question. Why do not remove from wd driver support for chipsets already implemented/tested in ata driver? Thus both clans would satisfied i.e. users with unsupported by ata chips still will have a chance, while all other will be encouraged to use and test better (IMHO) ata... Eventually at There also exist cases where the chipset is supported but a particular functionality isn´t supported yet (in my case it´s the possibility to access MS-DOS formated ZIP-disks, harddisk access works well, and I´m not the only one with this problem (not counting the people which have not tried to use the ata driver but need to access MS-DOS-ZIPs too)). I'm completely at a loss as to how the ata driver could be responsible for your inability to read these disks. I don't have a copy of your original problem report to hand, but since I have all the hardware here I'd appreciate it if you could be a little more explicit about your problem. The ata driver just moves bytes; it doesn't give a damn what they are. -- \\ 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: MCA support
On Thu, 9 Dec 1999, Mike Smith wrote: My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. The loader just uses the BIOS; you can't blame it. 8) Well, there you have it. My second guess would be an issue with the 2.88M drive reading a 1.44M floppy that was created in a 1.44M drive. I was going to try burning a 1.44M floppy in the 2.88M drive to see if it allowed the disk to boot without errors but I got local disk and network working before I got around to it. -- | 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: MCA support
My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. The loader just uses the BIOS; you can't blame it. 8) I can confirm the loader problem on IBM MCA machines with 2.88M drives, and you _CAN_ blame the loader if it does not make the _CORRECT_ calls to the BIOS :-) -- 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: HEADSUP: wd driver will be retired!
I'm completely at a loss as to how the ata driver could be responsible for your inability to read these disks. I don't have a copy of your original problem report to hand, but since I have all the hardware here I'd appreciate it if you could be a little more explicit about your problem. Re-reading this, it's not clear that what I'm saying here is "please tell me a little more about what you're doing so that I can reproduce the problem", not "your problem report is terrible, please go away and die". Sorry if that's caused any consternation. -- \\ 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: MCA support
My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. The loader just uses the BIOS; you can't blame it. 8) Ohh... and if you need a box to fix this just let me know, I've got a pile of old MCA 486's that won't boot the loader code from thier 2.88MB drives, I could ship you one... -- 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: Route table leaks
so can it be committed?
On Thu, 9 Dec 1999, Joe Greco wrote:
The patch previously mentioned has completely fixed my problem, as far as I
can tell.
routetbl 13117K 25K 40960K936240 0 16,32,64,128,256
after a day of uptime.
here's mine..
this is from a single homed machine, with a default route. it's also a IRC
server (irc.stanford.edu), with a LOT of filtering of inbound traffic.
FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999
11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00
routetbl 20529K 10489K 10489K 34799600 0 16,32,64,128,256
note that the table maxed out at some point (during a DoS attack.)
root-irc.stanford.edu-[11:34pm-52]#t netstat -ran | wc
70 4094741
looks like it leaked 135 in 2.8 days..
-- Welcome My Son, Welcome To The Machine --
Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | [EMAIL PROTECTED]
| P.O. Box 9792, Stanford, Ca 94309-9792
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
PNPBIOS vs cs423B codec
Managed to get the sound stuff working on this thinkpad 600e, for anyone who cares... Had to update to the most recent bios, and made sure "quick boot" was disabled (hold down F1 while powering on to get into bios). I removed the "csa0" device from the kernel config, despite having a CS4610 probed during boot. Also set up a pcm0 config line of the sort... device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Dec 9 1999 17:28:08 Installed devices: pcm0: SoundBlaster Pro 3.2 at io 0x220 irq 5 drq 0:1 (1/1 channels duplex) the relevant PNP boot messages without pcm enabled... CSC0100: adding io range 0x530-0x537, size=0x8, align=0 CSC0100: adding io range 0x388-0x38b, size=0x4, align=0 CSC0100: adding io range 0x220-0x233, size=0x14, align=0x20 CSC0100: adding irq mask 0x20 CSC0100: adding dma mask 0x2 CSC0100: adding dma mask 0x1 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) ... unknown6: CSC0100 at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Route table leaks
At 3:00 PM -0800 1999/12/9, Julian Elischer wrote: so can it be committed? In -CURRENT, I would say that this could probably be committed, if John feels safe. I am not yet convinced that it should be committed to -STABLE, although things do look good so far. -- These are my opinions -- not to be taken as official Skynet policy |o| Brad Knowles, [EMAIL PROTECTED]Belgacom Skynet NV/SA |o| |o| Systems Architect, News FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Route table leaks
Brad Knowles wrote: In -CURRENT, I would say that this could probably be committed, if John feels safe. I am not yet convinced that it should be committed to -STABLE, although things do look good so far. Just to clarify, I committed it to -current already this morning. John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Modules and sysctl tree
Andrzej Bialecki writes: I'd like to know whether we reached some conclusions concerning the naming of sysctl variables created (or related to) KLDs. I know that Linux emulator creates "compat.linux". I don't know if any other module creates sysctls (well, except my SPY module.. :-). So, what is the current thinking? Should we use modules.my_module.whatever, or kld.my_kld.whatever, or just sprinkle the new sysctls randomly over the tree, according to their functions, e.g. kern.my_module_kern_hook net.inet.my_module_inet_hook ... I think the latter. In 'theory' there should be no discernable difference between functionality from a KLD vs. the same functionality compiled directly into the kernel. KLD's are just a linking mechanism, and shouldn't have any more significance than that from a usability perspective. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
As Jeroen Ruigrok/Asmodai wrote ... -On [19991209 12:00], Wilko Bulte ([EMAIL PROTECTED]) wrote: As Mike Smith wrote ... On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: [there] were the SCSI drivers lost to CAM Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; Not quite true: the esp driver for the alphas got lost. No attack on anyone, just stating a fact. Another state of fact, until no-one finds it annoying enough to fix it it will be Atticised for quite some time longer. True. No doubt. Apparantly the people whom caused a ruckus about losing some functionality when moving to better designed new driver framework weren't quite that bothered at all. Else we would've seen submissions for those drivers to be upgraded to the new framework. Luoqi is a prime example for aic. (If my memory serves me right.) FWIW: I only discovered the esp thingy when I found myself with a Turbochannel Alpha box. Not earlier. ;) -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
As Warner Losh wrote ... In message [EMAIL PROTECTED] Brian Somers writes: : The aha driver broke somewhere between the 5th and 8th of this month. : Boot -v says ``aha0: status reg test failed ff''. Odd.. What kind of card do you have? Does it make a difference if you run boot without -v ? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
In message [EMAIL PROTECTED] Brian Somers writes: : The aha driver broke somewhere between the 5th and 8th of this month. : Boot -v says ``aha0: status reg test failed ff''. Odd.. What kind of card do you have? aha0 at port 0x330-0x333 irq 11 drq 7 on isa0 aha0: AHA-1542CP FW Rev. D.0 (ID=46) SCSI Host Adapter, SCSI ID 7, 16 CCBs It's PnP, but the BIOS says non-PnP OS and is assigning irq11/drq7 both with the old new kernels. The working kernel is a ``cd /sys; cvs up -D991205'' kernel and the broken one is anything more recent (although I don't know exactly where it broke). I'll try to get some time on the weekend to roll things forward 'till they break I moved my ISDN card from 0x160 because it was causing problems with wdc1 (@ 0x170) (which may be why ata1 was jamming up) to 0x260, but the card uses a whole bunch of i/o addresses The working kernel from the 5th has no ISDN support because I had to build it on another machine (one without the i4b patches installed). It's a horrible mess. If nobody else complains about ata, I'd assume it's just pilot error. Warner -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OpenSSL update
Due to time constraints (exams) I haven't been able to do much more towards the OpenSSL build infrastructure (specifically, jumping through the requisite hoops for US stupidity). I have it building fine, although compiling without RSA seems broken in openssl 0.9.4. Unfortunately, the openssl binary seems to depend nontrivially on both libcrypto and libssl, so we can't get away with just importing the former, without some recoding. Since I'm flying back home to australia next tuesday, and we have a feature freeze for -current coming up, what I'll probably do is just import all of openssl into the international repository, and enable the build only for people who have defined USA_RESIDENT==NO. When I get back in January I can get the munged version (i.e. w/o RSA sources, optionally building with RSAREF) imported and enabled for US people, as well as solving the binary distribution problem. The alternative, given the feature freeze, seems to be to forgo any kind of enhanced crypto support in 4.x, which would suck. Sound okay to everyone? Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
As Warner Losh wrote ... In message [EMAIL PROTECTED] Brian Somers writes: : The aha driver broke somewhere between the 5th and 8th of this month. : Boot -v says ``aha0: status reg test failed ff''. Odd.. What kind of card do you have? Does it make a difference if you run boot without -v ? Nope :-( -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test
On Thu, 09-Dec-1999 at 15:02:41 -0800, Alfred Perlstein wrote:
On Thu, 9 Dec 1999, Andre Albsmeier wrote:
...
For better reference, here is the current patch:
*** lpr.c.ORI Thu Dec 9 15:30:18 1999
--- lpr.c Thu Dec 9 15:30:35 1999
***
*** 370,375
--- 370,405
}
if (sflag)
printf("%s: %s: not linked, copying instead\n", name, arg);
+ /*
+* If lpr was invoked with -r we try to move the file to
+* be printed instead of copying and deleting it later.
+* This works if the file and lpd's spool directory are
+* on the same filesystem as it is often the case for files
+* printed by samba or pcnfsd. In this case, a lot of I/O
+* and temporary disk space can be avoided. Otherwise, we
+* will continue normally.
+*/
+ if (f) {/* file should be deleted */
+ seteuid(euid); /* needed for rename() */
+ if (!rename(arg, dfname)) {
+ int i;
+ #if 0
+ chown(dfname, userid, getegid());
+ chmod(dfname, S_IRUSR | S_IWUSR |
+ S_IRGRP | S_IWGRP);
+ #endif
+ seteuid(uid); /* restore old uid */
+ if (format == 'p')
+ card('T', title ? title : arg);
+ for (i = 0; i ncopies; i++)
+ card(format, dfname[inchar-2]);
+ card('U', dfname[inchar-2]);
+ card('N', arg);
+ nact++;
+ continue;
+ }
+ seteuid(uid); /* restore old uid */
+ }
if ((i = open(arg, O_RDONLY)) 0) {
printf("%s: cannot open %s\n", name, arg);
} else {
I don't have too much time to think about this, argue me this:
Sure, please tell me if you don't want to get CC'ed on this anymore.
why should I allow a user to print any file on the system?
the race condition is still there.
Right :-(. The file won't be given to the user anymore but he can
print everything. However, there must be a solution for this...
-Alfred
-Andre
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Flash (was: Re: Sound card support)
Hi .. Under current the flash plugin works with the linux version of Netscape and the linuxelator ... Sound etc, everything works ok ... except for the odd crash of netscape which is normal :) Just get the linux netscape and the linux flash plugin. Reinier [again subject changes] -On [19991209 16:00], Donn Miller ([EMAIL PROTECTED]) wrote: On Thu, 9 Dec 1999, Motoyuki Konno wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Atone me to my throes curtail... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenSSL update
On Thu, 9 Dec 1999, Kris Kennaway wrote: Due to time constraints (exams) I haven't been able to do much more towards the OpenSSL build infrastructure (specifically, jumping through the requisite hoops for US stupidity). I have it building fine, although compiling without RSA seems broken in openssl 0.9.4. Unfortunately, the openssl binary seems to depend nontrivially on both libcrypto and libssl, so we can't get away with just importing the former, without some recoding. Why don't you want libssl, too? If we don't have that, then we'll end up having to install the port for using SSL and there will be redundancy (wasted space) and two copies of OpenSSL to maintain, still. Since I'm flying back home to australia next tuesday, and we have a feature freeze for -current coming up, what I'll probably do is just import all of openssl into the international repository, and enable the build only for people who have defined USA_RESIDENT==NO. When I get back in January I can get the munged version (i.e. w/o RSA sources, optionally building with RSAREF) imported and enabled for US people, as well as solving the binary distribution problem. The alternative, given the feature freeze, seems to be to forgo any kind of enhanced crypto support in 4.x, which would suck. Sound okay to everyone? Sounds great. I hope this means I get to import OpenSSH! Kris -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Wed, 8 Dec 1999, Soren Schmidt wrote: It seems Julian Elischer wrote: please do not remove it.. And why is that ?? There is no point in having done a new one then, and you guys have known I've been working on this for ages so this cannot come as a surprise to anybody... The same thing is about to apply to the woxware sound code, we have a new shiny system that works and is much better designed... ATA doesn't do ESDI, does it? Therefore, wd(4) should still be available. NewPCM doesn't work with all the equipment VoxWare does, does it? I don't want to lose my SB16 (non-PnP) FM, certainly. -Søren -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
