Re: Perl issue on freebsd 4.x?
Leo Bicknell wrote:
I have a script where I attempt to use Sys::Syslog, and while it
works on several platforms it does not work on FreeBSD 4.x (well,
I just had this problem a few days ago, the machine it runs on also
uses -s with syslogd (on 4.7-stable). The solution was to use
use Sys::Syslog qw(:DEFAULT setlogsock);
instead of
use Sys::Syslog;
and later do a
setlogsock('unix');
right before the call to openlog().
Syslogd on the machine listens on an *.syslog udp4 socket. The machine
is multihomed. The -s flag to syslogd is explained as Do not log
messages from remote machines - perhaps the perl process is considered
to be remote ?
hellmuth
--
Hellmuth MichaelisHamburg, Europe[EMAIL PROTECTED]www.kts.org
There is a difference between an open mind and a hole in the head.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: IBM ATA Deskstars *without* tagged queueing?
Bruce M Simpson wrote: I bought a Deskstar 120GXP that *doesn't* appear to do tagged queueing. I was wondering if anyone else had encountered such a thing. It's somewhat annoying; generally I buy IBM drives for precisely the reason that they're meant to support tagging. Exactly the same thing happened here with a IC35L020AVER07-0; it did not do tagging and i bought it (and many other IBM drives) because of that. I spend some time verifying that it really was the drive that did not do tagging (rests: http://people.freebsd.org/~hm/misc/atacontrol.c) and when i was shure i called IBM technical support. This was one of the best support i ever got: the guy on the other side understood what i meant, he called back without me remebering him to call back, i got feedback, test software, and so on ... It turned out that the drive i bought had DELL firmware in it [ :- ] so they sent me an updated DELL firmware, but that did not enable tagged support. I asked for a cross update program to get IBM firmware; they had none. They wrote one :-), i got it and now my drive does tagged command queueing. And all this for a dirt cheap drive ... hellmuth (Cc trimmed down to -hackers) -- Hellmuth MichaelisHamburg, Europe[EMAIL PROTECTED]www.kts.org There is a difference between an open mind and a hole in the head. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 8 floppy drive anyone ?
Poul-Henning Kamp wrote: I have a bunch of 8 floppies I need to try to recover contents from, is there anybody out there who has a 8 drive they'd be willing to part with for $$ ? Sorry, but i'm in the same boat. I have an old Hewlett-Packard HPIB 8 Floppydrive here and i wonder if it is possible to connect (and access) it with one of those supported GPIB cards or directly by connecting it to a PC floppy controller ? Has anybody experience with this ? hellmuth -- Hellmuth MichaelisHamburg, Europe[EMAIL PROTECTED]www.kts.org There is a difference between an open mind and a hole in the head. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 8 floppy drive anyone ?
Poul-Henning Kamp wrote: Sorry, but i'm in the same boat. I have an old Hewlett-Packard HPIB 8 Floppydrive here and i wonder if it is possible to connect (and access) it with one of those supported GPIB cards or directly by connecting it to a PC floppy controller ? Has anybody experience with this ? If you have a NEC7210 based GPIB card, I have a rudimentary userland driver for it. I use it for some HP boxes when I fiddle my timekeeping gadgets. Yes, i've got an ISA card from Scientific Solutions, just mailed them for jumper docs ... I don't know about accessing floppies over GPIB (well, I _do_ know about the non-standard way Commodore did it but...) but if you can find the docs you can probably code it up pretty easily. Yes, i have docs (i suppose its the Amigo and/or SS1 command set) :-) Would you please mail me the driver ? hellmuth -- Hellmuth MichaelisHamburg, Europe[EMAIL PROTECTED]www.kts.org There is a difference between an open mind and a hole in the head. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: palm sdk?
Ken Marx wrote: In short, has anyone been able to develope apps for palm with the palm sdk, prc-tools-*, and palm emulation (e.g., pose) on freebsd? Yes, i've used all those tools recently on a 4.4-stable system, i've recompiled everything from the ports tree. The only problem i had was the initial configuration of the sdk and the compiler (so that the compiler was able to look for the include directory automatically), from then on everything worked nicely and without noticable problems. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: HP9000/L1000
daniel lawrence wrote: This is probably a long shot, but I'll ask anyway. We have 3 HP9000/L1000 machines which we may be able to make available (serial console and network) for some kind of BSD porting project. I'm very interested in having a FreeBSD running on the newer HP9000 server machines but i think the problem is getting the hardware documentation from HP (tell me if i'm wrong) for the Series 800 machines. Hardware is available here, if anyone is working on such a project and likes a helping hand, please mail. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 3Com 10/100 Mini PCI Ethernet
Mike Smith wrote: I think the ep driver (which does some funny things to the eeprom) managed to overwrite part of the eeprom so that the xl driver failed to recognize the card. I then tried to add it to the vx driver (at that point i think i started to know what i did) which failed too, so i wrote a subroutine to display the eeprom contents which (because i did not understood the the OP and SubOP command fields before running it) finally erased the eeprom contents to 0x in all locations (which now prevents the card from being initialized by the BIOS - has anybody an idea how to revive such a PCI card ). You would need to write the original EEPROM contents back into the EEPROM, after manually configuring it. Very difficult. Am i right assuming that pciconf is the right tool for this (manually configuring) job ? Do i understand you right in that you would do a fresh start with this card using the xl driver ? I'm a bit concerned about again accidentially overwriting the eeprom, its an _expensive_ card ... ;-) That's correct. The xl driver is not likely to trash the eeprom, although I'm quite surprised that the 'ep' driver did. What possessed you to start with an ISA-only driver when the device is so clearly a PCI device? It was the device ID 0x6055 in the ep driver which is identical to the device ID in the Mini PCI version. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3Com 10/100 Mini PCI Ethernet
Bill Paul wrote: I'm sorry, but after reading this thread, I'm having a hard time coming up with an explanation for this nonsense which doesn't involve you being a dumbass. Yes, i am. I'm guilty for the death of this innocent card, and it is just and only my personal fault and nobody else's. Please, whoever it currently has, give me the conical hat and i'll wear it for the next 2 or 3 months and i promise, i'll stick this "I damaged this card because, I'm a dumbass" paper on the top of the hat so everyone can see it. I will not anymore write PCI probe/attach routines for an unknown chip to connect it to drivers meant only for ISA, MCA, EISA and PCMCIA devices. I'm also very sorry to be the cause of your blood pressure going up, please accept my apologies. AFAIK, this card is a 3Com OEM product which is not available for purchase, all i can give you is an HP part number. It is also not a "normal" PCI card but a so called "Mini PCI" card and its about as large as a matchbox or even a bit smaller. Anyway, i have replaced the card, and i will try hard not to make the same mistakes again (before this whole mess, i was under the impression that only monitors can be destroyed by software, now i know better ...). But, i want to get this card supported. In case you have one or the other good suggestion (except "stay away from the card, don't even look at it !!") on how to proceed in a more orderly fashion, please let me hear them. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 3Com 10/100 Mini PCI Ethernet
Mike Smith wrote: I'm looking for docs for the Mini PCI card in the subject, it has the 3Com part/product no. 3CN3AV1556. It is a 10/100 ethernet 56k modem combo card built into an HP laptop. Have you tried booting FreeBSD on this system yet? If so, does the 'xl' driver pick it up? If not, can you send the output of 'pciconf -l', as it may just require a new PCI ID in the driver. Yes, i first tried the ep driver, then the xl and then the vx by adding the chip id (0x6055) to the probe routine. I think the ep driver (which does some funny things to the eeprom) managed to overwrite part of the eeprom so that the xl driver failed to recognize the card. I then tried to add it to the vx driver (at that point i think i started to know what i did) which failed too, so i wrote a subroutine to display the eeprom contents which (because i did not understood the the OP and SubOP command fields before running it) finally erased the eeprom contents to 0x in all locations (which now prevents the card from being initialized by the BIOS - has anybody an idea how to revive such a PCI card ). Anyway, i paid my "Lehrgeld" (money for learning ?) and i'm currently waiting for an exchange card. Someone from the Linux-camp wrote a vortex diagnostics program which displays the eeprom and register contents of those cards, i ported that in the meantime to be at least able to get a snapshot of the good eeprom contents. Do i understand you right in that you would do a fresh start with this card using the xl driver ? I'm a bit concerned about again accidentially overwriting the eeprom, its an _expensive_ card ... ;-) hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
3Com 10/100 Mini PCI Ethernet
Hi, I'm looking for docs for the Mini PCI card in the subject, it has the 3Com part/product no. 3CN3AV1556. It is a 10/100 ethernet 56k modem combo card built into an HP laptop. Is there any documentation available ? Has anybody experiences with this card already ? Is this card similar to any other (documented) 3Com card ? There are two 3Com chips on the card: Parallel Tasking II Flash (?) Performance 3Com 40 607 002 0012S 3210 7432 LUCENT 40 060 73 and 3Com AD 1807 JST ERJ4 1881A-0.6 0010 I've already called 3Com in Germany and the US, and although the people on the phone were trying to help, they were not able to help with docs. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: i4b: PCBIT PCI card support
Until some time ago I had a regular modem dial-up connection to my ISP, which was recently upgraded to a ISDN 64k connection. Along with the ISP ISDN Pack I purchased came a PCBIT PCI TigerJet Tiger300 ISDN card which works perfectly under Linux with ippp and the HiSAX module (loaded with these settings: insmod hisax type=20 protocol=2 id="HiSax"). Just out of pure curiosity, I ordered FreeBSD-4.0 from freebsdmall a couple of weeks ago and it arrived earlier this week. After installing, reading the docs and lots of other stuff, I came to the sad conclusion that i4b does not support my ISDN card. This card is not supported under i4b. Docs for the Tiger300 chip are available on request from the mailaddresses given in http://www.tjnet.com. I'd be happy to include a driver into i4b in case somebody would write one. hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Post-shutdown hook for UPS shutdown?
From the keyboard of Jeremy Lea: Just an idea... On Fri, May 19, 2000 at 05:00:26PM +0100, Cillian Sharkey wrote: Basically, is there currently any way to execute a post-shutdown script once the system has "halted" ? If not, is this feature possible to add ? Why not let the machine reboot, and check the power before anything else in /etc/rc. This is what i once did for a dumb UPS in FreeBSD 2.x and it worked quite well. That package is still available on http://www.freebsd-support.de/misc with all the scripts and driver if you might want to have a look at it. hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RFC: newsyslog enhancements
I've put a tarball of my enhancements to newsyslog on http://www.freebsd.org/~hm/newsyslog.tar.gz The differences to the in-tree versions are: - ability to archive rotated logfiles into a separate configurable directory - provide another method (in addition to the ISO 8601 format) of specifying log rotation times, i.e. it is now possible to specify rotate at the last day of every month at midnight or rotate every week on Sunday at 23:00 hr - much clean up source, run through bde's KNF filter The changes have in part or full already been reviewed by Sheldon Hearn and Gary Jennejohn. This version of newsyslog runs on several production (3.4) machines since November 3, 1999 without problems. If there are no strong objections, i'll commit it to current. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ijppp for isdn, ppp compression, and netgraph (also: load balancing)
(CC: stripped) From the keyboard of Archie Cobbs: Here is my list of things that 'should be done' at some point: 1. Implement the various PPP compression types as netgraph nodes, starting with Deflate, then maybe predictor-1, STAC (if we can do it legally), and MPPC (same thing). Sounds good. The link in the original mail points to a Linux (GPL) implementation of the STAC compression. Since i was under the impression that STAC is patented, i've contacted the author about this and it seems that STAC either did not notice his implementation, does not care about it, or that it is legal to reimplement it here in Germany or Europe. Perhaps it might be possible to use this somehow, or at least provide hooks to use it ... 2. We should come up with a 'standard' netgraph control message API for an ISDN basic rate interface, and have i4b implement this interface. Then mpd/ppp/etc can "know" this interface and therefore work automatically with any ISDN BRI device. Here is the interface that we use at Whistle: ftp://ftp.whistle.com/pub/archie/netgraph/ng_tn.h (note: the switch types are #defined in another file but include all of the usual suspects: ETSI, NI-1, ATT, DMS100, etc.) The problem here is, that the Whistle ISDN stack has a fundamentally different view of the world than i4b has :-) As far as i understood it, the Whistle ISDN stack is almost completely configurable by using netgraph messages whereas i4b is configured by its isdnd config file. I have made some experiments with mppd over the i4b netgraph b-channel interface and it works beautifully here without any additional configuration messages necessary. But i have no idea, if the real world demands some control messages, such as dial, dial a number, hangup etc. Any ideas how to proceed with this ? hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ijppp for isdn, ppp compression, and netgraph (also: load balancing)
From the keyboard of Julian Elischer: today... impressive stuff.) and is someone working on linking i4b and netgraph? There will be a netgraph node interface which will link an i4b B-channel to netgraph. There are no plans from my side to netgraphify the D-channel part of i4b. to add a negraph interface to the B channels should be quite easy. If you need help I can prbably almost do most of it.. Its already in the development sources (Archie had a look at it already) and it works with mppd. It was really quite easy, although if Archies daemonnews article had been available at that time i wrote it, it would have been even easier :-) when this is done the netgraph PPP nodes (which can support these compression types will be usable. In the mppd i worked with (looking ... mpd3.0b1/mpd3.0b2) deflate was not present, predictor was not usable, bsd was not present. There were just hooks for M$ and stac (which you can not release obviously). Currently i'm using ppp instead of mppd mostly just because it supports deflate compression. I had a look at both mppd and ppp to see how the mentioned free stac compression would be integrateable and found them both similar, given they both come from iijppp. It looks like if it were a good idea if Brian and Archie would merge both to get the best features from each one into a common product ;-) hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ijppp for isdn, ppp compression, and netgraph (also: load balancing)
From the keyboard of Juergen Lock: And the other reason i'm looking at ijppp is ppp compression. It currently supports deflate (rfc1979) and predictor1 (rfc1978), which should at least help if the other end is running bsd or linux, but if your other end is something like an ascend or an external router (zyxel, cisco(?), there are probably more that speak this protocol), you'd want stac lzs (rfc1974), or if its a wintendo box even you'd want M$' special version of that (yes of course they invented their own `standard' again.) So my question is, is anyone working on this? There is (alpha) code that does this on linux, http://www.ibh-dd.de/~beck/stuff/lzs4i4l/ I've looked at that. Its very Linux-centric and i gave up for the moment when i realized how much work it would be to port it. Brian's ppp over i4b does support deflate compression and i get very good results out of it - too good to put more work into the above URL. today... impressive stuff.) and is someone working on linking i4b and netgraph? There will be a netgraph node interface which will link an i4b B-channel to netgraph. There are no plans from my side to netgraphify the D-channel part of i4b. that seems to be the logical way to do more complex stuff like this aodi thing that e.g. the german Telekom wants to use for their low-bandwidth 10 DEM/month isdn `flatrate' which they plan to introduce around the end of the year. (and _if_ this really works it sure will become pretty popular over here as long as all the other `real' flatrates are still in the 100 DEM or more range... :/ ) this seems to be the current draft: - this "flatrate" will only be available to T-Online customers. Since i'm not such a beast and will probably never become one its of not much use for me. - my usage of the internet is not much compatible with what this "flatrate" offers. - the Telecom does not give away anything for free. Check when, why and most important how you are using the internet: the savings you get using this "flatrate" does not pay even a fraction of the time and work needed to implement this - in my eyes. Anyway, i will happily accepting (clean) code which implements it :-) hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: T1 / E1 PCI card for FreeBSD?
Archie Cobbs wrote: In my (biased) opinion, the right way to handle this is to make the card appear as a netgraph node. You configure it however you want with control messages, then attach netgraph interfaces, etc. Isn't this what Poul did? Yes. It looks like that. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: T1 / E1 PCI card for FreeBSD?
Len Conrad wrote: Something like the Ariel RS2000 card. Ariel supports NT and Linux, but I'm a pure FreeBSD shop now (on the opens source side) and would not like to add a Linux box just for this. Didn't Poul-Henning wrote an E1 driver for a Siemens Munich chipset based card which is part of -current ? hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
new PPP printer for tcpdump
Hi, i've put a new PPP decode/print routine print-ppp.c for tcpdump into my home dir on freefall. It would be good if someone could verify/review it. hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
new PPP printer for tcpdump
Hi, i've put a new PPP decode/print routine print-ppp.c for tcpdump into my home dir on freefall. It would be good if someone could verify/review it. hellmuth -- Hellmuth Michaelish...@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
howto allocate 32k phys. mem-space in driver ?
Hi, perhaps i don't see the wood for trees. I'd like to write a driver for a PCI ISDN chipset which uses a 32k byte memory window as a sort of "dual ported ram" in the memory address space. What has to be done in the driver attach routine is - allocate a 32k contingous memory window - get the physical address of it - program the ISDN PCI chipset with the start address of the window Now can i just malloc 32k and then use vtophys() to get the physical start address to program the PCI chip with ? hellmuth -- Hellmuth Michaelis[EMAIL PROTECTED] Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
howto allocate 32k phys. mem-space in driver ?
Hi, perhaps i don't see the wood for trees. I'd like to write a driver for a PCI ISDN chipset which uses a 32k byte memory window as a sort of dual ported ram in the memory address space. What has to be done in the driver attach routine is - allocate a 32k contingous memory window - get the physical address of it - program the ISDN PCI chipset with the start address of the window Now can i just malloc 32k and then use vtophys() to get the physical start address to program the PCI chip with ? hellmuth -- Hellmuth Michaelish...@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
