HELP: Disk/file-systems are loused up
I started up my (version 3.3 ) freeBSD , and the first thing that I did was mount a MSDOS diskette and did a find on it (with -name "*hd*" ). I got three lines of output stating something like 'date error; month (14) out of range', then a long pause (during which I typed several ctl-C's ), and the system crashed. I booted immediately, and the system informed me (after the boot) that the disk is loused up and I should run fsck , which I did. I ran it several times and it didn't fix the problem until I ran fsck -p . I tried the find again, with the same results, but this time I withdrew the floppy during the pause trying for another type of termination to the find (rather than a system crash, I was hoping for a message that the device was inaccessible and that I could respond in such a way that the command would abort). Unfortunately, the system crashed again. This time, no matter what I did with fsck I couldn't get the file systems cleaned up. Any suggestions? Send responses to me here and to me as [EMAIL PROTECTED] . _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
I've never thought of a use for fdescfs... -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Getting all the IP address for a machine from code...
On Wed, Sep 13, 2000 at 08:12:47PM -0700, Chris Ptacek wrote: I am looking for a way to get all the IP addresses that are configured a machine. I need to do this in c source code, and without using DNS services (ie: gethostname/gethostbyname won't work). I am hoping there are some system calls I can use to get this information. Thanks in advance for any help. You could use getifaddrs in FreeBSD 4 and later - otherwise you'll need to use sysctl to get the list of interfaces and addresses. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: I've never thought of a use for fdescfs... Well.. just a trivial example - imagine a program which takes a filename as an argument; imagine yourself trying to pipe something into it - passing /dev/fd/0 as a filename to process would do the trick. G'luck, Peter -- .sith ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
In message [EMAIL PROTECTED], Peter Pentchev writes
:
On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
I've never thought of a use for fdescfs...
Well.. just a trivial example - imagine a program which takes a filename
as an argument; imagine yourself trying to pipe something into it -
passing /dev/fd/0 as a filename to process would do the trick.
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a legitimate need.
If anything I would propose we ditch it...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
Poul-Henning Kamp wrote:
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a legitimate need.
You think adding a hack to every program to support "-" to mean
stdout/stdin is better? It seems to be that saying "/dev/stdin" when
you mean stdin is better than saying "-" and hoping the application
handles that correctly. Of course many programs will read stdin by
default, and write stdout by default, but that doesn't help when you
want to read more than one file, one of which is stdin.
If anything I would propose we ditch it...
And break loads of scripts at the same time?
--
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
In message [EMAIL PROTECTED], Ben Smithurs
t writes:
Poul-Henning Kamp wrote:
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a legitimate need.
You think adding a hack to every program to support "-" to mean
stdout/stdin is better?
The majority of these programs could be handled by adding knowledge
of "-" as a magic filename to fopen(3).
At the same time I would really love if we implemented "|.*" to mean
"do an popen(3)" instead.
But of course, this is bikeshed material...
If anything I would propose we ditch it...
And break loads of scripts at the same time?
I would argue that the programs and the scripts that call them are
already broken, but hey...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
[EMAIL PROTECTED] said: :- The majority of these programs could be handled by adding knowledge of :- "-" as a magic filename to fopen(3). Suppose I *want* a filename called "-"? My tough luck, huh? I *like* /dev/stdin. It's orthogonal! -- Robert Withrow -- (+1 978 288 8256) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Die über 350 besten Marketing-Praxis-Checklisten ...
Title: Mehr Effizienz und Erfolg mit den besten Marketing-Praxis-Checklisten Liebe Marketingverantwortliche Stellen Sie sich vor, Sie müssten bis morgen um 10.00 Uhr ein erfolgsversprechendes Messekonzept präsentieren. Oder kreative Ideen für die nächste Direct-Mail-Aktion und bis in zwei Tagen Vorschläge für ein erfolgreiches Internetmarketing vorlegen. Und dies natürlich neben dem üblichen Alltagsgeschäft! Kein Problem mit unseren Marketing-Praxis-Checklisten. Sie sorgen dafür, dass Sie bei Ihrer täglichen Arbeit entlastet werden und steigern den Erfolg Ihrer Marketingaktivitäten. Die Checklisten sind für Fr. 145.00/Stück erhältlich und damit bereits nach der ersten Anwendung amortisiert! Schauen Sie bei uns rein und überzeugen Sie sich von den Vorteilen des Marketing-Checklisten-Managers, als Handbuch oder CD-Rom erhältlich: http://www.stsmarketing.ch Wir freuen uns auf Ihren Besuch. Gruss Stefan Schmidlin Eid. dipl. Marketingleiter P.S.: Lassen Sie sich anhand von 5 kostenlosen Checklisten nach ihrer Wahl von der Qualität der Marketing-Checklisten-Sammlung überzeugen. This message was sent to you by Stefan Schmidlin, STS Marketing - Diese Nachricht wurde via MessageREACH versendet. Wenn Sie keine weiteren Emails von diesem Empfaenger wuenschen: 1. Klicken Sie auf Antworten. 2. Ersetzen Sie den Text in der Betreff-Zeile durch REMOVE. 3. Klicken Sie auf Senden. Sie werden ein letztes Mal eine Email mit einer Bestaetigung erhalten. - This message was sent using the MessageREACH Service. If you would prefer not to receive further messages from this sender: 1. Click on the Reply button. 2. Replace the Subject field with the word REMOVE. 3. Click the Send button. You will receive one additional e-mail message confirming your removal. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: c++ error
On Wed, Sep 13, 2000 at 11:02:28PM -0500, Jacques A. Vidrine wrote: Please see PR bin/13383 before doing anything like this. It addresses a similar situation. I'll comment more tomorrow after some sleep :-) I knew I needed some sleep. It ``addressess'' the exact same situation. In summary, gcc has a kluge to work around a bug in the C++ standard. It looks like you and Justin have both found edge cases where the gcc kluge loses. If you can come up with a reasonable test case that reproduces the problem, perhaps it can be PR'd to the GCC folks? As per the PR, I'm against #ifdef'ing structures like ip_opts for C++, since it is likely that a later C++ standard will be corrected. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.1 PCMCIA on IBM ThinkPad A20p
Hello all, We recently got one IBM ThinkPad A20p. This might be the top notebook so far. However, we could not make the pccard services work. We have tested some cards, including D-Link DFE-650, a fast ethernet adaptor, and Compaq WL100, a 802.11b wireless NIC, also a generic ata controller (it is actually a SmartMedia to PC Card adaptor). FreeBSD sees these cards. It could identify the card, but the driver allocation failed (at least for the ATA card). For D-Link DFE-650, ifconfig get a ed0 timeout message, ifconfig could assign inet address, but it could not provide media information. The same for Compaq WL100, which uses wi0 driver. Somehow the MAC address reported by wi0 driver for WL100 diffs every time, strange. A20p use TI 1450 pcic controller. The dmesg is attached below. Could someone provide some hints on how to solve this? We think this is a generic PC Card problem related to perhaps the unsupported TI PCI-1450 CardBus Bridge? Oh, none of the cards above are cardbus cards. We also try some cardbus cards, they can not be recognized by freebsd. = dmesg begins here = real memory = 536870912 (524288K bytes) avail memory = 519606272 (507428K bytes) Preloaded elf kernel "kernel" at 0xc032e000. module_register_init: MOD_LOAD (vesa, c02469e0, 0) error 6 Pentium Pro MTRR support enabled apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: ATI model 4c46 graphics accelerator at 0.0 irq 11 pcic-pci0: TI PCI-1450 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 2.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pcic-pci1: TI PCI-1450 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device 2.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pci0: unknown card (vendor=0x11c1, dev=0x0449) at 3.0 irq 11 csa0: Crystal Semiconductor CS4614/4622/4624 Audio accelerator/4280 Audio controller mem 0xf010-0xf01f,0xf0003000-0xf0003fff irq 11 at device 5.0 on pci0 pcm0: CS461x PCM Audio on csa0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0x1c10-0x1c1f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x1c20-0x1c3f irq 11 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: Intel 82371AB Power management controller port 0x1040-0x104f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 1040 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped 1000 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 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 pca0 at port 0x40 on isa0 pcic0: VLSI 82C146 at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 ad0: 19077MB IBM-DJSA-220 [41344/15/63] at ata0-master using UDMA33 acd0: DVD-ROM MATSHITADVD-ROM SR-8174 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a pccard: card inserted, slot 1 wi0: WaveLAN/IEEE 802.11 at port 0x240-0x27f irq 10 slot 1 on pccard1 wi0: Ethernet address: 80:72:25:c1:00:99 = dmesg ends here = -- Chen-Hsiung Chan [¸âÂíºµ](BIG5) Department of Life Science http://waru.life.nthu.edu.tw/~frankch/ National Tsing Hua University email: [EMAIL PROTECTED] Taiwan phone: 03-5715131#3482 fax: 03-5715934 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
[EMAIL PROTECTED] said: :- The majority of these programs could be handled by adding knowledge of :- "-" as a magic filename to fopen(3). Suppose I *want* a filename called "-"? My tough luck, huh? Could you settle for "./-"? Robert Withrow -- (+1 978 288 8256) [EMAIL PROTECTED] --Johnny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
/proc /dev/std* [Was: Fdescfs updates--coming to a devfs near you!]
Johnny Eriksson wrote:
[EMAIL PROTECTED] said:
:- The majority of these programs could be handled by adding knowledge of
:- "-" as a magic filename to fopen(3).
Suppose I *want* a filename called "-"? My tough luck, huh?
Could you settle for "./-"?
I think any "magic" name is not very good idea. To say more, it breaks POSIX.
File names are a tratitional UNIX way to access character and block devices;
in System V you can access much more via file names, using streams.
Magic numbers are for MS DOS (remember COM1 and LPT1? :-)
I am not sure /proc/any number names are very useful, but
/dev/std{in|out|err} definitely are.
--
* *Konstantin Chuguev - Application Engineer
* * Francis House, 112 Hills Road
* Cambridge CB2 1PQ, United Kingdom
D A N T E WWW:http://www.dante.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
/dev/cuaa0 locks my system up..Help!
Ok, I'm posting this here as a last resort. I've already done a search of the freebsd mailing lists and have posted several times to freebsd-questions but haven't received any information that has helped me resolve this problem. A while back, while trying to get my APC Smart-UPS 1000 to talk to my FreeBSD 3.4 system, I encountered a problem with the serial port. This problem inspired my to write an article that was published at this months edition of daemonnews. http://www.daemonnews.org/29/adventure.html Regardless of what application I use to access my serial port (/dev/cuaa0), when I do, it causes my system to freeze up. CTRL + ALT + BACKSPACE doesn't work, CTRL + ALT + F2 doesn't work,..you get the picture. When my system freezes like this, my only alternative is to do a cold reboot and I don't think this is too healthy a practice for any OS. After trying kermit to see if I can, at least, talk to the serial port, I get the same results when trying to connect. Someone suggested I also try minicom but I couldn't get it installed. It timed out when trying to access the ftp sites listed in the Makefile. I also tried to download and install a newer version but couldn't get that to work either. Possibly because my ports need to be updated. I've scoured the contents of all my logs and haven't found any error message that would give a clue as to why this keeps happening. The only thing I haven't tried is using a different serial cable. The folks at APC said they sell a specialized serial cable that's made to work with UNIX systems. I was about to purchase this cable and try it until I received an email from a guy, in response to my article at daemonnews, saying that he's experienced the exact same problem with his serial port as well. Even though he hasn't been trying to hook up a UPS but rather trying to get his modem to dial. My pc is a Compaq Deskpro 2000 (266mhz) with 64m RAM, running FreeBSD 3.4. There is only one serial port on this pc. There should be a way to find out why this keeps happening. Even if I find out that it's just not possible to get the serial port configured correctly for a UPS, I'd still like to know why. I've tried changing permissions for /dev/cuaa0 and the applications I've used to access the port/device, I've tried using ps aux, top and fstat to see if I can found out what process might be using the device but haven't found anything tangible. Even though it's not an emergency that I get this to work, it's a problem I'd like to get fixed or at least find out why I'll never get it to work. Any help would be greatly appreciated. Thanks Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
Poul-Henning Kamp writes:
In message [EMAIL PROTECTED], Ben Smithurs
t writes:
Poul-Henning Kamp wrote:
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a legitimate need.
You think adding a hack to every program to support "-" to mean
stdout/stdin is better?
The majority of these programs could be handled by adding knowledge
of "-" as a magic filename to fopen(3).
Ugh. So what happens when you *really* want to read a filed called
"-"? Adding magic characters to low-level calls is a bad idea.
I believe /dev/fd originated in Unix v8 (or maybe plan 9) to provide a
uniform mechanism to get a class of process-internal objects where
they can be manipulated by shell scripts. If that's the case, it's
provenance is impeccable.
At the same time I would really love if we implemented "|.*" to mean
"do an popen(3)" instead.
Again, putting magic character recognition in a low-level call is a
bad idea. Worse yet, this kind of thing is really useful in shells
(which don't generally have the ability to manipulate fd's). Consider
trying to use that syntax in the shell?
Which is why modern shells that implement this kind of thing use a
different syntax. Of course, they depend on something like /dev/fd or
named pipes to provide this feature.
But of course, this is bikeshed material...
Most certainly. If you really want to make C programming look like
Perl programming, could you do it by adding new library calls, instead
of changing the semantics of existing ones?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: HELP: Disk/file-systems are loused up
gerald stoller writes: I started up my (version 3.3 ) freeBSD , and the first thing that I did was mount a MSDOS diskette and did a find on it (with -name "*hd*" ). I got three lines of output stating something like 'date error; month (14) out of range', then a long pause (during which I typed several ctl-C's ), and the system crashed. I booted immediately, and the system informed me (after the boot) that the disk is loused up and I should run fsck , which I did. I ran it several times and it didn't fix the problem until I ran fsck -p . I tried the find again, with the same results, but this time I withdrew the floppy during the pause trying for another type of termination to the find (rather than a system crash, I was hoping for a message that the device was inaccessible and that I could respond in such a way that the command would abort). Unfortunately, the system crashed again. This time, no matter what I did with fsck I couldn't get the file systems cleaned up. Any suggestions? Send responses to me here and to me as [EMAIL PROTECTED] . I loose my file systems while use 3.3 and 3.4 versions and something wrong happen with different scenario. Do not use 3.X - it is highly unstable in wrong conditions. Use 4.X - it is more stable in the same conditions. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: rcp -x
Robert, Thanks for the explanation. That wasn't clear from the manpage. SSH sounds like the better path for me. -Steve On Wed, Sep 13, 2000 at 06:22:53PM -0400, Robert Watson wrote: The -x options on rsh, rcp, and rlogin rely on Kerberos support, which it appears you haven't installed. (example w/o kerberos installed) rcp -x rcp: illegal option -- x usage: rcp [-p] f1 f2 rcp [-pr] f1 ... fn directory (example w/kerberos installed) rcp -x usage: rcp [-Kpx] [-k realm] f1 f2 rcp [-Kprx] [-k realm] f1 ... fn directory There's a tutorial on setting up Kerberos in the handbook, although it may be out of date. However, Kerberos involves substantial administrative overhead -- if you're not interested in that, try using SSH. Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services On Wed, 13 Sep 2000, Steven E. Ames wrote: The man page for rcp(1) lists a '-x' option: -x Turn on DES encryption for all data passed by rcp. This may im- pact response time and CPU utilization, but provides increased security. But the command line doesn't seem to honor it? winrad3# rcp -x rcp: illegal option -- x usage: rcp [-p] f1 f2 rcp [-pr] f1 ... fn directory ditto -K and -k. -Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
Poul-Henning Kamp wrote:
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a legitimate need.
I strongly disagree. I actually have a script that I use daily which requires
a filename as an argument. By handing it /dev/stdin, I can make it take
output as a part of a pipe. A _very_ useful little feature, IMNSHO.
As far as fdescfs, well, Unixware has something very like it, and I believe
that other commercial Unices do as well. I suspect that it's useful to
some, if not to all.
One thing about end users as opposed to engineers, they put this stuff to
uses that we can't even imagine. Never underestimate the sheer ingenuity
of a relatively naive user. :-)
--
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://store.exit.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
We are trying to create a dynamic library of extensions to PHP 4.02. This library implements a C++ class and has a C interface using the "Extern C" declaration. This library is linked with libstdc++.so.3 . If the library is called in a C program = no trouble. If the library is called from PHP with the "dlopen()" function = [Warning: Unable to load dynamic library '/users/em/ftp/php/test_cpp/debug/libphptest.so' - /usr/lib/libstdc++.so.3: Undefined symbol "__ti9exception" in /usr/local/httpd/htdocs/www/Iti_q/testso.php on line 2 This is because FreeBSD uses an archive library "libgcc.a" instead of a shared library. That means that everything from libgcc which is needed by your shared libraries had better already be linked into the main program. The right solution is for us to use a shared library for libgcc. At one point libgcc was shared (FreeBSD 1.*), and it caused way more problems that it solved. Nate (Note to eager committers: don't do this without coordinating with obrien. There are ramifications that aren't obvious.) As a work-around, try adding this to your main program. (I am assuming it is a C++ program too.) extern void terminate(void); void (*kludge_city)(void) = terminate; Another possibility would be to link explicitly with libgcc when creating your dynamic library: cc -shared -o libphptest.so ... -lgcc That might cause other problems, but probably not. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
what the heck is ftime and why is the reference undefined???????
I need to read the temps off of a 1-Wire Lan. I know about the mlan stuff in the ports, but the themod is set to read an ibutton 1920 device. I'm using a DS1820. I'm not a programmer so I would have the first clue where to even try modifying this for my device. Is anyone using the DS1820 on a 1-Wire Lan with FreeBSD? I have downloaded Digitemp and the Dallas DS-1820 software listed on Freshmeat. They are both for Linux. I recompiled Digitemp and it runs but doesn't print out any results. The other looked a little more promising, but when I try to compile it, it screams about undefined reference to 'ftime' Any help would be appreciated. Thanks, Ray To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: what the heck is ftime and why is the reference undefined???????
In message 003101c01e60$eb3b4e40$[EMAIL PROTECTED], "Ray Seals" wri tes: I need to read the temps off of a 1-Wire Lan. I know about the mlan stuff in the ports, but the themod is set to read an ibutton 1920 device. I'm using a DS1820. I'm not a programmer so I would have the first clue where to even try modifying this for my device. Is anyone using the DS1820 on a 1-Wire Lan with FreeBSD? http://firtal.freebsd.dk/weather/ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: what the heck is ftime and why is the reference undefined???????
See the manpage on ftime(3) (especially the first and second lines of DESCRIPTION) - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UNIXREVIEW.com
FYI: (blatently stolen from UNIXREVIEW.COM EXTRA! Volume 1, Issue 11) UNIXREVIEW.COM Call for Papers unixreview.com is looking for contributors to write feature articles. See the list below for suggested topics, or contact us with your own article ideas. * FreeBSD * Storage Area Networks * Linux performance tuning * Java * Open Source Development * Systems Management * Web Security Issues * Embedded Linux * Comparison of window managers * Comparison of the main X servers for UNIX on Intel Contact Christi Bear ([EMAIL PROTECTED]) with proposals for articles, press releases, or general questions about the publication process. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: c++ error
In article [EMAIL PROTECTED], Jacques A. Vidrine [EMAIL PROTECTED] wrote: In summary, gcc has a kluge to work around a bug in the C++ standard. It looks like you and Justin Archie. have both found edge cases where the gcc kluge loses. If you can come up with a reasonable test case that reproduces the problem, perhaps it can be PR'd to the GCC folks? Actually, I don't have a test case. I was only able to make it fail when I moved netinet/in.h out of /usr/include -- which disables the gcc kludge. I hope that Archie will be able to come up with a test case that demonstrates the failure. BTW, Archie, there are 3 places in the gcc code which can produce that diagnostic: 1 in "cp/class.c" and 2 in "cp/decl.c". Search for "with same name as" and you'll find them. It would be useful to find out which one of those is the culprit in your failing case. As per the PR, I'm against #ifdef'ing structures like ip_opts for C++, since it is likely that a later C++ standard will be corrected. I can't argue with that. I don't like my "solution" very much either. :-) John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
In article [EMAIL PROTECTED], Nate Williams [EMAIL PROTECTED] wrote: At one point libgcc was shared (FreeBSD 1.*), and it caused way more problems that it solved. Do you remember any details? I analyzed it pretty thoroughly (I thought) more than a year ago, and decided the shared library was the best solution. At that time I asked PHK what the reasons were for eliminating the shared libgcc. (He is the person who got rid of it. See "src/gnu/lib/libgcc/Makefile" revisions 1.5 - 1.8.) He said he didn't think it would be a problem to make it shared again. At that time, I converted my -current system to using a shared libgcc and ran it like that for 6 months at least without any problems. I believe David O'Brien was also using a shared libgcc for a long time without problems. The non-shared libgcc used to work for us mainly because on the i386 architecture practically nothing from libgcc was ever used. That is no longer the case, because of all the exception support that has been added to it for C++. If a shared library uses exceptions (as does libstdc++) but the main program doesn't, you get undefined symbol errors as the original poster reported. Using a shared libgcc completely solves that. Also, we _desperately_ need to switch away from the setjmp/longjmp exception implementation and start using the now-standard DWARF2 implementation. It makes a tremendous performance difference even in programs that don't use exceptions at all. (I measured it once.) But that in turn requires more support from libgcc, and exacerbates the problems associated with using a non-shared libgcc. The egcs team used to argue vociferously against making libgcc shared. However, I found their list of reasons and decided that they didn't apply to us. In my view, many of the reasons boiled down to, "It would be too inconvenient for Red Hat." I.e., they didn't want to use their shared library version numbers the way they are supposed to be used. Also, many of the arguments against a shared libgcc which might make sense when gcc is a 3rd-party add-on just don't apply when it is _the_ system compiler. I don't follow the gcc mailing lists any more, but David O'Brien told me some months ago that they had done a complete turn-around on the issue and were planning on making libgcc shared again. (David, please correct me if I'm misrepresenting what you told me.) John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
At one point libgcc was shared (FreeBSD 1.*), and it caused way more problems that it solved. Do you remember any details? I analyzed it pretty thoroughly (I thought) more than a year ago, and decided the shared library was the best solution. If I remember right (and my memory is fuzzy for stuff that far bak) there were a couple of issues. 1) Speed. Shared libraries are slower than static libraries (PIC et. al), and the stuff in libgcc tends to be performance centric. 2) Ease of use. Everytime we upgrade or modify libgcc, it required keeping around the old libgcc.so. I don't think we had much experience with versioning back then, so we tended to either 'never' increment the versions or 'overdo' it. We weren't making releases nearly as often then, so keeping backwards compatability was more difficult as people tended to be running -stable instead of releases. Nowadays we handle backwards compatability better, so having N different versions of libgcc is still annoying, but easier to deal with (/usr/lib/compat). At that time, I converted my -current system to using a shared libgcc and ran it like that for 6 months at least without any problems. I believe David O'Brien was also using a shared libgcc for a long time without problems. There were no problems, it was just annoying. Many were of the opinion that 'not everything should be linked shared', since it tends to clutter up /usr/lib, and also tends to slow things down. Static linking isn't always bad The non-shared libgcc used to work for us mainly because on the i386 architecture practically nothing from libgcc was ever used. Aren't there quite a few 'math' routines inside libgcc (mods and diffs and all sorts of low-level 32/64 bit routines that are quite often used..) That is no longer the case, because of all the exception support that has been added to it for C++. If a shared library uses exceptions (as does libstdc++) but the main program doesn't, you get undefined symbol errors as the original poster reported. Using a shared libgcc completely solves that. Ahh. Can't we just make the linker *always* add libgcc onto the end? Because it's a static library, if it's the symbol isn't used, then it won't be linked into the library? Also, we _desperately_ need to switch away from the setjmp/longjmp exception implementation and start using the now-standard DWARF2 implementation. It makes a tremendous performance difference even in programs that don't use exceptions at all. (I measured it once.) But that in turn requires more support from libgcc, and exacerbates the problems associated with using a non-shared libgcc. How so? Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
hi, there! On Thu, 14 Sep 2000, John Polstra wrote: Also, we _desperately_ need to switch away from the setjmp/longjmp exception implementation and start using the now-standard DWARF2 implementation. It makes a tremendous performance difference even in programs that don't use exceptions at all. (I measured it once.) But that in turn requires more support from libgcc, and exacerbates the problems associated with using a non-shared libgcc. libgcc already has support for DWARF2. the only thing that should be changed is crtbegin.o/crtend.o. I have made all the necessary patches for this. I believe, David has them. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: c++ error
John Polstra writes: have both found edge cases where the gcc kluge loses. If you can come up with a reasonable test case that reproduces the problem, perhaps it can be PR'd to the GCC folks? Actually, I don't have a test case. I was only able to make it fail when I moved netinet/in.h out of /usr/include -- which disables the gcc kludge. I hope that Archie will be able to come up with a test case that demonstrates the failure. I was doing a build with DESTDIR=/usr/image and so in.h was actually being found in /usr/image/usr/include/netinet/in.h rather than the normal place, so this must be what happened to me as well. Ugh, I'm glad I got to skip C++ and go straight to Java :-) -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
[ I trimmed off current. ] :- Suppose I *want* a filename called "-"? My tough luck, huh? :- Could you settle for "./-"? I wouldn't want to. Consider: I have a program that takes user input (from an option or a file or whatever) and uses that to compose an output file name. With the above I have to either test for "magic" filenames, or I have to correctly re-write filenames to prepend "./" when appropriate (and *only* when appropriate). Sure, it can be done, but it isn't trivial work and it has to be done to every program or you have a unexpected lurking bug. IMO, "magic" filenames are bad design. Orthogonality should always win out. -- Robert Withrow -- (+1 978 288 8256) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: installing ...
On Wed, 13 Sep 2000, Danny Braniss wrote: after i made a 'make buidlworld' how can i get it to install in /5.0-CURRENT? i compiled on a 4.1. I respectfully suggest that if you dont know how to install FreeBSD from source, you shouldn't be using 5.0-CURRENT, which can and will screw up your system unless you already know how to fix it yourself. See http://www.freebsd.org/handbook/current-stable.html Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Peter Pentchev writes
:
On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
I've never thought of a use for fdescfs...
Well.. just a trivial example - imagine a program which takes a filename
as an argument; imagine yourself trying to pipe something into it -
passing /dev/fd/0 as a filename to process would do the trick.
I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
is bogus. It looks like something which happened "because we can" more
than something which has a legitimate need.
How about the fact that the printing chapter in the Handbook uses /dev/fd/0
in its example of setting up a print filter using ghostscript since gs
doesn't read from stdin by default or use '-' for that purpose. Hmmm??
If anything I would propose we ditch it...
Tools, not policy, as you are so fond of saying.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
re: /dev/cuaa0 locks my system up..Help!
I had some weird serial port problems myself a few days ago. I was having an (unrelated) problem with a PCI video card, and I swapped it to a different PCI slot on the advice of the manufacturer, which fixed the problem, but also caused my VGA card to change *it's* interrupt, which grabbed the same interrupt as one of my serial ports. The symptoms were, sometimes FreeBSD would identify the serial port on bootup, and sometimes it wouldn't see it at all. I would get a login banner on the terminal connected to that serial port when the system was booted, but the terminal wouldn't respond to keystrokes at all. Anyway, do this: dmesg | grep -i irq and look for two devices using the same IRQ number. Maybe that's it. -Joe Loughry [EMAIL PROTECTED] Regardless of what application I use to access my serial port (/dev/cuaa0), when I do, it causes my system to freeze up. CTRL + ALT + BACKSPACE doesn't work, CTRL + ALT + F2 doesn't work,..you get the picture. When my system freezes like this, my only alternative is to do a cold reboot and I don't think this is too healthy a practice for any OS. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: installing ...
In message [EMAIL PROTECTED]you write: }On Wed, 13 Sep 2000, Danny Braniss wrote: } } after i made a 'make buidlworld' how can i get it to install in /5.0-CURRENT? } i compiled on a 4.1. } }I respectfully suggest that if you dont know how to install FreeBSD from }source, you shouldn't be using 5.0-CURRENT, which can and will screw up }your system unless you already know how to fix it yourself. well, it shouldn't screw up my system, if, for example, the install is not to a live system but to another partition, or disk which i could later boot from. i only asked, since i saw that one can compile to /usr/obj, which is fine, so what happend to that extra mile? danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
Danny Braniss wrote: In message [EMAIL PROTECTED]you write: }How about the fact that the printing chapter in the Handbook uses /dev/fd/0 }in its example of setting up a print filter using ghostscript since gs }doesn't read from stdin by default or use '-' for that purpose. Hmmm?? } what about programs that were never meant to read from stdin, since, for example they like to seek ..., dvi2ps comes to mind. Well, then they won't work. But just because some program won't work with it but many do doesn't mean we shouldn't remove the functionality. If you want to blow your own foot off, the OS's job is to deliver the bullet quickly and accurately to its destination. :) danny -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: HELP: Disk/file-systems are loused up
Koster, K.J. writes Subject: RE: HELP: Disk/file-systems are loused up Date: Thu, 14 Sep 2000 10:16:38 +0100 Hello Gerald, I started up my (version 3.3 ) freeBSD , and the first thing that I did was mount a MSDOS diskette and did a find on it (with -name "*hd*" ). I got three lines of output stating something like 'date error; month (14) out of range', then a long pause (during which I typed several ctl-C's ), and the system crashed. I booted immediately, and the system informed me (after the boot) that the disk is loused up and I should run fsck , which I did. I ran it several times and it didn't fix the problem until I ran fsck -p . I tried the find again, with the same results, but this time I withdrew the floppy during the pause trying for another type of termination to the find (rather than a system crash, I was hoping for a message that the device was inaccessible and that I could respond in such a way that the command would abort). Unfortunately, the system crashed again. This time, no matter what I did with fsck I couldn't get the file systems cleaned up. Any suggestions? From your text it is not clear what you are fsck-ing. You cannot fsck an MSDOS floppy. fsck is only for your harddisk after the crash. First boot some form of MSDOS or windows and use some form of scandisk to fix the filesystem on the floppy. A broken filesystem on a floppy (or any other device for that matter) *will" panic your system. I suggest that after you found what you were looking for, you bin the floppy. One broken sector indicates it's about to die completely. Kees Jan The fsck was operating on and reporting on the hard disk; the floppy was not even mounted while I was booting. Since fsck in all the variations with which I am familiar didn't fix the disk, I am trying to find another variation or another program to run which will complete the job without causing any disasters. I also think that the find program should be checked to see why it crashed and fix it to keep it from doing similarly in the future; I don't know whom to contact as yet. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fdescfs updates--coming to a devfs near you!
At 11:48 AM +0200 9/14/00, Poul-Henning Kamp wrote:
I must admit that I think in general that /dev/std{in,out,err}
and /dev/fd is bogus. It looks like something which happened
"because we can" more than something which has a legitimate need.
If anything I would propose we ditch it...
I think it is a reasonable feature to have. It probably won't
be useful all that often, but it could be very useful in some
situations. I know I've hit situations where I wished I could
do something like this, but I couldn't tell you an example
right this minute.
So, I wouldn't want to see fdesfs ditched, but on the other
hand I don't have any clue how to address the loose ends that
Chris mentioned in his initial message. :-)
---
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: installing ...
On Thu, 14 Sep 2000, Danny Braniss wrote: In message [EMAIL PROTECTED]you write: }On Wed, 13 Sep 2000, Danny Braniss wrote: } } after i made a 'make buidlworld' how can i get it to install in /5.0-CURRENT? } i compiled on a 4.1. } }I respectfully suggest that if you dont know how to install FreeBSD from }source, you shouldn't be using 5.0-CURRENT, which can and will screw up }your system unless you already know how to fix it yourself. well, it shouldn't screw up my system, if, for example, the install is not to a live system but to another partition, or disk which i could later boot from. i only asked, since i saw that one can compile to /usr/obj, which is fine, so what happend to that extra mile? Current can screw up anything and everything :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
In article [EMAIL PROTECTED], Nate Williams [EMAIL PROTECTED] wrote: [shared libgcc?] If I remember right (and my memory is fuzzy for stuff that far bak) there were a couple of issues. 1) Speed. Shared libraries are slower than static libraries (PIC et. al), and the stuff in libgcc tends to be performance centric. True. But if we just make it link against "-lgcc" then knowledgeable users can always add "-static" if they know how to deal with the consequences and they need the performance. 2) Ease of use. Everytime we upgrade or modify libgcc, it required keeping around the old libgcc.so. I don't think we had much experience with versioning back then, so we tended to either 'never' increment the versions or 'overdo' it. Luckily, libgcc doesn't seem to be changing very often/much these days. Aren't there quite a few 'math' routines inside libgcc (mods and diffs and all sorts of low-level 32/64 bit routines that are quite often used..) I think most of the stuff that's actually used for C is just for the relatively rare 64-bit operations on the i386. Ahh. Can't we just make the linker *always* add libgcc onto the end? Because it's a static library, if it's the symbol isn't used, then it won't be linked into the library? I assume you mean always add it onto the end when building shared libraries. That's problematic because the exception stuff uses some static variables inside libgcc, and you end up with multiple copies of them. Also, we _desperately_ need to switch away from the setjmp/longjmp exception implementation and start using the now-standard DWARF2 implementation. It makes a tremendous performance difference even in programs that don't use exceptions at all. (I measured it once.) But that in turn requires more support from libgcc, and exacerbates the problems associated with using a non-shared libgcc. How so? Well, I should have made that a separate topic as it doesn't have that much to do with whether libgcc is shared or not. But what I meant was that the DWARF2 exception support uses more stuff from libgcc, so you're more likely to run into an undefined symbol if libgcc is not shared. Probably a bogus point for this discussion. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
In article [EMAIL PROTECTED], Max Khon [EMAIL PROTECTED] wrote: libgcc already has support for DWARF2. the only thing that should be changed is crtbegin.o/crtend.o. Yes. I have made all the necessary patches for this. I believe, David has them. Actually I now think we should simply build the crt* files from gcc's "crtstuff.c" in the standard way, rather than having our own versions. The gcc versions are messy but they work fine, and they are specifically exempted from the GPL as long as they are used together with gcc. There are some potential problems with backward compatibility when making this change, but we need to do it anyway. The performance penalty from the sjlj exceptions is really terrible. I think I decided that using a shared libgcc would help with the compatibility issues when I looked at the problem a long time ago. But I can't remember the details any more. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: c++ error
In article [EMAIL PROTECTED], Archie Cobbs [EMAIL PROTECTED] wrote: I was doing a build with DESTDIR=/usr/image and so in.h was actually being found in /usr/image/usr/include/netinet/in.h rather than the normal place, so this must be what happened to me as well. That explains it then. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
[shared libgcc?] If I remember right (and my memory is fuzzy for stuff that far bak) there were a couple of issues. 1) Speed. Shared libraries are slower than static libraries (PIC et. al), and the stuff in libgcc tends to be performance centric. True. But if we just make it link against "-lgcc" then knowledgeable users can always add "-static" if they know how to deal with the consequences and they need the performance. Ahh, but -static implies the entire enchilada is linked static, which may not be the case. :( 2) Ease of use. Everytime we upgrade or modify libgcc, it required keeping around the old libgcc.so. I don't think we had much experience with versioning back then, so we tended to either 'never' increment the versions or 'overdo' it. Luckily, libgcc doesn't seem to be changing very often/much these days. Aren't there quite a few 'math' routines inside libgcc (mods and diffs and all sorts of low-level 32/64 bit routines that are quite often used..) I think most of the stuff that's actually used for C is just for the relatively rare 64-bit operations on the i386. Bruce would know more. I know that the JDK uses them, but then again it also does 64-bit math, so that may be the case. :) Ahh. Can't we just make the linker *always* add libgcc onto the end? Because it's a static library, if it's the symbol isn't used, then it won't be linked into the library? I assume you mean always add it onto the end when building shared libraries. That's problematic because the exception stuff uses some static variables inside libgcc, and you end up with multiple copies of them. Hmmm Also, we _desperately_ need to switch away from the setjmp/longjmp exception implementation and start using the now-standard DWARF2 implementation. It makes a tremendous performance difference even in programs that don't use exceptions at all. (I measured it once.) But that in turn requires more support from libgcc, and exacerbates the problems associated with using a non-shared libgcc. How so? Well, I should have made that a separate topic as it doesn't have that much to do with whether libgcc is shared or not. But what I meant was that the DWARF2 exception support uses more stuff from libgcc, so you're more likely to run into an undefined symbol if libgcc is not shared. Probably a bogus point for this discussion. Gotcha... Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
In article [EMAIL PROTECTED], Nate Williams [EMAIL PROTECTED] wrote: True. But if we just make it link against "-lgcc" then knowledgeable users can always add "-static" if they know how to deal with the consequences and they need the performance. Ahh, but -static implies the entire enchilada is linked static, which may not be the case. :( Then you can sprinkle in the appropriate "-Wl,-Bstatic" and "-Wl,-Bdynamic" options in the right places. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: !.* [ was: Fdescfs updates--coming to a devfs near you! ]
On 14-Sep-00 at 05:37, Poul-Henning Kamp ([EMAIL PROTECTED]) wrote: You think adding a hack to every program to support "-" to mean stdout/stdin is better? The majority of these programs could be handled by adding knowledge of "-" as a magic filename to fopen(3). At the same time I would really love if we implemented "|.*" to mean "do an popen(3)" instead. Isn't that potentially a huge security hole in every program that gets a filename from an external source? But of course, this is bikeshed material... If anything I would propose we ditch it... And break loads of scripts at the same time? I would argue that the programs and the scripts that call them are already broken, but hey... And I would argue that the fdescfs is cleaner than the '-' hack. (Which, by the way, should not be considered a filename hack so much as a command-line-parameter hack; since it was invented before there was a way to say 'use stdin/stdout' on the command-line... You could think of '/dev/stdin' as "'-' version 2") -Pat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Trouble with dynamic loading of C++ libs in PHP v4.02 on FreeBSD 4.1
hi, there! On Thu, 14 Sep 2000, John Polstra wrote: I have made all the necessary patches for this. I believe, David has them. Actually I now think we should simply build the crt* files from gcc's "crtstuff.c" in the standard way, rather than having our own versions. The gcc versions are messy but they work fine, and they are specifically exempted from the GPL as long as they are used together with gcc. changes to crt* files to support DWARF2 are minimal, however. there were some problems with pthreads initialization (but David will not like the way I did it -- some files in contrib/gcc should be changed). this happened because we initialize pthreads from static object constructor (which is not the right thing anyway). there are some workarounds (to not change anything improted from vendor branch), of course. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
need a recommendation of NIC
Hao Zhang writes: I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets thru FreeBSD routers. It's found that the duplications happened in FreeBSD router. Now The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. To isolate this problem. We will try different NIC. Can anyone give me some recommendation for the high performance NIC for FreeBSD 3.3. Thanks in advance for any comments. Intell EtherExpress fxp driver in FreeBSD, I think it best low-cost ethernet card for FreeBSD now. -Hao -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
