killpower(UPS inverter shutdown)
Hello, If anyone have the working sources to killpower an USB UPS under FreeBSD please enlight me. I have APC RS 500, but an example for any other should also be ok. Thanks a lot in advance. -- With best regards, Gregory Edigarov -- profi.kharkov.uaSystems Administrator -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA/CHS problem (path + new information)
On Sun, 11 Apr 2004, Roman Kurakin wrote: I remind you that now I have two problems. First one that FreeBSD uses wrong assumption about which device should be CHS and which LBA: if (!ad_version(atadev-param-version_major) || !(atadev-param-atavalid ATA_FLAG_54_58) || !lbasize) atadev-flags |= ATA_D_USE_CHS; True ATA device may not have ATA_FLAG_54_58 valid bit, and also due to last ATA standard this bit is obsoleted. I also want to know why ata driver doesn't check LBA support from word 49? May be this one check could solve my problems and didn't breake code for non-ATA devices. Possibly for similar reasons. It's hard to tell what's in the LBA bit for pre-ATA devices older than LBA. Similarly for the lbasize words, but it's easier to do a sanity check on a 32-bit values that a 1-bit flag. Second one, that only 20G part of my hard disk works with CHS. This is other side of the same problem. Device should work in CHS mode. And it works witch ICH5 controller. But with ICH2 it doesn't with out hack. I've checked standard again and I sew command 91h (Initialize drive parameters). Check out the commands for limiting the (apparent) disk size. IIRC, the CHS limit can be set independently of the LBA limit, and some settings are harder than others so that they can't be cleared by old commands like 0x91. The limits may be set to prevent old drivers which only understand old commands from becoming confused by trying to actually use the whole disk. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Second RFC on pkg-data idea for ports
[this is BCC'ed to -hackers and -arch just so everyone has a chance to see it, but I expect the bulk of the discussion should take place on the freebsd-ports mailing list] Back in January I send out a long-ish email asking for feedback on some ideas I had for the ports-collection. I received a fair number of comments, and have finally re-organized my ideas into a few web pages. Hopefully these will make more sense. Initially I had written the ideas up as a bunch of Wiki pages, but the machine holding that Wiki died, taking with it all the pages I had written... I have not proof-read the web pages, so there's probably some spelling mistakes and odd sentences on them. Apologies for that, but I wanted to get *something* sent out this week. This project has been blocked due to a lack of time on my part, and I want to get it moving again... The basic idea is to collapse many of the separate files for a port into a single pkg-data file. The web pages explain why I think this might be worth doing. Please check them out at: http://people.freebsd.org/~gad/PkgData/ Some of the work for this has been done, mainly just to see how well it might work out. The project is still probably more work than Darren and I can finish, so we might limit ourselves to a subset of the idea. For instance, we might start out by just collapsing the distinfo, pkg-plist, and files/patches-* files into a pkg-data file, and leave the other files for some later project. What I'd like is some idea of whether this project is worth pursuing. If not, then Darren and I will concentrate on some other, less disruptive project. If people like the general idea of this project, then we'll see how much of we can do. If we have some of the details wrong, then let us know what we need to change or where we need to look for more information. I know that I am not a full-fledged expert in every facet of the ports collection, and I am not looking to ram some ideas down everyone's throat. I just think that some change like this one could be useful for the ports collection, and I'm trying to come up with something that everyone sees as useful. If this project does not seem like it would be worth the effort, then that will be perfectly okay too. Please let me know what you think. Also, please read the web pages before responding. It took me a fair amount of time to write the web pages that are there (as lame as they are...), and I'd rather not have to retype all of that into a long series of disjointed messages... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
sanity checking for config(8)
Hi I'm thinking of adding some basic kernel-config sanity checking to config(8) config would then complain about things like 'device da' without 'device scbus' and 'device gif' without 'options INET' and 'OPTIONS INET6' just to name a few. It would be really nice if the list of what a device depends on could be generated automaticly. Can any of you think of a way to do that? (aside from generating lots of config files and test if they make(1)) -- greetz Joost [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
looking for killpower source
Hi, I need killpower (invertor shutdown) source for any USB UPS. I have APC BackUPS RS 500, but any other source should help, if it works under FreeBSD. Thanks a lot in advance. -- With best regards, Gregory Edigarov -- profi.kharkov.uaSystems Administrator -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SYSV message queues
On Monday 12 Apr 2004 09:55, Vlad GALU wrote: Did you try to grok what the msgrcv() call is supposed to return? Specifically, read about -1/EAGAIN and IPC_NOWAIT. Then remove sleep(). It is supposed to block, waiting for more events to be inserted into the queue. Yes but sometimes it can't and will return an EAGAIN. You *MUST* trap this and try the msgrcv again. However, does anyone have a better design ? Yes. Use sockets. Sockets (streams etc) work excellently _unless_ you periodically need to pick messages out of the queue out of FIFO order. Priorities etc, or when you've got multiple processes reading a single queue and want to send a particular process a message. SYSV queues are just the ticket for this. Be carefull with SYSV Message Queues though as the default settings of queue size etc are broken in freeBSD/netBSD/openBSD (see my earlier email http://lists.FreeBSD.org/pipermail/freebsd-hackers/2004-March/006011.html ) Incidentally, what is the resolution of this?? Cheers, Chris -- Chris Smith Technical Architect - netFluid Technology Ltd. Internet Technologies, Distributed Systems and Tuxedo Consultancy E: [EMAIL PROTECTED] W: http://www.nfluid.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA/CHS problem (path + new information)
Bruce Evans wrote: On Sun, 11 Apr 2004, Roman Kurakin wrote: I remind you that now I have two problems. First one that FreeBSD uses wrong assumption about which device should be CHS and which LBA: if (!ad_version(atadev-param-version_major) || !(atadev-param-atavalid ATA_FLAG_54_58) || !lbasize) atadev-flags |= ATA_D_USE_CHS; True ATA device may not have ATA_FLAG_54_58 valid bit, and also due to last ATA standard this bit is obsoleted. I also want to know why ata driver doesn't check LBA support from word 49? May be this one check could solve my problems and didn't breake code for non-ATA devices. Possibly for similar reasons. It's hard to tell what's in the LBA bit for pre-ATA devices older than LBA. Similarly for the lbasize words, but it's easier to do a sanity check on a 32-bit values that a 1-bit flag. But since ATA_FLAG_54_58 bit from the fist spec means 1 - valid and 0 - may be valid this check is initialy incorrect. According to ATA-5 it is depricated. But in later revisions of ST380021A (according to their datasheet, I don't have one) Seagate changed this bit to 1 back, I may guess that this was done since probably others uses the same check. :-( Anyway, it seems that Soren already removed this check. So my ST380021A should back to the life. Second one, that only 20G part of my hard disk works with CHS. This is other side of the same problem. Device should work in CHS mode. And it works witch ICH5 controller. But with ICH2 it doesn't with out hack. I've checked standard again and I sew command 91h (Initialize drive parameters). Check out the commands for limiting the (apparent) disk size. IIRC, the CHS limit can be set independently of the LBA limit, and some settings are harder than others so that they can't be cleared by old commands like 0x91. The limits may be set to prevent old drivers which only understand old commands from becoming confused by trying to actually use the whole disk. This is good idea. I sew only LBA limits, but I didn't see anytihng about CHS limits. I'll try to check for some more commands. I can't get how ATA controller could affect on this. Brobably this is not controller problem but BIOS, but changing its settings didn't affect. Thanks for reply, I hope your suggestions will help me. Since Soren removed first bug I'll keep digging from obstinacy :-) rik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: looking for killpower source
Only one post is required... Take a look at NUT (Network UPS Tools), which is in the ports. It should do everything you want. You can find the web page at http://www.networkupstools.org. -- Rob | Oh my God! They killed init! You bastards! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Edigarov Sent: Tuesday, April 13, 2004 10:53 AM To: [EMAIL PROTECTED] Subject: looking for killpower source Hi, I need killpower (invertor shutdown) source for any USB UPS. I have APC BackUPS RS 500, but any other source should help, if it works under FreeBSD. Thanks a lot in advance. -- With best regards, Gregory Edigarov -- profi.kharkov.ua Systems Administrator -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
sysinstall
Hi, If sysinstall detects wrong geometry, it tries to correct it and suggests to use G option to chage geometry if I disagree with it. But it doesn't allow to set whatever geometry I want with G. Is this intentional behaviour or it should be fixed. (in case it should be fixed I may send my solution of this problem). PS. While searching for other things, I repeatedly faced with threads about such problem, and if my memory does not fail, I saw pr about it. But now I can't find any prs and messages about this behaviour of sysinstall. So please take my apologies if I am opening already closed subject. Best regards, Roman Kurakin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invalid realloc size of 0 when installing on an AMD athlonXP barton powered machine
Baldur Gislason wrote: I'm trying to install 5.2.1-rel from FTP with an intel 100Mb network card on an AMD AthlonXP barton 2500+ with an Aopen AK77-8XN motherboard and 1GB ram. When at 65% through extracting base, sysinstall crashes with the message: Fatal error: Invalid realloc size of 0! - PRESS ANY KEY TO REBOOT I know this is a very common problem these days, has any solution been found? I'd rather sell this machine than using some other operating system on it. Baldur ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to [EMAIL PROTECTED] I have an athlon barton core on an epox 8rda3i. I have never seen this problem and I cvsup every few weeks on current. I have not done a clean install since last year. Is that a local ftp or the net? Can you make a cd from the iso, or do you not want to? I have done both in the past and the cd is much faster, even if you hae broad band. Maybe not if you have a t3 or better, but not all ftp servers will be fast all the time. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: looking for killpower source
On Tue, 13 Apr 2004 16:50:41 +0100, in sentex.lists.freebsd.hackers you wrote: Only one post is required... Take a look at NUT (Network UPS Tools), which is in the ports. It should do everything you want. You can find the web page at http://www.networkupstools.org. I think he is looking for USB info. From the NUT FAQ, Q: I just bought a new WhizBang UPS that has a USB connector. How do I monitor it? A: If you're using a very new version of Linux that has hiddev support or just happen to have the hiddev patches applied and working, you're in luck. On any other system or an older Linux kernel, there's nothing for you just yet. Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
