Re: Staticaly allocated buffers in library. Is it correct?
-BEGIN PGP SIGNED MESSAGE- On Fri, 16 Feb 2001, Andrey Simonenko wrote: I patched some library files and noted that some functions, which parse some configuration files, use staticaly allocated buffers. Sizes of such staticaly allocated buffers are 8k, 10k and so on. These buffers are used to hold one line from parsed file. Usually it is enough for one line, but really this is error (I think). Well since config files can be only changed by root,I don't think that root will use too long lines to case heap overflow.So this isn't big problem. Vojislav Milunovic [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQEVAwUBOo5o5C3gPLld8IkLAQGaTQf/TNY5ODLUYmylF1KEuIsw2u7CvB4MSlRu H63ZIbWtWcuwc1Dlhuqp7H8biXamtvGcOC5gpvHUMMN/6BjdOyXAmXLxNKS+X+n6 MYZ3ODXwJkhqyUxPbfz46t3VUHH95Zo6aT26odhJy2PG4ttitzS+x3cnDfIaG15C FZQE3MYhTwT1A/cjSx9T1+uWwjMvrTXeHuDZMysCyNsjAilsoZ2+jty1jDibpa15 7D8+4aEC3RWisUPaQXWPCmCoT6C9j7YXWAi/J+O0olJn/Je21GvCeSVt2pp09B0L Dv6lenAMB2/OCXruSMnmtOfxI8iSCpSeNa16DH14neqZ0fA8loOEOQ== =ggia -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: boot1 changes and etherboot support
Luigi Rizzo wrote: I have spent some time trying to put etherboot[1] code onto the hard disk so that it can be selected using the FreeBSD boot manager. I ended up doing it with a small amt of modifications to the "boot1" code, for which a patch is attached. Maybe it could be interesting in applying this patch to the standard boot1 code (apart for the PRT_BSD change, which should be unmodified). The size of the boot1 code must be = 446 bytes. The code already gets customised a lot, for example, in embedded work and space needs to be left to allow for that. So I wouldn't personally be in favour of adding this to the standard boot1. -- Robert Nordier [EMAIL PROTECTED] // Le monde est plein de fous, et qui n'en veut pas voir [EMAIL PROTECTED] // Doit se tenir tout seul, et casser son miroir. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: boot1 changes and etherboot support
Luigi Rizzo wrote: I have spent some time trying to put etherboot[1] code onto the hard disk so that it can be selected using the FreeBSD boot manager. I ended up doing it with a small amt of modifications to the "boot1" code, for which a patch is attached. Maybe it could be interesting in applying this patch to the standard boot1 code (apart for the PRT_BSD change, which should be unmodified). The size of the boot1 code must be = 446 bytes. The code already gets customised a lot, for example, in embedded work and space needs to be left to allow for that. So I wouldn't personally be in favour of adding this to the standard boot1. If your point is that boot1.s should be some basic loader that people can easily customize, then i kind of understand and share your opinion. On the other hand, the ability to load a rom image is very useful, so i wonder what do you think is the best approach among the following: + put some conditional-compilation code in boot1.s + have a separate file, say bootrom.s, maybe in the same directory as the existing boot1 + pass the modified code to the etherboot people so they can include in their source tree. in all sincerity i'd love to have this code in the FreeBSD source tree rather than have to resort to some external repository. cheers luigi --+- Luigi RIZZO, [EMAIL PROTECTED] . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 --+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [moebius@bitstream.net: 4.1.1-release ldconfig issue]
On Fri, Feb 16, 2001 at 09:34:22PM -0600, Maximus [EMAIL PROTECTED] wrote: I installed libiconv-1.5.1 on my 4.1.1-release system with the following results: -rw-r--r-- 1 root wheel 452 Feb 16 09:05 libiconv.la lrwxr-xr-x 1 root wheel 15 Feb 16 09:05 libiconv.so - libiconv.so.2.2 -rw-r--r-- 1 root wheel 646265 Feb 16 09:05 libiconv.so.2.2 ^^ ELF libraries should only have a major version, not a major+minor version. Install the port instead of compiling it yourself, and this will be handled. Once finished I run 'ldconfig -m /usr/local/lib /usr/lib'. No errors to this point. I believe that ELF ldconfig will ignore libraries with more than one version number tagged on. But it doesn't matter much -- the hints file is not used with ELF. Once done I run 'ldconfig -r | grep icon' and nothing is there. The library is not making it into the hints file. Running file on the .so.2.2 file I get the following: libiconv.so.2.2: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped Obviously I'm missing something. What? Any pointer would be appreciated. At the minimum, where would I find the source for ldconfig? Which package? Package? ldconfig is in the base system, and a good guess would be: $ which ldconfig /sbin/ldconfig $ cd /usr/src/sbin/ldconfig $ ls Makefileelfhints.c ldconfig.8 ldconfig.c ldconfig.h Hope this helps! Cheers, -- 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
Re: boot1 changes and etherboot support
Luigi Rizzo wrote: Luigi Rizzo wrote: I have spent some time trying to put etherboot[1] code onto the hard disk so that it can be selected using the FreeBSD boot manager. I ended up doing it with a small amt of modifications to the "boot1" code, for which a patch is attached. Maybe it could be interesting in applying this patch to the standard boot1 code (apart for the PRT_BSD change, which should be unmodified). The size of the boot1 code must be = 446 bytes. The code already gets customised a lot, for example, in embedded work and space needs to be left to allow for that. So I wouldn't personally be in favour of adding this to the standard boot1. On the other hand, the ability to load a rom image is very useful, so i wonder what do you think is the best approach among the following: + put some conditional-compilation code in boot1.s + have a separate file, say bootrom.s, maybe in the same directory as the existing boot1 + pass the modified code to the etherboot people so they can include in their source tree. in all sincerity i'd love to have this code in the FreeBSD source tree rather than have to resort to some external repository. My preference would be for a separate file in a separate directory, more or less similar to cdldr and pxeldr; I'd be least keen on handling this with conditional-compilation. That's just me, though, and this probably isn't a case where the views of the author/maintainer should have any special weight. -- Robert Nordier [EMAIL PROTECTED] // Le monde est plein de fous, et qui n'en veut pas voir [EMAIL PROTECTED] // Doit se tenir tout seul, et casser son miroir. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
hotplug ata device?
Hi I'm looking for ideas on the following: I just added a CF-ata adapter to my system (see http://www.tapr.org). This works just fine, as long as the card is in the socket during boot. For obvious reasons this is not always the case. If it was not seen during boot one gets: freebie#mount /flash msdos: /dev/ad0: Device not configured Which I can understand (but don't appreciate in this case ;-) Is it possible to have something like the 'camcontrol rescan' that the SCSI CAM subsystem has? tnx Wilko -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) Bultehttp://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [moebius@bitstream.net: 4.1.1-release ldconfig issue]
Wonderful...partly. This worked to get the lib in ldconfig, but then I noticed that it still couldn't find the lib. Trussing 'ld -liconv' revealed that it was only looking in /usr/lib. I have a LD_LIBRARY_PATH, and even went so far as to create a LD_FLAGS var. Neither of these things made ld even glance beyond /usr/lib. Lost. but thanks anyway. On Sat, Feb 17, 2001 at 09:07:32AM -0600, Jacques A. Vidrine wrote: On Fri, Feb 16, 2001 at 09:34:22PM -0600, Maximus [EMAIL PROTECTED] wrote: I installed libiconv-1.5.1 on my 4.1.1-release system with the following results: -rw-r--r-- 1 root wheel 452 Feb 16 09:05 libiconv.la lrwxr-xr-x 1 root wheel 15 Feb 16 09:05 libiconv.so - libiconv.so.2.2 -rw-r--r-- 1 root wheel 646265 Feb 16 09:05 libiconv.so.2.2 ^^ ELF libraries should only have a major version, not a major+minor version. Install the port instead of compiling it yourself, and this will be handled. Once finished I run 'ldconfig -m /usr/local/lib /usr/lib'. No errors to this point. I believe that ELF ldconfig will ignore libraries with more than one version number tagged on. But it doesn't matter much -- the hints file is not used with ELF. Once done I run 'ldconfig -r | grep icon' and nothing is there. The library is not making it into the hints file. Running file on the .so.2.2 file I get the following: libiconv.so.2.2: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped Obviously I'm missing something. What? Any pointer would be appreciated. At the minimum, where would I find the source for ldconfig? Which package? Package? ldconfig is in the base system, and a good guess would be: $ which ldconfig /sbin/ldconfig $ cd /usr/src/sbin/ldconfig $ ls Makefileelfhints.c ldconfig.8 ldconfig.c ldconfig.h Hope this helps! Cheers, -- 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
Re: hotplug ata device?
It seems Wilko Bulte wrote: Hi I'm looking for ideas on the following: I just added a CF-ata adapter to my system (see http://www.tapr.org). This works just fine, as long as the card is in the socket during boot. For obvious reasons this is not always the case. If it was not seen during boot one gets: freebie#mount /flash msdos: /dev/ad0: Device not configured Which I can understand (but don't appreciate in this case ;-) Is it possible to have something like the 'camcontrol rescan' that the SCSI CAM subsystem has? Yes, I've already done that, but it needs alot of polishing before it goes into the public sources, plus an atacontrol util... -Sren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hotplug ata device?
In message [EMAIL PROTECTED] Wilko Bulte writes: : Is it possible to have something like the 'camcontrol rescan' that : the SCSI CAM subsystem has? NO. These cards are not hot pluggable. I've blown out two IDE Controllers hot plugging them. DO NOT TRY TO HOTPLUG THEM OR YOU WILL BE SORRY. I hate to shout like that, but after the second IDE controller fried, I got real conservative. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hotplug ata device?
In message [EMAIL PROTECTED] Wilko Bulte writes: : Is it possible to have something like the 'camcontrol rescan' that : the SCSI CAM subsystem has? NO. These cards are not hot pluggable. I've blown out two IDE Controllers hot plugging them. DO NOT TRY TO HOTPLUG THEM OR YOU WILL BE SORRY. I hate to shout like that, but after the second IDE controller fried, I got real conservative. i think he was referring to compactflash memories which you can stick into pcmcia adapters and are hot-pluggable. luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hotplug ata device?
On Sat, Feb 17, 2001 at 05:55:14PM -0800, Luigi Rizzo scribbled: | In message [EMAIL PROTECTED] Wilko Bulte writes: | : Is it possible to have something like the 'camcontrol rescan' that | : the SCSI CAM subsystem has? | | NO. These cards are not hot pluggable. I've blown out two IDE | Controllers hot plugging them. DO NOT TRY TO HOTPLUG THEM OR YOU WILL | BE SORRY. | | I hate to shout like that, but after the second IDE controller fried, | I got real conservative. | | i think he was referring to compactflash memories which you can stick | into pcmcia adapters and are hot-pluggable. And Warner uses these TAPR CompactFlash/IDE cards..:) I have fried my little Pentium 100's IDE controller with it too... -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hotplug ata device?
In message [EMAIL PROTECTED] Luigi Rizzo writes: : In message [EMAIL PROTECTED] Wilko Bulte writes: : : Is it possible to have something like the 'camcontrol rescan' that : : the SCSI CAM subsystem has? : : NO. These cards are not hot pluggable. I've blown out two IDE : Controllers hot plugging them. DO NOT TRY TO HOTPLUG THEM OR YOU WILL : BE SORRY. : : I hate to shout like that, but after the second IDE controller fried, : I got real conservative. : : i think he was referring to compactflash memories which you can stick : into pcmcia adapters and are hot-pluggable. No he wasn't. He talkd specifically about the TAPR adapter, which connects to the IDE bus and is not hot pluggable. I have one of these beasts, which is how I know :-) For the pccard ones, you don't generally need to rescan the bus unless you have an cdrom that wasn't attached at probe time... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hotplug ata device?
| NO. These cards are not hot pluggable. I've blown out two IDE | Controllers hot plugging them. DO NOT TRY TO HOTPLUG THEM OR YOU WILL | BE SORRY. ... | I hate to shout like that, but after the second IDE controller fried, | I got real conservative. ... And Warner uses these TAPR CompactFlash/IDE cards..:) I have fried my little Pentium 100's IDE controller with it too... i actually wonder, aren't there removable disk frames which support hot swap (by turning off power with the keylock, or the like) ? Plus, it is actually curious that you can fry the IDE controller, the simplest ones used to be just a couple of '245 and an address decoder... cheers luigi +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ 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: hotplug ata device?
In message [EMAIL PROTECTED] Luigi Rizzo writes: : i actually wonder, aren't there removable disk frames which support : hot swap (by turning off power with the keylock, or the like) ? I've not seen any, but I suppose they exist. The TAPR ones, however, definitely are not those beasts. they are simple and don't support hotswap. : Plus, it is actually curious that you can fry the IDE controller, : the simplest ones used to be just a couple of '245 and an : address decoder... I think that the main problem is lack of good grounding causing large transients when the card is removed. But I could be wrong about that. Each time I fried one it was definitely a remove + insert sequence. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [moebius@bitstream.net: 4.1.1-release ldconfig issue]
On Sat, Feb 17, 2001 at 12:41:25PM -0600, Maximus wrote: Wonderful...partly. This worked to get the lib in ldconfig, but then I noticed that it still couldn't find the lib. Well, as I said, the hints are not used for linking at all. Trussing 'ld -liconv' revealed that it was only looking in /usr/lib. I have a LD_LIBRARY_PATH, and even went so far as to create a LD_FLAGS var. Neither of these things made ld even glance beyond /usr/lib. LD_LIBRARY_PATH is not used at link time, only at run time. If you want additional paths to be searched for libraries, use the -L flag. You may want to read `info -f gcc' and/or `info -f ld' if you have further trouble. Cheers, -- 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
